Agenda

1. Quickly summarize points from last meeting.
2. Review the detailed scenarios. We will make sure that all the essential scenarios are covered.

Minutes

Atendees: Alan Yeung, Andy Berner, Brenda Ellis, Ian Green, Jim Amsden, Jonathan Harclerode, Vishy Ramaswamy, Jim Conallen

Vishy asked if the rdf:Description element could be used to add properties to any of the elements in the resource format (i.e. dc:decription). We agreed that this could happen using the current resource format.

Andy said that unless there is a good reason not to use and rely on RDF, then we should.

Brenda asked if this specification covered access permissions. As an example Doors manages projects, and has admins and dbas, that are all part of a group. We need to manage these permissions as a group.

Andy pointed out that access control is on the resource, and not the API.

Ian stated that the OSLC does not address the security model, and this is done outside of the spec. Access control in general is not part of any of the specifications at the OSLC, however each specification states that the service should provide BASIC and OAuth, and use SSL.

Andy also suggested that we need to stress that the resources are just being exposed in this form, and that this may not be the actual form they are stored in.

Vishy asked how links were added. Jim said that we are using the simplest approach, a PUT with the modified properties is used to add and remove links. The entire document must be PUT back in order to determine what gets deleted.