This page is to record and describe some of the common patterns of integrating products using OSLC.
This is a work-in-progress.
- HTTP client
- HTTP server
- Finds and uses resource representations created by others. (May also create representations to be passed to providers or repositories to create resources, but never actually "creates" the resource itself).
- Creates resources, and is responsible for their lifecycle.
- HTTP or RDF resources
- Serialization of a resource, such as used as HTTP message bodies
A server that accepts representations and creates & stores resources from them, making representations of those resources available to any client with appropriate authorization; and/or that stores copies of resources from providers.
There are a number of different sequences that can occur in an OSLC Automation integration:
Primary: Consumer requests Plan and creates remote Request
- Consumer creates remote Plan and Requests for it
Worker scenarios - http://open-services.net/wiki/automation/Automation-Worker-Scenarios/ (This is orthogonal to the previous two sequences)
Sequence: Consumer requests Plan and creates remote Request
Within this sequence there are a number of different ways that the integrated systems can be arranged:
- Consumer acting as client to single provider server.
Primary: Consumer acting as client to multiple provider servers.
- Consumer and multiple providers all acting as clients to a single shared repository server.
- Consumer acting as client watches for Results on a provider or repository, and uses the completion of a previous Result as a trigger for its own automation (which it may also expose via OSLC, simultaneously acting as a Provider).