[OASIS Issue Tracker] Updated: (CMIS-670) Return Codes example isambiguous

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

     [ http://tools.oasis-open.org/issues/browse/CMIS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Melahn updated CMIS-670:
--------------------------------

      Due Date: 24/Oct/10
    Resolution: Updated browser binding proposal

> Return Codes example is ambiguous
> ---------------------------------
>
>                 Key: CMIS-670
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-670
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Browser Binding
>    Affects Versions: Browser Binding Proposal
>            Reporter: Florian Mueller
>            Assignee: Gregory Melahn
>            Priority: Minor
>
> Section 1.3.9 describes the error handling and return codes.
> The example shows an error message with a HTTP status code 200 and response status code 400. Both should be the same status code.

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