- From: Niklas Lindström <lindstream@gmail.com>
- Date: Thu, 22 Mar 2012 22:57:50 +0100
- To: public-rdfa-wg <public-rdfa-wg@w3.org>
Hi all!
I'm catching up on my ACTION-113 [1] to add the test cases needed to
cover the resolution of ISSUE-131 [2].
1. The first part should be straightforward. I'll just add:
    <a href="http://example.org/" property="rdf:value"
content="value">ignored</a>
Which results in (as it always has):
    <http://example.org/> rdf:value "value" .
2. The other part is the spec fix for when @datatype is present. I'd
like to verify that I'm reading things correctly. I figure that this:
    <a href="http://example.org/" property="rdf:value" datatype="">value</a>
Should now also result in:
    <http://example.org/> rdf:value "value" .
(Before the fix, the result was that @href was used for both subject
and object.)
3. For completeness, I should also add a test to verify that @about
effectively overrides @href here. I.e.:
    <a about="http://example.net/" href="http://example.org/"
property="rdf:value" content="value">ignored</a>
Should become:
    <http://example.net/> rdf:value "value" .
I also figure that this results in <http://example.net/> being used as
the parent resource for nested statements, correct? Thus, I should
probably extend this to be:
    <a about="http://example.net/" href="http://example.org/"
property="rdf:value" content="value one">
      <span property="rdf:value">value two</span>
    </a>
Yielding:
    <http://example.net/> rdf:value "value one", "value two" .
If you all agree that I'm interpreting this correctly, I'll promptly
add these test cases and include them in the manifest.
(To pass them I had to amend clj-rdfa. Fairly simple, but not yet
committed as I want this confirmed first.)
Best regards,
Niklas
[1]: http://www.w3.org/2010/02/rdfa/track/actions/113
[2]: http://www.w3.org/2010/02/rdfa/track/issues/131
Received on Thursday, 22 March 2012 21:58:48 UTC