OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: OSLC CORE TC Minutes September 21, 2017


  • Jim Amsden (IBM)


  • Harish Krishnaswamy (Software AG)
  • Jim Amsden (IBM)
  • Martin Sarabura (PTC)
  • Nick Crossley (IBM)
  • Andrii Berezovskyi (KTH)
  • Jad El-Khoury (KTH)
  • Axel Reichwein (Ind)


  • David Honey LOA



  • Nick to create a committee note for clients of TRS servers
  • Nick to add version resolution to config mgmt spec based on feedback
  • Martin to update Wiki front page for new specs and roadmap

Chat transcript from room: oslc

[07:06] Martin Sarabura (PTC): https://wiki.oasis-open.org/oslc-core/Meetings/Telecon2017.09.14
[07:08] Jim Amsden: Minutes accepted
[07:08] Jim Amsden: Action items...
[07:08] Jim Amsden: TRS:
[07:09] Jim Amsden: Action: Nick to get refactored TRS spec read for TC review
[07:09] Jim Amsden: Axel offered to help
[07:10] Jim Amsden: document is currently split into files on Nick's desktop, needs to be completed and back into SVN for TC review
[07:11] Jim Amsden: Create a committee note for clients, using the content removed from the TRS server spec
[07:11] Jim Amsden: someone else could then contribute more effectively.
[07:11] Jim Amsden: Axel offered to help as soon as the spec is available
[07:12] Jim Amsden: Action: Martin to update Wiki front page for new specs and roadmap
[07:12] Martin Sarabura (PTC): https://issues.oasis-open.org/browse/oslccore
[07:12] Jim Amsden: All other former actions are in the issues list
[07:16] Jim Amsden: Axel tried to get bugzilla TRS, branch didnt contain all the necessary code. Doesnt think it works yet. Theres an older reference implementation too. Resource classes are now in core Bugzilla implements a TRS server,
[07:16] Jim Amsden: Libraries are now in Gerrit, and CQs are in progress.
[07:19] Jim Amsden: there is a CCM global configuration provider and several contributors. They different in the level of support for LDPC.
[07:20] Jim Amsden: Most implement the basic ability to contribute to a GC, they differ in the ability to create streams and baselines
[07:21] Jim Amsden: These implementations could be used as statements of use, but there is no single implementation that does all the MUST and SHOULD clauses.
[07:21] Jim Amsden: IBM GCM is close to a complete implementation. Has some gaps. Once the remaining technical issues are addressed...
[07:22] Jim Amsden: Change set lifecycle issue will be a new gap.
[07:23] Jim Amsden: One new CCM technical issue Nick will add once the issues and source have been moved to core.
[07:23] Jim Amsden: Came from customer feedback.
[07:24] Jim Amsden: re: version resolution
[07:24] Jim Amsden: After these two issues, get the RFP for the Config-Context header written
[07:25] Jim Amsden: waited for stable document reference for the header. Needs a CSD published for this.
[07:25] Jim Amsden: If the version resolution issue can be addressed, the CSD could also be a CSPRD.
[07:26] Jim Amsden: but public review is gated on addressing this issue.
[07:28] Jim Amsden: consider deferring RFP for Config-Context until we have CCM CSPRD to limit the number of publishes we have to do



PTC Logo

Dr. Martin Sarabura
Technical Fellow, Office of Research & Architecture

+1 519.502.4819



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]