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

htmldata-ISSUE-3 (Property-specific datatypes): Should the registry allow property datatype specification [Microdata to RDF]

From: HTML Data Task Force Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 28 Oct 2011 22:03:30 +0000
To: public-html-data-tf@w3.org
Message-Id: <E1RJuWQ-00039E-2s@lowblow.w3.org>

htmldata-ISSUE-3 (Property-specific datatypes): Should the registry allow property datatype specification [Microdata to RDF]

http://www.w3.org/2011/htmldata/track/issues/3

Raised by: Jeni Tennison
On product: Microdata to RDF

Currently, @itemprop values are either plain literals or URI refs, depending on the element and attributes used (@datetime will create a limited set of typed literals).

Should there be a mechanism, such as property-specific information in a vocabulary registry, for specifying the range of a property and coercing values to that datatype if there is a lexical match?

A JSON representation could be something like:

{
  "http://schema.org/" {
    "coerce": {
      "dateCreated": "http://www.w3.org/2001/XMLSchema#date",
      "price": [
        "http://www.w3.org/2001/XMLSchema#decimal",
        "http://www.w3.org/2001/XMLSchema#string"],
    }
   }
}
Received on Friday, 28 October 2011 22:03:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 28 October 2011 22:03:35 GMT