Need to distinguish in-progress change set from delivered/committed one

XMLWordPrintable

    • Hide

      [This part is replaced by a newer proposal in the comments] Add a new optional boolean property to the change set resource shape representing whether the change set has been delivered/committed. For example oslc_config:isCommitted.

      [This part is somewhat orthogonal to the newer proposal in the comments] Add an optional oslc_config:committed (already a vocabulary term for baselines) to the change set resource shape to record the xsd:dateTime at which this occurred.

      We should not assume that implementations record the dateTime in order to be able to distinguish between in-progress and delivered, so two separate properties are recommended,

      Show
      [This part is replaced by a newer proposal in the comments] Add a new optional boolean property to the change set resource shape representing whether the change set has been delivered/committed. For example oslc_config:isCommitted. [This part is somewhat orthogonal to the newer proposal in the comments] Add an optional oslc_config:committed (already a vocabulary term for baselines) to the change set resource shape to record the xsd:dateTime at which this occurred. We should not assume that implementations record the dateTime in order to be able to distinguish between in-progress and delivered, so two separate properties are recommended,

      The current change management spec describes the resource shape for a oslc_config:ChangeSet. We have a requirement to distinguish an in-progress change set from a delivered/committed change set. We have been using the deprecated oslc_config:mutable property. A value of "false"^xsd:boolean meant in-progress, and "true"^xsd:boolean meant delivered. However, this usage is a little obscure and not documented for in the spec for this specific use case.

            Assignee:
            Nick Crossley (Inactive)
            Reporter:
            davidhoney
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: