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

Use case for scripts using HTML data

From: Jeni Tennison <jeni@jenitennison.com>
Date: Tue, 18 Oct 2011 09:53:44 +0100
Message-Id: <55016E39-1648-4007-9ABA-AB2854D09E7C@jenitennison.com>
Cc: public-html-data-tf@w3.org
To: Rob Styles <rob.styles@talis.com>
Hi Rob,

You know a while ago you did that reading list application that used RDFa? I'm trying to collect use cases for the HTML Data Task Force, and I think it illustrates an important pattern of use that we might otherwise not capture, namely a site using HTML data for itself to consume using scripts.

I wonder if you'd do me a big favour and do just a really short summary of it under these headings:

  a short name that can be used to refer to the use case
  any necessary information about the domain of the use case that 
  helps to explain it
  how HTML data is used in the use case, with either embedded 
  examples of the markup or pointers to material that otherwise 
  illustrates it
  what makes this use case different from others? why was markup 
  used in the way described rather than an alternative?
  pointers to implementations that generate and/or consume HTML 
  data in this form, or ideas for such implementations

or point me to some other write-up from which we can create a summary.

I know it was done a few years ago. The one big question that I think people would have about it now is whether it would be preferable, assuming use of HTML5, to have had the data provided using data-* attributes instead. Are there any places in the markup where that approach wouldn't have worked, or reasons for using markup that can be read by consumers other than your script? If the latter, which consumers did you have in mind?

Thanks ever so much in advance,

Jeni Tennison
Received on Tuesday, 18 October 2011 08:54:18 UTC

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