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
>
MainOslcCommonArchitecture
>
ReportingHome
>
ReportingMeetings
>
ReportingMeeting20100222
(22 Feb 2010,
TackTong
)
(raw view)
---+ Reporting Meeting, 2010-02-22 <br />%TOC% See [[ReportingMeetings][Reporting Meetings]] for meeting logistics. ---++ Agenda and Minutes ---+++ Agenda 1 Update on [[ReportingMeeting20100222#action][outstanding actions]] 1 OSLC Core Spec Workgroup * [[http://open-services.net/pipermail/community_open-services.net/2010-February/000264.html][OSLC Community Announcement]] * [[ReportingHome#core][Reporting topics as related to Core Specification ]] 1 Extension to base OSLC resource * new properties * new non-OSLC defined resource 1 <span style="color: #000000" class="Apple-style-span"> </span> [[ImplementationScenario][Validation Implementation scenario]] - TackTong ---+++ Outstanding Action Items<a name="action" title="action"></a> * Action Item: TackTong and DragosCojocari to address the [[RSxUC][new use case based on RSx]] in spec. Note: Will be done later. * Will be tracked as a future item at http://open-services.net/bin/view/Main/ReportingHome#future * Action item: TackTong to sync up with SteveSpeicher on CM's use case on "schema" and align proposal to cover both Reporting and CM use cases. * Resource shape is now part of Core Spec. Both Reporting and CM WG will have representation at Core Spec WG. Thus, this action item will be addressed there. Closed. ---+++ Minutes *Attendees:* JamesMoody, DragosCojocari, SteveSpeicher, ScottBosworth, DaveJohnson, SebRose, ArthurRyman, XiangDongHu, BenjaminWilliams *Regrets:* VishyRamaswamy, JoanTouzet, StevePitschke 1. Discussed updates on Action items. 2. A [[http://open-services.net/pipermail/community_open-services.net/2010-February/000264.html][OSLC Core Specification WG]] is formed. Membership is open and member in the Reporting WG are encouraged to participate. 3. Discussed [[ReportingHome#core][Reporting topics as related to Core Spec]]. 4. Reporting Spec. will reference to Core Spec. as appropriate and may put more stringent conditios on top of Core Spec. as deemed required. 5. Reporting has no prior knowledge on domain resources. Thus, custom extensions (custom properties and custom OSLC resources) to OLSC resources are discovered via Resource Shape same as any properties and OSLC resources. 6. ImplementationScenario for the validating Query proposal was presented and discussed. First iteration of the implementation will be based on this scenairo. ---++ Next Week * Authentication * Query - what should Reporting say about currently Query proposal. * what is the behavior if service provider does not support Query * which features of Query are MUST/SHOULD/MAY? ---++ Comments Add your comments here: <br />%COMMENT%
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r3 - 22 Feb 2010 - 19:34:46 -
TackTong
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