Bug 21515 - Conformance section: need to note use of MUST that is "RFC-legal" as opposed to common English usage
Summary: Conformance section: need to note use of MUST that is "RFC-legal" as opposed ...
Alias: None
Product: AudioWG - OBSOLETE - Moved to Github
Classification: Unclassified
Component: Web Audio API - OBSOLETE - See Github (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL: https://dvcs.w3.org/hg/audio/raw-file...
Depends on:
Reported: 2013-04-02 12:30 UTC by Olivier Thereaux
Modified: 2014-10-28 17:17 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thereaux 2013-04-02 12:30:25 UTC
Per discussion at Audio WG f2f 2013-03-26

The conformance section should note that the use of keywords MUST, MAY, SHOULD are used per RFC-2119 and constitute normative statements.

The group did not express a strong preference for either of the following two options. The choice will be left to the discretion of the editor:

1. make sure all normative statements use upper-case MUST, MAY, etc


2. state in conformance statement that all usage of words must, may, should are per RFC2119 and remove/paraphrase all other uses of the keywords, so that only conformance assertions use them.
Comment 1 Olivier Thereaux 2014-10-28 17:14:26 UTC
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 2 Olivier Thereaux 2014-10-28 17:17:18 UTC
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.