Even i am facing the same problem. I think atom is missing it. Considering a blog use case(or any other for that matter), i may want to have different collections(i dont prefer caetgories) depending on the context of the data e.g, I want to have a collection called "Personal" where i will post all my personl stuff, "Official" where i post all office related docs etc. The server can always have a limit on the number of user collections which can be created apart from the standard ones. I feel managing different collections is more easy than having categories particularly when you want search, list. Also hierarchical data is easy to manage than a flat list.

In my implementation, i am just sending a atom feed with 1 entry and entry content type as "createcollection", just for the server to know that this is a create collection request. May not be a good approach though, it works for me. A more cleaner method would be  good.

On 4/26/06, John J. Barton <[EMAIL PROTECTED]> wrote:

As I started to try an implementation I got struck right off:

What is the protocol for creating a new workspace in Atom Pub?
(a good answer for me would be: create a new collection with attribute
workspace="Your Property", but thats another post...)

What is the protocol for creating a new collection in Atom Pub?
(Hmm...POST an introspection document?)

John.


______________________________________________________
John J. Barton  email:  johnjbarton<at> johnjbarton.com
http://www.johnjbarton.com




--
regards/Yogesh

You should always go to other people's funerals, otherwise, they won't come to yours - Yogi Berra

Reply via email to