Official response to RDFWA WG ISSUE-106: Ordered lists

Hi Jeni,

This is an official RDF Web Apps Working Group response to ISSUE-106: 
Should RDFa support the creation of ordered lists?

This issue was created after reading your excellent piece about the 
harmonization of RDFa and Microdata:

http://www.jenitennison.com/blog/node/165

Specifically, this section:

"""
Lists

It is easy for microdata to represent a property with a list of values, 
and really really hard to do the same in RDFa. This is in part because 
RDF views lists resources rather than a distinct data type, and in part 
because RDFa hasn’t added any syntax sugar to make creating rdf:List 
resources easy. Adding some syntax sugar for lists would make life a lot 
easier for anyone using RDFa, but especially if they are adapting 
existing microdata content to RDFa.
"""

This issue was discussed extensively on the mailing list and on the 
teleconference calls, resulting in a final decision to add an ordered 
list syntax to RDFa Core 1.1:

http://www.w3.org/2010/02/rdfa/meetings/2011-09-15#ISSUE__2d_106__3a__Ordered_Lists

The @inlist syntax has been added to the latest RDFa Core 1.1 
specification (search for "@inlist"):

http://www.w3.org/2010/02/rdfa/sources/rdfa-core/Overview-src.html

There are still a few minor technical issues that we need to hammer out 
related to the use of @rev and @inlist, but the Working Group believes 
that the technical issues are minor and can be addressed with some 
massaging of the RDFa Core 1.1 Processing rules.

We hope that this addresses your particular concern about list support 
in RDFa 1.1. Please let us know as soon as possible if this change is 
acceptable to you, and addresses your concern about ordered list support 
in RDFa 1.1.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Standardizing Payment Links - Why Online Tipping has Failed
http://manu.sporny.org/2011/payment-links/

Received on Sunday, 9 October 2011 19:03:01 UTC