OSLC OP Meeting minutes (Feb 09, 2023)

OSLC PGB Meeting 2023-03-21 - Meeting Notes

Jim Amsden

#288

OSLC-OP PGB meeting Tuesday, 21 March at 8:00 DST, meeting notes

Agenda:

Status on OSLC Specifications (TRS 3.0 COS, Configuration Management 1.0 COS, Change Management errata)
Status of Linking Profile
Status of Link Discovery Management spec
Proposal for OSLC Product Workgroup

Spec updates

TRS: v3.0 PS02 has been published. This revision contains updates requested by OASIS It is ready to promote to COS and go to public review.

Action, Jim: Schedule the SMV COS vote

Config 1.0: v1.0 PS01 has been published. This Product Specification is ready for COS pending SOU from IBM.

Action, Jim: Follow-up with IBM OASIS Representative

Change Management v3.0, OS: Errata completed to restore missing QM link properties needed when using configuration management.

Action, Jad, David: Complete pull request review

Action, Jim: merge approved pull request and work with OASIS on how to deliver the updated documents.

Linking Profile

OSLC enables a lot of required server implementation flexibility with MAYs and SHOULDs.

This flexibility is essential for server implementations to meet their specific needs.

But it leads to variability that inhibits interoperability between servers and increases development complexity.

The Linking Profile specification was intended to manage that variability somewhat to foster integration by providing different profile conformance levels through tightening MAYs and SHOULDs to MUSTs.

A draft specification has been created, and the scope of work and profile compliance points are known.

We have had some difficulty making progress due to limited contributions/participation.

Should Linking Profile be an OASIS spec or a Project Note providing implementation guidance?

Andrew originally proposed it should be a spec, but use different profiles to handle the variability.

The intention was for customers to be able to determine what integrations they need and to know what profiles their chosen tools would need to provide.

Customers are interested in the profiles, but perhaps vendors are less motivated because of the development effort to achieve conformance.

Are there any publicly available details on Polarion and Jazz integration?

No, these are private. But authentication was a significant issue.

Sodius-Willert and MID also have a lot of experience with OSLC integrations.

Consensus was to proceed on the standards track for the Linking Profile, but consider publishing as a project note once we have enough content to assess the pros and cons.

Link Discovery Management (LDM) Spec

An initial LDM 1.0 WD01 draft has been created, with an abstract and introduction.

Eran and Martin are editors.

The scope is reasonably well understood, except for possibly how an LDM server summarizes the scope of links it provides.

The PGB recommends creating a model of LDM clients and servers, and their resources, with sequence diagrams that describe the interactions for link discovery.

Then develop the REST APIs needed to support the data model and sequence diagrams.

Michael Rowe will help with LDM REST API details.

OSLC Product Workgroup Proposal

Gray presented meeting notes from Product Workgroup meeting that summarizes problem to be solved and value proposition.

Erik Herzog says: I think we need to consider two use cases: 1. Traditional OSLC to Tradtional PLM. 2. Traditional PLM to Traditional PLM.

Should we also explore ProStep and SysML v2 to understand what role they might play in a broader systems of systems integration and lifecycle management problem?

What are the overlaps with these standards and PLM?

We have understood the ALM/PLM integration problem for some number of years, but have struggled to make progress and deliver real integration value, despite specific customer needs.

We may need to understand these challenges to better inform the problem we are trying to solve.

Open discussion on possible future work or direction?

No further discussion.

OSLC-OP 2023-03-16 Meeting Minutes

Jim Amsden

#287

OSLC OP Meeting minutes (Mar 02, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

[x] Jim Amsden (KTH)
[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)
[ ] Frej (SodiusWillert)
[ ] Andrew Berezovskyi (KTH)
[x] Ralph Schoon (IBM)
[ ] Axel Reichwein (Koneksys)
[x] Martin Ulrich (Bosch)

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

Agenda

[ ] Change Management errata review and merge
[ ] 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

Change Management

Pull request pending reviews. May need ot add a section describing the erreata.

Prep for PGB meeting

The Quarterly PGB meeting is Tuesday 21 March. Proposed agenda:

Status on OSLC Specifications (TRS 3.0 COS, Configuration Management 1.0 COS, Change Management errata)
Status of Linking Profile
Status of Link Discovery Management spec
Proposal for OSLC Product Workgroup

LDM Specification review

using POST to {query endpoint} Config-Context header (optional) query request body: list of object URI references list of predicats Response: triples including: (incoming subject, predicate, reference object) The format of the POST entity request body can be specified ha having Content-Type application/x-www-form-urlencoded, multipart/form-datam, application/json, application/xml, etc. The LDM specification will need to state what Content-Types are supported and provide their request body formats.

Discovery of LDM servers URIs follows the same guidelines as in OSLC Core (e.g., rootservices, OPTIONS, etc.). LDM spec does not need to address this further

We agree that federating multiple LDM servers is out of scope, clients could use multiple LDM servers is they want, but how they do that is up to them. It could be to cluster multiple LDM servers that have the same data, or multiple LDM servers that have the same or possibly overlapping data.

An LDM server has a server URI, some descriptor URI that provides some metadata about the server. In that descriptor is the URI of the {query endpoint} referenced above.

The LDM spec needs to define: 1. GET on LDM serverURI results 2. URI to access and content for LDM metadata 3. queryBase URI for the POST query endpoint

IBM LDX is a TRS consumer. So it is possible to view the Admin page of that server to see what TRS providers are used as its data sources. This provides a means of determining what information is available in that LDX server.

LDM needs to optionally provide some similar mechanism to allow clients to discover the scope of links that are available from that server. It is possible that an OSLC ServiceProvider URL could provide minimal information.

This information might also include a means of discovering the predicates that are available.

Action items

[ ] 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
[ ] Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info)

2022-03-21 OSLC-OP PGB Meeting Agenda

Jim Amsden

#286

Just a reminder, the next OSLC-OP PGB meeting is scheduled for Tuesday, 21 March at 8:00 DST. Proposed agenda:

Status on OSLC Specifications (TRS 3.0 COS, Configuration Management 1.0 COS, Change Management errata)
Status of Linking Profile
Status of Link Discovery Management spec
Proposal for OSLC Product Workgroup

Hope to see you all there.

OSLC-OP Meeting Minutes 2023-03-09

Jim Amsden

#285

OSLC OP Meeting minutes (Mar 09, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

[x] Jim Amsden (KTH)
[ ] Jad El-khoury (KTH)
[x] Gray Bachelor (IBM)
[ ] David Honey (IBM)
[x] Eran Gray (IBM)
[ ] Jim Gammon (Raython Technologies)
[ ] Partrick Ollerton (PTC)
[ ] Michael Rowe (IBM)
[x] 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-02-23.md

Agenda

[ ] 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

[ ] Link Discovery Management

Minutes

Change Management

The missing properties will be added back to CM 3.0 using an errata. This will require a Full Majority Vote. Jim is working through the process with OASIS.

Linking Profiles

Ed will provide some content in the Authentication section. Many other sections are not complex, mostly requiring elaborating the table that outlines the profile conformance. Eran has some table formatting updating to do.

Link Discovery Management

Martin and Eran are working on this. An initial draft has been created and is in https://github.com/oslc-op/oslc-specs.

Jim had to leave early.

Action items

[ ] 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
[ ] Patrick & Tanupreet to provide a SoU for Config Management 1.0 (They got an email from Andrew with info)

Already? Yes - Daylight Savings Time is back

Chet Ensign

#284

Please share with your project teams as appropriate.

Seems like only yesterday we had to pull out the owners manual and re-learn how to set our dashboard clocks back an hour. And now, we have to do it again.

The North America starts daylight savings time this coming Sunday, March 12, at 2:00 AM. Much of Europe starts 2 weeks later on Sunday, March 26, at 1:00 AM. To see if you are affected, check your local listings.

So, if you are leading a project with folks from opposite sides of the oceans, check your calendars to see when your meetings are actually scheduled. One way or another, someone is going to be off by an hour.

Best,

/chet

Chet Ensign

Chief Technical Community Steward

OASIS Open

oslc-op-pgb@... oslc-op-pgb@...

OSLC-OP 2023-02-32 Meeting Minutes

Jim Amsden

#283

OSLC OP Meeting minutes (Feb 23, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

[x] Jim Amsden (KTH)
[ ] 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)
[x] Ed Gentry (MID)
[ ] Tanu (PTC)
[x] Frej (SodiusWillert)
[ ] Andrew Berezovskyi (KTH)
[x] Ralph Schoon (IBM)
[ ] Axel Reichwein (Koneksys)
[x] Unai Esandi (Ikerlan)
[x] Martin Ulrich (Bosch)

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

Agenda

[ ] 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

Adeptness

Unai joined, expects to resume OSLC work. Participating in European project: Adeptness, establish a framework for deployment, validation and monitoring of long-term systems. In the final stages. Works on a data model, want to enable integration with OSLC lifecycle tools. Implementation configuration management. Working on translating data model to participate in OSLC integrations. Some questions on how to model data in RDF. May be interested in OSLC Automation specification. Unai will prepare a presentation to provide more detail in a future meeting in the next week or two.

Linking Profiles

Eran's updates have been merged. Eran still has updates in response to Martin's comments in the pull request. Ed will only be able to work on the linking profile.

Link Discovery Management

Eran has submitted an introduction to Link Discovery Management. Eran and Martin will be coeditors. Jim will provide an initial document for editing.

Eran reviewed the submitted introduction. What do you index? If the object of an RDF statement is an Object (not primitive), then the statement is a link that is a candidate to be indexed. There could be other approaches where the links that are stored are specific to a usage pattern.

What links are contributed to an LDM server, and how those links are delivered is not the subject of the LDM specification. Rather the LDM specification defines what an LDM server must do to provide incoming link discovery services by some client application. TRS could be a way to deliver content to an LDM server, possibly filtered to store only links, or only specific links. But that defines what links the server is able to support, not what the service is that it provides to clients to access those links.

The information needed for link discovery is the target resource URLs, the desired link predicate URLs, and the configuration context URL and returns a list of triples of using concept resources. The request should be a POST whose entity body contains the request parameters.

There should be a means of discovering LDM server instances and to know the scope of the links they might provide.

How would an LDM server describe the scope of the links it is able to provide.

Action items

[x] Jim to research missing CM to QM backlinks with David Honey to determine if these properties are mssing in CM.
[x] Raise a CM issue
[x] Jad/Jim to re-initiate the PGB meetings - convert current series
[x] Eran to reach out the Linking Profile assignee's to ensure some progress occurs.
[ ] 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
[ ] Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info)

Re: IBM Statement of Use for OSLC Configuration Management Version 1.0

Jim Amsden

#282

Jason,

I can’t find the IBM SoU for this specification on https://lists.oasis-open-projects.org/g/oslc-op/topics?p=recentpostdate%2Fsticky%2C%2C%2C20%2C2%2C120%2C0&previd=1661428932515649703&nextid=1657202406508934239&jump=1. Maybe it was sent to some other mailing list?

It should go to: oslc-op@... oslc-op@... and

From: Jason Keirstead <Jason.Keirstead@...>
Date: Thursday, July 7, 2022 at 8:46 AM
To: Sky Matthews <sky@...>, Jim Amsden <jamsden@...>, David Bermingham <david.bermingham@...>, Daniel Moul <dmoul@...>, Tim Feeney <tfeeney@...>, David Honey2 <david.honey@...>
Subject: Re: IBM Statement of Use for OSLC Configuration Management Version 1.0

Thanks Jim & team, I will send the required notice to the list today.

-
Jason Keirstead
Distinguished Engineer, CTO - IBM Security Threat Management | www.ibm.com/security

Declare an Emergency: USA +1 888 241 9812, Global +1 312 212 8034

Assistant - Mauricio Durán Cambronero (mauduran@...)

See my calendar - https://ibm.biz/jkcalendar

Co-Chair - Open Cybersecurity Alliance, Project Governing Board

www.opencybersecurityalliance.org

From: Sky Matthews <sky@...>
Date: Thursday, June 30, 2022 at 8:03 PM
To: Jim Amsden <jamsden@...>, David Bermingham <david.bermingham@...>, Daniel Moul <dmoul@...>, Tim Feeney <tfeeney@...>, David Honey2 <david.honey@...>, Jason Keirstead <Jason.Keirstead@...>
Subject: Re: IBM Statement of Use for OSLC Configuration Management Version 1.0

Yes I approve

Regards,

-Sky

From: Jim Amsden <jamsden@...>
Date: Thursday, June 30, 2022 at 3:05 PM
To: David Bermingham <david.bermingham@...>, Daniel Moul <dmoul@...>, Tim Feeney <tfeeney@...>, Sky Matthews <sky@...>, David Honey2 <david.honey@...>, Jason Keirstead <Jason.Keirstead@...>
Subject: IBM Statement of Use for OSLC Configuration Management Version 1.0

Do all of you approve of submitting the following Statement of Use to the OASIS OSLC Open Project, Project Governing Board (PGB)? David and I will be happy to answer any related questions.

Jason Keirstead / IBM has successfully implemented Specification OSLC Configuration Management Version 1.0, revision 01, dated 30 May 2022, in accordance with the conformance clauses defined in Section 4 "Conformance" of the specification and its related multi-part specification. This use of the specification includes interoperation with other similar independent implementations, as well as integration with tools supporting other OSLC domain specifications.

OSLC-OP Telecom Meeting Minutes 2023-12-19

Jim Amsden

#281

OSLC OP Meeting minutes (Feb 16, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

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

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

Agenda

[x] Linking Profiles specification editing progress
[x] Request SMV to submit Config Management 1.0 for COS
[x] Configuration Management Topics - establishing the scope for config 1.1?

[x] Change Set Delivery
[x] History
[x] PLM versioning alignment

[x] Link Discovery Management

Minutes

Linking Profile

Eran has made some updates, and Martin has provided some review in the pull request. Jim will address the merge conflicts and merge the pull request next week after Eran has responded to Martin's feedback.

Ed will proceed with his sections and may have to cover some of the root services section since Jim has limited time to contribute.

Configuration Management

We briefly discussed the missing configuration management capabilities listed above. This is something that could be addressed by experts in the area. Perhaps we can see if Geoff Clemm would be intersted in contributing.

But otherwise this was a secondary priority for the current OSLC-OP participants.

Link Discovery Management

There is general concensus that some kind of Link Discovery Service should be the next priority.

Jim will look into what's available from open-services.net for a link index document and see what IBM can share regarding the private API used in ELM LDX. We can see if that's something that could be harvested as a starting point.

Link Discovery should focus first on requests to provide incoming links to one or more target resources. TRS could be assumed as the means for providing these links to a Link Discovery Management (LDM) server. LDM will need some discovery capability to advertise what links it can provide, establishing the scope of known relations.

There is a question as to whether a server or client could use congributions from multiple GCM servers. The same considerations might apply to LDM servers. There could be overlapping and potentially inconsistent contributions (due to timing issues). And there could be gaps where relations between resources across the LDM servers are not possible.

Eran will develop a proposed charter for the LDM specification that will cover the chanllenges addressed, the proposed solution and what the value would be for integration.

Action items

[ ] Jim to research missing CM to QM backlinks with David Honey to determine if these properties are mssing in CM.
[ ] Raise a CM issue
[ ] Jad/Jim to reinitiate the PGB meetings - convert current series
[ ] Eran to reach out the Linking Profile assignees to ensure some progress occurs.
[ ] 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
[ ] Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info)

OSLC-OP Meeting Minutes 2023-02-09

