XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Fwd: Fw: Imagine

Chet,

I see it being very much a (potential) reality. Sergio's comments point in that direction, as does the work being down with Solid, much of the work happening in metaverse shared data and elsewhere.

There are a few primary challenges to adoption:

1. For this kind of work to be effective, programmers have to work within a graph mindset, which is actually somewhat foreign to the way that most work (they see everything as trees, and don't necessarily understand why by-reference programming is superior to by-value programming. 
2. Much of the heavy lifting of conversion between tree formats (XML and JSON) and graph formats (RDF and, to a certain extent CSVs) needs to be handled on the ingest side of things, while all too often is underspecified in comparison to the tools that exist within the RDF. I think that systems such as Solid should extend beyond the database and tackle the ingestion problem as part of the overall stack.
3. Sparql and Turtle need to have some upgrades added: RDF-Star/Turtle-Star will help, but introducing Sparql array and dictionary objects with appropriate methods would go a long way as well. Additionally, there needs to be greater cross-linking between Sparql and SHACL. Right now, there are a few implementations that support some of these, but there is little consistency.
4. We need to stop assuming that people are going to rush to adopt Turtle and related techs and assuming that these remain as lower-level niche languages.
5. We need to get out of the one ring to rule them all trap at the conceptual level. I've been doing enterprise data modeling for twenty years. You know what? It's a pipe dream. Every organization is going to build its own ontology (or ten), because each organization has different requirements and different legacies. Ensure that data can be decomposable into a graph, then at least you've moved your inputs into a common format for manipulation.  

Kurt Cagle
Community/Managing Editor
Data Science Central, A TechTarget Property
443-837-8725


On Wed, Feb 2, 2022 at 8:31 AM Chet Ensign <chet.ensign@oasis-open.org> wrote:
I am posting this on behalf of Mr. Hans-Jürgen Rennau while we debug a problem with his emails being posted to the list.

--- 

Assume four datasets: an XML document, a JSON document, a CSV file and an HTML document (authored near the north pole, in the rain forest, in Athens and in the Antarctic, respectively).

Imagine a standard which enables you to define the mapping of a document node to a set of RDF triples.

Remember that all documents (XML, JSON, CSV, HTML) can be parsed into document nodes (for example see [1]).

Assume that the RDF graphs obtained from our documents contain the following triples:
  foo:oxygen foo:symbol "O"
  foo:oxygen foo:numberOfElectrons "8"
  foo:oxygen foo:atomic mass "16"
  foo:oxygen foo:electronegativity ."3.5"

each one found in a different one of the four RDF graphs.

Then we have integrated information, as we now know four things about oxygen, contributed by different data sources using a different data format. Of course it would be easy to serialize the integrated information into XML, or JSON, or CSV, or HTML or any other format (employing Inuit or any other natural language).

+ + + - - -

But I suppose you think this is an idle dream. Perhaps you think that the imagined standard would not be feasible to create or to use, or you question the practicality to leverage RDF IRIs for identifying resources and properties in more than a few specific cases.

Unfortunately I agree that it is an idle dream. Only the reason I see is a different one, as I am convinced that the imagined standard is not too difficult to create and to use and I do not question the practicality of using RDF IRIs in many fields, including natural science, pharmacology, health care, finance, many verticals and economical interaction. The reason I see is that it seems impossible to find minds with a deep interest in both, XML technology and semantic technology. if - then - but.

With kind regards,
Hans-Jürgen Rennau

[1]





--

Chet Ensign

Chief Technical Community Steward

OASIS Open

   
+1 201-341-1393
chet.ensign@oasis-open.org
www.oasis-open.org


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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS