Here is a proposed resolution for Rel22:
--
REL-22 Spec meta Editorial Unassigned Tom Rutt
Title: Optionality
Description: The use of the term OPTIONAL needs to be
revisited particularly in a specification of this nature where
interoperability is an explicit goal and RFC 2119 has been
referenced. [see original spec]
Proposal: Go to email on this issue
--
Proposed Resolution:
We inlude Conformance section in the spec.
The word "OPTIONAL " in the spec means
the element or attribute is optional to be in a message.
But it doesn't say anything about optionality
for implementation.
Comformance section should mention about
the optionality for implementation.
--
Any comments?
Thanks,