This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
TWiki> Main Web>RmHome>RmSpecificationV2>RmSpecificationV2Errata (21 Sep 2012, IanGreen)
Working Document

Errata for RM V2.0 Specification, 3rd May 2011.

Omissions

In order to support elaboration and specification scenarios between RM providers (described by RmElaborationBusinessRequirements), the RM workgroup and OSLC community (RmMeetings20110919) decided that the following vocabulary terms should be added to the published RM 2.0 specification:

  • oslc_rm:elaborates
  • oslc_rm:specifies

Following further conversation with OSLC stakeholders, the following additional vocabulary terms have been included:

  • oslc_rm:satisfies
  • oslc_rm:decomposes
  • oslc_rm:constrains

And that these OSLC defined properties are meaningful on both Requirement resources and on RequirementCollection resources.

Requirements:
  • Name: Requirement
  • Type URI http://open-services.net/ns/rm#Requirement

Prefixed Name Occurs Read-only Value-type Represen-tation Range Description
Relationship properties: This grouping of properties are used to identify relationships between resources managed by other OSLC Service Providers
oslc_rm:elaboratedBy zero-or-many False Resource Reference any The subject is elaborated by the object. For example, a user requirement is elaborated by use case.
oslc_rm:elaborates zero-or-many False Resource Reference any The object is elaborated by the subject.
oslc_rm:specifiedBy zero-or-many False Resource Reference any The subject is specified by the object. For example, a requirement is elaborated by a model element .
oslc_rm:specifies zero-or-many False Resource Reference any The object is specified by the subject.
oslc_rm:satisfiedBy zero-or-many False Resource Reference any The subject is satisfied by the object. For example, a user requirement is satisfied by a system requirement.
oslc_rm:satisfies zero-or-many False Resource Reference any The object is satisfied by the subject.
oslc_rm:decomposedBy zero-or-many False Resource Reference any The subject is decomposed by the object. For example, a system requirement is decomposed into a collection of system requirements.
oslc_rm:decomposes zero-or-many False Resource Reference any The object is decomposed by the subject.
oslc_rm:constrainedBy zero-or-many False Resource Reference any The subject is constrained by the object. For example, a functional requirement is constrained by a safety requirement.
oslc_rm:constrains zero-or-many False Resource Reference any The object is constrained by the subject.

RequirementCollections
  • Name: RequirementCollection
  • Type URI http://open-services.net/ns/rm#RequirementCollection

Prefixed Name Occurs Read-only Value-type Represen-tation Range Description
Relationship properties: This grouping of properties are used to identify relationships between resources managed by other OSLC Service Providers
oslc_rm:elaboratedBy zero-or-many False Resource Reference any The subject is elaborated by the object. For example, a collection of user requirements elaborates a business need, or a model elaborates a collection of system requirements.
oslc_rm:elaborates zero-or-many False Resource Reference any The object is elaborated by the subject.
oslc_rm:specifiedBy zero-or-many False Resource Reference any The subject is specified by the object. For example, a model element might make a requirement collection more precise.
oslc_rm:specifies zero-or-many False Resource Reference any The object is specified by the subject.
oslc_rm:satisfiedBy zero-or-many False Resource Reference any The subject is satisfied by the object. For example, a collection of user requirements is satisfied by a requirement collection of system requirements.
oslc_rm:satisfies zero-or-many False Resource Reference any The object is satisfied by the subject.
oslc_rm:decomposedBy zero-or-many False Resource Reference any The subject is decomposed by the object. For example, a collection of business requirements is decomposed by a collection of user requirements.
oslc_rm:decomposes zero-or-many False Resource Reference any The object is decomposed by the subject.
oslc_rm:constrainedBy zero-or-many False Resource Reference any The subject is constrained by the object. For example, a requirement collection is constrained by a requirement collection.
oslc_rm:constrains zero-or-many False Resource Reference any The object is constrained by the subject.

These omissions have been rectified in OSLC RM V2.0. The OSLC RM RDFS Volcabulary has also been updated.

A delta showing the changes may be found here.

The above errata have been resolved in RmSpecificationV2 (21 September 2012).

Edit | Attach | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r13 - 21 Sep 2012 - 10:45:30 - IanGreen
Main.RmSpecificationV2Errata moved from Main.RmSpecificationV2r20110503Errata on 31 Oct 2011 - 08:08 by IanGreen - put it back
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback