[OASIS Issue Tracker] Commented: (CMIS-61) SOAP methods seem to becovered in all parts of the spec, instead of just contained to Part III,the SOAP portion.

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

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

Ryan McVeigh commented on CMIS-61:
----------------------------------

I re-opened this issue and added a revised proposal.  This didn't generate an email notification, so I'm adding a comment to ensure everyone sees that.

> SOAP methods seem to be covered in all parts of the spec, instead of just contained to Part III, the SOAP portion. 
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CMIS-61
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-61
>             Project: OASIS Content Management Interoperability Services TC
>          Issue Type: Improvement
>          Components: Domain Model, REST/AtomPub Binding, Web Services Binding
>    Affects Versions: Draft 0.50
>            Reporter: Ryan McVeigh
>            Assignee: Ethan Gur-esh
>             Fix For: Draft 0.6
>
>
> Some of our developers are working actively on a prototype.  As new readers of the spec, they've provided this feedback:
> 1.  Part I describes the data model and methods.  The methods are very SOAP-like, it would be best to keep these methods in part III, the SOAP section.  Part I should cover the data model and functionality.
> 2. Part II shouldn't refer to SOAP methods, since this is the REST sections.
> 3. Part II and III should be peers

-- 
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