On Fri, Jul 3, 2009 at 4:56 PM, Michael Mulich<
[hidden email]> wrote:
> What is an AtomPub Workspace within Plone?
> We are thinking that by default there will be only one AtomPub
> Workspace. We could potentially make more Workspaces via some type of
> configuration. Does the workspace change on a per user basis?
Since a collection can theoretically be part of multiple workspaces in
AtomPub, it seems reasonable to support either case, with the default
being one-per-site.
> What is an AtomPub Collection within Plone? (or Aggregation vs. Collection)
> To avoid confusion, and I'm sure somebody will be confused, I'm talking
> about an AtomPub Collection rather than a Plone Collection.
Right, this sounds like a collection in the same sense WebDAV has for
a collection that a Plone "collection" (smart folder, topic, saved
search, whatever you want to call them).
> An AtomPub
> Collection is not the same as a Plone Collection. Plone Collections are
> aggregators, where as AtomPub Collections are a set of content collected
> in one location or URI.[2] Therefore, a Plone folderish object would be
> an AtomPub Collection, right?
Makes sense. Other representation of content listings such such as
search results are only possibly useful in a *read-only* sense to
front as collections in things like WebDAV or AtomPub.
> But there is the possiblity that it could
> only encompass the first level of folders, because AtomPub doesn't seem
> to support hierarchy.[3]
Instead, perhaps you should be able to assign any folder at any depth
in the system an alias or name that flattens a list of included
folders regardless of how deep they are as collections within the
workspace. What seems a flat listing to the protocol could front for
hierarchy within the site.
Sean
------------------------------------------------------------------------------
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
