Re: quick ping - ISSUE-104

Thanks for making your request clear.  I will discuss this with the 
editing team and we will get back to you.

Jonathan Rees wrote:
>
> OK, then please make sure that Appendix B of the RDFa Syntax and 
> Processing spec has definite statements about the value spaces of BOTH 
> of your new datatypes, CURIE and URIorSafeCURIE. Being especially 
> clear on the difference between the QName and CURIE value spaces, and 
> the similarities or differences betweeen anyURI and URIorSafeCURIE 
> value spaces, in this part of the document, seems pretty important.
>
> Not that I understand this stuff all that well, but there seems to be 
> so much potential for confusion that I don't think you can overdo the 
> explanations here.
>
> Jonathan
>
> On Jun 16, 2008, at 10:32 AM, Shane McCarron wrote:
>
>> Jonathan Rees wrote:
>>>
>>> On Jun 16, 2008, at 10:17 AM, Shane McCarron wrote:
>>>
>>>> Sorry, I misunderstood your request.  We have defined the lexical 
>>>> and value space for CURIEs in the CURIE spec itself 
>>>> (http://www.w3.org/MarkUp/Drafts#curie for the latest draft).   For 
>>>> a variety of reasons the RDFa spec does not reference the CURIE 
>>>> spec.  If I understand your request, you would like the text about 
>>>> CURIE lexical and value space copied into the RDFa specification.  
>>>> Is that correct?
>>>
>>> I found nothing relevant in Appendix A here:
>>>
>>> http://www.w3.org/TR/2008/WD-curie-20080506
>>>
>>> so I'm not sure what you're talking about.
>> Agreed - the definition of those spaces is in the normative section 
>> 3, and is stated as:
>>
>>> The concatenation of the prefix value associated with a CURIE and 
>>> its |reference| MUST be an IRI (as defined by the IRI production in 
>>> [IRI <http://www.w3.org/TR/2008/WD-curie-20080506/#ref_IRI>]). Note 
>>> that while the set of IRIs represents the /lexical space/ of a 
>>> CURIE, the /value space/ is the set of URIs (IRIs after 
>>> canonicalization - see [IRI 
>>> <http://www.w3.org/TR/2008/WD-curie-20080506/#ref_IRI>]).
>>
>>>
>>> Whether either document can cite the other depends on their 
>>> publication schedule. I don't advise having a recommendation cite a 
>>> draft.
>> Quite.  The publication schedules are disjoint, which is one of the 
>> reasons the two are not coupled together.
>>
>> -- 
>> Shane P. McCarron                          Phone: +1 763 786-8160 x120
>> Managing Director                            Fax: +1 763 786-8180
>> ApTest Minnesota                            Inet: shane@aptest.com
>>
>>
>

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

Received on Monday, 16 June 2008 15:39:16 UTC