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
>
CmMeetings02042009
(28 May 2009,
ScottBosworth
)
(raw view)
---++ Date: Wednesday, 4 February 2009 Time: 12:00 PM Eastern, 9:00 AM Pacific, 6:00 PM Zurich<br />(contact SteveSpeicher if you'd like to participate) ---+++ Agenda: * Review Scenario Contribution: * ScenariosMylyn * Specification Contribution CmRestApiV1: * Content-Types supported for various resource types * HTTP Query Parameters supported: * CmRestApiV1#queryoverview * <table cellspacing="1" cellpadding="0" border="1"><tbody><tr><th>Parameter</th><th>Value</th><th>Description</th><th>Sample</th></tr><tr><td>{property}</td><td>Value of property to be matched (on GET)</td><td>Resource's property name and specified value to filter a collection on</td><td>/changerequests?state="opened"</td></tr><tr><td>oslc.content-type</td><td>Valid MIME type</td><td>Client's desired response content type</td><td>/changerequests?oslc.content-type=application/xml</td></tr><tr><td>oslc.properties</td><td>Comma-separated list of requested properties</td><td>Used to retrieve only desired properties</td><td>/changerequests?oslc.properties="state,id,headline,owner"</td></tr><tr><td>oslc.inline</td><td>Comma-separated list of properties to inline</td><td>For specified properties, provide inline content instead of references</td><td>/changerequests?oslc.inline="owner"</td></tr><tr><td>oslc.search-terms</td><td>Full text search terms</td><td>Search terms for full text search</td><td>/changerequests?oslc.search-terms="server crash"</td></tr><tr><td> </td><td> </td><td> </td><td> </td></tr></tbody></table> * Key Issues: * <p>Resource Creation - launching CM tool UI to do the job </p> * Resource Reference Persistence - cardinality? directional? * Simple (yet powerful) GET-based query - SPARL,CQL,Lucene,??? * Resource Shape Definition - XSD for creation and UI * Service Discovery - need a service description document? * Work on scenario elaboration: * DefectScenario * CmScenariosAgilePlanningOfChangeRequests ---+++ Minutes: *Attendees*: Steve Speicher, Steve Abrams, Andre Weinand, Scott Bosworth, Randy Vogel, Sam Lee, Carolyn Pampino, Mik Kersten *Minutes:* * Introduction of new member: Mik Kersten * Review of ScenariosMylyn with feedback: * Cross-task references cardinality is 0-1, need to be 0-n and stored in both task repos * Separate out scenarios where schema (shape definition of tasks) is needed * Organize scenarios as 3 different priority levels to help drive the spec development * Add scenarios for: * off-line support * details on query for modified by date range * fuzzy search of fine possible duplicates * Review of spec CmRestApiV1: * Mik acknowledged ATOM as a workable collection response format * except for {property} concensous on query parameters * Actions for next meeting: * All review/contribute to specs and supporting scenarios * Approve specific specification approaches and supported scenarios for first round of spec * Next meeting: Feb 18, 12-1 Eastern
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r5
<
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r5 - 28 May 2009 - 14:12:18 -
ScottBosworth
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