This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This is a comment on the RDF mapping in the subsection Converting HTML to other formats ยป RDF of the HTML Microdata document. This comment concerns the RDF conversion of datetime values. Since literals in RDF are datatyped, it would be appropriate to map any values that were obtained from a datetime attribute to the respective datatype. In other words, if the datetime attribute contains a time, then the RDF conversion should generate an xsd:time typed literal; xsd:date for a date, and xsd:dateTime for a date and time.
That seems reasonable... do I just change the spec to say that when it comes from a <time> element, the generated triple is in fact a quad and the fourth field is a "type" with the URL corresponding to the appropriate xsd:* type name?
Instead of a "plain literal", you generate a "typed literal", which has a "datatype URI". http://www.w3.org/TR/rdf-concepts/#dfn-typed-literal http://www.w3.org/TR/rdf-concepts/#dfn-datatype-URI Something like this should work: If element is a time element, and value is a valid date or time string, then: - Let value be a typed literal - If value is a valid date string, then the datatype URI is http://www.w3.org/2001/XMLSchema#date - If value is a valid time string, then the datatype URI is http://www.w3.org/2001/XMLSchema#time - If value is a valid global date and time string, then the datatype URI is http://www.w3.org/2001/XMLSchema#dateTime
Thanks, will do.
Turns out there's actually a comment in the source saying I should do this. :-) I'm delaying fixing this a little longer, however, because there's a chance we're going to drop <time> altogether in favour of a more generic mechanism for machine-readable data.
mass-move component to LC1
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: no longer relevant since the RDF section was removed.