OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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 TC
          Issue Type: Improvement
          Components: REST/AtomPub Binding
            Reporter: Ryan McVeigh
            Assignee: Al Brown


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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]