This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
AssetHome
>
AssetMgMeetings
>
AssetMgMeetings29Jul2009
(29 Jul 2009,
HariPadmanabhan
)
(raw view)
---++ Date: Wednesday, 29 July 2009 Time: 8:00 AM Pacific, 11:00 AM Eastern, 5:00 PM Zurich<br />(contact [[GrantLarsen][Grant Larsen]] if you'd like to participate) ---+++ <a name="Agenda"></a><a name="_Agenda_"></a> <a name="Agenda"></a><a name="Agenda_"></a> Agenda: * Discuss completion of to-do items from previous meeting * [<font color="salmon" class="WYSIWYG_COLOR">Randy</font>] Emphasys Group will be writing [[AssetMgScenariosEmphasys][publish, search, retrieve scenarios for Architects]]. * [<font color="salmon" class="WYSIWYG_COLOR">Hari</font>] Hari will be writing [[AssetMgScenariosIRam][asset governance scenarios]]. * [<font color="salmon" class="WYSIWYG_COLOR">All</font>] When writing scenarios, rank them in order of importance from your perspective (1 most impt; 5 least impt). * [<font color="salmon" class="WYSIWYG_COLOR">All</font>] 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* * The group felt that it would be too premature today to try to vote on the services to be selected for initial specification * It was clarified that the scenarios help up understand the requirements for the services and serve as input for the service specifications * Randy walked through the Architect role scenarios he has added. One question that came up for the Publish scenario was regarding how much flexibility the publish scenario should provide for information model extensions needed. That is, in the publish scenario, how to distinguish and deal with information model changes that may be needed. E.g. publish value for an attribute that is not already defined for the type of asset being published. * Hari described the context for the GBS scenarios. There is a need to support operations on a set of assets rather than only one asset at a time. There was insufficient time for detailed walk through of any specific scenarios. * Blackduck are seeking management approval to add their scenarios/data <strong><font color="orangered">To Do</font></strong> * Present the different approaches for representing the resource (how to address information model flexibility needs) * Hari (GBS) to complete details for the identified scenarios * Additional scenarios to be added by others (Citi, Blackduck) * Clarify dependencies/requirements for the group to be ready to vote on the services to be specified initially, and vote ---++++ *Attendees* __BlackDuck__ Rich Sherrard __Citigroup__ __Emphasys Group__ Randy __IBM__ Steve Abrams Samit Mehta Hari Padmanabhan __Shell__ Edwin Freekenhorst __StateStreet__ __WebLayers__ John Favazza <strong><em><br /></em></strong>
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r3 - 29 Jul 2009 - 16:31:20 -
HariPadmanabhan
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
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