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 24229 - Replace "non-normative" with "informative"
Summary: Replace "non-normative" with "informative"
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) (show other bugs)
Version: unspecified
Hardware: PC All
: P3 enhancement
Target Milestone: ---
Assignee: Eliot Graff
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-08 01:01 UTC by Leif Halvard Silli
Modified: 2014-01-14 20:56 UTC (History)
4 users (show)

See Also:


Attachments

Description Leif Halvard Silli 2014-01-08 01:01:37 UTC
Recently, as result of bug 24047 (for the @longdesc spec), the editors replaced "non-normative" with "informative" (plus added a link to the definition of "Informative".

This came as a result of non-W3-members trying to read the spec, ending up confused by the fact that the *spec* emphasized that the text was "non-normative" unless it was explicitly stated that it was normative.

I don't think Polyglot Markup has run into the same trap. But I still think it would be better to use the positive word "informative" rather than "non-normative". So suggest replacing "non-normative" with "informative", possibly with a link to a defiition. Check the bug 24047 and the longdesc spec to see exactly what they did.
Comment 1 Eliot Graff 2014-01-14 20:56:40 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
    Rationale: This is by design in ReSpec, the script that produces the standardized specification across W3C