> the relationships between all these chunks of data must be captured
Capture is one thing. Interchange of information between dissimilar
systems is another.
Moreover, there are no simple rules for deciding which kind of tool or
representation is best for a given situation. Here I'm including
"moment in history" in the general definition of "situation", where
"situation" also includes, but is not limited to, all the issues that
arise from the distinctions that may need to be made between
interchange, capture, and processing-for-some-purpose.
So, in the general case, these true-or-false questions are all vexed.
There's another pair of problems, too:
* Is there some reason to limit all relationship-modeling to RDF?
More generally, is there *any* relationship-model that doesn't fail somehow?
* Is there some reason to limit all interchange representation to
XML? More generally, is there *any* interchange representation that
doesn't fail somehow?
For good or ill, choices must be made, regardless of the complexity of
the issues involved in making them. There's no substitute for real
engineering.
On 06/10/2016 02:35 PM, Costello, Roger L. wrote:
> Hi Folks,
>
> So, you have lots of chunks of data and the chunks are highly interrelated. Over time more chunks are added and those new chunks are easily connected in with the other chunks, i.e., the system expands over time.
>
> Example of highly interrelated chunks of data: You have data about an aircraft in flight: its current location, speed, heading, etc. You have data about the aircraft itself: fuel capacity, max speed, max altitude, cruising speed, date built, model number, etc. You have data from FAA radars tracking the aircraft. You have data about the destination and originating points of the aircraft. You have data about the passengers on the aircraft. And you have many other chunks of relevant data. And, the relationships between all these chunks of data must be captured.
>
> [True or False] The only reasonable way to express an expandable system with lots of chunks of highly interrelated data is with RDF, RDF Schema, and/or OWL. It is not practical to express an expandable system with lots of chunks of highly interrelated data using vanilla XML.
>
> [True or False] When dealing with an expandable system with lots of chunks of highly interrelated data it's not practical to use XML Schema to validate the data.
>
> [True or False] When dealing with an expandable system with lots of chunks of highly interrelated data you must adopt the Semantic Web technologies such as inference engines, triple stores, SPARQL, knowledge bases. And your trading partners will naturally join you in your adoption of the Semantic Web technologies.
>
> [True or False] Nobody has ever implemented an expandable system with lots of chunks of highly interrelated data using vanilla XML and using XML Schema for validation. Or, if they did, it was a complete failure.
>
> /Roger
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe:
> subscribe:
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
