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

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

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


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


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

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

Nick proposed an interesting potential solution on the TC call today, one that may not require any changes to the TRS specification.

A TRS provider could include elements in its base or change log that are LDPCs.
LDP already supports using the Prefer header to allow clients to express they don't want to see the members, only the properties on the container itself.
Currently a GET on the LDPC without the Prefer header would get the members. Like a TRS, they are only links.
A TRS consumer could Include a new Prefer header with GET on the LDPCs to indicate they want to see data about the members inlined in the resource.
We would need to define a Prefer value that asks for the members inline.
A TRS provider tool could publish TRS on LDPCs that do the partitioning.

A TRS provider would need to support the specification of the LDPCs, possibly often creationFactory URIs, that would be members of a TRS. 

> 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)


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