Re: PaceContentNegotiationSection

2006/8/18, Eric J. Bowman:
> Again, this is not my problem, it was not my idea to state that there could
> be this "service document" without giving me any hint at all as to where it
> should go, but did provide a MIME type.  So I assumed that was so that I
> could negotiate for it at some other address-in-use.  I complained that the
> spec was suggesting two distinct resources with the same URI by not
> describing a standard address to find the service document.

It is not suggesting anything along those lines. The spec says the
service document has an IRI, nothing more, nothing less.

If you want to use the Atom Protocol to edit your Google Calendar,
you'll find the collection IRI in the calendar's options.
If you want to use the Atom Protocol to edit your Blogger blog, you'll
find the collection IRI in a <link rel="service.post"> in the HTML
document at the root of your blog, or retrieve some kind of "service
document" by requesting the feed at
http://www.blogger.com/feeds/default/blogs using your user
credentials.
Yes, Google do not use the current draft's service document, but this
is not really different.

If you want to edit your WordPress blog, you'll find the admin section
by adding "/admin/" at the end of your blog's URI.
If you want to edit your MovableType blog, the "admin section" will
depend on how you installed and configured the system, but will likely
end with "/mt/mt.cgi".

Everything above is given in "help sections" of the related products.
Why would it be any different with the Atom Protocol used within any
other system?

--
Thomas Broyer