Jim Amsden

#280

OSLC OP Meeting minutes (Feb 09, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

[x] Jim Amsden (KTH)
[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)
[x] Ed Gentry (MID)
[ ] Tanu (PTC)
[ ] Frej (SodiusWillert)
[ ] Andrew Berezovskyi (KTH)
[ ] Ralph Schoon (IBM)
[ ] Axel Reichwein (Koneksys)
[ ] Unai Esandi
[x] Martin Ulrich (Bosch)

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

Agenda

[x] Linking Profiles specification editing progress
[x] Request SMV to submit Config Management 1.0 for COS
[ ] Configuration Management Topics - establishing the scope for config 1.1?

[ ] Change Set Delivery
[ ] History
[ ] PLM versioning alignment

Minutes

Linking Profile

We decided to distinguish OSLC properties as either primary or secondary. Primary properties are those properties where the server persists the subject of assertions involving the property. The linking profile will specify that the assertion triple (or link) involving a primary property must be stored on the same server as the subject of that assertion.

Secondary properties are optional and if supported, non-config-aware servers can store associated triples while config-aware servers must treate them as incoming links accessed through some query mechanism such as OSLC Query.

Where products have specific implementations for secondary link storage, that should be documented in the products to faclilitate integration with other servers.

We discussed Issue #588: OSLC Change Management 3.0 is missing link properties to OSLC Quality Management Resources that the RDF properties needed for the primary links between CM and QM resources are missing in OSLC CM 3.0. OSLC-OP members should review that issue and provide their feedback soon so that we can quickly address this issue with CM 1.1.

Eran presented a proposed set of primary and secondary link properties. This will be delivered to the link profile soon so that it can be reviewed.

The question of an Incoming Link Discovery Service is still open for duscssion.

Configuration Management 1.0 COS

Ed will provide the SoU from Mid this week.

Configuration Management 1.1

Discussion will continue in coming weeks.

Action items

[ ] Jim to research missing CM to QM backlinks with David Honey to determine if these properties are mssing in CM.
[ ] Raise a CM issue
[ ] Jad/Jim to reinitiate the PGB meetings - convert current series
[ ] Eran to reach out the Linking Profile assignees to ensure some progress occurs.
[ ] 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
[ ] Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info)

OSLC-OP Meeting Minutes 2023-02-02

Jim Amsden

#279

OSLC OP Meeting minutes (Feb 02, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

[x] Jim Amsden (KTH)
[ ] 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)
[x] Frej (SodiusWillert)
[ ] Andrew Berezovskyi (KTH)
[ ] Ralph Schoon (IBM)
[ ] Axel Reichwein (Koneksys)
[ ] Unai Esandi
[x] Martin Ulrich (Bosch)

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

Agenda

[ ] Linking Profiles specification editing progress
[ ] Request SMV to submit Config Management 1.0 for COS
[ ] Configuration Management Topics - establishing the scope for config 1.1?

[ ] Change Set Delivery
[ ] History
[ ] PLM versioning alignment

Minutes

Linking Profile

Linking profile has to address where links are stored, since there is no central storage. We have agreement that the active, outgoing, server owning the source resource would "own the link".

We will create a table of OSLC properties and specify which one is the forward property.

CM does not define back/inverse links for QM links such as affectedByChangeRequest, blockedByChangeRequest, relatedChangeRequest, testsChangeRequests, etc. This is because link guidance was to not define redundant backlinks.

We may wish to deprecate all such backlinks in all specs as a means of effecting link ownership.

But there is a specific issue with these missing backlinks. These backlinks are defined in IBM EWM, and since ChangeRequests are non-versioned, the CM server would alwasy own the links to potentially versioned test cases.

So these backlink properties may need to be added to CM.

Action items

[ ] Jim to research missing CM to QM backlinks with David Honey to determine if these properties are mssing in CM.
[ ] Raise a CM issue
[ ] Jad/Jim to reinitiate the PGB meetings - convert current series
[ ] Eran to reach out the Linking Profile assignees to ensure some progress occurs.
[ ] 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
[ ] Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info)

