W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > March 2010

ISSUE-1: Status of RDFa Profiles

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Thu, 11 Mar 2010 12:49:04 -0500
Message-ID: <4B992D10.6010109@digitalbazaar.com>
To: RDFa WG <public-rdfa-wg@w3.org>
"Are we limiting next/prev/index/license/etc to @rel/@rev or allowing
them everywhere?"

There are two viewpoints on this issue so far:

1. Allow all of the reserved keywords in RDFa 1.0 in all elements in
   RDFa 1.1. Call them tokens/keywords and unify the way we express
   these entities in the profile document.
2. Allow specific tokens/keywords in rel/rev/property/about - specify
   which attributes the keywords can be used in via the profile
   document.

The first would make this markup valid IF a) the web page author doesn't
specify anything using @profile and b) we have a default RDFa profile
document that defines all of the reserved words in RDFa 1.0 as
tokens/keywords in RDFa 1.1:

<span property="copyright">Copyright 2010 W3C</span>

Two things should jump out at you with that example: 1) copyright should
refer to a URL, not a piece of text and 2) copyright is used in property
instead of rel/rev. While this is atypical markup for RDFa 1.1, this is
the type of "dangerous markup" that we enable by allowing #1. One could
give warnings about this dangerous markup by specifying in the
profile/vocabulary that the rdfs:range is supposed to be a URI, not a
plain literal.

Allowing #2 would be more technically accurate, but would be more
complicated for web authors. If #2 is adopted, one must now understand
that certain keywords/tokens can only be used in certain RDFa
attributes. This could lead to markup not generating what you intended
because the "foobar" keyword/token is only allowed in @rel/@rev but not
@property.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: PaySwarming Goes Open Source
http://blog.digitalbazaar.com/2010/02/01/bitmunk-payswarming/
Received on Thursday, 11 March 2010 17:49:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:06 GMT