W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > February 2011

TERMorCURIEorAbsURIs definition problem

From: Nathan <nathan@webr3.org>
Date: Sat, 05 Feb 2011 23:40:30 +0000
Message-ID: <4D4DDFEE.5010704@webr3.org>
To: RDFA Working Group <public-rdfa-wg@w3.org>
CC: Shane McCarron <shane@aptest.com>
Hi Shane, all,

Currently TERMorCURIEorAbsURI is used by:
   @datatype
   @property
   @rel
   @rev
   @typeof

The text in CURIE and URI Processing [1] currently reads:

TERMorCURIEorAbsURI
   If the value is an NCName, then it is evaluated as a term according 
to General Use of Terms in Attributes. Note that this step may mean that 
the value is to be ignored.
   If the value is a valid CURIE, then the resulting URI is used.
   If the value is an absolute URI, that value is used.
   Otherwise, the value is ignored.

Now, "absolute URI" is defined as:

   scheme ":" hier-part [ "?" query ]
   scheme ":" ihier-part [ "?" iquery ] // IRI

So currently, by that text no URI with a fragment is allowed as the 
value of the five attributes aforementioned.

I'm quite sure this is just editorial and due to the definitions in an 
old URI RFC (rfc2396), but for current URI and IRI specs we'll be 
needing "valid URI" or "valid IRI"

   IRI   = scheme ":" ihier-part [ "?" iquery ] [ "#" ifragment ]

which includes the fragment :)

Suggest the text is changed from:

   "If the value is an absolute URI, that value is used."

To:

   "If the value is a valid URI, that value is used."

Which will clear this up.

As an aside, might also be good if the first line read "If the value is 
a term, then it is evaluated as a term acco.." rather than NCName, we 
have term defined in the spec and it's definition is NCName any way.

[1] http://www.w3.org/TR/rdfa-core/#s_curieprocessing

Best,

Nathan
Received on Saturday, 5 February 2011 23:41:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:50 UTC