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
>
CmMeetings08052009
(05 Aug 2009,
SteveSpeicher
)
(raw view)
---++ Date: Wednesday, 5 August 2009 Time: 12:00 PM Eastern, 9:00 AM Pacific, 6:00 PM Zurich<br />(contact SteveSpeicher if you'd like to participate) ---+++ Agenda: * Progress on extending participation - both as WG participants and implementations * 1.0 spec maintenance items * Feedback from implementations CmImplementationReports * CmSpecificationIssueTracking * 3 issues incorporated http://open-services.net/pipermail/community_open-services.net/2009-July/000082.html * 1 new _minor_ issue reported * Review of schema support in ClearQuest via REST * [[https://jazz.net/wiki/bin/view/Main/RcmRestCmApi#record_type][Jazz.net Wiki document detailing CQs schema support]] * Review of ScenariosMylyn * Progress on 2.0 specs * Prioritize scenarios * Define scope - CmArchitecturalDirectionV2 * Milestone plans ---+++ Minutes: Attendees: SteveSpeicher, JayGillibrand, SamLee, SamitMehta, MikKersten, SteveAbrams, AndreWeinand * Call for agenda changes, no changes * Progress on extending participation * Various initiatives started, following up with various levels of interests * 1.0 spec maintenance items review * no additional issues reported * no immediate action needed on new issue, will queue up for future cleanup * Reviewed CQ support of schema * Adds contribution to service provider document for URL for requesting collection of schemas * Each CQ "record type" has it's own URL which an XSD can be requested * The schemas are heavily cached (using HTTP caching constructs) * CQ provided extensions to XSD to support: read-only, URL's to get dynamic value sets, queryable * Schemas can be requested on a given resource instance, since constraints are dependent on current state and values. Can also be requested based on what action, as constraints are per state transition. * Primary scenario drivers for this support were for: * ScenariosMylyn : off-line task editing, task editor * Reporting scenarios * Some synchronization use cases * Discussion around needed schema support and right languages: XML Schema, RDF/S * [ACTION] WG to investigate which schema approaches are needed * Discussion around fixed vocabularies vs. open (schema discovered) * MikKersten described how some "fixed" concepts are required by Mylyn * Containment: Project and Component * States: open, working, closed * Attributes: priority, id, (didn't capture all) * [ACTION] SteveAbrams Look how scenarios may be satisfied with a more robust CM vocabulary, discuss at next OSLC CM call. * [ACTION] MikKersten to provide more details on how common vocabulary could be used in ScenariosMylyn * Next meeting 19-August-2009 12 ET
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 - 05 Aug 2009 - 17:43:02 -
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