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
>
QmHome
>
QmMeetings
>
QmMeetings20090930
(06 Nov 2009,
PaulMcMahan
)
(raw view)
---++ Date: Sep 30 2009 ---+++ Agenda: * Follow up on review comments from previous meeting * Reworded [[QmRestApiV1#Get_a_resource][language about handling ETag header]] * Handling of namespace prefixes in [[QmRestApiV1#Selective_Properties][selective properties]] * Reversal of position on prescribed namespace prefixes * Lack of standard for compact representation of QName * Added query support * [[QmQuerySyntaxV1][Quality Management Query Syntax]] * [[QmRestApiV1#Get_a_collection_of_QM_resources][Collections]] (for query results) * [[QmRestApiV1#Pagination][Pagination]] * Draft specifications * [[QmRestApiV1][Quality Management REST API]] * [[QmServiceDescriptionV1][QM service discovery & description]] * [[QmResourceDefinitionsV1][Quality Management Resource Definition]] * [[QmQuerySyntaxV1][Quality Management Query Syntax]] * Delegated Resource Selection and Creation (no draft available yet) * Proposed schedule for 1.0 deliverables * 8/28 scenarios (done) * 10/1 draft (today) * 11/1 final * Please review drafts and provide feedback on the QM email list oslc-qm@open-services.net ---+++ Minutes: Attendees: IngridJorgensen, JimConallen, ScottBosworth, PaulMcMahan, MikeSaylor, FarizSaracevic, SteveAbrams, PaulMcMahan * Reviewed recent changes/tweaks to [[QmRestApiV1][REST API]] * Query API and selective properties support now require predefined XML namespace prefixes (reversal from previous position) * It would be helpful for the spec to clarify where these predefined prefixes are used * Discussions about OSLC Common specifications are underway. QM is interested in participating in this discussion and adopting these common specs when they are ready. * Q: How much has QM REST API drifted from CM REST API? A: Hardly at all. The main difference is QM spec does not include JSON. * QM query syntax based on CM V1 query syntax spec except full text search * Concerns raised about lack of full text search support * Paul to investigate full text support * The testplan and testcase resource definitions only contain basic properties from Dublin Core * This is intentional for V1 spec. Future versions of the spec are expected to add more QM specific properties * Q: Should the resource definitions contain any properties related specifically to requirements so that the use cases are properly covered? A: The [[QmRestApiV1#Managing_multi_valued_properties][Multi-valued properties]] portion of the REST API spec satisfies the use case but in a generic way. A future version of the resource spec may add properties that describe the cross-OSLC relationships more concretely.
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 - 06 Nov 2009 - 22:34:04 -
PaulMcMahan
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