- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Wed, 14 May 2014 19:22:48 +0200
- To: <public-vocabs@w3.org>
On Wednesday, May 14, 2014 12:57 AM, Gregg Kellogg wrote: > On May 13, 2014, at 2:37 PM, Wallis,Richard wrote: > > On 13 May 2014, at 22:02, Niklas Lindström wrote: > > > (See also RDF lists, available through @inlist in RDFa, or @list in > > > JSON-LD. These should be judiciously used, when the order is > > > intrinsic and meaningful in itself.) > > > > A useful approach for RDFa & JSON-LD but not much help for those > > applying Microdata, RDFa Lite, or maybe even harvesting the data into > > raw RDF. It's actually just a syntactic *shortcut* to use terms defined by a different vocabulary, namely RDFS. > Microdata does support Lists, but we would need to update the > schema.org Registry to indicate that schema:itemMember is sequenced > (multipleValues: ordered). Of course, the registry is woefully out of > date. I suggested a while ago that we might want to re-address > Microdata to RDF and have it use the JSON-LD context associated with > the vocabulary for this purpose instead. That way, if schema publishes > a context that says that itemMember has @container: @list, a processor > would automatically pick that up. +1 > IMO, RDFa Lite has served it's purpose, and if concepts such as @rev > and @inlist are useful, examples should use it. +1 -- Markus Lanthaler @markuslanthaler
Received on Wednesday, 14 May 2014 17:23:20 UTC