-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major
-
None
-
Affects Version/s: None
-
Component/s: REST/AtomPub Binding
-
None
Our developers working on the atom rest CMIS prototype implementation have asked that the spec include examples of what users will do w/ CMIS Feeds and Entries? Specifically how will they consume them in a create, update or delete use case? This doesn't necessarily lend itself well to client-side development, but of course maps nicely to specific client implementations or atom pub clients.