Hi Katie,
Well, one option is not to encode any semantic information in the url (such as the collection the item is contained in or the back end server the item lives on). Long lived unique id perhaps?
Hmm, I'm not sure I'm following you. You're saying if John shares an item with me via email (sending me a Scooby URL), when I click on the URL, Scooby would somehow know on which collections John had permission to access an item with that UUID?
I'd been assuming when Chandler sent a sharing email, it would send a URL with either a universal read/write ticket for that item, or personalized read/write tickets for the item. It seems like in either case Chandler will need to create the relevant tickets, which would only apply to one collection.
Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
