Re: issue: draft posts

[Joe Gregorio <joe.gregorio@xxxxxxxxx>]

On Tue, 22 Mar 2005 07:23:03 -0800 (PST), Dare Obasanjo <kpako@xxxxxxxxx> wrote:
> 
> --- Joe Gregorio <joe.gregorio@xxxxxxxxx> wrote:
> >
> >
> >    3.X.1 "atom:state"
> >
> >
> >    This document defines 2 initial values for the
> > Registry of Link
> >    Relations:
> >
> >    The value "publish" signifies that the entry
> > should be published.
> >
> >    The value "draft" signifies that the entry should
> > not be published.
> 
> This assumes that the only use of atom:state is a
> client sending a request to the server. There's also
> the state of the entry when retrieved by the client in
> which case the state would be 'published' not
> 'publish'. I doubt that anyone would want to have both
> publish, published & draft but it should be indicated
> that this applies both to the client requests and
> server responses.

How about changing the wording to:

  The value "publish" signifies that the entry should be published
when it appears
  in a POST or PUT request body. When appearing in a GET response it 
  indicates that the entry has been published.

  The value "draft" signifies that the entry should not be published
when it appears
  in a POST or PUT request body. When appearing in a GET response it
  indicates that the entry has not been published.

  -joe
  
-- 
Joe Gregorio        http://bitworking.org