• Type: Improvement
    • Resolution: Fixed
    • Priority: Trivial
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide

      The specification should leverage the conformance language to normative sections of the specification

      Show
      The specification should leverage the conformance language to normative sections of the specification

      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>

            Assignee:
            Unassigned
            Reporter:
            Julian Reschke (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: