[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Converting a variety of data formats, containingvarious ki

  • From: David Carlisle <d.p.carlisle@gmail.com>
  • To: "Costello, Roger L." <costello@mitre.org>
  • Date: Tue, 4 Oct 2016 17:10:38 +0100

Re:  Converting a variety of data formats
On 4 October 2016 at 16:53, Costello, Roger L. <costello@mitre.org> wrote:
> Hi Folks,
>
> Scenario: You are tasked to build a system that will receive data from a
> variety of sources. The data arrives in different formats (e.g., CSV,
> binary, tab-delimited, JSON, XML). The data sources provide different kinds
> of data (e.g., one source provides book data, another source provides
> weather data, another source provides gardening data). The data will be
> converted to a common intermediary form and then from the intermediary form,
> placed into a data store.
>
> Recently I heard this statement:
>
>                 Converting data that is in various formats and contains
> various kinds
>                of data, into a common intermediate form is hard
> (computationally
>                expensive). RDF is the only data model the enables such
> conversions
>                to be done in a way that is computationally tractable.
> Therefore, we
>                must use RDF. And, as a corollary, we must use a triple store
> to store
>                the RDF data.
>
> Do you agree with that statement?

No.

> If you do, can you provide evidence that
> RDF is the only data model that supports such conversions in a
> computationally tractable manner?

--
>
> If you do not agree with that statement, can you provide evidence on why the
> statement is false?

It's self evidently false so by definition doesn't need more evidence:-)

But more to the point the problem as stated isn't sufficiently well
defined to have a meaningful answer.
Perhaps in some specific context RDF is the only viable way but in
general clearly that can't be the case.

Also converting between binary/csv/tab/xml/json is only as hard as you make it
for example conversion from binary to xml you can base64 encode the
binary and wrap it in <x>...</x>
and you have well formed XML which conversion can be done in a couple
of lines of script.
If your binary file is an image that's probably reasonable, if the
binary file is .doc and you wanted something more with the structure
of .docx then it is less so.

So in the generality in which you pose the question I doubt there is
anything meaningful you could say about the difficulty of converting
to a common format, or of a suitable format for that common storage
format.


>
> /Roger

David


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.