Re: Local ECM Provider

Some comments about workspaces.
Workspace and Sections are concepts defined in CPS.
They are regular folder resources that may contains other resources but
with the particularity that a Workspace folder is "editable"
(contents and children may be modified) while Section folders contains
read only resources (published content)
Each type of folder may impose it's own workflow and actions (on a
resource inside sections we may have available the action "unpublish"
while inside a workspace this action is not existing)
Anyway each, ECM provider may defines it's own type of folders. Other
provider than CPS may have more specialized folders or may not have the
workspace / section concepts.
This should be transparent to Apogee. Each ECM provider should be able
to define it's own object model, workflow and security rules.
Apogee will only know about allowed actions that can be done on a
resource in a given context.
So, Apogee should not be aware on the fact that CPS have workspace and
sections but it should only  know what kind of operations a resource is
supporting
This can be done by querying the ISiteController (that will consult the
right ECM provider bound to the current) thorugh the
ISiteController.isOperationEnabled() method. This method may delegate
the query to the underlying ECM provider but may also do some checks on
the local side such as if this type of operation was registered by the
ECM provider.

Bogdan

Workspaces are folders from