Joe Cheng wrote: > > Now, Steven indicates that their implementation will not > > include the tombstone by default. Clients that want > > tombstones would have to ask for them explicitly. > > This doesn't belong in the implementation, it belongs in the spec. > (Would this discussion even be taking place if opt-in had > been in the spec from the start?) I have advocated HTTP > headers for opt-in the past, but to avoid caching problems it > seems like a link relation would be better.
What kind of caching problems are you thinking of? - Brian
