[OASIS Issue Tracker] Commented: (CMIS-199)enumRepositoryRelationship is an XSD enum - why?

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

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

Al Brown commented on CMIS-199:
-------------------------------

It's used in the rest binding and should be returned as part of cmisRepositoryEntryType.  I believe the workspace element was not constrained as the server was free to extend the list with other options.  There is not really a good way in XSD (that I know of) to say the field can be this one of this list or any other generic string.  It basically comes back to a definition of string.

My proposal would be to add this to cmisRepositoryEntryType as it somehow got lost during the transition of the documents.

> enumRepositoryRelationship is an XSD enum - why?
> ------------------------------------------------
>
>                 Key: CMIS-199
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-199
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>            Reporter: Ryan McVeigh
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> Domain Model 0.62a:  Sections 2.1.2 and 2.1.2.1 describe enumRepositoryRelationship and an XSD enumeration which appears to be unused.  Why is this captured in XSD?  Must this be part of CMIS-Core.xsd?  

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