I was also wondering about this in a similar context. Our servers represent users with multiple blogs from multiple blog service providers. So for instance if a user has an account at Blogger and one at say LiveJournal and he also has multiple blogs at Blogger (myblog1.blogspot.com and myblog2.blogspot.com).
Would that map to two workspaces - one for Blogger and one for LiveJournal? Would myblog1 and myblog2 be represented by two different collections in the Blogger workspace? With PaceMediaEntries, there should be no other collections in this workspace. True or False? Thank you, Sammy "Yogesh Mujumdar" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] I am sorry if i am asking something silly ;) But i have this thought. Atom has one or more workspaces. Each workspace has one or more collections or A group of collections is a workspace. Workspaces also have a title. When interacting with an APP server, the client is always concerned with : the introspection document url (for the first time), collection uri and then the entry uri. Where is "workspace" coming here? I mean what is the significance of the "workspace" element? Is it that the group is planning to add some kind of access control over workspaces? or it is there just for some kind of facy structure ;) (no offence). If at all workspace is really something important then is it ok to have references in entries belonging to different workspaces. For e.g, Can i post an image to media collection of workspace1 and refer that image in an entry within entry collection of workspace2? Again, the above question revolves around the previous question, significance of workspace. If workspace is not not very important, then cross referencing is not at all a problem. If it is indeed something important then how should the server respond? Please help me understand :( -- regards/Yogesh You should always go to other people's funerals, otherwise, they won't come to yours - Yogi Berra
