OSLC OP Meeting minutes (Apr 28, 2022)

Chairs: Jim Amsden, Andrew Berezovskyi

Attendees: Jim Amsden, Andrew Berezovskyi, Jad El-khoury, David Honey, François-Régis Jaunatre (aka Frej).

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

Agenda

NA

Minutes

Updates:

Updated the Core PN to fix a link in response to https://issues.oasis-open.org/browse/TCADMIN-4135.
AM COS review period started.

Impact call discussion:

Stable clause numbering needed if we are to reference them from profile specs.
Profile scope need to be defined.
How about Abstract Profiles, or, rather, Generic Profiles?
- Parametrized by a resource type.
- Can be reused.
- Prevents extra work for vendors.
One extreme is 1 profile per MAY/SHOULD clause. Not helpful for determining what capabilities are achievable.
Need to cover use-cases
- UI linking
  - For example, cannot create an oslc_rm:parentOf link from Jazz to Polarion resources.
- API CRUD manipulation
- TRS exposure (eg for Jazz Eng Insights)
Full lifecycle of a profile should be considered to define a useful profile
- Eg on the first linking profile
- Requirements, use-case, API, testing?
- Adopt BDD approach, even if not executable
Market segments for the OSLC Profile users
- Tool purchasers
- Vendors

Action items

Invite Ed to the impact call