Handling of missing @profile from Gregg Kellogg on 2010-08-04 (public-rdfa-wg@w3.org from August 2010)

From: Gregg Kellogg <gregg@kellogg-assoc.com>
Date: Tue, 3 Aug 2010 22:40:47 -0400
To: RDFa WG <public-rdfa-wg@w3.org>
Message-ID: <0885D131-65B4-4049-8461-E2C8417C66F5@kellogg-assoc.com>

I'm confused about wording in the latest heartbeat draft of RDFa Core 1.1:

Section 7.5 step 2 indicates that if any referenced RDFa Profile is not available, then the current element and it's children MUST NOT be processed.

Section 9 outlines steps to process profiles and indicates that if a retrieval fails to continue with the next URI.

Presuming that 7.5 step 2 is the intention, then the steps in section 9 would seem to be pointless, as the effect of any more processing would be thrown away.

Consider the following

<body profile="http://im-not-here http://im-here"> ... </body>

This would fail attempting to process the first profile, and according the 7.5s2 would cause the remainder of the sub-tree to not be processed, but according to section 9, the processor would go on to process the second URI and continue.



Gregg

Received on Wednesday, 4 August 2010 02:41:49 UTC