This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"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...).
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.
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]"
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.
Checked in as WHATWG revision r6072. Check-in comment: clarification http://html5.org/tools/web-apps-tracker?from=6071&to=6072
mass-move component to LC1