[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Suggestions for PaceIntrospection


On Nov 11, 2004, at 8:06 PM, Joe Gregorio wrote:

On Thu, 11 Nov 2004 22:46:21 -0500, Robert Sayre <mint@xxxxxxxxxxxxxxx> wrote:

3.) Remove "service" children of <site> and use a single 'href' attr
I can't see anything that differentiates the 'feed' and 'post'
relations, other than the methods they accept. 

I think I've agreed to this in the past, in the context of
PaceCollectionIdiom, that the feed and post resource
should be the same, so agreed to that point.

Forgive me if I've misunderstood this, as I might have missed some of the history. Is the "feed resource" the same as the public-facing read-only feed? If so, I think there's a risk of creating a difficult-to-implement requirement.

This is the plight of Bob, who runs CGI-based software on a standard server: his public-facing Atom feed (as fetched by news readers) may be a static file that the webserver knows how to GET. But typically Bob won't be able to respond dynamically to POST on the same resource. So the public-facing "alternate" for the site should be allowed to be distinct from the service URI where an author could GET and POST entries. Is that compatible with PaceIntrospection?

But I disagree on removing the <service> children. As of right now we
do have only a single service (managing entries), but we still
have to add in services for managing users, templates,
preferences, simple resources, etc. I think that each of those
should be listed here.

I agree that the service description resource should indicate how to manipulate these other kinds of resources.

Ezra