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
>
ReportingMeeting20100322
(23 Mar 2010,
GaoWeibin
)
(raw view)
---+ Reporting Meeting, 2010-03-22 <br />%TOC% See [[ReportingMeetings][Reporting Meetings]] for meeting logistics. ---++ Agenda and Minutes ---+++ Agenda 1 Update on [[ReportingMeeting20100322#action][outstanding actions]] 1 Query Resource * as discussed and agreed in previous calls - ResourceQuery * For each resource type that an OSLC Service wants to support for reporting, the OSLC Service *MUST* provide a Query Resource for a collection of resource of that resource type, and *MUST* support the OSLC Query Syntax for that Query Resource. 1 Resource Shape Resource * as defined in [[http://open-services.net/bin/view/Main/OSLCCoreSpecDRAFT?sortcol=table;table=up#Resource_Shape_Resources][Core Spec.]] * For every Query Resource that an OSLC Service provides for reporting, that *MUST* be corresponding Resource Shape Resources for those resources in the Query Resource. 1 Authentication * as defined in [[http://open-services.net/bin/view/Main/OSLCCoreSpecDRAFT?sortcol=table;table=up;up=#Authentication][Core Spec]]. * What is defined in Core Spec is sufficient for Reporting. 1 Service Resource * as defined in [[http://open-services.net/bin/view/Main/OSLCCoreSpecDRAFT?sortcol=table;up=#Service_Resources][Core Spec]]. * An OSLC Service *SHOULD* have queryCapability defined in Service Resource for all Query Resources intended for Reporting. * A Query Capability *MUST* provide Resource Shapes (oslc:shapeURI) to describe the resources that can be queried by the capability. 1 Resource Representation * as defined in [[http://open-services.net/bin/view/Main/OSLCCoreSpecDRAFT?sortcol=table;table=up;up=#RDF_XML_Representation][Core Spec]]. * "An OSLC Service *MUST* provide RDF/XML representations of all OSLC Defined Resources" as defined in Core Spec. is sufficient for Reporting. 1 Deletion * Reporting client sends query to get resource URL (or an unique identifier if exist) for all current records (excluding hard and soft deleted). It would be reporting client's responsibility to map out what has been deleted in its data repository. ---+++ Outstanding Action Items<a name="action" title="action"></a> ---+++ Minutes *Attendees:* JamesMoody, DragosCojocari, JeromeMathieu, SebRose, PaulMcMahan, ScottBosworth, XiangDongHu, ArthurRyman, BenjaminWilliams *Regrets:* VishyRamaswamy, GaoWeibin 1. The followings were discussed and agreed. 1 Query Resource * For each resource type that an OSLC Service wants to support for reporting, the OSLC Service *MUST* provide a Query Resource for a collection of resource of that resource type, and *MUST* support the OSLC Query Syntax for that Query Resource. 1 Resource Shape Resource * For every Query Resource that an OSLC Service provides for reporting, there *MUST* be corresponding Resource Shape Resources for those resources in the Query Resource. 1 Authentication * What is defined in Core Spec is sufficient for Reporting. 1 Service Resource * An OSLC Service *MUST* have queryCapability defined in Service Resource for all Query Resources intended for Reporting. * A Query Capability *MUST* provide Resource Shapes (oslc:shapeURI) to describe the resources that can be queried by the capability. 1 Resource Representation * "An OSLC Service *MUST* provide RDF/XML representations of all OSLC Defined Resources" as defined in Core Spec. is sufficient for Reporting. 1 Deletion * Reporting client sends query to get resource URL (or an unique identifier if exist) for all current records (excluding hard and soft deleted). It would be reporting client's responsibility to map out what has been deleted in its data repository. 2. Paging were discussed further. * Collection Resource Shape is not clear in Core Spec. Consensus is that it should be in Core Spec. * Action Item: TackTong to comment on Core Spec requesting clarification on Collection Resource shape. Done. * Action Item: Revisit after clarification in Core Spec. and make sure Reporting requirements are met. - TackTong * There were discussion on the followings: * duplicates * missing records * changed records * resultset cache expired * Action Item: TackTong to comment on Core Spec. requesting consideration of these topics in the context of Paging. Done. * Action Item: TackTong to summarize discussion and continue discussion via email. ---++ Next Week * paging ---++ Comments Add your comments here: %COMMENT%
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r4 - 23 Mar 2010 - 01:40:03 -
GaoWeibin
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