RE: Reject or accept non-draft entries in Wordpress

["Brian Smith" <brian@xxxxxxxxxxxxxx>]

Teo Hui Ming wrote:
> In WordPress, a contributor is allowed to create drafts, as 
> well as view, edit  and remove his own drafts. So, a separate 
> collection feed listed with his own drafts is a good idea. 
> But then, a contributor can also view other users' posts, 
> meaning that server should provide another read-only 
> collection feed listed with all users' posts.

<snip>

> > The server doesn't need to mint a new URI for each 
> individualized service document or feed.
> 
> Since server actually needs two separate collection feeds, 1) 
> a list of editable posts/drafts, 2) a list of read-only 
> posts/drafts from all users, it makes sense to provide a 
> per-user URI for (1) and a common URI for (2). But I wonder 
> how other blog applications actually deal with this issue.

The public subscription feed (the one that people subscribe to using their feed readers) is an acceptable substitute for the "read-only collection feed," AFAICT. It is sorted by atom:updated instead of app:edited, but that is probably better anyway. A blog editor can usually discover the subscription feed at the same time it discovers the service document.

- Brian