OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Created: (CMIS-35) Use of IETF BCP 14terminology

Use of IETF BCP 14 terminology

                 Key: CMIS-35
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-35
             Project: OASIS Content Management Interoperability Services TC
          Issue Type: Improvement
            Reporter: Julian Reschke
            Priority: Trivial

Example: "These capabilities and interfaces will not match every existing content management system and MAY require some level of change to existing products, at least in terms of conforming"

The terminology defined in IETF BCP 14 (RFC 2119) should be used solely for the purpose of defining requirements. Please do not use it anywhere else, and also please use is sparingly:

"6. Guidance in the use of these Imperatives

   Imperatives of the type defined in this memo must be used with care
   and sparingly.  In particular, they MUST only be used where it is
   actually required for interoperation or to limit behavior which has
   potential for causing harm (e.g., limiting retransmisssions)  For
   example, they must not be used to try to impose a particular method
   on implementors where the method is not required for
   interoperability." -- <http://tools.ietf.org/html/rfc2119#section-6>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]