- From: Robert Sanderson <azaroth42@gmail.com>
- Date: Wed, 23 Apr 2014 14:29:24 -0700
- To: Linked JSON <public-linked-json@w3.org>, Tom Johnson <johnson.tom@gmail.com>
- Message-ID: <CABevsUFt=G9FGOKYiBG_iHACEanXCQeiSiBrU0LM4tS5LA=V-g@mail.gmail.com>
Dear all, The @container property has an enumerated set of possible values (@list, @set, @language, @index, null) where, in particular, @list gets turned into an rdf:List. There are several other ontologies that express an ordering in RDF, such as the Ordered List Ontology ( http://smiy.sourceforge.net/olo/spec/orderedlistontology.html ) or Resource List ( http://vocab.org/resourcelist/schema ) It was felt that it would be nice to be able to specify different ways to parse/serialize the different list structures into JSON-LD. This would allow interoperability at the JSON level, without mandating a particular ordered list construction in the RDF graph. Our first thought was to put some identifier as the value of @container, and have a specialized parser/serializer that recognized other @containers and would generate the right syntax, other than rdf:List (or JSON list from the triples). However as the enumerated @container ship has sailed, is there an alternative? Could we, perhaps, use @container:@list, and the some other field to give the appropriate syntax to use for the list? Many thanks for your consideration :) Rob -- Rob Sanderson Technology Collaboration Facilitator Digital Library Systems and Services Stanford, CA 94305
Received on Wednesday, 23 April 2014 21:29:51 UTC