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
>
PmHome
>
MetricsHome
>
MetricsMeetings
>
MetricsMeeting20100305
(31 Mar 2010,
ArthurRyman
)
(raw view)
---+ Estimation and Measurement Telecon, 2010-03-05 %TOC% See [[MetricsMeetings#Weekly_Meeting_Logistics][Weekly Meeting Logistics]] for telecon information. [[MetricsMeeting20100129][Previous telecon 2010-01-29]] [[MetricsMeeting20100402][Next telecon planned for 2010-04-02]] ---++ Attendees AndyBerner, ArthurRyman, DaveJohnson, LawrencePutnamJr ---+++ Regrets ScottBosworth ---++ Minutes ---+++ 1. Review of [[MetricsEMS10RestApi][EMS 1.0 REST API]] DaveJohnson is currently editing the [[OslcCore][OSLC Core]] specification that all workgroups should adopt. The current [[MetricsEMS10RestApi][EMS 1.0 REST API]] specification contains some material that should be replaced with references to the OSLC Core specification when that is finalized. ---++++ [[MetricsEMS10RestApiArchitecture][Architecture]] ArthurRyman reviewed the [[MetricsEMS10RestApiArchitecture][Architecture]] page. The main issue that requires further discussion is how multiple servers should collaboration. The current specification makes the simplifying assumption that all resources for a given project are stored in one server. This allows searching and baselining to be performed easily. In practice, there may be several servers, e.g. there may be one for PPM and one for estimation, or there may be two for estimation. The specification should clearly state where the assumption of a single server is used, and possibly relax this constraint or describe how multiple servers should work together. In some cases this may cause additional work on the part of the consumer. ---++++++ ACTION: ArthurRyman will add a section on multiple servers to the Architecture page and add appropriate clarifications throughout the specification. LawrencePutnamJr said that this type of review is better performed for QSM by AndrewCanham, who will participate in the reviews going forward. AndyBerner offerred to help AndrewCanham get up to speed on the spec. ---++++++ ACTION: LawrencePutnamJr will ask AndrewCanham to review the specification. ---++++ [[MetricsEMS10RestApiDesign][Design]] ArthurRyman reviewed the [[MetricsEMS10RestApiDesign][Design]] page. This page describes the general resource design, general usage of HTTP methods, and aspects not covered by this specification. No issues here. We expect further discussion on the applicability of some HTTP methods in some cases. ---++++ [[MetricsEMS10RestApiDataModel][Data Model]] ArthurRyman reviewed the main [[MetricsEMS10RestApiDataModel][Data Model]] page. This page describes some standard properties which should be described in the [[OslcCore][OSLC Core]] specification. ---+++ 2. [[OslcQuery][OSLC Simple Query Specification]] ArthurRyman has been editing the [[OslcQuery][OSLC Simple Query]] specification which the EMS 1.0 specification depends on. It will be incorporated into the [[OslcCore][OSLC Core]] specification. ---+++ 3. Implementation Status ArthurRyman reported that a Rational product development team has taken over the EMS 1.0 prototype and will continue its development in order to provide implementation experience feedback to the workgroup. ---++ Comments Add your comments here: %COMMENT%
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 - 31 Mar 2010 - 14:27:18 -
ArthurRyman
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