[OASIS Issue Tracker] Commented: (CMIS-65) Including clientimplementation use cases for the CMIS REST services would be helpful.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10216#action_10216 ] 

Al Brown commented on CMIS-65:
------------------------------

Need to hear back from the TC on material to include in this section. This will be in 61c

> Including client implementation use cases for the CMIS REST services would be helpful.
> --------------------------------------------------------------------------------------
>
>                 Key: CMIS-65
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-65
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: REST/AtomPub Binding
>    Affects Versions: Draft 0.50, Draft 0.6
>            Reporter: Ryan McVeigh
>            Assignee: Al Brown
>             Fix For: Draft 0.61
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira