[OASIS Issue Tracker] (SRAMP-75) Consider removing the updateContent and deleteContent capabilities

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Brett Meyer created SRAMP-75:
--------------------------------

             Summary: Consider removing the updateContent and deleteContent capabilities
                 Key: SRAMP-75
                 URL: https://issues.oasis-open.org/browse/SRAMP-75
             Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
          Issue Type: Task
            Reporter: Brett Meyer


Most importantly, in my opinion, these capabilities directly violate the concept of a "repository".  Rather than allowing content modifications, it would be better to focus on updates through *versioning*, but allow the deprecated versions to remain permanently.

Further, updateContent/deleteContent introduce numerous technical issues.  What happens if an artifact has derived artifacts?  What happens if those derived artifacts have relationships pointing to them, or custom properties defined on them?  I'd argue that automatically removing or updating those would violate the "impact analysis" use case and could directly result in numerous conflicts.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)