Uploaded image for project: 'OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC'
  1. OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
  2. SRAMP-14

Supporting History

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0
    • Fix Version/s: 1.1
    • Component/s: Foundation
    • Labels:
      None
    • Environment:

      N/A

    • Proposal:
      Hide

      The TC needs to discuss this and come to a conclusion on how best to handle change history.

      Show
      The TC needs to discuss this and come to a conclusion on how best to handle change history.
    • Resolution:
      Hide

      Based on the vote on a motion to move this issue to a future release that was unanimously carried. I am moving this issue to release 1.1 of S-RAMP.

      Show
      Based on the vote on a motion to move this issue to a future release that was unanimously carried. I am moving this issue to release 1.1 of S-RAMP.

      Description

      Issue-014 from the contributed issues document

      Upgrade lastModified... attributes to support longer history of changes.

      Both lastModifiedTimestamp and lastModifiedBy currently are required and have a default cardinality of 1.
      The question is should we change these attributes in the Core Model to their own type and then have a
      sequence of them in the BaseArtifactType?

        Attachments

          Activity

            People

            • Assignee:
              kstam Kurt Stam (Inactive)
              Reporter:
              brunssen Vincent Brunssen
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: