This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
Date: 21 January 2010
Time: 7:00 AM Pacific, 10:00 AM Eastern, 3:00 PM UK, 4:00 PM Frankfurt, 5:00 PM Haifa
Call In Number: (emailed)
Participation request: contact JimConallen

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, Brenda Ellis, David Johnson, Jonathan Harclerode, Scott Bosworth, Tom Piccoli, Jim conallen

The team reviewed the detailed examples on the scenarios page.

Brenda asked if we could explain use authorization in the specification better.

Alan asked which properties were returned on the ATOM responses.

Brenda asked about the link direction. We should be able to traverse it in both directions. This is a responsibility of the tool vendors.

Brenda asked if we could include history as part of the 2.0 spec.

Tom suggested that the examples show more than one link.

Brenda asked what happens we we delete a resource. That happens to the links to/from it, will there be dangling references. Jim said that it is the responsibilty of the service provider to handle this correctly, however good clients should always be prepard to encounter dangling links.

Topic revision: r1 - 04 Feb 2010 - 14:21:29 - JimConallen
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback