Hi

Please use this link for the full recording. My previous link only allowed you to view the first 15 minutes.

https://kth-my.sharepoint.com/:v:/g/personal/jad_ug_kth_se/EYJhBrSTBnxDmPHMdZs_la0BSZab-B4QHLQT6mOg9WOk-A?e=Cilrnu

Hi

Here’s the recording from our last meeting

https://www.dropbox.com/s/wsnmnsla6c9gmex/oslc-op%20on%202022-09-08%2015-06.mp4?dl=0

This meeting introduced OSLC for Products. People interested in product definition and the relationship between PLM, ALM, SSE and OSLC lifecycle management may find the referenced presentation interesting. We welcome participation and contribution in this important potential new area for OSLC-OP.

https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-09-08.md

See https://github.com/oslc-op/oslc-specs/tree/master/notes/linking-profiles.

Next week we will discuss the overall layout of the document, and start assigning sections to contributors.

To edit, you will minimally need to be able to edit Markdown (https://www.markdownguide.org) and GitHub.

If this becomes a problem, we can consider using https://hackmd.io to collaboratively edit the document with the document editor periodically committing to https://github.com/oslc-op. See https://hackmd.io/c/tutorials/%2Fs%2Flink-with-github (limited to 20 pushes without premium account).

@Jim Amsden (jamsden@...) I saved the minutes under https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-09-01.md

But I would appreciate a review since I don’t think I managed to capture some of the items in the minutes.

______________________________

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

Thanks Jim!

Attached is a consolidated version of the document… I accepted most of the proposed changes.

Best regards,

Eran

All,

See my attached comments building on the changes already forwarded.

In short, my proposed edits of the Problem Statement section reflect my experiential presentation of the burning platform up front. And, while I didn’t take the liberty or time to completely restructure the entire document out of respect for the work already performed, I do recommend we seriously consider merging the Overview (Outline) with the Problem Statement section.  As an OSLC end user, that would help me most understand what I am reading and why it exists.

I also really like the explanations in the Solution section and believe this is a great foundation for the path forward.

Regards,

James E Gammon Jr.
SNS Engineering
Enterprise & RI&S Digital Engineering

O:  +1 972.344.5637
C:  +1 972.880.0413
James.E.Gammon@...



Engineering
13510 North Central Expressway

Dallas, TX  75243

I have added some tracked changes and comments to Andrew’s comments.

Overall, I think this is an excellent description of the interoperability challenge we are trying to address, the proposed solution scope, and its business value. This is a good foundation upon which OSLC-OP can proceed. Thank Eran for your contribution.

Key issues I think we will need to address:

1. Separating the specification of how profiles are defined, from the specification of linking profile instances that address a specific integration problem
2. Establishing some standard way of expressing link storage ownership (e.g., ResourceShape extension)
3. Maintaining a seamless shift from OSLC Query based approach to discovering incoming links vs. a possibly future Link Discovery Service – ideally a richer profile layers on additional capabilities without invalidating existing approaches or creating its own interoperability challenges
4. Establishing some standard way of expressing how incoming links are accessed if the approach depends on the link type (as it does in DOOR Next)
5. Ensuring the profile clauses are machine readable and testable to facilitate automation of profile compliance verification

Hi,

Please find my comments attached! Great start!

/Andrew

Hi All

Here is an initial draft of the outline, motivation, and solution requirements for the OSLC linking profiles supplement

Best regards,

Eran Gery – Global Industry Solutions Lead, IBM ELM

Minutes are at:

https://github.com/oslc-op/oslc-admin/blob/master/minutes/2022/2022-08-25.md

Please note that the next meeting, 1 Sep, will discuss Product Definition to determine interest in progressing this important topic.

Hi,

Please find my comments attached! Great start!

/Andrew

Hi All

Here is an initial draft of the outline, motivation, and solution requirements for the OSLC linking profiles supplement

Best regards,

Eran Gery – Global Industry Solutions Lead, IBM ELM

Hi

I unfortunately need to attend another meeting at the same time, so will miss our meeting today.

______________________________

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

The minutes from today’s meeting https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-08-18.md

Thanks all for joining.

______________________________

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

See you all next week.

Hi Robert

The profiles do not focus on ELM, but where there are choices to be made (mostly around link storage) we align with ELM choices as they are also most widely known. Also, ELM is currently the only system that natively implements global config, while others are at best currently mapped to it via connectors – so obviously it is the low hanging reference for global config related conventions. Other than that, all the other profile guidelines are generic and driven from the need to support the use case.

I agree that we need to add failure handling to the guidelines based on the experience gained. I expect you to add the right text once we decide on how to write the guidelines for each profile.

Thanks

Eran