[Cosmo-dev] Cosmo URL proposal

[Jared Rhine]

On Mon, 2006-09-18 at 13:36 -0700, Morgen Sagen wrote:
> http://wiki.osafoundation.org/bin/view/Journal/CosmoWebURLProposal

The specification looked good upon review.  Couple thoughts from that:

* I agree with Brian's initial instinct that there should be a dedicated
URL chosen where the alternate links can be retrieved via HTML, in
*addition* to the web URL.  Unless the Atom Service Document is going to
provide 

* So if the web URL serves up the Cosmo UI HTML, how does an iCal user
go about getting the appropriate webcal URL?  That is, if the Cosmo web
URL serves up the Cosmo UI immediately instead of a "here's a list of
options" page, then does it necessarily follow that we want/need a link
inside the Cosmo UI which provides just such a list-of-available-URLs
page?

* This design does not preclude any later "autoredirect" functionality
being added to Cosmo or even outside Cosmo via a mashup (probably REST).
It does presume that any code that wants to lookup the proper URL can
parse the HTML output, or at least hack a regexp up.  That gives a lower
bound to the complexity of clients (versus say a pure REST API), but
seems a reasonable design for all current use cases.

* What's the authentication model that's used on the Cosmo web URL?
Tickets then basic auth, but no anonymous?

-- 
Jared Rhine <jared at wordzoo.com>