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
>
AmHome
>
ArchMgmtMeetings
>
ArchMgmtMeetings20120202
(02 Feb 2012,
JimConallen
)
(raw view)
Date: *2 Feburary 2012* <br />Time: 7:00 AM Pacific, 10:00 AM Eastern, 3:00 PM UK, 4:00 PM Frankfurt, 5:00 PM Haifa, 7:30 PM Bangalore<br />Call In Number: (emailed)<br />Participation request: contact JimConallen ---++ Agenda 1 Update on core activities 1 Discuss priorities and themes for v 3.0 1 Introduce agenda topics * [[AMScenariosV3CRLinking][Change Request Linking]] * [[AMCoreV3Alignment][Alignment with OSLC Core 3.0]] * [[AMScenariosV3MDD][Long running processes like MDD transformations]] * [[AMResPropertiesV3][Common OSLC AM Resource Properties]] * [[AMResTypesV3][Common OSLC AM Resource Types]] * [[AMDiagramResType][OSLC AM Diagram Resource Type]] * [[AmPredefinedQuery][Predefined Queries]] * [[AMDeprecationLTR][Deprecate LTR]] 1 Discuss order of importance and schedule activities 1 Open up oppertunity for new meeting time(s). ---++ Attendance <br />Regrets: <br /><br />Atendees: Parham Vasaiely, Vishwanath Ramaswamy, John Crouchley, Alan Yeung, Steve Speicher, Clyde D. Icuspit, Gary Johnston, Jim Conallen ---++ Minutes Steve got us up to date on Core activities. He talked about work being done with the W3C recently in a workshop, with some of the core link life cycle concepts of resources (i.e. ui preview). OSLC Query and shapes however were out of scope. He discussed some of the future topics for core (found on the wiki). The Core is moving to a model where the individual domain specifications would evolve independently instead of trying to release with the core or other specs. Jim asked if there were any topics that our workgroup should avoid and Steve indicated that for the most part our work in all topics is appreciated, especially use case scenarios. Even prototype specs could be fruitful and useful as a means of explaning our concerns to the other workgoups. Parham, Clyde and John indicated that traceability and variablility are inmportant topics for us to discuss. John in particular pointed out the need to be able to get a the delta of changes (either as a first class resource or with links to the before and after change). This topic will feature prominantly in our future discussions. Jim took as an action item to reach out to those active in the discussion to document specific use case scenarios. They were forewarned :-) Gray correctly pointed out that the topic of long running transformations is a cross workgoup topic, however we can continue to work it in our workgoup, and then coorrdinate with the Automation and core workgroups. Parham and Vishy expressed an interest in the importance of the common properties and common types topics. Since this is a potentially long topic, we should try to do a lot of the work offline and schedule a meeting discussion when sufficient work has been completed on it.
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 - 02 Feb 2012 - 17:02:59 -
JimConallen
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