[OASIS Issue Tracker] (SRAMP-69) Clarify constraints on update/updateContent/delete/deleteContent

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

     [ https://issues.oasis-open.org/browse/SRAMP-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-69:
-----------------------------

    Description: 
The update/updateContent/delete/deleteContent actions could use some clarifications describing required constraints.  Ideas are described here: https://developer.jboss.org/thread/250173

Also, the foundational spec's "2.2.2 Document Artifact Types" mentions "Documents which have a Derived Model associated with them cannot be updated in the repository.  They must be removed and republished.".  Consider removing that -- allow content updates (and re-generate derived content), as long as that derived content does not have custom metadata, nor is it the target of a relationship.

The atom spec's "2.3.5.5 Deleting an Artifact Entry" mentions "If an artifact is deleted which is the Target Entry of a relationship instance owned by some other Source Entry, then that relationship instance is also deleted in that Source Entry.".  That needs clarified, based on possible constraints.

Deleting an artifact's *content* should also delete its derived artifacts.

  was:
The update/updateContent/delete/deleteContent actions could use some clarifications describing required constraints.  Ideas are described here: https://developer.jboss.org/thread/250173

Also, the foundational spec's "2.2.2 Document Artifact Types" mentions "Documents which have a Derived Model associated with them cannot be updated in the repository.  They must be removed and republished.".  Consider removing that -- allow content updates (and re-generate derived content), as long as that derived content does not have custom metadata, nor is it the target of a relationship.

The atom spec's "2.3.5.5 Deleting an Artifact Entry" mentions "If an artifact is deleted which is the Target Entry of a relationship instance owned by some other Source Entry, then that relationship instance is also deleted in that Source Entry.".  That needs clarified, based on possible constraints.


> Clarify constraints on update/updateContent/delete/deleteContent
> ----------------------------------------------------------------
>
>                 Key: SRAMP-69
>                 URL: https://issues.oasis-open.org/browse/SRAMP-69
>             Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
>          Issue Type: Improvement
>            Reporter: Brett Meyer
>
> The update/updateContent/delete/deleteContent actions could use some clarifications describing required constraints.  Ideas are described here: https://developer.jboss.org/thread/250173
> Also, the foundational spec's "2.2.2 Document Artifact Types" mentions "Documents which have a Derived Model associated with them cannot be updated in the repository.  They must be removed and republished.".  Consider removing that -- allow content updates (and re-generate derived content), as long as that derived content does not have custom metadata, nor is it the target of a relationship.
> The atom spec's "2.3.5.5 Deleting an Artifact Entry" mentions "If an artifact is deleted which is the Target Entry of a relationship instance owned by some other Source Entry, then that relationship instance is also deleted in that Source Entry.".  That needs clarified, based on possible constraints.
> Deleting an artifact's *content* should also delete its derived artifacts.



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