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.

Date: 23 August 2010


  • spec issues resolved since last workgroup meeting
  • Version 1.0 compatibility
  • Collect additional feedback from work group on current draft spec


Attendance: IngridJorgensen, PaulMcMahan, ScottFairbrother, PaulSlauenwhite, ScottBosworth, TomNeal?

  • Reviewed the items marked as RESOLVED in the spec issues page. Workgroup agreed CLOSE them.
  • Discussed the approach for backwards compatibility with the V1 specification. The desire is to provide as much backwards compatibility as possible without requiring V2 clients to send the OSLC-Core-Version http header. The language in the QM spec is now more instructive on how the Accept headers will be interpreted. Service providers that need to provide compatibility with both V1 and V2 consumers can use the qm specific media types defined in the V1 spec as a first hint. And since application/rdf+xml was not used in the V1 spec it is a clear signal that the consumer supports V2. The gray area is when the content type is application/xml. In that case the service provider may choose to respond with V1 content unless the explicit OSLC-Core-Version header indicates otherwise.
  • Discussed finalization of the spec. The workgroup is satisfied that all of the issues that were raised have been resolved and that the spec is adequate for the V2 scenarios. During finalization stage the spec will use a more tightly controlled access control list for write permission. The only changes allowed during this phase would be for typos, clarifications where needed, or based on concerns raised by the broader OSLC community such as implementers of the spec.
Topic revision: r2 - 25 Aug 2010 - 20:47:16 - PaulMcMahan
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