[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=65166#comment-65166 ] 

James Amsden commented on OSLCCORE-71:
--------------------------------------

Nick's approach organizes collections of resources whose contents one might want to obtain in a single GET request in an LDPC. This could result in some coupling between the use of tracked resources and the persistence structure of the server. 

It is important to distinguish a server's persistence architecture, or how it organizes information in its repository for its purposes, and the different purposes a client might have in accessing that data. Flexible definitions of TRS resources provided by a server will allow clients to get the data they need for their purposes and keep it efficiently updated. So the organization of the data from the consumer's perspective may often be different than that of the provider.

Servers might provide some view-like mechanism to define virtual LDPCs that provide flexible, extensible, varying or perhaps even dynamic organization of their data.

Alternatively, we could consider separating the organization of data by the TRS provider from the organization from the perspective of the user.

1. When a TRS is defined, members of the set can be organized into named partitions (groups, sets, collections, whatever we want to call it). 

2. These sets are defined in the TRS base and are also used to partition events in the change log. 

3. TRS polling works as usual. Without the partitioning, it is transparent to TRS clients that don't use the facility

4. TRS clients MAY do a GET on the partition to obtain a resource that has inlined representations of the resources in that partition. 

5. The usual OSLC selected properties query strings can be used with the partition query parameter to obtain a subset of the resource properties

This would allow different TRS feeds to be created for different purposes on the same server data sources.


> 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
>            Reporter: David Honey
>            Assignee: James Amsden
>              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
(v6.2.2#6258)