Re: ProtocolDataModel issues

[Joe Gregorio <joe.gregorio@xxxxxxxxx>]

On Tue, 14 Sep 2004 16:43:22 -0700, Ezra Cooper <ezra@xxxxxxxxxxxx> wrote:
> Maybe this is the same as the PostURI; maybe when you GET the PostURI,
> you get this feed-level resource.
> To rephrase that, suppose the PostURI is really a "weblog resource" or
> an "editable feed resource." When you POST to that resource, you're
> posting a new entry into the feed. When you GET that resource, you get
> the feed-level metadata (or even the full feed). This resource would
> also be the place where feed configuration extensions could be made.
> 
> This would also be a place to offer links for discoverability of the
> other "lists": like the list of available categories. Currently, in
> TypePad, to get a list of available categories, you GET a URL ending in
> "/t/atom/weblog/blog_id=<blog id>/svc=categories". Rather than set a
> standard form for this URL, I'm proposing it be chosen by the server
> and listed in the uber-discoverability resource which can be GOT at the
> PostURI.
> 
> I like the idea of hiding most of the discoverability links at this
> feed-level resource, as opposed to dragging them down the front street
> on the HTML page.

I would offer the Introspection file as a good place to 
store all such links. The Introspection file was part of 
the protocol at one point, then dropped in the 
name of 'simplifying' the protocol. We should
consider bringing it back. 

Note that the Introspection file had it's own URI that
was seperate from the other protcol URIs.

http://bitworking.org/projects/atom/draft-gregorio-05.html#rfc.section.4.1
http://bitworking.org/news/Extending_the_AtomAPI

    -joe

-- 
Joe Gregorio        http://bitworking.org