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 CmRestApi? :
  • Content-Types supported for various resource types
  • HTTP Query Parameters supported:
    • CmRestApi#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:
  • Slide 2 .O {color:black; font-size:149%;} a:link {color:silver important;} a:active {color:#2DB6B3 important;} a:visited {color:#D18213 important;}

    Resource Creation - launching CM tool UI to do the job

  • Slide 2 .O {color:black; font-size:149%;} a:link {color:silver important;} a:active {color:#2DB6B3 important;} a:visited {color:#D18213 important;}

    Resource Reference Persistence - ordinality? 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