W3C home > Mailing lists > Public > public-html-data-tf@w3.org > December 2011

Re: HTML Data Guide draft

From: Jeni Tennison <jeni@jenitennison.com>
Date: Mon, 12 Dec 2011 17:06:42 +0000
Cc: HTML Data Task Force WG <public-html-data-tf@w3.org>
Message-Id: <84F15DED-0987-4395-B4A5-3692CC2734BD@jenitennison.com>
To: Gregg Kellogg <gregg@kellogg-assoc.com>
Thanks Gregg,

On 11 Dec 2011, at 18:37, Gregg Kellogg wrote:
> Looks good Jeni. Do we want to mention Turtle in HTML at all?

I added this in a Scope section:


> Regarding <time> element value range in RDFa. Note that the current resolution of the WG [1] is to accept datatype ranges described in the HTML5 document where they match XSD; this would go in the html+rdfa spec, which is on a different publication timeline than rdfa-core and xhtml+rdfa. Presently, this includes xsd:date, xsd:dateTime, xsd:time, xsd:duration, xsd:gYear, and xsd:gYearMonth. The value can be expressed either using the @datetime attribute or the element's value, but must be a complete lexical match, including possible whitespace, otherwise a plain literal is generated.

I *think* that this is covered in:


(which I expanded following comments) but let me know if not.

> The use of @resource within RDFa Lite is still under discussion. My view is that it should be added, and possibly replace @about. Manu feels that @about was long considered and conveys more inherent semantic meaning than @resource. The current draft of RDFa Lite 1.1 discusses this and solicits feedback on the topic.

Yep, I know. Have you got some suggested rewording for:



> RDFa Core 1.1 and HTML+RDFa define just three link relations: describedby, license and role. XHTML+RDFa has the existing step.

I've rejigged


Let me know if that's not accurate.

> One thing I would suggest as a best practice for authors is that the encorporate a data round-tripping step when testing, to ensure that the data extracted from the page matches the data used to create it. For example, if data is modeled using Turtle, this can be used through a template-based writer to create the HTML markup. This should then be distilled back to RDF to ensure that the two reasonably match. The same process can be done for JSON-based representations.

I've added that suggestion at:



Jeni Tennison
Received on Monday, 12 December 2011 17:09:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:08:26 UTC