Re: PaceNoServiceDocument

I owe you an apology for shouting.  I think I should just go away and leave 
you guys to your spec while writing whatever I need to write that works for 
me.  Because when I try to describe a problem, people in this group respond 
by trying to educate me as to the nature of the problem.

But I assure you, whatever my problems with communicating the problem I'm 
seeing, the fact that I am seeing them does not mean that I need to be 
educated about how to avoid them.  If I could have avoided them I would have, 
without bothering the group.

Yes, I can assign a location for my service document and negotiate for it 
based on user privileges, just like you say.  In fact that's what I was 
doing.  The problem still remains that the result will be a URI collision no 
matter what URI I locate it at.

This URI collision is evident in every other example which has been put forth 
to me as a "solution to my error".  The spec describes a URI collision, it 
will only not affect single-user systems.  I'm not here asking for help, I'm 
here offering to help.

-EJB

>-----Original Message-----
>From: Thomas Broyer [mailto:t.broyer-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx]
>Sent: Friday, August 18, 2006 08:37 AM
>To: 'Atom-Protocol'
>Subject: Re: PaceNoServiceDocument
>
>
>2006/8/16, Eric J. Bowman:
>>
>> So you're saying I can set up http://example.com/ to sometimes return my home
>> page, and other times it can return a list of collections based on the user's
>> edit privilege.
>
>2 resources == (at least) 2 URIs
>
>> How shall I determine exactly which intention the user has in mind, when they
>> dereference http://example.com/ ?
>
>Use another URI for the service document.
>
>As for your "persistent question": "Where else do you people expect
>anyone to look for a service description, other than by using a MIME
>type as the basis for content negotiation at the domain's root?", just
>tell your users the exact URI to use, e.g. http://example.net/admin)
>Many CMSes do it like that, you have to add "admin" or a similar
>URI-segment at the end of your CMS's "root URI" to gain access to the
>"admin section" where you'll be able to edit
>pages/articles/items/entries.
>
>Note that you could use other means to help clients "redirect" from
>the home page to the service document. For example:
> - Yadis (http://yadis.org) uses an X-XRDS-Location HTTP header or an
>equivalent "meta http-equiv" in an HTML document.
> - OpenID 1.x (http://openid.net) relies on "link" elements in HTML documents
>
>-- 
>Thomas Broyer
>
>