LDP Use Cases and Requirements

["Jim Amsden" <jamsden@us.ibm.com>]

Nick,
I'm envisioning something like this
for TRS where the use cases and requirements set out what a server needs
do do in order to meet with clients needs. That is, the use cases and requirement
specify the demand-side view of TRS from the client's perspective while
the TRS specification describes the supply-side view of what the servers
must, should, or may implement in order to satisfy the demand side needs.

https://www.w3.org/TR/ldp-ucr/

I could imagine the following use cases:

1. TRS consumer discovers TRS providers

2. TRS consumer accesses TRS provider

3. TRS consumer specifies access control
of resources it exposes of a TRS provider

4. TRS consumer processes base resources

5. TRS consumer processes change logs

6. TRS consumer detects potentially
missing changes



Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575