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

Re: Proposal, allow Colon in a Term

From: Nathan <nathan@webr3.org>
Date: Mon, 07 Feb 2011 11:46:35 +0000
Message-ID: <4D4FDB9B.8010701@webr3.org>
To: Ivan Herman <ivan@w3.org>
CC: RDFa Working Group <public-rdfa-wg@w3.org>
Ivan Herman wrote:
> I am not sure what 'Name' includes (and I am lazy to check it:-). Would that allow for characters like #, ? etc?

Nope, Name is just NCName + a colon (NCName being No-Colon-Name maybe?)


Name     ::= NameStartChar (NameChar)*

NameStartChar ::=
    ":" | [A-Z] | "_" | [a-z] | [#xC0-#xD6] | [#xD8-#xF6] | [#xF8-#x2FF]
    | [#x370-#x37D] | [#x37F-#x1FFF] | [#x200C-#x200D] | [#x2070-#x218F]
    | [#x2C00-#x2FEF] | [#x3001-#xD7FF] | [#xF900-#xFDCF]
    |[#xFDF0-#xFFFD] | [#x10000-#xEFFFF]

NameChar ::=
    NameStartChar | "-" | "." | [0-9] | #xB7 | [#x0300-#x036F]
    | [#x203F-#x2040]

> Remember that other thread on whether we can simplify the spec by referring to full URI-s as CURIE-s with specific prefixes? Ie, we could define, in our default profile (yes, I know, I will answer to that separately...) a prefix for "http" mapping to, hm, "http:", and all the rest of the spec could simply refer to CURIE-s. But then we would have to allow for the '/' and other characters in the reference

hm, atm every IRI is a valid CURIE (if it's prefix is declared that is).

Anyway, I guess my point would be, that even with this change and the 
other one, what you propose above, to refer to full URI-s as CURIE-s 
with specific prefixes would still be possible, just map "http:" to "http:".

(I might be missing something)

Best,

Nathan
Received on Monday, 7 February 2011 11:48:22 UTC

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