RDF-in-XHTML Task Force

Action Review

ACTION: Manu write 2 new tests for img[@src] as subject [recorded in http://www.w3.org/2008/01/31-rdfa-minutes.html#action08] [CONTINUES]

ACTION: [DONE] Ralph ask if tracker can also track public-rdf-in-xhtml-tf [recorded in http://www.w3.org/2008/01/31-rdfa-minutes.html#action09]

Ralph: the answer was 'yes'; I guess I now need to ask for it to be done :)

ACTION: Ben followup with Fabien on getting his RDFa GRDDL transform transferred to W3C [recorded in http://www.w3.org/2007/11/15-rdfa-minutes.html#action01] [CONTINUES]

Ben: there was some issue; what was it? something about recursion?

Manu: I don't think it was recursion
... I'm processing things in a completely different way
... had no problems until step 9
... there are some steps that we might not need
... logically some of the other things make some of the checks redundant
... but nothing major that I see
... Mark did note xml:lang / lang question

Ben: something deeper
... there was something uncovered in direct translation of the spec to code

Manu: parent bnode not initalized

ACTION: Ben to add status of various implementations on rdfa.info [recorded in http://www.w3.org/2007/10/04-rdfa-minutes.html#action06] [CONTINUES]

ACTION: [DONE] Ben to respond to comment on follow-your-nose [recorded in http://www.w3.org/2007/12/06-rdfa-minutes.html#action02]

Ben: I forgot to copy the rdfa mailing list

-> Re: Best Practices Issue: RDF Format Discovery [Ben 2008-02-06]

ACTION: Ben to set up a proper scribe schedule [recorded in http://www.w3.org/2007/10/11-rdfa-minutes.html#action01] [WITHDRAWN]

ACTION: [DONE] Ben to update tracker with todays resolutions. [recorded in http://www.w3.org/2008/01/24-rdfa-minutes.html#action07]

-> RDFa issues tracker

ACTION: Ben to email mailing list to think about last substantive issue on tracker: issue-6 [recorded in http://www.w3.org/2008/02/07-rdfa-minutes.html#action07]

ACTION: Michael to create "Microformats done right -- unambiguous taxonomies via RDF" on the wiki [recorded in http://www.w3.org/2007/08/23-rdfa-minutes.html#action06] [CONTINUES]

ACTION: [DONE] Ralph followup with Dublin Core on what's going on with their namespace URI [recorded in http://www.w3.org/2007/12/06-rdfa-minutes.html#action01]

-> Followup on Dublin Core namespace [Ralph 2008-02-04]

Test Case Review

-> rdfa-test-harness

-- test 78; Multiple incomplete triples

Manu: I have an implementation question; how do we detect the difference between an unsafe CURIE and a mailto: URI?

Ben: we don't -- can't mix them in the same field

Manu: so mailto: looks like an unsafe CURIE?

Ben: yes

Shane: in what context?

Manu: consider test case 78

<benadida> <p rel="foaf:mailbox" resource="mailto:ivan@w3.org">

Manu: if this was @href='mailto:ivan@w3.org'
... we don't know if this is a CURIE

Shane: resource has a datatype; by definition the value is only a CURIE if it has '[]'
... and @href does not accept CURIEs
... the spec gives the datatype for each attribute

<ShaneM> #s_metaAttributes

Ralph: but don't take our word for it here :) make sure you agree that the spec is unambiguous on this question

Manu: again, only the XHTML and SPARQL are what we're evaluating

Ben, Ralph: SPARQL looks like what we'd expect

-- test 79; @resource and @href in completing incomplete triples

Ben: typo in the SPARQL "foaf:knows"
... same typo in test 78
... also, expand the nsprefix to full URIs

Shane: another typo; "http://http://"

Ben: also ';' should be ','

Manu: if we've use foaf:@@ in any existing tests they should fail and there's a flag for that, so we'll catch errors soon

-- test 80; @about overrides @resoruce in incomplete triples

Manu: same typos 'foaf knows', same nsprefix issue

Ben: is this the best title?

Ralph: is "@about sets subject" better?

Ben: "@about sets object"

Ralph: :)

Manu: also tests hanging @rel

<Ralph> perhaps "@about sets object for hanging @rel"

Ben: consider what else happens if additional markup is inside the P
... not sure if we have consistent views on this
... I think the @resource traverses down the tree
... but it's an edge case and we should defer this

-- test 81; multiple ways of handling incomplete triples (with @rev)

Ben: your parser is doing really well if it passes test 81

Manu: again, use full URIs not PREFIX

Ben: anyone who actually _uses_ this markup has a twisted mind :)
... 81 looks good to me

-- test 82; multiple ways of handling incomplete triples (with @rel and @rev)

Manu: thanks to Ivan for making these up
... typo; first triple should end in '.', not ';'
... missing predicate
... in second triple

Ben: 82 looks good, with typos corrected

-- test 83; multiple ways of handling incomplete triples (merged)

Ben: 83 looks good with same typo fixes
... is test 78 with the bnodes named

-- test 84; multiple ways of handling incomplete triples, this time with both @rel and @rev

Ben: appears to be the same as 82; probably meant to be different
... probably the second node was meant to be named, like 83
... add @about to second node
... [as I'm out next week], I'll look at tests 85 - 88 offline and mail comments

Schedule

Ben: reminder, regrets for next week -- both SWD WG and RDFa calls
... regrets for 14-Feb and 21-Feb

Manu: I'll attend the SWD call

Shane: the XHTML2 WG resolved to request Last Call transition

<ShaneM> record of resolution

[adjourned]