Curating our MAY/MUST (RFC 2119) Statement for Content Module

Dear all,

In the process of authoring the exit criteria, Matt and I found that our
WAI-Adapt Content Specification has no RFC 2119 statements. After some
consideration, and raising this issue with the Task Force today, we propose
adding this sentence in the appropriate spot:

User agents MAY implement any set of attributes from this specification.
Whenever a user agent implements an Adapt attribute, it MUST provide
support for all possible values of that attribute.


The above will be marked up with ReSpec, adding a <section
id="conformance">. This tells ReSpec that the specification is dealing with
"normative" statements. ReSpec can then warn if RFC2119 keywords are
accidentally used in informative/non-normative contexts.

In addition to the text, the group shall approve where we are adding the
conformance statement. I propose adding it as section "1.4 Conformance",
and leaving the current "Use Cases and Requirements" to become 1.5.

Thanks,

Lionel



[image: Lionel Wolberger]
<https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>

Lionel Wolberger
COO, UserWay Inc.
[image: UserWay.org]
<https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
[image: Phone Icon] +1 (415) 800-4557 <+14158004557>
[image: Envelope Icon]
lionel@userway.org <lionel@userway.org>
[image: Schedule with Me]
<https://userway.org/s/lionel?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
Important Reads: Accessibility and SEO Impact
<https://userway.org/blog/the-impact-of-accessibility-on-seo/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
 & Accessibility Tax Credits
<https://userway.org/blog/everything-you-need-to-know-about-web-accessibility-tax-benefits/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>