Cart
[Home] [By Thread] [By Date] [Recent Entries]
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 On Wed, Feb 2, 2022 at 8:31 AM Chet Ensign <chet.ensign@o...> wrote:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
