[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-564) 3.4.1.3 createDocumentexceptions and 3.4.2.3 createDocumentFromSource versioningState param needsclarification
[ http://tools.oasis-open.org/issues/browse/CMIS-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868#action_16868 ] Al Brown commented on CMIS-564: ------------------------------- Fixed > 3.4.1.3 createDocument exceptions and 3.4.2.3 createDocumentFromSource versioningState param needs clarification > ---------------------------------------------------------------------------------------------------------------- > > Key: CMIS-564 > URL: http://tools.oasis-open.org/issues/browse/CMIS-564 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Components: Domain Model > Affects Versions: Draft 0.70 > Reporter: Ryan McVeigh > Assignee: Ethan Gur-esh > Fix For: Committee Draft 05 > > > The versioningState parameter is optional and defaults to "major". However, for non-versionable object types, it is required to be "none", which makes versioningState a required parameter in this case. This makes no sense. Proposal - make the default major for versionable documents, none for non-versionable. Or make the parameter not allowed at all for non-versionable. > Note also that 2.9.6 says that repos which do not support versioning "MAY create new Document objects in a Major Version state". If this is so, why is the versioningState param not allowed to be "major"? -- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]