Discuss the proposal that the C/ALM scenarios describe a useful scope of work for inclusion within OSLC RM 1.0 specification, scheduled for completion September 2009.
Get agreement that the deadline for the 1.0 specification is acheivable and that we will work to that.
We agreed at the OSLC RM meeting held during RSC that scoping our work around scenarios was critical if we are to stay on track and deliver something useful.
The proposal is that the existing C/ALM scenarios define the scope of a first revision of the OSLC RM specification and that we want to deliver this specification by September 2009. Additionally, there is strong feedback from the OSLC CM workgroup that developing a practical, useful specification of the sort we are aiming for requires that the specification and one or more implementations proceed concurrently.
The C/ALM scenarios relating to RM can be found at http://open-services.net/bin/view/Main/RmScenarios. I suggest that participants review these scenarios in advance of our meeting on the Monday 22nd June.
Please be prepared to discuss any concerns you have over these scenarios at this meeting.
We will briefly discuss the guidance on resource design, in particular the use of JSON and Resource Description Framework (RDF) Resource Design.
Specification work for the proposal
Identify key specification needs for the C/ALM scenarios
A.O.B.
Minutes
Ian presented the attached slides (included here, with errors
Time-boxed activities were agreed, with an understanding that longer-term planning ensures short-term efforts add to coherent set of specifications which add-up to big problems. (See "groundrules", below.)
Brenda requests that we work on "groundrules" for the workgroup, and that these "rules" should emphasise the need for longer-term planning so that the OSLC RM effort is coherent over an extended period of time.
There was a suggestion the workgroup make use of web-based meetings so that wiki updates etc be carried out in real-time (for example, editing scenarios). There was also the suggestion that we could use tools other than the wiki where appropriate (for example www.websequencediagrams.com, or perhaps tools from other vendors).
We got as far as slide 10, then a combination of running out of time and telecon problems drew the meeting to a close. As a result, there are no action items.
Next meeting: 29th July 2009, 4pm BST (8am PDT, 11am EST, 5pm CET)
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use Ideas, requests, problems regarding this site? Send feedback