Joe Gregorio wrote:
Allowing editing via multiple representations seems like an edge case and not something the core protocol should be optimized for, but I don't think it is disallowed either. That is, as long as you list content/@src as the 'primary' edit location you can list all the other representations via link/@rel='edit-media' links.
What does primary edit location mean though? Why should there be a primary representation of the calendar data? these all feel like peers to me. I guess I'm not understanding why specifying content/@src is mandatory for media elements. Any APP client that wants to manipulate the resource is going to ignore the content/@src uri and instead focus its operations on the "edit-media" links. IMO mandating content/@src seems to limit some edge cases for no particular gain.
Rob
