12084 2011-02-15 13:07:07 +0000 application/microdata+json fragment identifiers not really defined 2011-08-04 05:05:37 +0000 1 1 1 Unclassified HTML WG LC1 HTML Microdata (editor: Ian Hickson) unspecified PC Windows NT RESOLVED FIXED http://dev.w3.org/html5/md/#refsJSON P2 normal --- 1 julian.reschke ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 45586 0 julian.reschke 2011-02-15 13:07:07 +0000 "Fragment identifiers used with application/microdata+json resources have the same semantics as when used with application/json. [JSON]" This is misleading in that the JSON spec does not define fragment identifiers (maybe it should, but that's a separate issue...). 47883 1 ian 2011-05-03 19:43:08 +0000 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: The idea is to make sure that when someone fixes the problem for JSON in general, we don't contradict it, and until they do, we are equally undefined. 47929 2 julian.reschke 2011-05-04 08:03:42 +0000 I understand the idea, but this doesn't change the fact that the spec text is confusing. Please say something like "Fragment identifiers used with application/microdata+json resources have the same semantics as when used with application/json (which are undefined at the time this was written). [JSON]" 48005 3 ian 2011-05-04 23:37:24 +0000 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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 48006 4 contributor 2011-05-04 23:38:16 +0000 Checked in as WHATWG revision r6072. Check-in comment: clarification http://html5.org/tools/web-apps-tracker?from=6071&to=6072 52956 5 mike 2011-08-04 05:05:37 +0000 mass-move component to LC1