2. Is it problematic to nest workspaces and collections to allow several companies with different logins access to their own repository simultaneously?
I didn't feel that I got a good answer to this question. Is it problematic to somehow nest workspaces and/or collections? Much can be achieved with categories, but when you want to add different authentication credentials on different levels down the hierarchy, it doesn't really scale.
We're picturing a top level workspace only available for administrators, with an "accounts" collection that can be maintained through AtomPub. We want each customer's account with their own "photos" and "templates" collection, perhaps organized through sub-collections.
So, I'm thinking the URIs would look a little something like this:
All of those URIs might need a little "accounts/" in front of them if the accounts collection needs to exist at something else than just "/". What say yee?
-- Asbjørn Ulsberg -=|=- asbjorn@xxxxxxxxxx
«He's a loathsome offensive brute, yet I can't look away»