OSLC Core and Domains Meeting notes 20180321

["Jim Amsden" <jamsden@us.ibm.com>]

anonymous morphed
into Gray Bachelor
Jim Amsden
(IBM): Jim
Jim Amsden
(IBM): Jim Scribe
Jim Amsden
(IBM): Agenda:
Jim Amsden
(IBM): TRS, QM and Query spec
updates
Jim Amsden
(IBM): Open Project status
List of attendees:
David Honey (Persistent/IBM), Gray Bachelor, Gray Bachelor1, Jim Amsden
(IBM), anonymous
Jim Amsden
(IBM): TRS - Nick was going
to address MUST about implementing TRS order. There are some technical
challenges conforming to this.
Jim Amsden
(IBM): Nick might provide
some implementation guidance to be tolerant of small windows in which TRS
might not be strictly correct
David Honey
(Persistent/IBM): https://github.com/oasis-tcs/oslc-core/issues/20
Jim Amsden
(IBM): QM done with updates.
Alignment on v2 vs. more documentation consistent with RM, CM. No remaining
open items
Jim Amsden
(IBM): Ready for public review
Jim Amsden
(IBM): Action: Jim to prepare
published documents for public review.
Jim Amsden
(IBM): Question: should we
do this in the context of the Domain TC, Core TC or Open Project
Jim Amsden
(IBM): If we want to go to
public review now, the only option is Domains TC
Jim Amsden
(IBM): Action: Jim to ask
Chet what he would like us to do
Jim Amsden
(IBM): From Steve Gerdt:
1) The Entity CLA should be signed
by an IBM exec - could be an exec closest to this contribution activity.

2) Once this ongoing contribution
proposal is approved, individual CLA signees would simply need their mgr
ok to be included and should coordinate with the IBM leader of this contribution
activity. Does the OASIS CLA setup require updating the entity CLA for
a current list of IBM contributors? 

3) You'll need to discuss with legal
on the contractor setup. Whether it's a "work for hire" is a
key question.

Jim Amsden, Senior
Technical Staff Member
OSLC and Linked Lifecycle
Data
919-525-6575