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
>
CmHome
>
CmMeetings
>
CmMeetings07212010
(21 Jul 2010,
SteveSpeicher
)
(raw view)
---++ Date: Wednesday, 21 July 2010 Time: *12:00 PM* Eastern, 9:00 AM Pacific, 6:00 PM Zurich (contact SteveSpeicher if you'd like to participate) ---+++ Agenda: * Progress on 2.0 spec * Review and resolve any CmSpecV2Issues on CmSpecificationV2 * Recent Changes: * Split of documents: CmSpecificationV2Samples, CmSpecificationV2Shapes, CmSpecificationV2ImplGuidance * drop partial update/patch as a MUST requirement * introduction of dcterms:abstract and removal of dcterms:name * UI Preview change of dcterms:name to oslc:shortTitle * updated oslc:usage to be task and planItem * rename of 5 relationship properties to better align with their usage * formatting rules: * RDF/XML, no additional definition needed * JSON, need to provide mapping * Determine whether to declare specification as entering "finalization" * Addition of whoami service to CmExperimental * Community updates * Minor updates to CmHome: intro text to be more broad, added link to V2 impl guidance * Implementation progress * Next meetings: * 4-Aug-2010 regular ---+++ Minutes: Attendees: SteveSpeicher, AndreWeinand, RobertElves, SofiaYeung, SamPadgett, SamLee, SamitMehta, BrianSteele, TomPoulin, DaveJohnson Regrets: ScottBosworth, MikKersten * Progress on 2.0 spec * Review and resolve any CmSpecV2Issues on CmSpecificationV2 * Recent Changes: * Split of documents: CmSpecificationV2Samples, CmSpecificationV2Shapes, CmSpecificationV2ImplGuidance * drop partial update/patch as a MUST requirement * introduction of dcterms:abstract and removal of dcterms:name * UI Preview change of dcterms:name to oslc:shortTitle * updated oslc:usage to be task and planItem * rename of 5 relationship properties to better align with their usage * formatting rules: * RDF/XML, no additional definition needed * JSON, need to provide mapping * no objections to these changes * Determine whether to declare specification as entering "finalization" * WG decided to defer entering finalization until July 28 to align with Core finalization and closing on 3 items: * JSON rules * Further updates to relationship meaning * Further clarification of state predicates * Review of finalization process: * Declared final once 2 service provider implementations have been completed and implementation reports have been given. * Spec edits are limited to 1 or 2 authors, edit approvals are reviewed by working group * Addition of whoami service to CmExperimental * Discussed alternatives: query language variables ($currentuser) vs. this approach. Leaning towards SP discovery of service as to not introduce new capabilities to the query syntax. * Need to clarify usage as state is not maintained on server (current user), though derived from request headers and http sessions.a * Community updates * Minor updates to CmHome: intro text to be more broad, added link to V2 impl guidance * Implementation progress * Rational CM products reported good progress on 2.0 based service providers * External WG members inquired about availability of these: beta, etc. * Continued adoption report by Oracle consuming 1.0 and planning to evaluate 2.0 * Next meetings: * 28-Jul-2010 regular (adding to declare entering finalization) * 4-Aug-2010 regular _Update as necessary with corrections_
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r6
<
r5
<
r4
<
r3
<
r2
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r6 - 21 Jul 2010 - 18:52:27 -
SteveSpeicher
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