OSLC CORE TC Minutes Nov 15, 2018

[Martin Sarabura <martin.sarabura@gmail.com>]

Andrew Berezovskyi (KTH): https://github.com/oasis-tcs/oslc-core/wiki/!TC-work

Andrew Berezovskyi (KTH): Previous minutes: https://lists.oasis-open.org/archives/oslc-core/201811/msg00010.html

David Honey (Persistent/IBM): David is scribe.

David Honey (Persistent/IBM): Minutes accepted.

David Honey (Persistent/IBM): Jim has requested statement of use for DNG to George DeCandio, Dibbie Edwards, Daniel Moul.

David Honey (Persistent/IBM): We can have normative references to non-normative texts/documents.

Andrew Berezovskyi (KTH): http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part3-csdl/odata-v4.0-errata03-os-part3-csdl-complete.html

Andrew Berezovskyi (KTH): http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html

Andrew Berezovskyi (KTH): "In computing, Open Data Protocol (OData) is an open protocol which allows the creation and consumption of queryable and interoperable RESTful APIs in a simple and standard way. Microsoft initiated OData in 2007.[1] Versions 1.0, 2.0, and 3.0 are released under the Microsoft Open Specification Promise. Version 4.0 was standardized at OASIS,[2] with a release in March 2014.[3] In April 2015 OASIS submitted OData v4 and OData JSON Format v4 to ISO/IEC JTC 1 for approval as an international standard.[4]"

Andrew Berezovskyi (KTH): from https://en.wikipedia.org/wiki/Open_Data_Protocol

Andrew Berezovskyi (KTH): Multiple OASIS RESTful protocol standards is not a good thing.
it is not a bad thing
Do OData and OSLC payloads conform to the same metamodel?
no
Is the use of HTTP verbs consistent across both OData and OSLC?
yes
Is the use of HTTP headers consistent across both OData and OSLC?
only the ones defnd in HTTP
Are the set of query parameters consistent across both OData and OSLC?
no
Does discovery from a known service access point follow the same rules?
no

David Honey (Persistent/IBM): Having adapters OSLC -> ODATA or ODATA -> OSLC might provide integration between tools, but may be limited to overlapping features of both.

David Honey (Persistent/IBM): Jim has already responded to George's post about ODATA vs OSLC.

David Honey (Persistent/IBM): Config Mgmt issue from OSLC Domains meeting.

David Honey (Persistent/IBM): Spec does not provide for versioning capabilities in PLM.

David Honey (Persistent/IBM): Should address the issues before Config Mgmt spec goes to public review.

David Honey (Persistent/IBM): There are differences in approach in PLM - use of effectivity rules rather than selection sets.

David Honey (Persistent/IBM): Dynamic evaluation of members and versions in PLM vs selection sets in OSLC Config Mgmt.

David Honey (Persistent/IBM): Attendees from OSLC Fest should be involved with OSLC Config Mgmt. However, many are not OASIS members, so will probably requirement a separate telecon. Concerns about IPR (addressed by OASIS membership conditions) need to be considered.

David Honey (Persistent/IBM): Agenda for next meeting:

David Honey (Persistent/IBM): Version header

David Honey (Persistent/IBM): OSLC query - action Jim to produce committee spec draft.

David Honey (Persistent/IBM): Action for everyone before next week: Provide Github id and access token to Jim.

David Honey (Persistent/IBM): Some historic contributors to issues might not have Github ids. Can be migrated using Jim, but add text to indicate name of origina=l contributor.

David Honey (Persistent/IBM): Number of issues to migrate: 104 open of 180 total.

David Honey (Persistent/IBM): Tackle some issues in next meeting. TBD.

David Honey (Persistent/IBM): Meeting adjourned.

List of attendees: Andrew Berezovskyi (KTH), David Honey (Persistent/IBM), Jim Amsden, Martin Sarabura, anonymous, ian green