Re: URI constraints

[Robert Sayre <mint@xxxxxxxxxxxxxxx>]

Greg Stein wrote:

> Now consider the blogspot blog case. The blog's HTML representation and
> feed lives over on blogspot. The atom-capable resources(*) live over on
> blogger.com.

I agree that "source vs. derived resources" is a useful distinction for 
us, and it is not subject to the hierarchical constraints of WebDAV.

>     https://www.blogger.com/atom-1.0/blogs/12345678/
>
> POST'ing to that resource would create a new blog post. Running PROPFIND
> on it would return "all" the posts (non-scalable, so I need to think a bit
> on that one). The PROPFIND results contain URLs for the posts within that
> collection (where the collection represents the blog). 

I think this is where we have a big culture clash, which is kind of 
humorous considering all GETs have previously been tunneled through POST 
in blogging APIs.

Why can't we define the response to a GET on the collection resource? 
The typical DAV "html index" behavior doesn't seem real useful. I was 
thinking the WG could define the collection's response to a GET as 
equivalent to some prefab PROPFIND request (probably Depth: 1) the WG 
agrees on.

> There is an open question for what to do with the blog that has 100,000
> posts in it. That would be a scary-huge PROPFIND result (legal, if a bit
> expensive; could be about a 20 meg response).

What's stopping you from having child collections? But yes, in general, 
we have a query problem.

Robert Sayre