- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Thu, 4 Jul 2013 13:07:00 +0200
- To: <public-rdf-wg@w3.org>
On Thursday, July 04, 2013 12:41 PM, Andy Seaborne wrote: > On 03/07/13 22:38, Gregg Kellogg wrote: > > I don't consider JSON-LD lists as being conceptually any different > that Turtle Lists; these are artifacts of the serialization, and not > the underlying data model. > > Are all JSON-LD lists transformed to RDF lists by the > json-ld-api/#list-to-rdf-conversion? Yes.. but not all RDF lists are converted to JSON-LD lists. Only well-formed lists that are referenced exactly once. > It's not clear -- it says "a list > may be represented using the @list keyword as follows:" -- not a RFC- > MAY but only a "may" nevertheless). Where's that statement? > Suggestion: clarify as to whether there are other ways or not. E.g. "a > list is represented using the @list keyword as follows:") > > > The problem is about syntax and which data model is which. > This confusion is manifest by the fact that the documents are split > Serialization / Algorithms where the document entitles "serialization" > includes an appendix on "Data Model". > > A separate document on "Data Model" would have been good. Making that > it not-an-appendix, but still at the end of the document, might help. Most of our appendixes are normative. I would be fine with turning them (or even all) into normal sections. -- Markus Lanthaler @markuslanthaler
Received on Thursday, 4 July 2013 11:07:38 UTC