SCM Meeting 2010-01-27

Agenda:

• Update on linking
• Continue listing common properties

Minutes:

Present: NickCrossley, PaulKomar, ScottBosworth, SteveSpeicher, DaveJohnson

Following last week's discussion about link information being returned from service discovery, Nick related the discussions he had with Ian, and the issue of discovering which service provides which links. Ian had suggested that we approach Scott Rich to ask what Jazz Foundation intends to do about this problem.

Nick asked Scott about Atlassian's possible involvement in OSLC, in particular for integration with the FishEye? and Crucible code review tools.

Since Steve had not been on the previous call where link discovery was discussed, Nick outlined that issue again, and asked if the CM workgroup had yet considered it; the response was that they had not. However, there had been some discussions of a related issue: given a URL for a resource - possibly from a property returned from a query - how can the client find the service description for the provider that owns the resource, so the client can find information on resource shapes, etc.? This reverse service discovery needs to be an agreed OSLC common feature.

There followed a long discussion of this cross-provider linking issue, bringing Dave up to date on our previous discussions.

Finally, we discussed media types, and whether each SCM resource type really needs its own media type (as for example the CM spec currently requires). Dave mentioned that the proliferation of media types was a concern, and that he would be addressing this soon.