Re: ISSUE-76 (Core - Jeni Tennison 4): RDFa Profiles [LC Comment - RDFa Core 1.1]

Hi Shane, All,

I've just been preparing the LC response for 76, and there are a couple 
of bit's we've missed in the editorial changes - in line from here:

RDFa Working Group Issue Tracker wrote:
> (Ed) Section 2.2 Examples: When profiles are first introduced here, I think it would be helpful to:
>   (c) be explicit about the assumption of content negotiation of some kind that means that requests to http://www.example.org/vocab-rdf-dc will result in the RDFa document at http://www.example.org/vocab-rdf-dc.html

The profile example here says: "The following (mythical) example RDFa 
Profile document, with a URI of 
http://www.example.org/vocab-rdf-dc.html" and then the "Using 
@profile..." example following has:

  <p about="http://www.example.org/doc"
    profile="http://www.example.org/vocab-rdf-dc">

Which raises Jeni's question, could we align the two URIs? note that the 
full .html URI is also used in section 8.1.1 and 8.3.2 - so I'd suggest 
we simply change the quoted example to be .html too.

> (Tech) Section 4.2 Host Language Conformance says:
> 
>> The Host Language may define a default RDFa Profile. If it does, the RDFa Profile triples that establish term or URI mappings associated with that profile must not change without changing the profile URI. RDFa Processors may embed, cache, or retrieve the RDFa Profile triples associated with that profile.
>>
>> Note: Host Languages are required to change the URI of their default profile if items are added or removed from the default profile document. The URI change is required to accomodate RDFa Processors that statically embed the terms defined in the profile. Host Languages are expected to change their profiles very rarely.
> 
> Will this restriction cause problems for HTML5 + RDFa given that HTML5 says that the rel attribute may take values defined in http://wiki.whatwg.org/wiki/RelExtensions, which is not going to be static and may change very rapidly? Or will the profile for HTML5 set a default vocabulary and thus possibly interpret NMTOKENs that should be ignored as CURIEs?

sanity check, we're not going to define a default vocab for HTML5, and 
the default profile will specify exactly which terms should be picked up 
- correct understanding?

Cheers,

Nathan

Received on Thursday, 3 March 2011 11:56:46 UTC