Date   

OSLC-OP Meeting Minutes 2023-05-25

Jim Amsden
 

OSLC OP Meeting minutes (May 25, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

  • Jim Amsden (IBM)
  • David Honey (IBM)
  • Ralph Schoon (IBM)
  • Martin Ulrich (Bosch)

Previous minutes: OSLC-OP Meeting Minutes 2023-05-11 (no minutes published for 2023-005-18)

Agenda

  • Publish Change Management errata
  • Link Discovery Management Topics
  • Configuration Management Topics - establishing the scope for config 1.1?
    • Change Set Delivery
    • History
    • PLM versioning alignment

Minutes

Where are the resource types relevant to OSLC defined? All OSLC specifications provide vocabulary terms and constraints in Turtle files and which are rendered in HTML documents that are part of the multi-part specifications. In addition, all OSLC namespaces are published on open-services.net and accessing these namespaces will return the RDF vocabularies.

Where is the model for a configuration ConceptResource? There is no ConceptResource resource defined. Rather there the configuration management specification defines how a compliant server resolves a GET on a resource URI with a Configuration-Context header URI. Concept URI is a conventional name for these resource URIs.

How should LDM support paging? LDM should simply reference OSLC core paging as described in the OSLC Core Specification, sections 4.1.10.3 and 4.1.10.4.

Should LDM specify any means of limiting the number of target and/or predicate URIs that the server will process? Probably, as part of the LDM discovery.

Action items

  • √ Jim to check on CM errata SMV - the vote to certify that the errata does not include material changes only requires a FMV. Once that fote passes, https://issues.oasis-open.org/browse/TCADMIN-4351 will start the 15 day review.
  • Jim (or Jad?) to publish NS files - with help of Andrew. Config Management PSD01 was published, but not TRS? Andrew says PSD01 files were published for TRS
  • Jim to publish NS files for PS01 Config and TRS, not wait until OS. COS is not really a published stage, just a milestone
  • Jim will check the release tags, at least the latest revision is tagged.

 


Re: OSLC-OP Meeting Minutes 2023-05-11

Jad El-Khoury
 

Eran

 

For LDM and the use of Open API, I get the impression you want to work bottom up with real examples.

Unless you already have it, have you considered setting up a mock-up server? I think it can be relatively easily to do.

Maybe this way, we can also have more concrete examples in our discussions.

 

Jad

 

From: oslc-op-pgb@... <oslc-op-pgb@...> On Behalf Of Jim Amsden
Sent: Thursday, 11 May 2023 17:35
To: oslc-op@...; oslc-op-pgb@...
Subject: [oslc-op-pgb] OSLC-OP Meeting Minutes 2023-05-11

 

OSLC OP Meeting minutes (May 11, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

  • Jim Amsden (IBM)
  • Jad El-khoury (KTH)
  • David Honey (IBM)
  • Eran Gray (IBM)
  • Frej (SodiusWillert)
  • Ralph Schoon (IBM)

Previous minutes: OSLC-OP Meeting Minutes 2023-05-04

Agenda

  • OSLC-OP Meeting Minutes
  • Publish Change Management errata.
  • √ TRS SoUs
  • Linking Profiles specification editing progress
  • Link Discovery Management Topics
  • Configuration Management Topics - establishing the scope for config 1.1?
    • Change Set Delivery
    • History
    • PLM versioning alignment

Minutes

TRS and Configuration Management public reviews are in progress and will complete 27 June.

Proposal: OASIS guidelines are meeting minutes must be published in the OP mailing list archive accessible from https://lists.oasis-open-projects.org/g/oslc-op. The OSLC-OP therefore should no longer need to also publish meeting minutes in GitHub. Proposal is to stop publishing meeting minutes in GitHub and to only publish on the OSLC-OP mailing archive: https://lists.oasis-open-projects.org/g/oslc-op/topics.

Discussion: White ballot: approved.

Linking Profiles

We are suspending work on Linking Profiles until the Link Discovery Management spec is further along. This is because the full profile depends on LDM. There is nothing blocking continued contribution, it’s just a question of resource capacity.

LDM

OpenAPI is a useful way to document a REST API. However, OpenAPI doesn’t work as well with RDF resources.

Using a yaml file and OpenAPI is a fine approach to describe the LDM API. POST should not have any parameters; any required information should be in the POST entity request body. The entity response body from an LDM request should support multiple formats including turtle, JSON-LD, and RDF/XML. These formats will be difficult to describe in OpenAPI and should follow existing OSLC approaches to returning lists of things as done for OSLC Query. That is, they should use LDPCs with a vocabulary for any in-line content.

Configuration context should be in the standard OSLC Configuration-Context header.

The POST request should be a application/x-www-form-urlencoded key/value pairs.

Action items

 

 


OSLC-OP Meeting Minutes 2023-05-11

Jim Amsden
 

OSLC OP Meeting minutes (May 11, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

  • Jim Amsden (IBM)
  • Jad El-khoury (KTH)
  • David Honey (IBM)
  • Eran Gray (IBM)
  • Frej (SodiusWillert)
  • Ralph Schoon (IBM)

Previous minutes: OSLC-OP Meeting Minutes 2023-05-04

Agenda

  • OSLC-OP Meeting Minutes
  • Publish Change Management errata.
  • √ TRS SoUs
  • Linking Profiles specification editing progress
  • Link Discovery Management Topics
  • Configuration Management Topics - establishing the scope for config 1.1?
    • Change Set Delivery
    • History
    • PLM versioning alignment

Minutes

TRS and Configuration Management public reviews are in progress and will complete 27 June.

Proposal: OASIS guidelines are meeting minutes must be published in the OP mailing list archive accessible from https://lists.oasis-open-projects.org/g/oslc-op. The OSLC-OP therefore should no longer need to also publish meeting minutes in GitHub. Proposal is to stop publishing meeting minutes in GitHub and to only publish on the OSLC-OP mailing archive: https://lists.oasis-open-projects.org/g/oslc-op/topics.

Discussion: White ballot: approved.

Linking Profiles

We are suspending work on Linking Profiles until the Link Discovery Management spec is further along. This is because the full profile depends on LDM. There is nothing blocking continued contribution, it’s just a question of resource capacity.

LDM

OpenAPI is a useful way to document a REST API. However, OpenAPI doesn’t work as well with RDF resources.

Using a yaml file and OpenAPI is a fine approach to describe the LDM API. POST should not have any parameters; any required information should be in the POST entity request body. The entity response body from an LDM request should support multiple formats including turtle, JSON-LD, and RDF/XML. These formats will be difficult to describe in OpenAPI and should follow existing OSLC approaches to returning lists of things as done for OSLC Query. That is, they should use LDPCs with a vocabulary for any in-line content.

Configuration context should be in the standard OSLC Configuration-Context header.

The POST request should be a application/x-www-form-urlencoded key/value pairs.

Action items

 

 


OSLC-OP Meeting Minutes 2023-05-04

Jim Amsden
 

OSLC OP Meeting minutes (May 4, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

  • [x] Jim Amsden (IBM)
  • [ ] Jad El-khoury (KTH)
  • [ ] Gray Bachelor (IBM)
  • [x] David Honey (IBM)
  • [x] Eran Gray (IBM)
  • [ ] Jim Gammon (Raython Technologies)
  • [ ] Partrick Ollerton (PTC)
  • [ ] Michael Rowe (IBM)
  • [ ] Ed Gentry (MID)
  • [ ] Tanu (PTC)
  • [x] Frej (SodiusWillert)
  • [ ] Andrew Berezovskyi (KTH)
  • [ ] Ralph Schoon (IBM)
  • [ ] Axel Reichwein (Koneksys)
  • [x] Martin Ulrich (Bosch)

Previous minutes: https://github.com/oslc-op/oslc-admin/blob/master/minutes/2022/2023-04-20.md

Agenda

  • [ ] Publish Change Management errata
  • [ ] TRS SoUs
  • [ ] Linking Profiles specification editing progress
  • [ ] Link Discovery Management Topics
  • [ ] Configuration Management Topics - establishing the scope for config 1.1?
    • [ ] Change Set Delivery
    • [ ] History
    • [ ] PLM versioning alignment

Minutes

Link Discovery Managment Discussion

Eran and Martin had a number of questions.

How are predicates represented?

Predicates are just URIs, and should used typicaly URI syntax, e.g., https://open-services.net/ns/cm#implementsRequirement or oslc_cm:implementsRequirement

LDM servers could manage links between versioned and/or unversioned resources.

What happens when a Configuration-Context is not specified?

If either the target resource for which the client is requesting incoming links, or the potential source resources of those incoming links are versioned resources, then a Configuration-Context must be specified. An error would need to be raised in an oslc:Error response.

Action items

  • [ ] David will send out a link to a document describing how IBM handles links to non-versioned resources such as change requests.
  • [ ] Jim (or Jad?) to publish NS files - with help of Andrew. Config Management PSD01 was published, but not TRS? Andrew says PSD01 files were published for TRS 
  • [ ] Jim to publish NS files for PS01 Config and TRS, not wait until OS. COS is not really a published stage, just a milestone 
  • [ ] Jim will check the release tags, at least the latest revision is tagged.

 


Your 60-day public reviews for Configuration Management and Tracked Resource Set have been announced

Chet Ensign
 

Participants in the OSLC Open Project

The 60-day public reviews for OSLC Configuration Management V1.0 and OSLC Tracked Resource Set V3.0  before call for consent as OASIS Standard has been announced. The reviews end June 27th. See https://lists.oasis-open.org/archives/members/202304/msg00008.html.

Please keep in mind the OASIS requirements for handling comments [1]. Feedback should be sent to the project's mailing list at oslc-op@.... All submitted comments must be acknowledged by the OP. In addition, the OP needs to maintain a log of comments received and their resolutions. The comment resolution log will need to be available when call for consent opens. A simple comment resolution log template is available in OpenDocument [2] and Office [3] format.

Let me know if you have any questions regarding the review or next steps.

=== Additional references:
[1] https://www.oasis-open.org/resources/tcadmin/handling-the-comments-received-during-a-public-review

[2] https://www.oasis-open.org/sites/www.oasis-open.org/files/Simple-comment-resolution-log-template_0.ods

[3] https://www.oasis-open.org/sites/www.oasis-open.org/files/Simple-comment-resolution-log-template_0.xls



--

Chet Ensign

Chief Technical Community Steward

OASIS Open

   
+1 201-341-1393
chet.ensign@...
www.oasis-open.org


Invitation to comment on OSLC Configuration Management V1.0 and OSLC Tracked Resource Set V3.0 before call for consent as OASIS Standard - ends June 27th

Chet Ensign
 

Two Project Specifications from Open Services for Lifecycle Collaboration Open Project take next step towards OASIS Standard

OASIS members and other interested parties,

OASIS and the Open Services for Lifecycle Collaboration Open Project [1] are pleased to announce that OSLC Configuration Management V1.0 PS01 and OSLC Tracked Resource Set V3.0 PS02 are now available for public review and comment.

Managing change and configuration in a complex systems development life cycle is very difficult, especially in heterogeneous environments that include homegrown tools, open source projects, and commercial tools from different vendors. The OSLC initiative applies World Wide Web and Linked Data principles to enable interoperation of change, configuration, and asset management processes across a product's entire application and product lifecycle.

Configuration Management Version 1.0 defines an RDF vocabulary and a set of REST APIs for managing versions and configurations of linked data resources from multiple domains.

Tracked Resource Set Version 3.0 allows a server to expose a set of resources in a way that allows clients to discover them, track additions to and removals from the set, and track state changes to the resources in the set. The protocol is suitable for dealing with sets containing a large number of resources, as well as highly active resource sets that undergo continual change.

Configuration Management received 3 Statements of Use from MID, SodiusWillert, and IBM.

Tracked Resource Set received 3 Statements of Use from IBM, KTH Royal Institute of Technology, and SodiusWillert [3].

The candidate specifications and related files are available here:

- OSLC Configuration Management Version 1.0. Part 1: Overview
Project Specification 01
30 May 2022

HTML:  https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.html (Authoritative)

PDF: https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.pdf

- OSLC Tracked Resource Set Version 3.0. Part 1: Specification
Project Specification 02
24 November 2022

HTML: https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set.html (Authoritative)

PDF: https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set.pdf

For 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:

- Configuration Management: https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-v1.0-ps01.zip

- Tracked Resource Set: http://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/trs-v3.0-ps02.zip
 
Public Review Period

The 60-day public review starts 29 April 2023 at 00:00 UTC and ends 27 June 2023 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@.... To subscribe, send an empty email to oslc-op+subscribe@... 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 Configuration Management and Tracked Resource Set, we call your attention to the Open Project's LICENSE.md file [4] that applies to the work of the OP. 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.

==============

[1] Open Services for Lifecycle Collaboration Open Project
https://open-services.net/

[2] Approval ballot:
- Configuration Management: https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/296
- Tracked Resource Set: https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/303

[3] Statements of Use:

- Configuration Management:
  - MID: https://lists.oasis-open-projects.org/g/oslc-op/message/1138
  - SodiusWillert: https://lists.oasis-open-projects.org/g/oslc-op/message/879
  - IBM: https://lists.oasis-open-projects.org/g/oslc-op/message/1215

- Tracked Resource Set:
  - IBM: https://lists.oasis-open-projects.org/g/oslc-op/message/1225
  - KTH Royal Institute of Technology: https://lists.oasis-open-projects.org/g/oslc-op/message/1246
  - SodiusWillert: https://lists.oasis-open-projects.org/g/oslc-op/message/1240

[4] https://github.com/oslc-op/oasis-open-project/blob/master/LICENSE.md


--

Chet Ensign

Chief Technical Community Steward

OASIS Open

   
+1 201-341-1393
chet.ensign@...
www.oasis-open.org


(Second) Ballot for OSLC Special Majority Vote Has Started

Kelly Cullinane
 

Members of the OSLC Open Project:

A Special Majority Vote to consider OSLC Tracked Resource Set Version 3.0 has been set up.

This ballot opens on 12:00AM 21 April 2023 UTC and closes 11:59PM 27 April 2023 UTC.

You can access the ballot using this link.

This ballot is only open to eligible voting members of the OSLC PGB. I currently show the following members as eligible to vote:

* Jim Amsden (co-chair, IBM)

* Jad El-Khoury (co-chair, KTH Royal Institute of Technology)

* Axel Reichwein (Koneksys)


Please send any questions to the list.

--

Kelly Cullinane

Technical Community Program Steward 

OASIS Open

  
+1-903-241-6063
kelly.cullinane@oasis-open.org
www.oasis-open.org


Locked A Special Majority Vote to consider OSLC Tracked Resource Set Version 3.0 as a Candidate for OASIS Standard #poll-notice #poll #poll-result

Group Notification <kelly.cullinane@...>
 

To Members of the OSLC PGB:

 

Do you approve submitting this Project Specification to the OASIS membership for consideration as a candidate for OASIS Standard?


OSLC Tracked Resource Set Version 3.0 [1] was approved as a Project Specification on 24 November 2022. 

 

The Open Project has received 3 Statements of Use from IBM, KTH Royal Institute of Technology, and SodiusWillert [2]. 

 

Approving this ballot will result in a 60-day public review after which, if no comments are received, the PS will be submitted to a membership-wide call for consent. If comments are received, the OP will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [3].

 

This ballot requires a Special Majority Vote [4]. The PGB roster currently lists 3 voting members. In order to pass, at least 2 (2/3 x 3) have to vote Yes and no more than 1 (1/4 x 3) member may vote No.

 

Only members of the OSLC Project Governing Board are eligible to vote on this ballot. The members of the PGB are:

 

  • Jim Amsden (IBM)
  • Jad El-Khoury (KTH Royal Institute of Technology)
  • Axel Reichwein (Koneksys)

 

This ballot opens on 12:00AM 21 April 2023 UTC and closes 11:59PM 27 April 2023 UTC.

[1] URI to the Project Specification: 

https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set.html

 

[2] Links to statements of use 

 

- IBM

https://lists.oasis-open-projects.org/g/oslc-op/topic/ibm_statement_of_use_for_the/97825340?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,97825340,previd%3D1679670047231280636,nextid%3D1677797129867128668&previd=1679670047231280636&nextid=1677797129867128668

 

- KTH Royal Institute of Technology

https://lists.oasis-open-projects.org/g/oslc-op/topic/kth_statement_of_use_for_the/98366631?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,98366631,previd%3D1681911719223578117,nextid%3D1679396401697016267&previd=1681911719223578117&nextid=1679396401697016267

 

- SodiusWillert

https://lists.oasis-open-projects.org/g/oslc-op/topic/sodiuswillert_statement_of/98315795?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,98315795,previd%3D1681911719223578117,nextid%3D1679396401697016267&previd=1681911719223578117&nextid=1679396401697016267

 

[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard

 

[4] Special Majority Vote: https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dSpecialMajority

Results

See Who Responded


OSLC-OP Meeting Minutes 2023-04-20

Jim Amsden
 

OSLC OP Meeting minutes (Apr 20, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

  • [x] Jim Amsden (IBM)
  • [x] Jad El-khoury (KTH)
  • [ ] Gray Bachelor (IBM)
  • [x] David Honey (IBM)
  • [x] Eran Gray (IBM)
  • [ ] Jim Gammon (Raython Technologies)
  • [ ] Partrick Ollerton (PTC)
  • [ ] Michael Rowe (IBM)
  • [ ] Ed Gentry (MID)
  • [ ] Tanu (PTC)
  • [x] Frej (SodiusWillert)
  • [ ] Andrew Berezovskyi (KTH)
  • [x] Ralph Schoon (IBM)
  • [ ] Axel Reichwein (Koneksys)
  • [ ] Martin Ulrich (Bosch)

Previous minutes: https://github.com/oslc-op/oslc-admin/blob/master/minutes/2022/2023-04-13.md

Agenda

  • [ ] Publish Change Management errata
  • [ ] TRS SoUs
  • [ ] Linking Profiles specification editing progress
  • [ ] Link Discovery Management Topics
  • [ ] Configuration Management Topics - establishing the scope for config 1.1?
    • [ ] Change Set Delivery
    • [ ] History
    • [ ] PLM versioning alignment

Minutes

Publish Change Management errata

Jim is working on it. Next steps are to schedule a FMV on 28 April that there are not substative changes in the CM errata, and create an updated zip file with the new OASIS icon and new publish date.

TRS SoUs

We have 3 SoUs from IBM, SodiusWilert and KTH. We can now proceed to on the OASIS standards track. FMV has been requested to submit as CoS.

Configuration Management

The Special Majority Vote to approve a candidate for OASIS Standard for OSLC Tracked Resource Set Version 3.0 passed. Configuration Managment will now progress to public review.

Linking Profiles

Call for contribution. Ralph will see what he can contribute. 

Frej points out that the linking profile is more focused on helping introduce OSLC to new users. The Link Discovery Management specification might be more useful for expanding OSLC capabilities.

Product Definition

The OSLC-OP agrees that product definition is a valuable space to explore. But the OP would prefer that the strategy for product definition be addressed by the PGB (with collaboration from other interested parties) to establish a vision and scope of work that we could then contribute to.

Action items

  • [x] Jim to ping Chet and Paul again about CM errata and Config Management FMV for COS.
  • [ ] Jim (or Jad?) to publish NS files - with help of Andrew. Config Management PSD01 was published, but not TRS? Andrew says PSD01 files were published for TRS 
  • [ ] Jim to publish NS files for PS01 Config and TRS, not wait until OS. COS is not really a published stage, just a milestone 
  • [ ] Jim will check the release tags, at least the latest revision is tagged.
  • [x] Jim will continue the process to submit Config Management 1.0 for COS - pending 3rd SoU

 


KTH Statement of Use for The OSLC Open Project OSLC Tracked Resource Set Version 3.0

Jad El-Khoury
 

 

 

KTH Royal Institute of Technology has successfully implemented the OASIS  OSLC Tracked Resource Set Version 3.0, dated 24 November 2022, in accordance with the conformance clauses defined in Section 14 "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations, as well as integration with tools supporting other OSLC domain specifications.

 

The implementation is available as part of the Eclipse Lyo project https://github.com/eclipse/lyo/tree/master/trs/server.

 

Jad, On behalf of Martin Törngren, KTH’s primary OASIS representative

______________________________

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

jad@..., www.kth.se

 

 

 


Locked Re: A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice #poll-result

Chet Ensign
 

Hi Jad - sorry, our mistake. You are correct - we made that update. Just missed it here. 

/chet

On Tue, Apr 18, 2023 at 2:05 AM Jad El-Khoury <jad@...> wrote:

Btw, I was able to vote anyway.

 

From: oslc-op-pgb@... <oslc-op-pgb@...> On Behalf Of Jad El-Khoury
Sent: Tuesday, 18 April 2023 08:04
To: oslc-op-pgb@...; kelly.cullinane@...
Cc: Andrii Berezovskyi <andriib@...>
Subject: Re: [oslc-op-pgb] A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice

 

Hi

 

Below it says that Andrew Berezovskyi (KTH) is the PGB member.

I have earlier checked (somewhere somehow) and we did make the change so that I am the PGB member from KTH.

 

Is this just an error in the email, or did we not change in the system somewhere?

 

Regards

Jad

 

 

 

From: oslc-op-pgb@... <oslc-op-pgb@...> On Behalf Of Group Notification
Sent: Monday, 17 April 2023 22:18
To: oslc-op-pgb@...
Subject: [oslc-op-pgb] A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice

 

A poll has been updated:

To Members of the OSLC PGB:

 

Do you approve submitting this Project Specification to the OASIS membership for consideration as a candidate for OASIS Standard?

OSLC Configuration Management Version 1.0 [1] was approved as a Project Specification on 30 May 2022. 

 

The Open Project has received 3 Statements of Use from MID, SodiusWillert, and IBM [2]. 

 

Approving this ballot will result in a 60-day public review after which, if no comments are received, the PS will be submitted to a membership-wide call for consent. If comments are received, the OP will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [3].

 

This ballot requires a Special Majority Vote [4]. The PGB roster currently lists 3 voting members. In order to pass, at least 2 (2/3 x 3) have to vote Yes and no more than 1 (1/4 x 3) member may vote No.

 

Only members of the OSLC Project Governing Board are eligible to vote on this ballot. The members of the PGB are:

 

  • Jim Amsden (IBM)
  • Andrew Berezovskyi (KTH Royal Institute of Technology)
  • Axel Reichwein (Koneksys)

 

This ballot opens on 12:00AM 17 April 2023 UTC and closes 11:59PM 25 April 2023 UTC. 

[1] URI to the Project Specification: 

https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.html

 

[2] Links to statements of use 

 

- MID

https://lists.oasis-open-projects.org/g/oslc-op/topic/statements_of_use_for_oslc/96956636?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,96956636,previd%3D1676569522097489935,nextid%3D1674758343251802901&previd=1676569522097489935&nextid=1674758343251802901

 

- SodiusWillert

https://lists.oasis-open-projects.org/g/oslc-op/topic/call_for_statements_of_use/92093780?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,100,92093780,previd%3D1661428932515649703,nextid%3D1657202406508934239&previd=1661428932515649703&nextid=1657202406508934239

 

- IBM

https://lists.oasis-open-projects.org/g/oslc-op/topic/ibm_statement_of_use_for_oslc/97013171?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,97013171,previd%3D1679415965598995728,nextid%3D1677518908597034086&previd=1679415965598995728&nextid=1677518908597034086

 

 

[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard

 

 

[4] Special Majority Vote: https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dSpecialMajority

 

1. Yes
2. No
3. Abstain

Click Here To Vote

Do not reply to this message to vote in the poll. You can vote in polls only through the group's website.



--

Chet Ensign

Chief Technical Community Steward

OASIS Open

   
+1 201-341-1393
chet.ensign@...
www.oasis-open.org


Locked Re: A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice #poll-result

Jad El-Khoury
 

Btw, I was able to vote anyway.

 

From: oslc-op-pgb@... <oslc-op-pgb@...> On Behalf Of Jad El-Khoury
Sent: Tuesday, 18 April 2023 08:04
To: oslc-op-pgb@...; kelly.cullinane@...
Cc: Andrii Berezovskyi <andriib@...>
Subject: Re: [oslc-op-pgb] A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice

 

Hi

 

Below it says that Andrew Berezovskyi (KTH) is the PGB member.

I have earlier checked (somewhere somehow) and we did make the change so that I am the PGB member from KTH.

 

Is this just an error in the email, or did we not change in the system somewhere?

 

Regards

Jad

 

 

 

From: oslc-op-pgb@... <oslc-op-pgb@...> On Behalf Of Group Notification
Sent: Monday, 17 April 2023 22:18
To: oslc-op-pgb@...
Subject: [oslc-op-pgb] A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice

 

A poll has been updated:

To Members of the OSLC PGB:

 

Do you approve submitting this Project Specification to the OASIS membership for consideration as a candidate for OASIS Standard?

OSLC Configuration Management Version 1.0 [1] was approved as a Project Specification on 30 May 2022. 

 

The Open Project has received 3 Statements of Use from MID, SodiusWillert, and IBM [2]. 

 

Approving this ballot will result in a 60-day public review after which, if no comments are received, the PS will be submitted to a membership-wide call for consent. If comments are received, the OP will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [3].

 

This ballot requires a Special Majority Vote [4]. The PGB roster currently lists 3 voting members. In order to pass, at least 2 (2/3 x 3) have to vote Yes and no more than 1 (1/4 x 3) member may vote No.

 

Only members of the OSLC Project Governing Board are eligible to vote on this ballot. The members of the PGB are:

 

  • Jim Amsden (IBM)
  • Andrew Berezovskyi (KTH Royal Institute of Technology)
  • Axel Reichwein (Koneksys)

 

This ballot opens on 12:00AM 17 April 2023 UTC and closes 11:59PM 25 April 2023 UTC. 

[1] URI to the Project Specification: 

https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.html

 

[2] Links to statements of use 

 

- MID

https://lists.oasis-open-projects.org/g/oslc-op/topic/statements_of_use_for_oslc/96956636?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,96956636,previd%3D1676569522097489935,nextid%3D1674758343251802901&previd=1676569522097489935&nextid=1674758343251802901

 

- SodiusWillert

https://lists.oasis-open-projects.org/g/oslc-op/topic/call_for_statements_of_use/92093780?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,100,92093780,previd%3D1661428932515649703,nextid%3D1657202406508934239&previd=1661428932515649703&nextid=1657202406508934239

 

- IBM

https://lists.oasis-open-projects.org/g/oslc-op/topic/ibm_statement_of_use_for_oslc/97013171?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,97013171,previd%3D1679415965598995728,nextid%3D1677518908597034086&previd=1679415965598995728&nextid=1677518908597034086

 

 

[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard

 

 

[4] Special Majority Vote: https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dSpecialMajority

 

1. Yes
2. No
3. Abstain

Click Here To Vote

Do not reply to this message to vote in the poll. You can vote in polls only through the group's website.


Locked Re: A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice #poll-result

Jad El-Khoury
 

Hi

 

Below it says that Andrew Berezovskyi (KTH) is the PGB member.

I have earlier checked (somewhere somehow) and we did make the change so that I am the PGB member from KTH.

 

Is this just an error in the email, or did we not change in the system somewhere?

 

Regards

Jad

 

 

 

From: oslc-op-pgb@... <oslc-op-pgb@...> On Behalf Of Group Notification
Sent: Monday, 17 April 2023 22:18
To: oslc-op-pgb@...
Subject: [oslc-op-pgb] A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice

 

A poll has been updated:

To Members of the OSLC PGB:

 

Do you approve submitting this Project Specification to the OASIS membership for consideration as a candidate for OASIS Standard?

OSLC Configuration Management Version 1.0 [1] was approved as a Project Specification on 30 May 2022. 

 

The Open Project has received 3 Statements of Use from MID, SodiusWillert, and IBM [2]. 

 

Approving this ballot will result in a 60-day public review after which, if no comments are received, the PS will be submitted to a membership-wide call for consent. If comments are received, the OP will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [3].

 

This ballot requires a Special Majority Vote [4]. The PGB roster currently lists 3 voting members. In order to pass, at least 2 (2/3 x 3) have to vote Yes and no more than 1 (1/4 x 3) member may vote No.

 

Only members of the OSLC Project Governing Board are eligible to vote on this ballot. The members of the PGB are:

 

  • Jim Amsden (IBM)
  • Andrew Berezovskyi (KTH Royal Institute of Technology)
  • Axel Reichwein (Koneksys)

 

This ballot opens on 12:00AM 17 April 2023 UTC and closes 11:59PM 25 April 2023 UTC. 

[1] URI to the Project Specification: 

https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.html

 

[2] Links to statements of use 

 

- MID

https://lists.oasis-open-projects.org/g/oslc-op/topic/statements_of_use_for_oslc/96956636?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,96956636,previd%3D1676569522097489935,nextid%3D1674758343251802901&previd=1676569522097489935&nextid=1674758343251802901

 

- SodiusWillert

https://lists.oasis-open-projects.org/g/oslc-op/topic/call_for_statements_of_use/92093780?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,100,92093780,previd%3D1661428932515649703,nextid%3D1657202406508934239&previd=1661428932515649703&nextid=1657202406508934239

 

- IBM

https://lists.oasis-open-projects.org/g/oslc-op/topic/ibm_statement_of_use_for_oslc/97013171?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,97013171,previd%3D1679415965598995728,nextid%3D1677518908597034086&previd=1679415965598995728&nextid=1677518908597034086

 

 

[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard

 

 

[4] Special Majority Vote: https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dSpecialMajority

 

1. Yes
2. No
3. Abstain

Click Here To Vote

Do not reply to this message to vote in the poll. You can vote in polls only through the group's website.


Ballot for OSLC Special Majority Vote Has Started #poll-notice

Kelly Cullinane
 

Members of the OSLC Open Project:


A Special Majority Vote to consider OSLC Configuration Management Version 1.0 has been set up.


This ballot opens on 12:00AM 18 April 2023 UTC and closes 11:59PM 25 April 2023 UTC. 


You can access the ballot using this link.


This ballot is only open to eligible voting members of the OSLC PGB. I currently show the following members as eligible to vote:


* Jim Amsden (co-chair, IBM)

* Andrew Berezovskyi (co-chair, KTH Royal Institute of Technology)

* Axel Reichwein (Koneksys)

 

Please send any questions to the list.

 


Locked A Special Majority Vote to consider OSLC Configuration Management Version 1.0 as a Candidate for OASIS Standard #poll #poll-notice #poll-result

Group Notification <kelly.cullinane@...>
 
Edited

To Members of the OSLC PGB:

 

Do you approve submitting this Project Specification to the OASIS membership for consideration as a candidate for OASIS Standard?

OSLC Configuration Management Version 1.0 [1] was approved as a Project Specification on 30 May 2022. 

 

The Open Project has received 3 Statements of Use from MID, SodiusWillert, and IBM [2]. 

 

Approving this ballot will result in a 60-day public review after which, if no comments are received, the PS will be submitted to a membership-wide call for consent. If comments are received, the OP will be asked to vote by Special Majority Ballot on whether to continue to the membership vote. This is explained in TC Process section 3.4.2, Public Review of a Candidate OASIS Standard [3].

 

This ballot requires a Special Majority Vote [4]. The PGB roster currently lists 3 voting members. In order to pass, at least 2 (2/3 x 3) have to vote Yes and no more than 1 (1/4 x 3) member may vote No.

 

Only members of the OSLC Project Governing Board are eligible to vote on this ballot. The members of the PGB are:

 

  • Jim Amsden (IBM)
  • Andrew Berezovskyi (KTH Royal Institute of Technology)
  • Axel Reichwein (Koneksys)

 

This ballot opens on 12:00AM 17 April 2023 UTC and closes 11:59PM 25 April 2023 UTC. 

[1] URI to the Project Specification: 

https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.html

 

[2] Links to statements of use 

 

- MID

https://lists.oasis-open-projects.org/g/oslc-op/topic/statements_of_use_for_oslc/96956636?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,96956636,previd%3D1676569522097489935,nextid%3D1674758343251802901&previd=1676569522097489935&nextid=1674758343251802901

 

- SodiusWillert

https://lists.oasis-open-projects.org/g/oslc-op/topic/call_for_statements_of_use/92093780?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,100,92093780,previd%3D1661428932515649703,nextid%3D1657202406508934239&previd=1661428932515649703&nextid=1657202406508934239

 

- IBM

https://lists.oasis-open-projects.org/g/oslc-op/topic/ibm_statement_of_use_for_oslc/97013171?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,97013171,previd%3D1679415965598995728,nextid%3D1677518908597034086&previd=1679415965598995728&nextid=1677518908597034086

 

 

[3] http://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard

 

 

[4] Special Majority Vote: https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dSpecialMajority

 

Results

See Who Responded


Formal Notice of intent to publish OSLC Change Management Version 3.0 PSD01, OASIS Standard with Draft 01 of Errata 01

Jim Amsden
 

Dear PGB members,

The rules require us to notify you at least 14 days before submitting the ballots for the spec drafts publication. We are hereby notifying you of the OP intention to publish OSLC Change Management Version 3.0 PSD01, OASIS Standard with Draft 01 of Errata 01 in 2 weeks’ time.

The package is attached. Comments can be sent to the oslc-op@... mailing list.

 

OSLC Change Management version 2.0 deprecated a number of properties that refer to OSLC Quality Management artifacts. OSLC version 3.0 preserved these deprecated properties, and in addition, removed them from the resource constraints. This errata removes the deprecation of the following properties and adds them back to the resource constraints:

  • oslc_cm:testedByTestCase
  • oslc_cm:affectsTestResult
  • oslc_cm:blocksTestExecutionRecord
  • oslc_cm:relatedTestExecutionRecord
  • oslc_cm:relatedTestCase
  • oslc_cm:relatedTestPlan
  • oslc_cm:relatedTestScript

These links were deprecated as part of the resolution of Issue on redundant inverse predicates. OSLC CM 3.0 does define the corresponding properties representing links from the other direction, but marks them as deprecated. This was done to follow link guidance best practices and only define the links from one direction to avoid backlinks and data redundancy issues.

With the introduction of OSLC Configuration Management 1.0, and that OSLC Change Management resources are not versioned resources, these properties will now be required to create links between non-versioned Change Management resources and versioned Quality Management resources. Therefore these properties are no longer deprecated, and their ResourceShapes have been added to the constraints.

The changes are listed in Appendix C. Errata of OSLC Change Management Version 3.0. Part 1: Specification in the attached files.

Regards,
Jim on behalf of the OSLC OP maintainers

 


OSLC-OP Meeting Minutes 2023-04-13

Jim Amsden
 

OSLC OP Meeting minutes (Apr 13, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

  • [x] Jim Amsden (IBM)
  • [ ] Jad El-khoury (KTH)
  • [ ] Gray Bachelor (IBM)
  • [x] David Honey (IBM)
  • [ ] Eran Gray (IBM)
  • [ ] Jim Gammon (Raython Technologies)
  • [ ] Partrick Ollerton (PTC)
  • [ ] Michael Rowe (IBM)
  • [ ] Ed Gentry (MID)
  • [ ] Tanu (PTC)
  • [x] Frej (SodiusWillert)
  • [ ] Andrew Berezovskyi (KTH)
  • [x] Ralph Schoon (IBM)
  • [ ] Axel Reichwein (Koneksys)
  • [ ] Martin Ulrich (Bosch)

Previous minutes: https://github.com/oslc-op/oslc-admin/blob/master/minutes/2022/2023-03-30.md

Agenda

  • [ ] Publish Change Management errata
  • [ ] TRS SoUs
  • [ ] Linking Profiles specification editing progress
  • [ ] Link Discovery Management Topics
  • [ ] Configuration Management Topics - establishing the scope for config 1.1?
    • [ ] Change Set Delivery
    • [ ] History
    • [ ] PLM versioning alignment

Minutes

TRS SoUs

Frej will look into one from Sodius-Willert

No further topics today.

Action items

  • [ ] Jim to ping Chet and Paul again about CM errata and Config Management FMV for COS.
  • [ ] Jim (or Jad?) to publish NS files - with help of Andrew. Config Management PSD01 was published, but not TRS? Andrew says PSD01 files were published for TRS 
  • [ ] Jim to publish NS files for PS01 Config and TRS, not wait until OS. COS is not really a published stage, just a milestone 
  • [ ] Jim will check the release tags, at least the latest revision is tagged.
  • [ ] Jim will continue the process to submit Config Management 1.0 for COS - pending 3rd SoU

 


Re: OSLC-OP Meeting Minutes 2023-03-30

Jad El-Khoury
 

Hi all

We also decided today to cancel next Thursday’s (6th April) meetings due to easter & Pesach that week.

 

Regards

Jad

 

 

From: oslc-op-pgb@... <oslc-op-pgb@...> On Behalf Of Jim Amsden
Sent: Thursday, 30 March 2023 17:10
To: oslc-op@...; oslc-op-pgb@...
Subject: [oslc-op-pgb] OSLC-OP Meeting Minutes 2023-03-30

 

OSLC OP Meeting minutes (Mar 30, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

  • [x] Jim Amsden (IBM)
  • [x] Jad El-khoury (KTH)
  • [ ] Gray Bachelor (IBM)
  • [ ] David Honey (IBM)
  • [x] Eran Gray (IBM)
  • [ ] Jim Gammon (Raython Technologies)
  • [ ] Partrick Ollerton (PTC)
  • [ ] Michael Rowe (IBM)
  • [ ] Ed Gentry (MID)
  • [ ] Tanu (PTC)
  • [ ] Frej (SodiusWillert)
  • [ ] Andrew Berezovskyi (KTH)
  • [x] Ralph Schoon (IBM)
  • [ ] Axel Reichwein (Koneksys)
  • [ ] Martin Ulrich (Bosch)

Previous minutes: https://github.com/oslc-op/oslc-admin/blob/master/minutes/2022/2023-03-23.md

Agenda

  • [ ] Publish Change Management errata
  • [ ] GET vs POST for managing sensitive information
  • [ ] TRS SoUs
  • [ ] Linking Profiles specification editing progress
  • [ ] Link Discovery Management Topics
  • [ ] Configuration Management Topics - establishing the scope for config 1.1?
    • [ ] Change Set Delivery
    • [ ] History
    • [ ] PLM versioning alignment

Minutes

CM Errata

Zip file sent to OASIS, no feedback yet. Jim to ping Paul to make sure he has everything he needs.

TRS SoUs

IBM has submitted. KTH and Sodius-Willert are listed as potential submitters, but haven't yet (at least I couldn't find the SoUs in the oslc-op mailing archive).

GET vs POST

OSLC makes much us of GET with query parameters in some cases, that could expose information that has security implications. The POST entity request bodies could be encrypted to avoid exposing query strings in the URI. See CWE-598: Use of GET Request Method With Sensitive Query Strings.

This is a broader HTTP issue that could be resolved by using TLS. But there may be cases where certain URLs have to be sent unencrpted to get through various proxies, etc. Or decrypted GET URLs could be stored in a user's browser where they could be exposed to hackers. TLS only addresses secure transition of HTTP requests, it does not address security of the content of those resources once they are consummed by a client or server. 

We could do an inventory of all OSLC GETs, see which ones use query parameters, and which of these parameters might expose security issues and would therefore require updating the specs to support POST.

OSLC Query already supports GET and POST for query strings. The only other GET in OSLC that might expose information is GET with selective properties. This would only expose property names, not values. CWE-598 explicity uses an example of exposing database column names which would be similar to exposing RDF resource property URLs. 

Jim will create an issue against OSLC core to support GET or POST with selective properties.

Action items

  • [ ] Jim will create an issue against OSLC core to support GET or POST with selective properties.
  • [ ] Jim to ping Chet and Paul about CM errata and Config Management FMV for COS.
  • [ ] Jim (or Jad?) to publish NS files - with help of Andrew. Config Management PSD01 was published, but not TRS? Andrew says PSD01 files were published for TRS 
  • [ ] Jim to publish NS files for PS01 Config and TRS, not wait until OS. COS is not really a published stage, just a milestone 
  • [ ] Jim will check the release tags, at least the latest revision is tagged.
  • [x] Jim will continue the process to submit Config Management 1.0 for COS - pending 3rd SoU
  • [x] Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info) - no longer needed, but welcome.

 


OSLC-OP Meeting Minutes 2023-03-30

Jim Amsden
 

OSLC OP Meeting minutes (Mar 30, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

  • [x] Jim Amsden (IBM)
  • [x] Jad El-khoury (KTH)
  • [ ] Gray Bachelor (IBM)
  • [ ] David Honey (IBM)
  • [x] Eran Gray (IBM)
  • [ ] Jim Gammon (Raython Technologies)
  • [ ] Partrick Ollerton (PTC)
  • [ ] Michael Rowe (IBM)
  • [ ] Ed Gentry (MID)
  • [ ] Tanu (PTC)
  • [ ] Frej (SodiusWillert)
  • [ ] Andrew Berezovskyi (KTH)
  • [x] Ralph Schoon (IBM)
  • [ ] Axel Reichwein (Koneksys)
  • [ ] Martin Ulrich (Bosch)

Previous minutes: https://github.com/oslc-op/oslc-admin/blob/master/minutes/2022/2023-03-23.md

Agenda

  • [ ] Publish Change Management errata
  • [ ] GET vs POST for managing sensitive information
  • [ ] TRS SoUs
  • [ ] Linking Profiles specification editing progress
  • [ ] Link Discovery Management Topics
  • [ ] Configuration Management Topics - establishing the scope for config 1.1?
    • [ ] Change Set Delivery
    • [ ] History
    • [ ] PLM versioning alignment

Minutes

CM Errata

Zip file sent to OASIS, no feedback yet. Jim to ping Paul to make sure he has everything he needs.

TRS SoUs

IBM has submitted. KTH and Sodius-Willert are listed as potential submitters, but haven't yet (at least I couldn't find the SoUs in the oslc-op mailing archive).

GET vs POST

OSLC makes much us of GET with query parameters in some cases, that could expose information that has security implications. The POST entity request bodies could be encrypted to avoid exposing query strings in the URI. See CWE-598: Use of GET Request Method With Sensitive Query Strings.

This is a broader HTTP issue that could be resolved by using TLS. But there may be cases where certain URLs have to be sent unencrpted to get through various proxies, etc. Or decrypted GET URLs could be stored in a user's browser where they could be exposed to hackers. TLS only addresses secure transition of HTTP requests, it does not address security of the content of those resources once they are consummed by a client or server. 

We could do an inventory of all OSLC GETs, see which ones use query parameters, and which of these parameters might expose security issues and would therefore require updating the specs to support POST.

OSLC Query already supports GET and POST for query strings. The only other GET in OSLC that might expose information is GET with selective properties. This would only expose property names, not values. CWE-598 explicity uses an example of exposing database column names which would be similar to exposing RDF resource property URLs. 

Jim will create an issue against OSLC core to support GET or POST with selective properties.

Action items

  • [ ] Jim will create an issue against OSLC core to support GET or POST with selective properties.
  • [ ] Jim to ping Chet and Paul about CM errata and Config Management FMV for COS.
  • [ ] Jim (or Jad?) to publish NS files - with help of Andrew. Config Management PSD01 was published, but not TRS? Andrew says PSD01 files were published for TRS 
  • [ ] Jim to publish NS files for PS01 Config and TRS, not wait until OS. COS is not really a published stage, just a milestone 
  • [ ] Jim will check the release tags, at least the latest revision is tagged.
  • [x] Jim will continue the process to submit Config Management 1.0 for COS - pending 3rd SoU
  • [x] Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info) - no longer needed, but welcome.

 


Soliciting Statements of Use for OSLC Tracked Resource Set Version 3.0

Jim Amsden
 

The OSLC Open Project OSLC Tracked Resource Set Version 3.0, Project Specification, revision 02 is now soliciting Statements of Use in order to proceed on the OASIS standards track. This revision incorporates the insight gained from many implementations, integrations with other lifecycle management tools, and user experience, while maintaining compatibility with OSLC specifications. Implementations of this specification are therefore applicable for Statements of Use required to progress to OASIS Standard.

 

The OSLC Open Project is ready to accept Statements of Use from implementers. This is an essential part of the OASIS standardization process and will enable us to progress to OASIS Standard. Please see Section 14 of the OASIS Open Project Rules for more information. In summary:

 

Statement of Use“, with respect to a Committee Specification or Project Specification, is a written statement that a party has successfully used or implemented that specification in accordance with all or some of its conformance clauses, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations. The Statement of Use must be made to a specific version of the Specification and must include the Specification’s approval date. The party may be an OASIS Member or a non-member. In case of a non-member, the Statement of Use must be submitted via the Technical Committee’s or Project Governing Board’s comment facility. A TC or PGB may require a Statement of Use to include hyperlinks to documents, files or demonstration transcripts that enable the committee’s members to evaluate the implementation or usage. A Statement of Use submitted to the TC or PGB must be approved by TC Resolution or PGB action as an acceptable Statement of Use with respect to the Specification. A party can only issue one Statement of Use for a given specification. When issued by an OASIS Organizational Member, a Statement of Use must be endorsed by the Organizational Member’s Primary Representative

 

Statements of Use must be endorsed by the OASIS Organizational Member's Primary Representative. Submitters just need to notify the OOSLC-OP PGB, by submitting their 'Statement of Use' to the oslc-op@... oslc-op@... mailing list.

 

A typical statement of use could be:

 

<insert primary representative name / org here> has successfully implemented the OASIS  OSLC Tracked Resource Set Version 3.0, dated 24 November 2022, in accordance with the conformance clauses defined in Section 14 "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations, as well as integration with tools supporting other OSLC domain specifications.