Quoting Melvin Carvalho (2021-05-19 13:14:37) > On Tue, 18 May 2021 at 21:33, Kingsley Idehen <kidehen@openlinksw.com> > wrote: > > The Super Set should always be the point of focus if > > interoperability is the goal. That's a classic route to more "AND" > > and less "OR" . > > +100 to this > > It took me some time to fully understand the subject, predicate, > object model of RDF, and it was made much easier for me when you first > explained the Entity Attribute Value (EAV) model > > We've generally taken the semantic web approach to standards in this > group, with some evangelism. That has had mixed success. > > We should be inclusive of the many thousands (millions?) of developers > that enjoy working with JSON(-LD) > > And also introduce them to the benefits of a more structures EAV model > ie making merges cheap, enabling federation, allowing anyone to say > anything about anything (ie decentralized features), discovery, follow > your nose, indexing, allowing multiple things to exist in a document. > > And we can also learn from the tooling and network around JSON, how it > makes parsing easy and ubiquitous, fast startup time, easy to work > with arrays, easy to work with numbers > > If you want to create an MVP or be first to market, which is a valid > approach, you probably will want to go down the JSON path, IMHO Related to the above, Atomic Data seems an interesting concrete approach to use a subset of RDF optimized for lesser confusion for non-RDF developers: https://docs.atomicdata.dev/motivation.html - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Received on Wednesday, 19 May 2021 12:21:24 UTC