This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13374 - Incorrect predicate URIs
Summary: Incorrect predicate URIs
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on: 13314
Blocks:
  Show dependency tree / graph
 
Reported: 2011-07-26 21:12 UTC by contributor
Modified: 2011-08-11 22:31 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-07-26 21:12:53 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html
Multipage: http://www.whatwg.org/C#conversion-to-rdf
Complete: http://www.whatwg.org/c#conversion-to-rdf

Comment:
Incorrect predicate URIs

Posted from: 81.234.240.242
User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.9.181 Version/12.00
Comment 1 Philip Jägenstedt 2011-07-26 21:14:26 UTC 
Just in case the RDF conversion is not axed, note that the OWL triples for the license vocab have incorrect predicate URIs. Example:

<http://www.w3.org/1999/xhtml/microdata#http%3A%2F%2Fn.whatwg.org%2Fwork%23%3Awork>

should be

<http://www.w3.org/1999/xhtml/microdata#http://n.whatwg.org/work%23:work>
Comment 2 Michael[tm] Smith 2011-08-04 05:05:21 UTC 
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-11 22:31:21 UTC 
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