Re: [OSCOM] OSR-101 spec started

hi guys,

> >>because it's not just about exchanging documents (get and put),
> >>but about the whole CMS user interface.
> >>Makes sense?
> >I think Webdav can  support a lot of think. The webdav methods are not
> >only GET and PUT.
> agreed
<smartass>
i would not even agree to that. WebDAV did not specify GET and PUT
since those methods were already speced in HTTP
http://www.w3.org/Protocols/rfc2616/rfc2616.html
</smartass>

> >There are others method used to search, manage content versions,
> >create folder, get resources properties,  ...
> ok. So let's put the WebDAV analogies beside the items which are already
> listed within OSR-101. Help is very much appreciated
a somewhat useful WebDAV layer mapped to all the
methods speced in JSR-170 can be found here: 
http://www.day.com/jsr170/server/JCR_Webdav_Protocol.zip
the server implementation can already be found in jackrabbit.

> >Maybe I'm wrong but can you explain me what is missing in the webdav
> >protocol ?
> for instance how would you implement the "New" action?
hmmm? a "New" action? is this a list of "templates"?
could this be a SEARCH or PROPFIND?

> Or what about workflow?
well, indeed... 

> > There are more and more editors which are supporting
> >webdav.
> Please don't get me wrong. The idea is not to reinvent the wheel,
> but put together a list what makes a standardized "CMS UI client"
> and see what can be leveraged and what is missing.
my gap analysis between WebDAV (and friends) and the 
OSR-101 proposal would probably boil down to workflow... 
is that correct? 
if so, what workflow model were you thinking of? 
do you also intend to standardize how workflow should work
in cms?

regards,
david