< Return to Calendar Previous | Next
 OSLC Domains TC Weekly Meeting (Conference Call) |
|
| Name | OSLC Domains TC Weekly Meeting (Conference Call) |
| Time | Thursday, 26 July 2018, 09:30am to 10:00am EDT
(Thursday, 26 July 2018, 01:30pm to 02:00pm UTC) |
| Description | Metting URl: https://ibm.webex.com/join/jamsden Chat Room: http://webconf.soaphub.org/conf/room/oslc-domains |
| Minutes | Jim Amsden: https://www.oasis-open.org/apps/org/workgroup/oslc-domains/event.php?event_id=45864 Jim Amsden: Scribe: Gray GrayBachelor (IBM): Gray scribe List of members: Andrew Berezovskyi (KTH), GrayBachelor (IBM), Jim Amsden, Nick Crossley (IBM) GrayBachelor (IBM): Comments on last minutes GrayBachelor (IBM): None GrayBachelor (IBM): Minutes approved GrayBachelor (IBM): Last minutes are at https://www.oasis-open.org/apps/org/workgroup/oslc-domains/event.php?event_id=45864&referring_url=%2Fkws GrayBachelor (IBM): Attendees: Jim, Gray, Andrew, Nick GrayBachelor (IBM): ACTION: jim to check Andrew was recorded as in attendance for last 2 meetings GrayBachelor (IBM): ACTION: Regarding statements of use - need to form a list of orgs, academic and companies of OSLC users GrayBachelor (IBM): Updated ACTION: Regarding statements of CM use - need to form a list of orgs, academic and companies of OSLC users GrayBachelor (IBM): Jim has taken a look at the CM 3.0 Lyo implementation - its rather lightweight one 1 property, only LDP basic container - could be used for testing (used with bluemix/IBM Cloud OSLC testsuite Jim Amsden: "Statement of Use", with respect to a Committee Specification or Project Specification, is a written statement that a party has successfully used or implemented that specification in accordance with all or some of its conformance clauses, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations. The Statement of Use must be made to a specific version of the Specification and must include the Specification's approval date. The party may be an OASIS Member or a non-member. In case of a non-member, the Statement of Use must be submitted via the Technical Committee's or Project Governing Board's comment facility. A TC or PGB may require a Statement of Use to include hyperlinks to documents, files or demonstration transcripts that enable the committee's members to evaluate the implementation or usage. A Statement of Use submitted to the TC or PGB must be approved by TC Resolution or PGB action as an acceptable Statement of Use with respect to the Specification. A party can only issue one Statement of Use for a given specification. When issued by an OASIS Organizational Member, a Statement of Use must be endorsed by the Organizational Member's Primary Representative. The TC can require more data to support the SoU - links to an implementation or to documentation or etc. Also, the SoUs from OASIS organizational members must be approved by the Primary Rep. GrayBachelor (IBM): Jim looked into the statements of use and has loo GrayBachelor (IBM): We have control of what constitutes statements of use Jim Amsden: Dimensions for consideration in statements of use: Jim Amsden: coverage Jim Amsden: OSLC 2 and/or 3 Jim Amsden: validated test cases Andrew Berezovskyi (KTH): W3C approach to this: https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/reports/ldp.html but is likely too much for us now GrayBachelor (IBM): Validated test case would be to show some level of compliance Andrew Berezovskyi (KTH): https://docs.google.com/spreadsheets/d/13ow_XZ84fjbd_TBI61X75o3r6cua_SAoY96EDbObryE/edit#gid=0 Andrew Berezovskyi (KTH): DDS Andrew Berezovskyi (KTH): OPC-UA Andrew Berezovskyi (KTH): WoT GrayBachelor (IBM): AM is ready for review |
| Agenda | Weekly meeting to facilitate migration of OSLC 2.x domain specifications from open-services.net to OASIS. This meeting follows the OSLC Core TC meeting. |
| Submitter | Mr. James Amsden |
| Group | OASIS OSLC Lifecycle Integration for Domains (OSLC Domains) TC |
| Access | This event is visible to OASIS OSLC Lifecycle Integration for Domains (OSLC Domains) TC and shared with
|