Re: safe curies with undefined prefixes in @about/@resource

Hey Toby,

I appreciate that, and it might, technically, be a good idea to treat it that way. However... doesn't that break backward compatibility? In RDFa 1.0 that safe CURIE would definitely be ignored...

I am not saying we should not do that if we have evidence that this would not create major issues with deployed RDFa. But we should definitely be careful...

Ivan

On Apr 12, 2010, at 09:28 , Toby Inkster wrote:

> Consider:
> 
>  <div profile="http://example.com/profile"
>    xmlns:foaf="http://xmlns.com/foaf/0.1/">
>    <p about="#bob">
>      <span property="foaf:name">Bob</span>
>      <span about="[fred:me]" property="foaf:name">Fred</span>
>    </p>
>  </div>
> 
> Assuming that the profile document defines the prefix "fred", then the
> names "Fred" and "Bob" are taken to be different resources.
> 
> If prefix "fred" being undefined leads to the about="[fred:me]" attribute
> being completely ignored, then a processor will assume that the names
> "Bob" and "Fred" both apply to the same resource.
> 
> It seems to me that a more useful way of processing it would be to take
> about="[fred:me]", when "fred" is undefined, to introduce a new blank
> node. That way, like the correct behaviour when "fred" is defined, the
> names apply to two different resources; it's just that we don't know the
> URI for one of them.
> 
> -Toby
> 


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf