[OASIS Issue Tracker] (OSLCCORE-71) Provide data in a TRS event for filtering

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

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

Nick Crossley commented on OSLCCORE-71:
---------------------------------------

This appears to introduce new possible errors or edge cases. For example, what if one of the properties being quoted changes (or the TRS change event is just wrong), and a GET of the resource indicates different values for that property? Or if the resource does not even have that property? 

> Provide data in a TRS event for filtering
> -----------------------------------------
>
>                 Key: OSLCCORE-71
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-71
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>          Components: TRS
>            Reporter: David Honey
>            Assignee: James Amsden
>            Priority: Major
>              Labels: TRS
>
> Currently, a TRS event only references the tracked resource's URI. If a consumer of the TRS data is only interested in a subset of the exposed tracked resources, it has to consume the events and perform a GET on each referenced tracked resource in order to determine whether it is of interest.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)