• Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: 1.2
    • Component/s: Spec
    • None
    • Environment:

      Normative

    • Hide

      I would clean up the paragraph to define type, say that details of what is identified by type are not specified and use SHOULD for namespaces.

      Show
      I would clean up the paragraph to define type, say that details of what is identified by type are not specified and use SHOULD for namespaces.
    • Hide

      This was resolved as not a bug on the 2017-08-31 call https://www.oasis-open.org/committees/document.php?document_id=61489&wg_abbrev=camp
      The TC believes that it is premature to have a SHOULD and best practices are yet to emerge

      Show
      This was resolved as not a bug on the 2017-08-31 call https://www.oasis-open.org/committees/document.php?document_id=61489&wg_abbrev=camp The TC believes that it is premature to have a SHOULD and best practices are yet to emerge

      4.2.1 in addition to being a disclaimer of what CAMP (this specification?) does not define, contains the following:

      "...To promote portability, both providers and consumers of the CAMP API are encouraged to namespace-qualify the types that they use....."

      Isn't that a normative SHOULD?

            Assignee:
            Unassigned
            Reporter:
            Chet Ensign
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: