HistoryViewLinks to this page 2013 June 17 | 11:27 am

OSLC RM V2.0 defines a number of link predicates (see the specification for details).

This page serves as a discussion point to help define the meaning of the links we need around RM resources. These terms will later be defined in some vocabulary description.

We refer to Link Guidance for OSLC V3.0 Core Links.

OSLC-defined relationships that involve RM resources


A requirement can be implemented by any resource which causes that requirement to be satisfied in some operational context. In 2.0 implementations a requirement is implemented by a change request.

Concern: this has not been raised by our community, but there have been some discussions that a change request does not implement a requirement; rather a change request asks that a requirement be implemented (an implementation request).

oslc_rm:implementedBy and oslc_cm:implementsRequirement.


A resource which contributes to the satisfaction of a requirement.


A resource which describes how evidence supporting the assertion that a requirement has been implemented can be created (a test execution record is an example of such evidence).



Eg a defect in some code affects a requirement because the requirement is not correctly or completely implemented in an executable.


Governes the workflow of the tracked resource. The changes made to a requirement may be guarded by a workflow which is dictated by the tracking resource.


A requirement is broken down into other requirements. The meaning of this decomposition is unspecified.


A requirement imposes some constraints on the object resource. The meaning of the constraint is not specified.

OSLC Core 3.0 Vocabulary

In OSLC 2.0, all of these associations are present in the RM2.0 specification; some of them are also present in other domain specifications since the associations are realized by “two” link predicates.

As part of RM3.0 we need to provide a corresponding expression which is compatible with the 3.0 Link Guidance, and perhaps, some guidance on how providers and consumers should transition from one to the other.

Name Occurs Read-only Value-type Representation Range Description
specifies * False Resource Reference any Makes more precise.
implements * False Resource Reference any A realization of (or causes the realization of?)