4.3.4.1 id - anchor for intra-Deployment Plan references - unique? note?

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Public Review
    • None
    • Hide

      1) Add Plan as a conformance target in section 8

      2) Add this normative text to 4.3.4.1:

      Plans SHALL use an id value that is unique in the scope of the Plan.

      Show
      1) Add Plan as a conformance target in section 8 2) Add this normative text to 4.3.4.1: Plans SHALL use an id value that is unique in the scope of the Plan.

      4.3.4.1 id reads:

      *****
      The value of this node serves as an anchor for intra-Deployment Plan references. See Section 4.3.6.2, "fulfillment", for information on how this anchor is used.
      *****

      Should the value of this node be required to be unique within a Deployment Plan? I am assuming inter-Deployment plan that references are prefixed to make them unique in other contexts. Yes?

      Suggest:

      *****
      The id node specifies a unique (within its Deployment Plan) identifier.

      Note: The identifier specified by a id node is used as an anchor for intra-Deployment Plan references. Section 4.3.6.2 fulfillment has further details on use of this identifier.
      *****

      I don't know what (if any) restrictions are needed on this or other identifiers, so just note the issue as one that needs to be resolved.

            Assignee:
            Unassigned
            Reporter:
            Gilbert Pilz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: