The OSLC Server provides the following Service Providers:

The OSLC Server is pre-configured to work with the fields and types defined in the Requirements and Validation solution, which can be customized to work with any custom solution.

You can use the OSLC Server to map the Requirements and Requirement collections in the Requirements domain with the Document and Node types, respectively. For more information on mapping the requirements domain, see Mapping Requirements Domain Using Windchill RV&S OSLC Server.

The OSLC Server enables OSLC client applications such as to create a trace using a field (Incoming OSLC Link field) on a requirement type and also view the same. The server also provides compact resources for accessing small previews of Document and Node types. For more information on resource previews, see Working with Resource Previews.

The OSLC Server supports application/ld+json and application/rdf+xml as the content type for all request responses (except for resource previews). If no Accept header is specified in the requests, the OSLC Server provides an error response as per the application/ld+json content type. The OSLC Server also supports rdf+xml and ld+json output as per OSLC Core Version 3.0 specification. If the OSCL client applications pass the OSLC-Core-version header with value as 3.0, the server provides response in the rdf+xml or ld+json output as per OSLC Core Version 3.0 specification. PTC recommends using the OSLC-Core-version header with value as 3.0 in the OSLC client requests to get response in the rdf+xml or ld+json output.

The OSLC Server also supports access to versioned item of Document and Node types that have a unique identifier in the format Live Item ID-Major Version ID.Minor Version ID. For example, 7201-1.0. For more information on URIs for version support, see Accessing Windchill RV&S Data Using the Windchill RV&S OSLC Server.