OSLC Core Meeting October 27, 2010

Last week's meeting

Meeting logistics

See the OslcCoreMeetings for more information, more dial-in numbers and on-line meeting information.

• Conference Access
  • Toll free: 1-866-423-8350
  • Toll: 1-719-387-8273
• Participant passcode: 558663

Online meeting:

• For IBM employees, use the following link:
  https://lli.ibm.com/meeting/join/?schedid=4446009 (IBM intranet authentication required)

• For people outside IBM, use the following link:
  https://apps.lotuslive.com/meetings/join?id=4446009

Agenda

Review actions taken since last meeting

• Clarified behavior when query is specified incorrectly by adding to the Query Syntax section a sub-section called Query Specification Errors with the following text: "If there is an error in the specification of the query, whether the query is specified by key=value pairs in the HTTP GET URL or key=value pairs in the body of an HTTP POST, then the provider MUST respond with an error. The error response should be an HTTP 400 Bad Request error and an explanation of the error in the OSLC Error Response format (see Error Responses below)."

• Fixes in the Representation guidance:
  • Fixed lingering RDF/XML reference in XML section
  • Now use content-types in the section titles for the sake of clarity
  • In the Atom rule 1.4, don't say MUST

• Promoted Representation and Link Guidance to appendices of Core spec
  • Moved Representations Guidance into the Core Spec as Appendix B and Link Guidance in as C. The old appendices B, C and D are now example pages, linked to from the new Appendix B. Here's the structure of the Core spec now:
    • Main Spec - http://open-services.net/bin/view/Main/OslcCoreSpecification
      • Query Syntax Spec - http://open-services.net/bin/view/Main/OSLCCoreSpecQuery
      • Appendix A - http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA
      • Appendix B - http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixRepresentations
        • http://open-services.net/bin/view/Main/OSLCCoreSpecRDFXMLExamples
        • http://open-services.net/bin/view/Main/OSLCCoreSpecJSONExamples
        • http://open-services.net/bin/view/Main/OSLCCoreSpecTurtleExamples
        • http://open-services.net/bin/view/Main/OSLCCoreSpecAtomExamples
      • Appendix C - http://open-services.net/bin/view/Main/OslcCoreSpecAppendixLinks

• Normative vs. Informative... need some more time on this

New topics

• Update on Test Suite
• Should UI Preview be considered part of Core spec? As Appendix or like Query Syntax?

Minutes

Attendees and notes from the meeting

Attendees

• DaveJohnson
• MikeLoeffler
• ScottBosworth
• JimConallen
• ArthurRyman

Topics discussed

• AI Dave: Include UI preview in Core as outline heading, but with link to separate document
• AI Dave: Dave to propose way to mark spec sections as normative vs. informative