Call-in info: https://www.oasis-open.org/apps/org/workgroup/oslc-core/members/action_item.php?action_item_id=3688 (access restricted to OASIS members)
Chat room: http://webconf.soaphub.org/conf/room/oslc
Issue list: https://issues.oasis-open.org/browse/oslccore
- Scribe nomination
- Roll Call
Approval of July 23 minutes
- Next meeting August 20
- Actions from the previous meeting
- Jim A to ask Chet whether a spec that depends on core can go to public review before core does
- Martin S and Jim A to review issues list to see what can be closed, next week and ongoing
- Other business
- David Honey (IBM)
- Harish Krishnaswamy (Sofware AG)
- Jim Amsden (IBM)
- Martin Pain (IBM)
- Martin Sarabura (PTC)
- Nick Crossley (IBM)
- Jim Amsden
Jim Amsden (IBM)
Nick Crossley (IBM)
Martin Pain (IBM)
David Honey (IBM)
- Martin Sarabura
- David will write a proposal for the resolution of OSLCCORE-9 for review and potential vote next meeting
- Nick will write up a scenario describing how to finde the component LDPC - i.e., how to determine the usage of a particular LDPC
Jim will create a wiki page describing what information is capture in an OSLC2 ServiceProviderCatalog, and what information is available from an LDPC in order to determine the gap.
- Jim will propose additional LDPC OSLC properties in oder to close the above gap so that the same discovery information is available from either discovery approach
Jim will discuss ReSpec ownership and maintenance with Chet.
Chat transcript from room: oslc
[07:05] Martin Pain (IBM): Martin Pain joined
[07:08] Jim Amsden (IBM): turtle source for OSLC2 core namespace is in the open-services.net wiki
[07:08] Jim Amsden (IBM): this was used to generate the HTML and RDF/XML for the OSLC2 specs using XSLT
[07:09] Jim Amsden (IBM): the shapes were hand written in the HTML specs
[07:09] Jim Amsden (IBM): there are multiple versions of the XSLT file, not sure if these have all been merged.
[07:10] Jim Amsden (IBM): the same script may not have been used for all the OSLC2 specs, different domains may have used a different version of the XSLT
[07:10] Jim Amsden (IBM): OSLC3 is in better shape with ReSpec
[07:13] Harish (SoftwareAG): Harish to scribe today
[07:14] Harish (SoftwareAG): Any objections to approval of minutes of last meeting?
[07:14] Harish (SoftwareAG): No objections. Minutes approved.
[07:17] Harish (SoftwareAG): Review of TC documents - many recent changes.
[07:19] Harish (SoftwareAG): Update after checking with Chet - TCs can refer to specs not yet OASIS specs. Possible objections but it is up to the discretion of TCs to manage dependencies.
[07:19] Jim Amsden (IBM): OSLCCORE-20 Service provider should describe domain/scope OSLCCORE-9 Bootstrapping discovery OSLCCORE-25 Define a stable URI for OSLC Shape resources OSLCCORE-23 Should a ServiceProviderCatalog or ServiceProvider resource be an LDPC? OSLCCORE-28 Update ReSpec to support multiple vocabulary files OSLCCORE-26 Linking from Service resource to read-only LDPC Added a clause that the same information should be available through any discovery mechanism, SPC, Link or Prefer headers OSLCCORE-16 Discovery should include text about vocabulary discovery OSLCCORE-1 Ian to add scenario to https://wiki.oasis-open.org/oslc-core/DelegatedUIUseCases OSLCCORE-15 Allow client to request different icon sizes for resource preview OSLCCORE-18 link-guidance.html final editing issues
[07:20] David Honey (IBM): https://issues.oasis-open.org/browse/OSLCCORE-9?jql=project%20%3D%20OSLCCORE
[07:21] David Honey (IBM): https://issues.oasis-open.org/browse/OSLCCORE-20?jql=project%20%3D%20OSLCCORE
[07:30] Harish (SoftwareAG): It is difficult to figure out which query capability to use when several are available - what is the OSLC equivalent for a 'project area'?
[07:35] Harish (SoftwareAG): There are discovery problems when the data is partitioned in some way. UseCase - discovering a service provider using an identifier.
[07:36] Harish (SoftwareAG): with reference to unknown types
[07:46] Nick Crossley (IBM): Proposal: use oslc:details, when requested with content type RDF, to point to the 'project area' or equivalent
[07:47] Nick Crossley (IBM): oslc:details may still return a web page when requested with HTML or no specific content type
[07:47] Martin Pain (IBM): Two use cases: 1. A human user looking for the ServiceProvider (SP) a human-readable name 2. An automated process looking for the SP for a data partition for which it has the URI Case 1 Can be addressed by a selection dialog for SPs on the SP catalog. Case 2 can be addressed by using oslc:details to point to an RDF resource which the SP is describing the services of.
[07:48] Nick Crossley (IBM): The resource referenced by oslc:details MAY be an LDPC. It SHOULD have a dcterms:title. The title of the resource may be used to find a particular service provider
[07:51] Jim Amsden (IBM): David will update the proposal in the issue and we will schedule a vote for the next meeting
[08:03] Nick Crossley (IBM): Discussions of OSLCCore-9, Bootstrapping discovery. Is this a nice to have? Discussions about how this topic is related to, or orthogonal to, a decision as to whether or not ServiceProviderCatalog, ServiceProvider, and Service resources are also LDPCs.
[08:11] Nick Crossley (IBM): Here's the current language in the spec:Chat transcript from room: oslc
[08:11] Nick Crossley (IBM): Configuration Management providers MUST provide a single <a href="http://www.w3.org/TR/ldp/#ldpc">Linked Data Platform Container (LDPC)</a> for all components in that provider.</p> <p>This component container MUST be advertised as an <a href="http://open-services.net/bin/view/Main/OslcCoreSpecification#Creation_Factories">OSLC 2.0 Creation Factory</a> in the <a href="http://open-services.net/bin/view/Main/OslcCoreSpecification#Resource_Service">Service resource</a> for the configuration server.
[08:34] Nick Crossley (IBM): Nick is to write a scenario for discovery of the Configuration Management component LDPC