W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > August 2010

Re: Format of @profile files (summarizing ISSUE-39, maybe moving forward...)

From: Richard Cyganiak <richard.cyganiak@deri.org>
Date: Wed, 25 Aug 2010 17:11:10 +0100
Cc: W3C RDFa WG <public-rdfa-wg@w3.org>
Message-Id: <6103CFBA-B4ED-43F4-AD6F-901E8A22F2C5@deri.org>
To: Ivan Herman <ivan@w3.org>

On 24 Aug 2010, at 13:32, Ivan Herman wrote:
> Modeling wise it should be
>
> <http://example.com/my-host-language#> rdfa:vocabulary  
> "True"^^xsd:boolean .
>
> But I was not sure whether it is worth the trouble to add that  
> explicit request in the processing rules...

Oh, I see. I think the processing is fine as is, but the spec should  
somehow indicate that a boolean literal is supposed to be used as the  
object, so that the question doesn't arise for a reader. One way of  
doing this would be to have an example with rdfa:vocab in Section 2.2,  
and link to it from the passage in the Profiles section.

>>>> 10. There should be a sub-section on default profiles.
>>>
>>> I added instead a reference to section 6 where this is described.
>>
>> I see a reference for default vocabulary URI, but what I meant was  
>> profiles (incl. term and prefix mappings) pre-defined by the host  
>> language.
>
> But this can be used for other purposes as well, not only for the  
> host language thingy! Essentially, an rdf:vocabulary triplet is  
> equivalent to a @vocab attribute used on the same node. That is why  
> I have put the reference to section 6

My request for a sub-section on default profiles is not specifically  
about @vocab/rdfa:vocab.

What I meant is that I'd like to see a single subsection where one can  
read how default profiles work. Currently this information is  
scattered throughout 4.2, 7.2, 7.5 and 9, under headlines that mostly  
have nothing to do with “profiles”. This makes it hard to understand  
the mechanism. (I certainly didn't succeed, as you have seen  
throughout this thread!)

So this is an editorial request to add something like this as a  
subsection of Section 9:


== 9.1 Default profile documents ==

Host languages MAY define a '''default profile document'''. Its URI is  
known as the host language's '''profile URI'''.

Any prefix mappings, term mappings, and default vocabulary URIs  
defined in the default profile document are used as initial values for  
the evaluation context (see 7.2).

RDFa processors MAY embed, cache or retrieve the default profile  
document of supported host languages.

Host languages MUST NOT change the prefix mappings, term mappings or  
default vocabulary URI defined in their profile document without  
changing the profile URI.



(Collecting the information for writing the above, I notice that it's  
a bit unclear wether default profiles can define *prefix* mappings; I  
read sections 4.2 and 7.2 as saying “no”, and section 7.5 as saying  
“yes”. One more reason for having a dedicated section for this!)

Best,
Richard



>
> Ivan
>
>
>> Best,
>> Richard
>>
>>
>>
>>>
>>> Ivan
>>>
>>>>
>>>> Best,
>>>> Richard
>>>>
>>>>> [4] http://www.w3.org/TR/2010/WD-rdfa-core-20100803/#s_profiles
>>>>> [5] http://www.w3.org/2010/02/rdfa/wiki/ProfileSpec
>>>>
>>>
>>>
>>> ----
>>> 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
>>>
>>>
>>>
>>>
>>>
>>
>> -- 
>> Linked Data Technologist • Linked Data Research Centre
>> Digital Enterprise Research Institute (DERI), NUI Galway, Ireland
>> http://linkeddata.deri.ie/
>> skype:richard.cyganiak
>> tel:+353-91-49-5711
>>
>
>
> ----
> 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
>
>
>
>
>

-- 
Linked Data Technologist • Linked Data Research Centre
Digital Enterprise Research Institute (DERI), NUI Galway, Ireland
http://linkeddata.deri.ie/
skype:richard.cyganiak
tel:+353-91-49-5711
Received on Wednesday, 25 August 2010 16:11:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:07 GMT