On 27 April 2016 at 23:07, Martynas Jusevičius <martynas@graphity.org> wrote: > How is JSON an EAV model? Where's the Entity in it? > I suppose typically it would be a bnode? > > On Wed, Apr 27, 2016 at 10:49 PM, Melvin Carvalho > <melvincarvalho@gmail.com> wrote: > > The test of independent invention [1] asks "If someone else had already > > invented your system, would theirs work with yours?" > > > > Now imagine if someone had invented RDF (lets call it RDF-L) but with one > > slight difference. You are allowed to have literals in the predicate > > position. > > > > Is there a way that RDF could be made to work with RDF-L. > > > > This is more than a theoretical question, it has practical implications. > > The "triple" model which ties key value pairs to a subject, could be > thought > > of as a type of Entity Attribute Value (EAV) [2] model. There are many > > examples of EAV models that allow literals in the "second" position. > JSON > > springs to mind. > > > > Does RDF pass the TOII? If not, can we work out a way to make it do so. > > After some thought my current favourite idea is to make the following two > > equivalent: > > > > "predicate" <--> urn:literal:predicate > > > > Thoughts? > > > > [1] https://www.w3.org/DesignIssues/Principles.html > > [2] > > > https://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model >Received on Wednesday, 27 April 2016 21:11:32 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:45 UTC