Re: Updated RDFa Core and XHTML+RDFa drafts

Ivan Herman wrote:
> Hi Shane,
>
> My comment is purely editorial and is still around the explanation of handling the CURIE-s and URI-s etc... Although I could convince myself that all is there in terms of a specification, I think we should have a section which clearly specifies what SafeCURIEorCURIEorURI means. At the moment, it goes to a text in the appendix that says "A single SafeCURIE or CURIEorURI"; the latter says "A URI or a CURIE". (This is actually misleading because one could read that as an order in processing, ie, URI first and then a CURIE, which is not true.). That is all. It is only syntax, it does not really tell me what I have to _do_. 
>   

Fair enough (and I will fix the CURIEorURI datatype).

> Of course, we have 7.4 that says a lot of things with lots of examples; more specifically 7.4.2. that says how these are processed. But it is still a bit vague for my taste in terms of what attribute does what exactly.
>
> What I would propose is to start section 7.4 by a separate and very explicit description on what is happening. Something like:
>
> [[[
>
> The values of RDFa attributes that refer to URIs can use three different types of attributes (see Section 5): URI,  SafeCURIEorCURIEorURI, or TERMorCURIEorURI. All these attributes map, after processing, to URI-s[RFC-XXXX]. The handling of these attributes is as follows.
>
> - SafeCURIEorCURIEorURI:
>     - In case the value is surrounded by square brackets, then the content within the brackets is evaluated as a CURIE according to the CURIE Syntax definition. If it is not a valid CURIE, the value MUST be ignored
>     - Otherwise, the value is evaluated as a CURIE. If it is a valid CURIE, the resulting URI is used; otherwise, the value is processed as a URI. 
> - TERMorCURIEorURI:
>     - If the value is an NCName, then it is evaluated as a term according to the general use of terms in attributes. Note that this step may mean that the value is to be ignored
>     - Otherwise, the value is evaluated as a CURIE. If it is a valid CURIE, the resulting URI is used; otherwise, the value will be processed as a URI. 
>
> The sections that follow give somewhat more details and examples.
> ]]]
>
> What do you think?
>   

Sure.  I will put in something based upon this shortly.  Thanks!

> Ivan
>
> On Apr 14, 2010, at 05:53 , Shane McCarron wrote:
>
>   
>> I have updated editors drafts available via the drafts page at http://www.w3.org/2010/02/rdfa/drafts - there are diff marked versions from the last Editor's Draft to ease in your review process.  Please be prepared to discuss and vote on moving these to FPWD during the call on Thursday.
>>
>> -- 
>> Shane P. McCarron                          Phone: +1 763 786-8160 x120
>> Managing Director                            Fax: +1 763 786-8180
>> ApTest Minnesota                            Inet: shane@aptest.com
>>
>>
>>
>>     
>
>
> ----
> 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
>
>
>
>
>
>   

-- 
Shane P. McCarron                          Phone: +1 763 786-8160 x120
Managing Director                            Fax: +1 763 786-8180
ApTest Minnesota                            Inet: shane@aptest.com

Received on Wednesday, 14 April 2010 11:33:14 UTC