[OASIS Issue Tracker] Commented: (SRAMP-14) Supporting History

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

    [ http://tools.oasis-open.org/issues/browse/SRAMP-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29851#action_29851 ] 

Kurt Stam  commented on SRAMP-14:
---------------------------------

I recommend:

1.  to keep the current lastModifiedTimestamp and lastModifiedBy attributes, and
2. to add modifiedTimestamp and modifiedBy element which by default are not returned. Only when a certain flag is set on the request the full history should be returned.

For more details see:
http://www.oasis-open.org/apps/org/workgroup/s-ramp/download.php/45511/s-ramp-14.html

I can present the recommendation at the next meeting. One question is what this flag should be to get the verbose answer.

> Supporting History
> ------------------
>
>                 Key: SRAMP-14
>                 URL: http://tools.oasis-open.org/issues/browse/SRAMP-14
>             Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
>          Issue Type: Improvement
>          Components: Foundation
>    Affects Versions: 1.0
>         Environment: N/A
>            Reporter: Vincent Brunssen
>            Assignee: Kurt Stam 
>             Fix For: 1.0
>
>
> 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?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira