ISSUE-3: Should the registry allow property datatype specification

Property-specific datatypes

Should the registry allow property datatype specification

State:
PENDING REVIEW
Product:
Microdata to RDF
Raised by:
Jeni Tennison
Opened on:
2011-10-28
Description:
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"],
}
}
}
Related Actions Items:
No related actions
Related emails:
  1. htmldata-ISSUE-3 (Property-specific datatypes): Should the registry allow property datatype specification [Microdata to RDF] (from sysbot+tracker@w3.org on 2011-10-28)

Related notes:

The concensus is that datatypes are only derived from HTML semantics, so that only <time> values have a datatype other than plain.

Gregg Kellogg, 7 Jan 2012, 20:50:35

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $