|
Re: [OASIS Issue Tracker] (TCADMIN-3996) Publish OSLC Change Management v3.0 as an OASIS Standard
Hello everyone,
I just prepared the CM v3.0 OS package. Please find it under https://issues.oasis-open.org/browse/TCADMIN-3996. Chet, Paul, please review if it ready to proceed to publication.
Jim, the changes to the spec are under https://github.com/oslc-op/oslc-specs/pull/515. Please do a sanity check.
Nick, I had to adjust ReSpec templates and a bit of logic. Please review https://github.com/oasis-tcs/tab-respec/pull/51
I wish everyone a nice weekend!
–Andrew.
From:
OASIS Issues Tracker <workgroup_mailer@...>
Paul Knight commented on TCADMIN-3996: --------------------------------------
For OASIS Standard, there is no numbering, just "OASIS Standard".
Any subsequent changes to an OASIS Standard may only be handled as Errata [1], or as a later Version number.
A later Version number could be Version 3.1 or Version 4.0, or possibly some other number. OASIS does not define any semantic meaning to the decimal form.
[1] Errata process: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#errata
-- This message was sent by Atlassian Jira (v8.3.3#803004)
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: OSLC Change Management v3.0 approved as an OASIS Standard
François-Régis Jaunatre <frjaunatre@...>
I believe we could adjust the wording so that OSLC services may require authentication. But that if authentication is implemented, it must be one of OpenIDConnect, OAuth1.0a (for core 2.0 backward compat), or HTTP Basic auth. And should be over SSL. That’s
directly in Core I guess.
This is more work on the client, and the discovery for the authentication actively used by the server from a client perspective should probably be determined/ adjusted at some point.
But I believe that would address both comments.
François-Régis Jaunatre
Architect & OSLC Lab Team Lead
34, Boulevard du Maréchal Alphonse Juin, 44100 Nantes, France
Ph: +33 (0) 2 28 23 55 23 | sodiuswillert.com
De : oslc-op@... <oslc-op@...> de la part de Jim Amsden via lists.oasis-open-projects.org <jamsden=us.ibm.com@...>
Envoyé : Thursday, May 27, 2021 7:33:30 PM À : oslc-op@... <oslc-op@...> Cc : chet.ensign@... <chet.ensign@...> Objet : Re: [oslc-op] OSLC Change Management v3.0 approved as an OASIS Standard Authentication needs vary from organization to organization and domain to domain. Some OSLC resources may be public and require no authentication or authroization to access. Other may be only available inside a firewall of constrained users and don't need
additional authentication or authorization. Still other organizations may prefer authentication protocols other than those recommended by OSLC. For these reasons, SHOULD seemed like the best option.
-----oslc-op@... wrote: ----- To: "oslc-op@..." <oslc-op@...>
From: "Andrii Berezovskyi" Sent by: oslc-op@... Date: 05/27/2021 01:21PM Cc: "chet.ensign@..." <chet.ensign@...> Subject: [EXTERNAL] Re: [oslc-op] OSLC Change Management v3.0 approved as an OASIS Standard Thank you, Chet, and to everyone who contributed to this amazing milestone! The posts are up on the OSLC blog and the forum, please keep spreading the word. One comment we should deal with is https://www.oasis-open.org/committees/vote_details.php?id=3619&voter_id=18338 ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
Thank you, Chet, and to everyone who contributed to this amazing milestone!
The posts are up on the OSLC blog and the forum, please keep spreading the word.
One comment we should deal with is https://www.oasis-open.org/committees/vote_details.php?id=3619&voter_id=18338. Finally, I find a friendly soul who does not like SHOULDs and MAYs 😊
–Andrew
From:
<oslc-op@...> on behalf of Chet Ensign <chet.ensign@...>
OASIS is pleased to announce that the call for consent has closed [1] and, effective 26 May 2021, OSLC Change Management Version 3.0 is an OASIS Standard. Project Administration will now undertake the final tasks of publishing the standard.
Our congratulations to the members of the OSLC Open Project and to the community of implementers, developers and users who have brought the work successfully to this milestone. [2] OSLC Open Projecthttps://github.com/oslc-op/oslc-adminhttps://open-services.net/
--
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: IBM Statements of use: for OSLC Core Version 3.0 Project Specification
Dear Jason,
I would like to thank you on behalf of the board and all OSLC project contributors for providing these statements of use! These statements as well as the continued participation of the IBM on the board and in the project work are instrumental to the success of the OSLC project.
Best regards, Andrew Berezovskyi OSLC OP PGB co-chair
From:
<oslc-op@...> on behalf of Jason Keirstead <Jason.Keirstead@...>
Dear OSLC PGB and and members;
IBM has successfully implemented the OASIS OSLC Core Version 3.0 Project Specification 01 (https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps02/oslc-core.html) dated 23 April 2021), in accordance with the conformance clauses defined in Section "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations in the jazz.net applications, specifically the Engineering Lifecycle Management suite of products, as well as integration with other 3rd party tools supporting this and other OSLC domain specifications. Additionally, IBM jazz.net products include test suites covering the OSLC Core specification v2.0 that still conforms to the v3.0 revision 02 specification and which can be used for ensuring backwards compatibility of the OSLC Core 2.0 tools according to the relevant conformance clauses.
IBM has successfully implemented the OASIS OSLC Query Version 3.0 Project Specification Revision 01 (https://docs.oasis-open-projects.org/oslc-op/query/v3.0/oslc-query.html) dated 01 October 2020), in accordance with the conformance clauses defined in Section "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations in the jazz.net applications, specifically the Engineering Lifecycle Management suite of products, as well as integration with other 3rd party tools supporting this and other OSLC domain specifications. Additionally, IBM jazz.net products include test suites covering the OSLC Query specification v2.0 that still conforms to the v3.0 revision 01 specification and which can be
used for ensuring backwards compatibility of the OSLC Query 2.0 tools according to the relevant conformance clauses. - www.opencybersecurityalliance.org
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
IBM Statements of use: for OSLC Core Version 3.0 Project Specification
Jason Keirstead <Jason.Keirstead@...>
Dear OSLC PGB and and members;
As primary representative for IBM to OASIS, I approve the following Statement of Use: IBM Statements of use: for OSLC Core Version 3.0 Project Specification IBM has successfully implemented the OASIS OSLC Core Version 3.0 Project Specification 01 (https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps02/oslc-core.html) dated 23 April 2021), in accordance with the conformance clauses defined in Section "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations in the jazz.net applications, specifically the Engineering Lifecycle Management suite of products, as well as integration with other 3rd party tools supporting this and other OSLC domain specifications.
Additionally, IBM jazz.net products include test suites covering the OSLC Core specification v2.0 that still conforms to the v3.0 revision 02 specification and which can be used for ensuring backwards compatibility of the OSLC Core 2.0 tools according to the relevant conformance clauses.
IBM Statements of use: for OSLC Quuery Version 3.0 Project Specification IBM has successfully implemented the OASIS OSLC Query Version 3.0 Project Specification Revision 01 (https://docs.oasis-open-projects.org/oslc-op/query/v3.0/oslc-query.html) dated 01 October 2020), in accordance with the conformance clauses defined in Section "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations in the jazz.net applications, specifically the Engineering Lifecycle Management suite of products, as well as integration with other 3rd party tools supporting this and other OSLC domain specifications.
Additionally, IBM jazz.net products include test suites covering the OSLC Query specification v2.0 that still conforms to the v3.0 revision 01 specification and which can be used for ensuring backwards compatibility of the OSLC Query 2.0 tools according to the relevant conformance clauses. -
Jason Keirstead Distinguished Engineer, CTO - IBM Security Threat Management www.ibm.com/security Co-Chair - Open Cybersecurity Alliance, Project Governing Board www.opencybersecurityalliance.org |
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: OSLC Change Management v3.0 approved as an OASIS Standard
Authentication needs vary from organization to organization and domain to domain. Some OSLC resources may be public and require no authentication or authroization to access. Other may be only available inside a firewall of constrained users and don't need additional authentication or authorization. Still other organizations may prefer authentication protocols other than those recommended by OSLC. For these reasons, SHOULD seemed like the best option. -----oslc-op@... wrote: ----- To: "oslc-op@..." <oslc-op@...> From: "Andrii Berezovskyi" Sent by: oslc-op@... Date: 05/27/2021 01:21PM Cc: "chet.ensign@..." <chet.ensign@...> Subject: [EXTERNAL] Re: [oslc-op] OSLC Change Management v3.0 approved as an OASIS Standard Thank you, Chet, and to everyone who contributed to this amazing milestone! The posts are up on the OSLC blog and the forum, please keep spreading the word. One comment we should deal with is https://www.oasis-open.org/committees/vote_details.php?id=3619&voter_id=18338 ZjQcmQRYFpfptBannerStart This Message Is From an External Sender
This message came from outside your organization.
Thank you, Chet, and to everyone who contributed to this amazing milestone!
The posts are up on the OSLC blog and the forum, please keep spreading the word.
One comment we should deal with is https://www.oasis-open.org/committees/vote_details.php?id=3619&voter_id=18338. Finally, I find a friendly soul who does not like SHOULDs and MAYs 😊
–Andrew
From:
<oslc-op@...> on behalf of Chet Ensign <chet.ensign@...>
OASIS is pleased to announce that the call for consent has closed [1] and, effective 26 May 2021, OSLC Change Management Version 3.0 is an OASIS Standard. Project Administration will now undertake the final tasks of publishing the standard.
Our congratulations to the members of the OSLC Open Project and to the community of implementers, developers and users who have brought the work successfully to this milestone. [2] OSLC Open Projecthttps://github.com/oslc-op/oslc-adminhttps://open-services.net/
--
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: OSLC Change Management v3.0 approved as an OASIS Standard
Thank you, Chet, and to everyone who contributed to this amazing milestone!
The posts are up on the OSLC blog and the forum, please keep spreading the word.
One comment we should deal with is https://www.oasis-open.org/committees/vote_details.php?id=3619&voter_id=18338. Finally, I find a friendly soul who does not like SHOULDs and MAYs 😊
–Andrew
From:
<oslc-op@...> on behalf of Chet Ensign <chet.ensign@...>
OASIS is pleased to announce that the call for consent has closed [1] and, effective 26 May 2021, OSLC Change Management Version 3.0 is an OASIS Standard. Project Administration will now undertake the final tasks of publishing the standard.
Our congratulations to the members of the OSLC Open Project and to the community of implementers, developers and users who have brought the work successfully to this milestone. [2] OSLC Open Projecthttps://github.com/oslc-op/oslc-adminhttps://open-services.net/
--
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: Event: oslc-op Weekly Contributors Meeting - 05/27/2021
#cal-notice
Minutes: https://github.com/oslc-op/oslc-admin/blob/master/minutes/2021/2021-05-27.md
–Andrew
From:
<oslc-op@...> on behalf of "oslc-op@... Calendar" <noreply@...>
oslc-op Weekly Contributors Meeting When: Where: Organizer: Jim Amsden jamsden@... Description:
Meeting ID: 2979764690#
The meeting minutes are edited in
https://hackmd.io/@driib/oslc-op-minutes/edit
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
OSLC Change Management v3.0 approved as an OASIS Standard
Chet Ensign
OASIS is pleased to announce that the call for consent has closed [1] and, effective 26 May 2021, OSLC Change Management Version 3.0 is an OASIS Standard. Project Administration will now undertake the final tasks of publishing the standard. Change Management Version 3.0 was produced by the OASIS OSLC Open Project [2]. This is the first OASIS Standard delivered by the Open Projects program. The ballot was held under the OASIS call for consent procedure [3]. In the ballot, the Candidate OASIS Standard received 7 affirmative consents and no objections. Our congratulations to the members of the OSLC Open Project and to the community of implementers, developers and users who have brought the work successfully to this milestone. Additional information
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: [oslc-op-pgb] Call for Consent for OSLC Change Management v3.0 as OASIS Standard
Chet Ensign
yes. I will be announcing the good news today. Congratulations! /chet On Thu, May 27, 2021 at 10:57 AM Andrii Berezovskyi <andriib@...> wrote:
--
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: [oslc-op-pgb] Call for Consent for OSLC Change Management v3.0 as OASIS Standard
Hello Chet,
toggle quoted message
Show quoted text
Can we consider the call for consent to have concluded last night successfully?
–Andrew.
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Event: oslc-op Weekly Contributors Meeting - 05/27/2021
#cal-notice
oslc-op@lists.oasis-open-projects.org Calendar <noreply@...>
oslc-op Weekly Contributors Meeting When: Where: Organizer: Jim Amsden jamsden@... Description: One tap audio Dial In: +15124022718,,,,2979764690# (US) or +498938038719,,,,2979764690# (Germany) Looking for a different dial in number? Please see: https://meet.jit.si/static/dialInInfo.html?room=oslc-op Meeting ID: 2979764690#
The meeting minutes are edited in https://hackmd.io/@driib/oslc-op-minutes/edit
Previous minutes can be found under https://github.com/oslc-op/oslc-admin/tree/master/minutes/2019 OASIS OSLC Open Project group home: https://lists.oasis-open-projects.org/g/oslc-op oslc-op GitHub Organization: https://github.com/oslc-op Mailing list: oslc-op@... (archives: https://lists.oasis-open-projects.org/g/oslc-op) |
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Ballot to approve OSLC Requirements Management Version 2.1 PS02 with Non-Material Changes as a candidate for OASIS Standard has been set up
Chet Ensign
The OASIS Open Services for Lifecycle Collaboration (OSLC) Open Project Project Governing Board [1] has requested a Special Majority Vote to approve a working draft of OSLC Requirements Management Version 2.1 with non-material changes as Project Specification 02 and submitting this to the OASIS membership in the call for consent as OASIS Standard. This is being done under the rules of section 2.8.2 Public Review of a Committee Specification candidate for OASIS Standard (https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#OSpublicRev) Changes have been made to this Project Specification working draft to address comments received during its 60-day public review. The TC judges these changes to be non-material. The description of the changes can be inspected in Response-to-comments-on-OSLC-Requirements-Management-PS01.pdf (https://www.oasis-open.org/committees/document.php?document_id=68639&wg_abbrev=tca). The ballot can be inspected at https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/143. The ballot is open now and closes 28 May 2021 at 11:59 UTC. Any Eligible Person concerned that the changes are Material is asked to bring their concern to OASIS Project Administration at project-admin@... so that the appropriate actions can be taken. [1] OASIS Open Services for Lifecycle Collaboration (OSLC) OP https://open-services.net/about/
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
A Special Majority Vote to consider approving working draft of OSLC Requirements Management Version 2.1 as PS02 and submitting it in the call for consent has been set up
Chet Ensign
Members of the OSLC Open Project, A Special Majority Vote to consider approving the working draft for OSLC Requirements Management Version 2.1 with non-material changes as PS02 and submitting it in the call for consent has been set up. The ballot is open now. It closes 28 May 2021 at 23:59 UTC. You can view the ballot at: https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/143 This ballot is only open to the members of the Project Governing Board of the OP. I currently show the following members as eligible to vote: Jim Amsden (IBM) Axel Reichwein (Koneksys) Andrew Berezovskyi (KTH Royal Institute of Technology) Please send any questions to the list. /chet
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: Response to the OP Administrator for the public comments received on OSLC RM 2.1 PS 01 submitted as a Candidate for OASIS Standard
Chet Ensign
Paul, the pdf will serve as the comment resolution log. On Thu, May 20, 2021 at 3:18 PM Andrii Berezovskyi <andriib@...> wrote:
--
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: oslc-op Weekly Contributors Meeting - Thu, 05/20/2021
#cal-notice
Minutes: https://github.com/oslc-op/oslc-admin/blob/master/minutes/2021/2021-05-20.md
From: <oslc-op@...> on behalf of Jad El-Khoury <jad@...>
No meeting today? Just joined and I feel lonely.
______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
From: oslc-op@... <oslc-op@...>
On Behalf Of oslc-op@... Calendar
Sent: Thursday, 20 May 2021 16:00 To: oslc-op@... Subject: [oslc-op] oslc-op Weekly Contributors Meeting - Thu, 05/20/2021 #cal-notice
oslc-op Weekly Contributors Meeting When: Where: Organizer: Description:
Meeting ID: 2979764690#
The meeting minutes are edited in
https://hackmd.io/@driib/oslc-op-minutes/edit
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Response to the OP Administrator for the public comments received on OSLC RM 2.1 PS 01 submitted as a Candidate for OASIS Standard
Hello Chet, Hello Paul,
I would like to submit a response to the OP Administrator for the public comments received on OSLC Requirements Management 2.1 PS 01 submitted as a Candidate for OASIS Standard as per https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#OSpublicRev. The response includes itemised list of comments and our response to them.
Also please find attached the PS 02 revision package with the changes applied in accordance with the response. The revision only contains non-material changes. While the revision does not contain any further changes than requested, additional metadata updates were made that are routine in the publication process.
Please submit the following package for the Special Majority Vote. We have indicated the publication date to be 2021-05-28 but can adjust it if you think more time is needed.
Best regards, Andrew on behalf of the OSLC OP PGB and the contributors |
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: oslc-op Weekly Contributors Meeting - Thu, 05/20/2021
#cal-notice
Jad El-Khoury
No meeting today? Just joined and I feel lonely.
______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
From: oslc-op@... <oslc-op@...>
On Behalf Of oslc-op@... Calendar
Sent: Thursday, 20 May 2021 16:00 To: oslc-op@... Subject: [oslc-op] oslc-op Weekly Contributors Meeting - Thu, 05/20/2021 #cal-notice
oslc-op Weekly Contributors Meeting When: Where: Organizer: Description:
Meeting ID: 2979764690#
The meeting minutes are edited in
https://hackmd.io/@driib/oslc-op-minutes/edit
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
oslc-op Weekly Contributors Meeting - Thu, 05/20/2021
#cal-notice
oslc-op@lists.oasis-open-projects.org Calendar <noreply@...>
oslc-op Weekly Contributors Meeting When: Where: Organizer: Description: One tap audio Dial In: +15124022718,,,,2979764690# (US) or +498938038719,,,,2979764690# (Germany) Looking for a different dial in number? Please see: https://meet.jit.si/static/dialInInfo.html?room=oslc-op Meeting ID: 2979764690#
The meeting minutes are edited in https://hackmd.io/@driib/oslc-op-minutes/edit
Previous minutes can be found under https://github.com/oslc-op/oslc-admin/tree/master/minutes/2019 OASIS OSLC Open Project group home: https://lists.oasis-open-projects.org/g/oslc-op oslc-op GitHub Organization: https://github.com/oslc-op Mailing list: oslc-op@... (archives: https://lists.oasis-open-projects.org/g/oslc-op) |
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: 60-day public reviews for OSLC Requirements Management v2.1 and Change Management v3.0 have closed
Hello,
In accordance with the process outlined in https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#OSpublicRev, we have recorded a total of one (1) comments on the OSLC Requirements Management v2.1 specification and acknowledged the receipt publicly on this mailing list. Further, https://github.com/oslc-op/oslc-specs/issues/514 was opened to track the comments and the work to address them.
As per point 3 of the public review process §2.8.2, we are now preparing a revised Project Specification that will contain non-material changes only.
If you believe that you sent your comment in accordance with the OASIS rules but the receipt of your comment has not been acknowledged, please notify us promptly.
–Andrew
From: <oslc-op@...> on behalf of Andrii Berezovskyi <andriib@...>
Dear OSLC project members,
The 60-day public reviews for OSLC Requirements Management v2.1 and Change Management v3.0 announced on 09 March 2021 in https://lists.oasis-open-projects.org/g/oslc-op/message/483 has closed:
Next steps:
I am very excited about the progress reached so far and would like to thank everyone in the OP as well as in OASIS for working hard to make this happen!
Best regards, Andrew on behalf of the PGB
P.S. Special thanks to Chet for the email template (:
|
||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||
|
Re: Comments on OSLC Requirements Management v2.1 PS01
#publicreview
Hello Paul,
Thank you for your comments. I hereby acknowledge the receipt of the comment. The comment is tracked under https://github.com/oslc-op/oslc-specs/issues/514 as comment no. 1. I will reply in this mailing list once the items in your comment have been addressed.
–Andrew
From:
<oslc-op@...> on behalf of Paul Knight <paul.knight@...>
Hi OSLC OP members,
In reviewing OSLC Requirements Management v2.1 PS01, I noted a couple of items which should be considered:
- The four references to OSLC Core (in the References section, at https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-spec.html#references) all point to old (May 2018) documents, instead of the updated documents (September 2020, at https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/oslc-core.html). It would probably be best to use the "Latest stage" URI references, like https://docs.oasis-open-projects.org/oslc-op/core/v3.0/oslc-core.html.
- Review use of keywords and their capitalization, and references from the Conformance section (Conformance Clause IDs).
NOTE: These comments appear to have been properly addressed in a set of proposed modifications listed at https://github.com/oasis-open-projects/administration/issues/19#issuecomment-793142961.
Best regards, Paul --
|
||||||||||||||||||||||||||||||
|
|
