The OSLC Specifications collectively define a core set of services and domain vocabularies for lifecycle management including requirement, change and quality management. The Architecture Management Specification provides a means of defining the things whose lifecycles are being managed, and for linking those resources to the requirements they meet, the change requests that affect them, and the test cases that verify and validate those changes. The specification now enters the 60-day public review that precedes the call for consent as an OASIS Standard. General information about this public review can be found in
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/am-v3.0-ps01-public-review-metadata.html.
OASIS members and other interested parties,
OASIS and the OSLC Open Project [1] are pleased to announce that
OSLC Architecture Management Version 3.0 is now available for public review and comment.
The OSLC Specifications collectively define a core set of services and domain vocabularies for lifecycle management including requirement, change and quality management.
OSLC Architecture Management defines a RESTful web services interface for the management of architectural resources and relationships between those and related resources such as product change requests, activities, tasks, requirements or test cases. To support these scenarios, the specification defines a set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, as well as HTTP response codes, content type handling and resource formats.
The specification is part of a broader set of OSLC specifications that are part of the OSLC-OP project. In particular, OSLC-Core (
https://docs.oasis-open-projects.org/oslc-op/core/v3.0/oslc-core.html) provides the core services upon which the Architecture Management specification is built.
The OP has received 3 Statements of Use from IBM, KTH Royal Institute of Technology, and SodiusWillert [3].
The candidate specification and related files are available here:
OSLC Architecture Management Version 3.0Project Specification 0130 September 2021
- OSLC Architecture Management Version 3.0. Part 1: Specification
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-spec.html (Authoritative)
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-spec.pdf- OSLC Architecture Management Version 3.0. Part 2: Vocabulary
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-vocab.html (Authoritative)
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-vocab.pdf- OSLC Architecture Management Version 3.0. Part 3: Constraints
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-shapes.html (Authoritative)
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-shapes.pdf- OSLC Architecture Management Vocabulary definitions file:
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-vocab.ttlOSLC Architecture Management Resource Shape Constraints definitions file:
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-shapes.ttlFor your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/am-v3.0-ps01.zipÂ
Public Review PeriodThe 60-day public review starts 26 April 2022 at 00:00 UTC and ends 24 June 2022 at 23:59 UTC.
This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
Comments may be submitted to the OP by any person via the project mailing list at
oslc-op@lists.oasis-open-projects.org. To subscribe, send an empty email to
oslc-op+subscribe@lists.oasis-open-projects.org and reply to the confirmation email.
Please append the hashtag #publicreview to the end of the subject line of your message.
All emails to the OP are publicly archived and can be viewed at:
https://lists.oasis-open-projects.org/g/oslc-op/topics.
All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the OP members. In connection with this public review of âOSLC Architecture Management Version 3.0,â we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the applicable open source license. All members of the OP should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification.
OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this OP's work.
Additional information[1] OASIS Open Services for Lifecycle Collaboration (OSLC) OP
https://open-services.net/about/[2] Approval ballot:
https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/234[3] Statements of Use:
- IBM
https://lists.oasis-open-projects.org/g/oslc-op/message/768Â
- KTH
https://lists.oasis-open-projects.org/g/oslc-op/message/756Â
- SodiusWillert
https://lists.oasis-open-projects.org/g/oslc-op/message/771[4]
http://www.oasis-open.org/policies-guidelines/ipr[5]
https://github.com/oslc-op/oasis-open-project/blob/master/LICENSE.md
--
| ChetÂEnsignChief Technical Community Steward OASIS Open | Â | Â | Â | |