Re: ProtocolDataModel issues

[Janne Jalkanen <Janne.Jalkanen@xxxxxxxxx>]

> > PaceSimpleResoucePosting takes care of this, right? I guess the only 
> > remaining question is how a client locates them, or what resource has 
> > these non-entry resources as a many: property.
>
> Yes, I think so. I don't see any need to model these as anything other 
> than a generic web resource.

Generic web resources *with metadata*  :-)

Actually, one thing I would like to work on is the 
PaceExtendedResourcePosting.

> > >   * Templates
Hmm... Are templates possibly too platform-specific?

> 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. As has been discussed before, in a system with 
> multiple blogs per author, author X might not want to reveal that she 
> authors blogs B and C in addition to A; but she wants her posting 
> client to recognize this so that she can move amongst them with ease. 
> A GET on the PostURI would be authenticated.

+1 on the basic idea, +0.1 on the GET on PostURI... Sort of smells like 
overloading a function with a functionality that is not quite there. It 
smells of a hack :).  Still, it does make sense on some metaphysical 
level.  After all, it is a resource to POST things to...

> Also at the feed level in the protocol: how about a link to the 
> server's help pages?

In order to provide generic Wiki editing capabilities, it would be 
useful to have a guide to the WikiMarkup, yes :)  So a resounding +1 to 
this one.

/Janne