Great! I'll summarise where they are and do a last call.
On 22/10/2005, at 9:52 AM, Tim Bray wrote:
On Oct 22, 2005, at 8:40 AM, Mark Nottingham wrote:
You seem to be saying that because link/@rel="self" was designed
for a specific purpose, and even though its definition is quite
descriptive (its definition *only* says it should be used to link
to the current document; -11 says nothing about subscription) it
should be the only way defined to do subscription.
Agreed that the description could be better. What I'm actually
saying is "since we already have a way to do subscription, we don't
need to invent another." Also that the problem of pointing from
the static/archived version of a feed to the dynamic/subscribable
one is a related but different problem, and the one that you ought
to be solving.
OTOH, I'm happy to make this relation more declarative. How about:
- Attribute Value: current
- Description: A URI that, when dereferenced, returns a feed
document containing the most recent entries in the feed.
- Expected display characteristics: Undefined.
- Security considerations: Automated agents should take care
when this relation crosses administrative domains (e.g., the URI
has a different authority than the current document).
Thank you. +1 -Tim
--
Mark Nottingham http://www.mnot.net/
