[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes for CCM TC meeting on July 2nd
Here are the approved minutes from our meeting on June 18th, also posted at https://wiki.oasis-open.org/oslc-ccm/Meetings/Telecon2015.06.18.
Nick Crossley (IBM): Pre-meeting chat about rdf:type vs. dcterms:type vs RTC non-standard extensions to define work item types ...
Brian Steele (IBM): Brian is scribe for today
List of attendees: Brian Steele (IBM), Jim Amsden (IBM), Martin Sarabura (PTC), Nick Crossley (IBM)
Nick Crossley (IBM): List of attendees: Brian Steele (IBM), Jim Amsden (IBM), Martin Sarabura (PTC), Nick Crossley (IBM)
Nick Crossley (IBM): Minutes of previous meeting: https://wiki.oasis-open.org/oslc-ccm/Meetings/Telecon2015.06.04
Brian Steele (IBM): Minutes from the previous meeting were approved
Brian Steele (IBM): Change management status update: No progress other than Jim getting up to speed
Brian Steele (IBM): Configuration Management status update: No update committed but Nick has been doing some editing and working on a straw man implementation.
Brian Steele (IBM): Discussions ongoing about creation of baselines, how long they might take, and how the client interaction might work.
Nick Crossley (IBM): Decided to add an LDPC per baseline - post to that LDPC creates a new stream copied from that baseline
Nick Crossley (IBM): And an LDPC per stream - post to that LDPC creates a new baseline of that stream
Nick Crossley (IBM): Could add properties or link headers to those LDPCs indicating likely response time, but we feel clients MUST/SHOULD (which?) be prepared to handle http response code 202, so we do not need to define such properties or link headers yet
Nick Crossley (IBM): Keep the component-related LDPC of all configurations for that component, but make it read only.
Nick Crossley (IBM): while working on the Config Mgmt spec, I want a way to validate the consistency and coherency of the shape and vocabulary documents. Think of writing some form of validator, reusable for other spec editors. Could be Java program, bunch of XSLT, or just a set of SPARQL queries. For the latter, can I assume everyone has access to a triple store and SPARQL endpoint?
Jim Amsden (IBM): 4store.org is a very easy to use triple store with a SPARQL endpoint
Brian Steele (IBM): No other business
Brian Steele (IBM): Meeting is adjourned
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]