- From: Nathan <nathan@webr3.org>
- Date: Tue, 28 Sep 2010 20:38:12 +0100
- To: Shane McCarron <shane@aptest.com>
- CC: RDFA Working Group <public-rdfa-wg@w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3264#c15
"The ˇvalue spaceˇ of anyURI is the set of finite-length sequences of
zero or more characters.."
If this (a 0 length uri-reference as you find in href="") isn't valid
for @prefix then do we need to define that in rdfa core with a note /
constraint / bnf?
Best,
Nathan
Shane McCarron wrote:
> Actually, I think I disagree. The first example would not match the
> pattern for @prefix values. The second wouldn't either, but in some
> implementations might map 'foo' to 'bar:' then not do anything with the
> rest of the value.
>
> On 9/28/2010 12:32 PM, Nathan wrote:
>> Hi All,
>>
>> Just been working on CURIE (and prefix) resolution and realised that
>> given that @prefix contains a whitespace separated list of NCName to
>> xs:anyURI's then a zero length value is possible, as in:
>> <div prefix="foo: ">
>> and:
>> <div prefix="foo: bar: http://example.org/o#">
>>
>> Unsure if this is an issue or not but thought it best to mention.
>>
>> Best,
>>
>> Nathan
>>
>> expanded info:
>>
>> - @prefix = NCName ':' ' ' + xs:anyURI
>> - xs:anyURI can be a URI or a URI Reference
>> - URI-reference = URI / relative-ref
>>
>> relative-ref can be (amongst other things) path-empty (0-length) or
>> path-noscheme, which given the (trimmed) BNF:
>>
>> path-noscheme = segment-nz-nc *( "/" segment )
>> segment-nz-nc = 1*( unreserved / pct-encoded / sub-delims / "@" )
>> unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
>> sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
>> / "*" / "+" / "," / ";" / "="
>>
>> means that afaict, the following is currently valid
>>
>> <div prefix="foo: bar: @ baz: $!+~"> ...
>>
>> resulting in:
>> "foo" => ""
>> "bar" => "@"
>> "baz" => "$!+~"
>>
>>
>>
>
Received on Tuesday, 28 September 2010 19:39:07 UTC