Date: Wednesday, 12 Aug 2009

Time: 8:00 AM Pacific, 11:00 AM Eastern, 5:00 PM Zurich
(contact Grant Larsen if you'd like to participate)

Agenda:

• Discuss completion of to-do items from previous meeting
• [Randy] Emphasys Group will be writing publish, search, retrieve scenarios for Architects.
• [Hari] Hari will be writing asset governance scenarios.
• [All] When writing scenarios, rank them in order of importance from your perspective (1 most impt; 5 least impt).
• [All] Review scenarios from Randy, Hari, Grant and be prepared to vote on 29 Jul 2009 on which scenarios should be included in version 1 of the REST specification.

Notes from Meeting

• Grant sent his regrets and asked Scott to lead the discussion today.
• The group discussed the work that Randy and Hari have done to update the scenarios.
• Hari will be adding additional details for the Priority 1 items this week. Scott mentioned that in discussions with Grant, it seems that Hari's top priorities are consistent with (and maybe variations of) the Publish, Search, and Retrieve scenarios that Grant initially outlined. One exception is the "Initiate review for asset(s)" scenario, which Grant believes should be considered a Priority 2 topic that gets dealt with in round 2 of the specification. Hari was happy to hear feedback on the priorities and will consider if Grant's suggestion to lower this particular scenario to Priority 2 can work for him or not.
• Jaimin indicated that the WebLayers team would like to offer some additional thinking on governance scenarios, more from a systematic point of view rather than an end-user action point of view. Scott created a link (AssetMgScenariosWebLayers) for this purpose. Jaimin agreed to have this complete by August 28.
• Steve Abrams remarked that the governance scenarios and their emphasis on retrieving and changing the state of assets was reminscent of other discussions that have come up in the Change Management and Requirements Management workgroups. He wondered whether we should think about this from a cross-domain perspective and will plan to raise that question at the OSLC workgroup leads call next week.
• Randy reminded the group of his mailing list post which questions whether the documented scenarios are bringing to light the right issues or not. The currect scenarios are end-user task focused, rather than focused on the tool-to-tool interactions and data flow that is required to accomplish the end user scenarios. Everyone was in agreement with Randy's observation. Scott suggested that the tool interaction could be the next logical step in the spec development and should accompany the early drafts of the spec. Scott pointed to the Estimation workgroup (MetricsHome, MetricsEMS10PrimerInitiating, MetricsModel) as a potential examples for how other workgroups have documented this tool-to-tool interaction.
• Scott suggested that the group needs to settle on the V1 scenario scope and move on to V1 spec authoring (Grant would like to have an early draft of the V1 spec by the end of August). Scott polled the group to get their sense. Jaimin suggested that we have to get the fundamentals of Publish, Search, and Retrieve in place as a baseline no matter what, and then can move on to address additional scenarios around governance. Hari, Randy, Steve, and Samit agreed and all voiced interest in driving forward (enough talk already!). Samit made a good point that the governance scenario work by GBS and WebLayers is important in the longer term and should be kept in mind even if not specifically tackled in the V1 spec -- i.e. we don't want to do anything in V1 that will preclude us from addressing those needs in V2.
• Hari asked for example templates for the specification and how the spec authoring would physically happen. Scott pointed to the CmSpecificationV1 topic as a template. Grant will take the lead as the primary author of the spec and will look for help and review from members of the workgroup and his own team.

To Do

• Lock and load on the V1 spec scope - assumed to be Publish, Search, Retrieve and including the Priority 1 variations from Hari's document (note discussion point above on one of those variations) - all, next meeting.
• Create first early draft of the specification and address the tool-to-tool interactions and data flows - Grant, end of August
• Complete details for the Priority 1 scenarios and close the loop with Grant on the priority of the "Initiate review of asset(s)" scenario - Hari, end of this week.
• Flesh out additional governance scenarios - WebLayers team, August 28.
• Take up the question of cross-domain focus on state and state management with OSLC leads workgroup - Steve, next week.

Attendees

BlackDuck

Citigroup

Emphasys Group

Randy Lexvold

IBM

Steve Abrams

Samit Mehta

Hari Padmanabhan

Scott Bosworth

Shell

StateStreet

WebLayers

Jaimin Patel