Reporting Meeting, 2010-05-03

See Reporting Meetings for meeting logistics.

Agenda and Minutes

Agenda

1. Update on outstanding actions

2. Discuss logged issues in http://open-services.net/bin/view/Main/OSLCReportingV1Issues

3. Guidance for Form Based Authentication

4. Update on Implementation Validation

5. More Example based on Use Cases

• an example based on CM done
• should we do one for QM and RM
• RSxUC

Outstanding Action Items

Minutes

Attendees: JamesMoody, ArthurRyman, DaveJohnson, DragosCojocari, ScottBosworth, SebRose, PaulMcMahan, XiangDongHu

Regrets: SteveSpeicher

1. Reviewed logged V1 issues

• Action Item: TackTong to update Sequence Diagram with text description.
• Action Item: DaveJohnson to update Core Spec with SHOULD support for Paging.
• Action Item: TackTong to remove SHOULD support for Paging in Reporting Spec., since it is now SHOULD in Core.
• Action Item: TackTong to update Reporting Spec. to reflect changes in Core re: removing self-subject/multi-subject Query Capability.

2. TackTong proposed Reporting V1.0 Spec. entering Convergence. No objection registered from WG member present in the call.

• Action Item: TackTong to send email to the Reporting mailing list declaring Convergence.

3. Implementation

• JamesMoody reported no progress so far on RTC as a service provider due to other product works.
• XiangDongHu reported there are some progress on Insight as a Reporting Consumer, but nothing significant to show yet.
• Dragos reported that the RPE implementation as a Reporting Consumer will have to be postponed for at least two months.
• ArthurRyman mentioned the OSLC EMS implementation could be use a a service provider for Reporting.

4. Authentication

• Action Item: Draogos will draft the section on Guidance - Form-based Authentication.

5. More Examples

• PaulMcMahan indicated that OSLC QM V2 will have a use case on reporting
• ArthurRyman also mentioned that OSLC EMS could also be used as an example for Reporting.

Next Week

Comments

Add your comments here: