[OASIS Issue Tracker] Commented: (CMIS-413)enumServiceException.type in CMIS-Messaging schema is not defined in part 1or part 2 exceptions

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

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

Al Brown commented on CMIS-413:
-------------------------------

JIRA Cleanup

> enumServiceException.type in CMIS-Messaging schema is not defined in part 1 or part 2 exceptions
> ------------------------------------------------------------------------------------------------
>
>                 Key: CMIS-413
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-413
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Schema
>    Affects Versions: Draft 0.62
>            Reporter: Norrie Quinn
>            Assignee: Florian Mueller
>            Priority: Minor
>             Fix For: Draft 0.63
>
>
> It is not clear what this is:
> <xs:simpleType name="enumServiceException">
> <xs:restriction base="xs:string">
> ...
> <xs:enumeration value="type" />
> The specification used to define typeNotFound.  It is not clear if this should be defined or simply removed from the schema.

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