issue: Collection Document Fidelity

[Robert Sayre <mint@xxxxxxxxxxxxxxx>]

If my collection document lists a resource on another server as a 
member, MUST it track the state of that resource? If you send a DELETE 
to the other server, MUST the collection document remove it from its 
representation? Since PaceSliceAndDice3 allows a totally hip basically 
freeform version of collection membership, MUST all collections remove 
the document from its representation? Are 404s OK? If 404s just happen 
in the same way they do on the web, should users send complaints to 
client developers or server developers? Is it the responsibility of a 
client to at least HEAD every member resource to ensure that it's present?

"Hypermedia is the engine of application state", and it says I have ten 
posts, but really I only have nine because one is a 404.

Robert Sayre