The namespace URI for this vocabulary is:
http://open-services.net/ns/rm#
This page lists the RDFS classes and RDF properties that make up the OSLC vocabulary. Following W3C best practices, this information is available in HTML format (this page) and in RDFS format.
More details on how this page is generated and other related material can be found in the OSLC URI Naming Guidelines.
Description:
This RDFS Schema defines the Open Services for Lifecycle Collaboration Requirements Management and Definition vocabulary, also known as OSLC RM. This vocabulary is part of the OSLC RM 2.0 specification, which is part of the OSLC group of specifications.
See Also:
RDFS Classes in this namespace
Requirement, RequirementCollection
RDF Properties in this namespace
affectedBy, elaboratedBy, implementedBy, specifiedBy, trackedBy, uses, validatedBy
Expresses an affects relationship between entities. For example, a defect may be said to affect a requirement.
An entity which in some way affects the object entity.
See Also:
Expresses an elaboration relationship between entities. For example, a model element can elaborate a requirement.
An entity which elaborates.
See Also:
Expresses an implementation relationship between entities.
An entity which is a necessary or desirable aspect of an implementation.
See Also:
Statement of need.
See Also:
Collection of requirements. A collection uses zero or more requirements.
See Also:
Expresses a specification relationship between entities. For example, a model element can specifiy a requirement.
An entity which further clarifies or specifies.
See Also:
Expresses a tracking relationship between entities. For example, a change request may be said to track a requirement, in that it governs the changes to a requirement according to some process machinery.
An entity which in some way tracks or governs the evolution of an entity.
See Also:
Expresses a use relationship between entities. For example, a requirement collection may use a requirement.
An entity which is used by another resource.
See Also:
Expresses a validation relationship between entities. For example, a test plan may be said to validated a requirement collection.
An entity which in some way validates.
See Also: