• Review action items
  • RmSpecificationNeedsV2
• OLSC UI Preview investigation
  • UI Preview is a means for a consumer to fetch a representation of a resource that can be rendered for a user (e.g., in an iframe). How should OLSC RM resources present their UI Preview
  • Scenarios for UI Preview?
• AOB

Apologies: DominicTulley, GeorgeDeCandio

Attendees: IanGreen, NickKruk? , ScottBosworth, DaveJohnston? , JimConallen, PaulMcMahan,

Minutes:Discussion around need for there to be, for example, query could be a MAY not a MUST

Discussion around the proposed plan to focus on RM 1.0 functionality in a RM 2.0 specification which is compliant with OSLC Core. This was seen to be valuable and an important step in aligning the workgroup efforts around OSLC Core, as well as validating the OSLC Core specification.

IanGreen volunteered to collect current Jazz C/ALM link types with a view to standardizing them (or something like them) at OSLC. This would embrace V2.0 specification work from all current OSLC Workgroups, Simon's link types work from 2009.

Interesting discussion on how OSLC can define the scope of problems it is trying to address - where does tool-to-tool become ecosystem of tools and how do participants in the ecosystem know their role and the roles of other participants in that system.