IBM Statement of Use for OASIS Architecture Management Specification, Version 2.1, Committee Specification 01

["Jim Amsden" <jamsden@us.ibm.com>]

As IBM's Primary
Representative to OASIS, I, Jason Keirstead (Jason.Keirstead@ca.ibm.com),
approve the following statement of use:

IBM has successfully
implemented the OASIS Architecture Management Specification, Version 2.1,
Committee Specification 01 (http://docs.oasis-open.org/oslc-domains/oslc-am/v2.1/cs01/part1-architecture-management-spec/oslc-am-v2.1-cs01-part1-architecture-management-spec.html)
dated 09 October 2018, in accordance with the conformance clauses defined
in Section 5 "Conformance" of that specification. This use of
the specification is implemented in Rational Design Manager (RDM) version
5.0 and beyond, and includes interoperability with other similar independent
implementations, as well as integration with tools supporting other OSLC
domain specifications including Rational Team Concert (Change Management),
and Rational DOORS Next Generation (Requirements Management). 

Some background
on the versioning: OSLC Core 3.0 has additional capabilities and vocabulary
over what was in OSLC Core 2.0, referenced in OSLC Architecture Management
2.0 (developed on open-services.net), and implemented in RDM. RDM does
not implement these additional capabilities. But since 1) OSLC Core 3.0
is intended to be backward compatible with 2.0, 2) all the new features
are optional and 3) OASIS Architecture Management 2.1 is a document maintenance
release, covering migration from open-services.net to OASIS document formatting
and layout conventions and does not introduce any substantive changes,
RDM can state conformance and is a valid statement of use for these specifications.

Jim Amsden, Senior
Technical Staff Member
OSLC and Linked Lifecycle
Data
919-525-6575