OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

s-ramp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

Brett Meyer commented on SRAMP-14:
----------------------------------

Additionally, Artificer includes an "auditing" concept: http://docs.jboss.org/artificer/0.8.0-SNAPSHOT/html_single/#_auditing

> Supporting History
> ------------------
>
>                 Key: SRAMP-14
>                 URL: https://issues.oasis-open.org/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.1
>
>
> 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 was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]