HistoryViewLinks to this page Revision from: 2013 February 27 | 10:59 am
This is the revision from 2013 February 27 at 10:59 amView the current live version of the article.

Open Services for Lifecycle Collaboration
Tracked Resource Set Specification Version 2.0

Status: WORKING DRAFT 2.0 Specification - February 27, 2013

This Version

Latest Version


  • N/A



Table of Contents



Creative Commons Attribution License
This work is licensed under a Creative Commons Attribution License.

Notation and Conventions

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC2119. Domain name examples use RFC2606.


The Tracked Resource Set protocol allows a server to expose a set of resources in a way that allows clients to discover the exact set of resources in the set, to track all additions to and removals from the set, and to track state changes to all resources in the set. The protocol does not assume that clients will dereference the resources. The protocol is suitable for dealing with large sets containing a large number of resources, as well as highly active resource sets that undergo continual change. The protocol is HTTP-based and follows RESTful principles.

Appendix A: Samples

(this section is informative)

See TrackedResourceSet 2.0 Samples

Appendix B: Resource Shapes

(this section is informative)

See TrackedResourceSet 2.0 Shapes

Appendix C: Notices and References


Reporting Issues on the Specification

The working group participants who author and maintain this working draft specification, monitor a distribution list where issues or questions can be raised, see Core Mailing List

Also the issues found with this specification and their resolution can be found at @@@CoreV2Issues.

License and Intellectual Property

We make this specification available under the terms and conditions set forth in the site Terms of Use, IP Policy, and the Workgroup Participation Agreement for this Workgroup.


Appendix D: Changes

  • TBD