Requesting Delegated UI Using the Service Resource
The client applications can navigate to the URIs of the delegated UI for resource selection through discovery of service provider catalogs and service provider resources provided by the OSLC Server.
The OSLC client applications can discover the URIs of the delegated UI for resource selection by sending GET request on a project to the OSLC Server per the following URI:
GET <protocol scheme>://<server host name>:<server port number>/<context URI>/project/<project name>
For example:
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2
The client applications must set the Accept header to application/ld+json or application/rdf+xml as the content type in the GET requests to the OSLC Server. The OSLC clients must also set the OSLC-Core-version header to 3.0 when sending the GET requests. The response for such GET request includes URIs for the delegated UI for resource selection and query capabilities.
The OSLC Server supports the following URI with the supported authentication for the delegated UI corresponding to the requirements:
GET <protocol scheme>://<server host name>:<server port number>/<context URI>/project/<project name>/requirements/dialog/selection
For example:
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/requirements/dialog/selection
The OSLC Server supports the following URI with the supported authentication for the delegated UI corresponding to the requirement documents:
GET <protocol scheme>://<server host name>:<server port number>/<context URI>/project/<project name>/contents/dialog/selection
For example:
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/contents/dialog/selection