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 7540 - Spec for metadata extensions does not define which states are allowed/conforming
Summary: Spec for metadata extensions does not define which states are allowed/conforming
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE
Depends on:
Reported: 2009-09-07 21:00 UTC by Maciej Stachowiak
Modified: 2010-10-04 14:49 UTC (History)
4 users (show)

See Also:


Description Maciej Stachowiak 2009-09-07 21:00:00 UTC
The spec for meta extensions (currently section defines three statuses for extensions (Proposal, Accepted, and Unendorsed) and says that conformance checkers must check the wiki to determine whether a meta name value is allowed. However, it does not say which of these three statuses count as allowed - is it only the Accepted status, Accepted and Proposal status, or all three statuses that count as allowed for validators (and therefore presumably conforming)? The wiki page does not make this clear either. The spec should be explicit about this.
Comment 1 Ian 'Hixie' Hickson 2009-09-18 21:31:00 UTC
Fixed the spec. I haven't updated the wiki pages, but anyone who feels like doing that should feel entitled to go ahead and clean them up accordingly.
Comment 2 Maciej Stachowiak 2010-03-14 14:50:49 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.