RDF in XHTML Task Force

Action Items

<scribe> ACTION: ShaneM to craft errata about case insensitive reserved words. [recorded in http://www.w3.org/2009/10/08-rdfa-minutes.html#action03] [DONE]

<scribe> ACTION: ShaneM to craft errata text about canonical XMLLiterals [recorded in http://www.w3.org/2009/10/08-rdfa-minutes.html#action02] [DONE]

<scribe> ACTION: Ben to update JS xmlns getter code on implementors' guide for xhtml mime type support [recorded in http://www.w3.org/2009/09/17-rdfa-minutes.html#action02] [CONTINUES]

<manu> scribenick: manu

Ivan: When does HTML+RDFa get published?

Manu: Today at some point...

RDFa Updates

Manu: Any updates from Mark?

Ivan: We have a book chapter on RDFa that we wrote.
... There is a book that Handler and Fentel and Dom?? which is published by Stringer
... Handbook for the Semantic Web
... Collects usual technologies and presents them.
... Still being heavily edited, published sometime late 2009

Manu: HTML+RDFa being published later today
... @version and @profile are being fought in HTML WG

Ivan: @version and @profile are not mandatory

Manu: Right, but they're important for the default generation of XMLLiterals
... We probably don't want to do it in RDFa 1.1

Ivan: That would be an incompatible change on RDFa 1.0

Shane: If there is no versioning mechanism, then we can't make the change.

Manu: @profile was obsoleted in HTML5, so that creates an issue for us
... So we have an HTML5 EPB spec for addressing the @version and @profile issue.

Ivan: So we would be forced to not make backwards-incompatible changes.
... I also don't like that by default new lines and other formatting characters are saved.
... What about the xmlns: issue?

Manu: Microsoft seems to be backing it... but no proposal yet.

Discuss and approve Shane's errata text

Manu:Reserved word values and case-sensitivity

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Oct/0010.html

Shane: Wait... new feedback from Philip Taylor
... on XMLLiteral issue.

Manu: So, we might need to defer talking about the XMLLiteral issue based on Philips feedback

Ivan: Ivan is right, it should be Exclusive Canonical XML if we are going to do this
... Yes, it's a mess right now, so I'll try to explain clearly.
... It should be Exclusive Canonical XML if we are going to require this.
... in my understanding, if RDFa Processors serialize the triples it will depend on which serialization they use
... if they serialize into TURTLE, they have to use Exclusive XML Canonicalization.
... if they serialize to RDF/XML, they don't have to.
... we have to be careful in the examples and the primer, that they should be in Exclusive Canonical XML.
... there are some tests today that are more permissive than they should be.
... RDF/XML spec says that XML Literals must produce a canonical representation of that.

Manu: Do you think RDFa should place this in the spec, to ensure downstream RDF tools don't have to worry about c14n.

Ivan: I think it places a burden on implementations that only generate RDF/XML?

Shane: It's necessary because the triples that we generate should be identical... if they aren't, it affects triple stores.

Ivan: I think it's good advice to give, but don't think it should be a requirement...

Manu: It causes a problem when RDFa Processors are used to generate RDF/XML which is then sent to SPARQL processors.

Ivan: I think we need feedback from developers before we make this requirement.

Mark: I agree with both of Ivan's points.
... At the very least, I think we should look at what this means for HTML+RDFa vs. XHTML+RDFa
... So, this might only apply to the XHTML version.
... We have to be very careful - because prefixes might not have come from xmlns:, they might have come from @token.

Ivan: having something in the document that is advisory is a good idea.

Manu: Would we feel okay with making this a recommendation, but not a requirement?

Shane: I think it's Philips issue, primarily.

Ivan: How much work would it require to Canonicalize XML in your implementation, Shane?

Shane: I need to look at the new spec Philip sent out first.

Manu: Ok, so we just need to change the RDFa Test Suite

<scribe> ACTION: Shane to re-draft XMLLiteral errata text [recorded in http://www.w3.org/2009/10/15-rdfa-minutes.html#action04]

<scribe> ACTION: Manu change test suite to use Exclusive Canonical XMLLiteral tests [recorded in http://www.w3.org/2009/10/15-rdfa-minutes.html#action05]

<scribe> ACTION: Manu speak with Andy Seaborne about SPARQL.org implementation re: c14n [recorded in http://www.w3.org/2009/10/15-rdfa-minutes.html#action06]