- From: Shane McCarron <shane@aptest.com>
- Date: Fri, 09 Apr 2010 11:52:15 -0500
- To: Ivan Herman <ivan@w3.org>
- CC: RDFa WG <public-rdfa-wg@w3.org>
Thanks for your quick review. Comments inline: Ivan Herman wrote: > Hey Shane, > > Some comments > > - (Editorial) now that typeof="" is ok in generating a new blank node, can you replace typeof="rdfa:PrefixMapping" by typeof="" in the example on profile files? There is also a typeof="_:a" which is actually wrong and unnecessary, too, should be also typeof="". That also means removing the node in brackets right under the example prefix mapping > Okay. > - (Editorial) same comment on the example for profile files defining terms: typeof="_:a" and typeof="_:b" should be replaced by typeof="" > Sure. > - in section 6.5 and elsewhere... my recollection of yesterday's telco is a bit different and, unfortunately, the minutes are indeed not clear. My recollection is that: > > - <head><body><base> _do_ move to the XHTML document, ie, we do not ask for further community feedback explicitly > Okay. > - the issue on default namespace^h^h^h^h^h^h^h^hvocabulary URI being the XHTML one is indeed explicitly flagged as a question (as you did). > > maybe other participants of yesterday's discussion can help out here... > > - I see you use URIorCURIE as a type for @about and you say 'term or URIorCURIE' for, say, @property. I also see that you have separated term processing from the general CURIE processing. I must admit I preferred the previous version where term processing was part of the CURIE processing; I think it is better for implementers to have everything in on place, so to say. (But I can live with the current version, if the majority of the group is fine with this.) > The group asked me to make this change whilst you were away. It makes the datatypes more explicit. > But... > > - Is it stated somewhere that the term processing must precede the CURIE processing (I have not found it) > I believe that the processing order is defined in the datatype eBNF ( ( term | URIorCURIE )+ indicates term is evaluated first, as eBNF is evaluated left to right), but I can put it in the prose as well. Also, I note that this eBNF didn't really make it into section 5 like I meant it to, so that section (which is prose) needs to be made more explicit. I will take care of it. > - What happens with relative URI-s? At the moment, if I follow section 8 for, say, @about="./something" then this will be rejected because the the text says that we prohibit a CURIE without a colon. Where is that taken care of? > Section 8 describes CURIE processing. For a datatype of URIorCURIE, since that is not a CURIE it would be processed as a URI. This is defined in section 6.4 - and in particular in section 6.4.2. > - And... if we do take care of that, would that mean that I can use @property="./something", ie, a relative URI for a @property? I thought we disallowed that... > Well... since @property has a datatype of (term | URIorCURIE)+, term gets evaluated first. Your relative URI in this example does not match the production for term, (see section 6.4.3) so it is evaluated as a URIorCURIE. It does not match the production rules for a CURIE in RDFa, so it is treated as a (relative) URI. This is something that got changed whilst you were away. > Ivan > > On Apr 8, 2010, at 19:41 , Shane McCarron wrote: > > >> As per my action items today, I have updated the RDFa Core spec and pushed a new Editor's Draft. This is available via our drafts page at http://www.w3.org/2010/02/rdfa/drafts >> >> I have also done some work on our publishing toolchain, so we are getting diff marks, postscript, and PDF versions of specs automatically now. >> >> Please take a close look at this document, as I expect it is in the nearly final form for FPWD. >> >> -- >> 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 Friday, 9 April 2010 16:52:51 UTC