[OASIS Issue Tracker] (OSLCCORE-70) Define behaviour for two create events for the same tracked resource

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

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

James Amsden updated OSLCCORE-70:
---------------------------------

    Proposal: 
The spec should define if it is valid, and if so, define the recommended behaviour of a link index provider that consumes those events.

This is already covered in the spec with this clause: 

The TRS Provider SHOULD NOT report unnecessary Change Events although it might happen, for example, if changes occur while the Base is being computed. A TRS Consumer SHOULD ignore a creation event for a Tracked Resource that is already a member of the Tracked Resource Set, and SHOULD ignore a deletion or modification event for a Tracked Resource that is not a member of the Tracked Resource Set.

  was:The spec should define if it is valid, and if so, define the recommended behaviour of a link index provider that consumes those events.


> Define behaviour for two create events for the same tracked resource
> --------------------------------------------------------------------
>
>                 Key: OSLCCORE-70
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-70
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>            Reporter: David Honey
>            Assignee: James Amsden
>
> The current TRS spec does not define whether it is valid for a TRS data provider to have two or more TRS creation events for the same tracked resource without an intervening deletion event, and if so, what the recommended behaviour is for a link index provider.



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