Your OASIS primary point of contact

Chet Ensign

#278

With Kelly Cullinane joining OASIS and the project management team, I am taking the opportunity to improve our support by divvying up support between her and Claudia.

Each will now be primary OASIS staff contact for their respective projects. While you're welcome to contact whoever you wish (this is OASIS Open after all), think of your primary contact as your starting point when you need to get in touch. They'll know your situation best and will be best able to provide direction, support, or get you to the right person.

Going forward, Claudia will be the primary OASIS staff contact for:

- EEA Community Projects
- OCA: Open Cybersecurity Alliance
- OriginBX
- PRVD

Kelly will cover:

- NIEMOpen
- OSLC: Open Services for Lifecycle Collaboration
- RECITE: REasoning for Conversation and Information Technology Exchange

As well as the next Open Project starting up.

You can email Claudia at claudia.rauch@... and Kelly at kelly.cullinane@....

We look forward to continuing to provide you with the service you need to do the great work you do. Please don't hesitate to contact Claudia or Kelly with questions or comments.

Best,

/chet

Chet Ensign

Chief Technical Community Steward

OASIS Open

OSLC Tracked Resource Set v3.0 Project Specification 02 approved by the OSLC Open Project

Paul Knight

#277

OASIS is pleased to announce that OSLC Tracked Resource Set Version 3.0 from the Open Services for Lifecycle Collaboration Open Project [1] has been approved as an OASIS Project Specification.

Managing change and configuration in a complex systems development lifecycle 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.

The Tracked Resource Set protocol allows a server to expose a set of resources in a way that allows clients to discover that set of resources, to track additions to and removals from the set, and to track state changes to the resources in the set. The protocol does not assume that clients will dereference the resources, but they could do so. 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. The protocol is HTTP-based and follows RESTful principles.

This Project Specification is an OASIS deliverable, completed and approved by the OP's Project Governing Board and fully ready for testing and implementation. The applicable open source licenses can be found in the project's administrative repository at https://github.com/oslc-op/oslc-admin/blob/master/LICENSE.md.

The specification and related files are available at:

OSLC Tracked Resource Set Version 3.0
Project Specification 01
24 November 2022

- OSLC Tracked Resource Set Version 3.0. Part 1: Specification
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set.html
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set.pdf

- OSLC Tracked Resource Set Version 3.0. Part 2: Vocabulary
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set-vocab.html
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set-vocab.pdf

- OSLC Tracked Resource Set Version 3.0. Part 3: Constraints
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set-shapes.html
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/tracked-resource-set-shapes.pdf

- OSLC Tracked Resource Set RDF Vocabulary definitions file:
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/trs-vocab.ttl

- OSLC Tracked Resource Set Resource Shape Constraints definitions file:
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/trs-shapes.ttl

Distribution ZIP file

For your convenience, OASIS provides a complete package of the specification and related files in a ZIP distribution file. You can download the ZIP file at:
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps02/trs-v3.0-ps02.zip

Members of the OSLC OP Project Governing Board approved this specification by Special Majority Votes [2] as required by the Open Project rules [3].

Our congratulations to the participants and contributors in the Open Services for Lifecycle Collaboration Open Project on their achieving this milestone.

========== Additional references:

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

[2] Approval ballot:
https://lists.oasis-open-projects.org/g/oslc-op/message/1048

[3] https://www.oasis-open.org/policies-guidelines/open-projects-process/

Paul Knight....Document Process Analyst

OASIS...Setting the standard for open collaboration

Cancelling today's OSLC-OP meeting

Jim Amsden

#276

I have a hard conflict today, and I don’t know if Jad can host or not, so cancelling today’s meeting.

OSLC-OP Meeting Minutes 2023-01-12

Jim Amsden

#275

OSLC OP Meeting minutes (Jan 12, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

Jim Amsden (KTH)
Jad El-khoury (KTH)
Frej (SodiusWillert)
Martin Ulrich (Bosch)

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

Agenda

[ ] Linking Profiles specification editing progress
[ ] Request SMV to submit Config Management 1.0 for COS
[ ] OSLC Automation spec

Minutes

TRS 3.0 PS02

Ready to publish. Followup with SMV vote for COS.

Configuration Management

Still looking for 3rd SoU.

Considerations for Configuration Management 1.1: * Change set delivery * Stream history * Variability management * Normalization with PLM versioning * Stable URLs

Martin Ulrich Joined the OSLC-OP

PLM architect at Bosch. Uses all of the current PLM products. Can provide a comprehensive point of view from the user's perspective.

Configuration management most important OSLC spec, but also the most complicated and least understood.

There may be some missing content in the Configuration Management Primer.

Working on developing a cross-domain configuration management solution to address extensibility and scalability requirements as well as all domains including systems engineering, electronics, etc.

Action items

[ ] Jad to ensure he is a member of the PGB
[ ] Jad to invite new members to the PGB
[ ] Ed to provide Configuration Management Statement of Use from MID
[ ] 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
[ ] Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info)

OSLC OP Meeting minutes (Jan 5, 2023)

Jim Amsden

#274

OSLC OP Meeting minutes (Jan 5, 2023)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

Jim Amsden (KTH)
David Honey (IBM)
Partrick Ollerton (PTC)
Frej (SodiusWillert)

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

Agenda

Linking Profiles specification editing progress
Request SMV to submit Config Management 1.0 for COS
OSLC Automation spec

Minutes

TRS 3.0 PS02 is in the process of being published. Once published we can request a SMV to submit as candidate OASIS Standard and start the public review period.

Config Management 1.0 is still blocked pending a third statement of use.

No followup activity on the Automation spec as yet. Still pending.

Linking profile progress is slow due to resource commitments.

Priorities for 2023:

TRS to OASIS Standard
Config Management to OASIS Standard
Complete Linking Profile and determine implications for Incoming Link Discovery Service, understanding PLM versioning and relationship to OSLC Config Management
Start working on Config Management 2.0 - address change set delivery, history operations, and PLM versioning

Action items

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
Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info)

OSLC-OP Meeting Minutes 2022-12-22

Jim Amsden

#273

OSLC OP Meeting minutes (Dec 22, 2022)

Chairs: Jim Amsden, Jad El-khoury

Attendees:

Jim Amsden (KTH)
David Honey (IBM)
Ean Gray (IBM)

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

Agenda

Linking Profiles specification editing progress
Request SMV to submit Config Management 1.0 for COS
OSLC Automation spec

Minutes

What's needed in OSLC to enable standard drag and drop? A resource and have 2 URIs, GET with Accept=RDF type, will get content. Or it could be a GET on a URI for accessing a UI representation, Accept=text/html could redirect to the Web UI to display that resource.

Use case: standardize how to do drag-and-drop to create linking. i.e., like the selection dialog standardizes how the selected resource URIs are returned to the application through the iframe, something similar could be done for drag-and-drop. The source and target URIs for drag and drop need to be predictable.

Jim is working on the final changes to get TRS 3.0 PS02 published, which will become the Candidate OASIS Standard.

Open discussion on PLM and configuration management.

Action items

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
Patrick & Tanupreet to provide a SoU for Config Managemnet 1.0 (They got an email from Andrew with info)

Official paperwork, signatures, and such

Chet Ensign

#272

Dear Project Chairs,

Recently, we had a situation where someone on a project was asked to sign some paperwork associated with their project. Fortunately, the person contacted staff and asked what to do.

Please be aware all contracts go through OASIS, who is empowered to sign for any legal commitments. You should never be in a position where you are asked to sign something. You may not and should not be asked to sign any legal documentation, conveyances or MoUs on behalf of your TC/OP/PGB/etc. We take that karma on ourselves.

Should you receive such a request, please forward it to OASIS staff. We are ready and happy to help.

Chet Ensign

Chief Technical Community Steward

OASIS Open