Reporting Meeting, 2009-10-19

See Reporting Meetings for meeting logistics.

Agenda and Minutes

Agenda

1. Call for last minute agenda changes
2. Reminder to register for Reporting-specific mailing list at http://open-services.net/mailman/listinfo/oslc-reporting_open-services.net
3. Update on outstanding actions
4. Discuss Use Cases (ReportingUseCases)

Outstanding Action Items

Action Item: Scott Fairbrother to followup with CAST, Actuate, BusinessObject

• ScottFairbrother reported that business partners need to understand the value of the REST interfaces while direct DB access is readily available.

Action Item: TackTong to arrange off-line call to discuss and address this. (TackTong, ScottFairbrother, XiangDongHu) TackTong to consult ArthurRyman on his experience with the OSLC Software Estimation workgroup.

• TackTong sent email with rationale to ScottFairbrother and XiangDongHu.

Action Item: Tack Tong to followup with OSLC leads in other topics to solicitate external service providers.

• Email sent.
• Presented to Estimation and Measurement workgroup.

Action Item: Benjamin Williams to followup with InfoSphere Data Architect.

Action item: StevePitschke and BenjaminWilliams to draft this motivation section.

• Motivation section added to begining of ReportingUseCases

Action item: BenjaminWilliams to draft document gen. high level use case.

Action item: TackTong to add a terminology section.

• Terminology section added to ReportingUseCases.

Action item: Tack to update ReportingUseCases

• updated based on discussion.

Minutes

Attendees: TackTong JoanTouzet, SebRose, JamesMoody, ScottBosworth, MikKersten, StevePitschke, BenjaminWilliams, XiangDongHu, DragosCojocari

Regrets: SteveAbrams, ScottFairbrother, JimDaly?

1. Joan requested more information on REST. Ben will send out a link that would help. (Ben sent this link http://tomayko.com/writings/rest-to-my-wife)

2. The following sections in the ReportingUseCases were discussed and agreed.

• Motivation
• Terminology
• High Level Use Cases
  • 1. Monitor defects arrival trend
  • 2. Produce a compliance document listing out all requirements of a product release according to the organisation's document standards.
• Functional Use Cases
  • 1. Reporting system retrieving data from a resource service provider for loading into a data warehouse.
  • 5. Reporting system retrieving data from a resource service provider for operational reporting.
  • 6. Reporting system retrieving data from a resource service provider for document generation.

3. Action item: SteveSpeicher will lead drafting of high level use case 3 for C/ALM. BenjaminWilliams and TackTong to participate.

4. Action item: StevePitschke will investigate alternatives for resource schema. (XML schema vs. RDF schema or others)

5. The workgroup agreed this assumption: The reporting system does not have any knowledge on any special domains. It will base on resource schema to understand the format of the resource data.

Next week

• ReportingUseCases discussion - High level use case 3 - C/ALM
• Resource schema discussion

Comments

Add your comments here: