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:all-tabpanel ]

Nick Crossley updated OSLCCORE-71:
----------------------------------

    Proposal: 
1) Update the specification to describe the use case as non-normative text. Perhaps as a new section. The use case is that a TRS provider and a TRS consumer might wish to cooperatively support efficient filtering of tracked resources. We should include an example.

2) Allow some subset of data about the tracked resource to be included in the change event. Allow a trs:Creation or trs:Modifcation resource to use a trs:changedResource (new predicate) to reference some properties. For example:
<urn-3:a.example.com:2014-04-28T17:39:32.000Z:102>
  a trs:Modification ;
  trs:changed <https://a.example.com/config/a1> ;
  trs:order "102"^^xsd:integer ;
  trs:changedResource [
      a rm:Requirement
  ]

3) Include trs:changedResource in vocabulary for trs:Creation and trs:Modification

  was:
1) Update the specification to describe the use case as non-normative text. Perhaps as a new section. The use case is that a TRS provider and a TRS consumer might wish to cooperatively support efficient filtering of tracked resources. We should include an example.

2) Allow some subset of data about the tracked resource to be included in the change event. Allow a trs:Creation or trs:Modifcation resource to use a trs:changedResource (new predicate) to reference some properties. For example:
<urn-3:a.example.com:2014-04-28T17:39:32.000Z:102>
  a trs:Modification;
  trs:changed <https://a.example.com/config/a1>;
  trs:order "102"^^xsd:integer;
  trs:changedResource [
      a rm:Requirement
  ]

3) Include trs:changedResource in vocabulary for trs:Creation and trs:Modification


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