This specification defines a vocabulary and resource shapes for the OSLC Requirements Management domain.
This specification defines a vocabulary and resource shapes for the OSLC Requirements Management resources. The intent is to define resources needed to support common integration scenarios and not to provide a comprehensive definition of a Requirement. The resource formats may not match exactly the native models supported by requirement management service providers, but are intended to be compatible with them. The approach to supporting these scenarios is to delegate operations, as driven by service provider contributed user interfaces, as much as possible and not require a service provider to expose its complete data model and application logic.
Terminology is based on OSLC Core Overview [[!OSLCCore3]], W3C Linked Data Platform [[!LDP]], W3C's Architecture of the World Wide Web [[WEBARCH]], Hyper-text Transfer Protocol [[!HTTP11]].
In addition to the namespace URIs and namespace prefixes oslc
, rdf
, dcterms
and foaf
defined in the OSLC Core specification, OSLC RM defines the namespace URI of http://open-services.net/ns/rm#
with a namespace prefix of oslc_rm
This specification defines the **root** superclass, and a number of specific, commonly occurring subclasses, properties and values. Servers may define additional **root** subclasses and provide additional properties as needed.
The meaning of Requirement resource properties are defined in the tables below, together with their multiplicity constraints. Requirement resource properties are not limited to the ones defined in this specification. Service providers may provide additional properties. It is strongly recommended that any additional properties be defined in XML namespaces distinct from those defined by OSLC in these specifications. Requirement creation through a Creation Factory resource in the Service Description is REQUIRED by this specification.
Any resource asserted to be of rdf:type
http://open-services.net/ns/rm#Requirement
MUST conform to the constraints and meaning of properties defined below. Notice that partial representations of a requirement resource are admitted by this specification (for example, in query results, or where oslc.properties
has been used), and such partial representations will in general not conform to these constraints.
The meaning of RequirementCollection resource properties are defined in the tables below, together with their multiplicity constraints. RequirementCollection resource properties are not limited to the ones defined in this specification, service providers may provide additional properties. It is strongly recommended that any additional properties be defined in XML namespaces distinct from those defined by OSLC in these specifications. RequirementCollection creation through a Creation Factory resource in the Service Description is OPTIONAL in this specification.
Any resource asserted to be of rdf:type
http://open-services.net/ns/rm#RequirementCollection
MUST conform to the constraints and meaning of properties defined below. Notice that partial representations of a requirement collection resource are admitted by this specification (for example, in query results, or where oslc.properties
has been used), and such partial representations will in general not conform to these constraints.
Revision | Date | Editor | Changes Made |
01 | 07/06/2016 | Jim Amsden | Initial CSPRD01 |