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.

Reporting Meeting, 2010-02-01


See Reporting Meetings for meeting logistics.

Agenda and Minutes

Agenda

  1. Update on outstanding actions
  2. Paging for large data volume
  3. REST API - DragosCojocari

4. Reference implementation discussion

  • should we start looking into implementation validation of Query specification in the context of reporting?

Outstanding Action Items

Minutes

Attendees: SebRose, JamesMoody, DragosCojocari, SteveSpeicher, DaveJohnson, StevePitschke, XiangDongHu, ScottBosworth, PaulTasillo? , PaulMcMahan

Regrets: ArthurRyman, VishyRamaswamy

1. Paging will be defined in OSLC Core specification for consistency across domains. Reporting use cases requires "next page" defined in RDF/XML representation.

2. Authentication will be defined in OSLC Core specification for consistency across domains. Reporting use cases requires programmatic authentication.

3. Will start up a implementation workgroup to start reference implementation to validate the Query proposal.

  • fully aware that Query proposal is not finalized, but good enough for a start
  • will adjust a the spec evolving
  • will report progress to this WG on regular basis

Next Week

  • Core Specification (tentative)
  • Implementation Update

Comments

Add your comments here:


 
Topic revision: r2 - 01 Feb 2010 - 17:42:33 - TackTong
 
This site is powered by the TWiki collaboration platform 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