COMPLETE : These items have been considered "complete" and part of the CmSpecificationV2. See CmArchitecturalDirectionV3 for the follow on work.
The purpose of this page is to collect the architectural direction as driven by scenario priorities for the next version of CM specifications (V2). It also contains various 1.0 issues to be addressed in the next version. This follows on to the CmArchitecturalDirection work done for 1.0.
Better handling of differing authentication models
We've run into some issues when clients don't always know when and how to handle form auth, like when using a batch-mode RESTful interface (feed readers, etc).
Schema
A number of scenarios have shown the need for information for schema of change request resources. Not limited to what is available in XML Schema but addition metadata such as:
Since resources are URL-addressable, they often get pasted into tools without going through service discovery.
A possible solution would be to support requesting the service discovery document an the change request resource URI:
or by embedding the service discovery doc URL in the change request resource definition
Reportable REST
Linking issues:
These backlog items have moved to the next iteration of this document for V3