Date: Wednesday, 4 February 2009

Time: 12:00 PM Eastern, 9:00 AM Pacific, 6:00 PM Zurich
(contact SteveSpeicher if you'd like to participate)

Agenda:

• Review Scenario Contribution:
  • ScenariosMylyn
• Specification Contribution CmRestApiV1:
  • Content-Types supported for various resource types
  • HTTP Query Parameters supported:
    • CmRestApiV1#queryoverview

    • Parameter	Value	Description	Sample
      {property}	Value of property to be matched (on GET)	Resource's property name and specified value to filter a collection on	/changerequests?state="opened"
      oslc.content-type	Valid MIME type	Client's desired response content type	/changerequests?oslc.content-type=application/xml
      oslc.properties	Comma-separated list of requested properties	Used to retrieve only desired properties	/changerequests?oslc.properties="state,id,headline,owner"
      oslc.inline	Comma-separated list of properties to inline	For specified properties, provide inline content instead of references	/changerequests?oslc.inline="owner"
      oslc.search-terms	Full text search terms	Search terms for full text search	/changerequests?oslc.search-terms="server crash"

• Key Issues:

  • Resource Creation - launching CM tool UI to do the job

  • Resource Reference Persistence - cardinality? directional?
  • Simple (yet powerful) GET-based query - SPARL,CQL,Lucene,???
  • Resource Shape Definition - XSD for creation and UI
  • Service Discovery - need a service description document?
• Work on scenario elaboration:
  • DefectScenario
  • CmScenariosAgilePlanningOfChangeRequests

Minutes:

Attendees: Steve Speicher, Steve Abrams, Andre Weinand, Scott Bosworth, Randy Vogel, Sam Lee, Carolyn Pampino, Mik Kersten

Minutes:

• Introduction of new member: Mik Kersten
• Review of ScenariosMylyn with feedback:
  • Cross-task references cardinality is 0-1, need to be 0-n and stored in both task repos
  • Separate out scenarios where schema (shape definition of tasks) is needed
  • Organize scenarios as 3 different priority levels to help drive the spec development
  • Add scenarios for:
    • off-line support
    • details on query for modified by date range
    • fuzzy search of fine possible duplicates
• Review of spec CmRestApiV1:
  • Mik acknowledged ATOM as a workable collection response format
  • except for {property} concensous on query parameters
• Actions for next meeting:
  • All review/contribute to specs and supporting scenarios
  • Approve specific specification approaches and supported scenarios for first round of spec
• Next meeting: Feb 18, 12-1 Eastern