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-03-15


See Reporting Meetings for meeting logistics.

Agenda and Minutes

Agenda

  1. Update on outstanding actions
  2. Update on Implementation - a consumer POC proposal
  3. Query
  4. Authentication
  5. Resource Shape

Outstanding Action Items

  • Action item : ArthurRyman to add oslc.properties=* and oslc.select=* to the Query Proposal for the Core Spec.
    • already in Query spec.
  • Action item : TackTong to update the proposal to set the low bar as oslc.properties/select=* and paging.
    • done.
  • Action item : TackTong to send the update proposal for Query for review via email prior to next week's call.
    • email sent and no further feedback received.

Minutes

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

Regrets: VishyRamaswamy

1. Action items were discussed.

2. TackTong gave a brief update on implementation.

3. Query Spec. was further discussed.

  • Need clarification on what oslc.properties=* and oslc.select=* would return.
    • oslc.properties=* and oslc.select=* MUST return at least those properties advertised by Resource Shape Resource, but MAY have additional ones. Reporting consumers MUST tolerate these additional unknown properties. (Spec. updated accordingly)
    • Action Item : ArthurRyman to add semantic clarification of oslc.properties=* and oslc.select=* to Query in Core Spec.
  • A link to Paging in Core Spec. is added to the clause for supporting paging.
  • How OSLC service responds with error should be defined in Core Spec.
  • "OSLC Resources SHOULD have a property dc:modified for modification timestamp." was discussed. A proposal was made to make it a MUST. After discussion, it was agreed to remain as SHOULD.
  • There were no more objection and comments on ResourceQuery and thus considered consensus reached for ResourceQuery.

4. Authentication was partially discussed.

  • Will continue discussion in next call.

Next Week

  • Authentication
  • Resource Shape

Comments

Add your comments here:

 
Topic revision: r3 - 15 Mar 2010 - 23:17:39 - 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