[#CMIS-199] enumRepositoryRelationship is an XSD enum - why? - OASIS Technical Committees Issue Tracker

OASIS Content Management Interoperability Services (CMIS) TC

enumRepositoryRelationship is an XSD enum - why?

Created: 02/Jun/09 11:03 PM Updated: 08/Jul/09 08:10 PM

Component/s:

Domain Model

Affects Version/s:

None

Fix Version/s:

Draft 0.62

Proposal:

accepted - clarification, see Al's comment

Description

« Hide

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?

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Al Brown added a comment - 03/Jun/09 05:50 PM

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.

[ Permalink | « Hide ]

Al Brown added a comment - 22/Jun/09 01:03 PM

accepted