Reporting Meeting, 2010-03-22

See Reporting Meetings for meeting logistics.

Agenda and Minutes

Agenda

1. Update on outstanding actions
2. 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.
3. Resource Shape Resource
   • as defined in 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.
4. Authentication
   • as defined in Core Spec.
   • What is defined in Core Spec is sufficient for Reporting.
5. Service Resource
   • as defined in 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.
6. Resource Representation
   • as defined in Core Spec.
   • "An OSLC Service MUST provide RDF/XML representations of all OSLC Defined Resources" as defined in Core Spec. is sufficient for Reporting.
7. 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

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.
2. 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.
3. Authentication
   • What is defined in Core Spec is sufficient for Reporting.
4. 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.
5. Resource Representation
   • "An OSLC Service MUST provide RDF/XML representations of all OSLC Defined Resources" as defined in Core Spec. is sufficient for Reporting.
6. 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: