- From: Ivan Herman <ivan@w3.org>
- Date: Mon, 3 May 2010 10:47:12 +0200
- To: Gregg Kellogg <gregg@kellogg-assoc.com>
- Cc: "public-rdfa-wg@w3.org" <public-rdfa-wg@w3.org>
- Message-Id: <A6C9BD44-1028-4CC1-8889-DA5E7F85AB89@w3.org>
Ouch, I should have reported that. My implementation, of course, led to the same infinite loop at the beginning and, of course, I had to built in measures to avoid that... Ivan On May 2, 2010, at 23:04 , Gregg Kellogg wrote: > Okay, first cut of implementing @profile goes into an infinite loop. Section 7.5 item 3 indicates that any element containing an @profile document is processed as indicated in RDFa Profiles (section 9). Test 0089 contains <head profile="http://www.w3.org/1999/xhtml/vocab">, which causes the parser to load <http://www.w3.org/1999/xhtml/vocab> to extract the vocabulary. That vocabulary also contains the same <head> element, so the parser goes into an infinite loop. > > Clearly, the parser can check for a recursive call to call an already opened profile, but the processing instructions should discuss this. It seems that in the case of < http://www.w3.org/1999/xhtml/vocab>, it is intended to note that this defines a profile, not requires a profile. Should processing rules be different the <head>, is the profile use in this case just wrong? In any case, it looks like an existing useage pattern that is incompatible with the processing instructions. > > Gregg > > ---- 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
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Monday, 3 May 2010 08:47:25 UTC