The actual CMIS version 0.61 is available since April 2009 . Everybody who wants to know about the status of the upcoming version 0.62 can have a look at the OASIS CMIS project website.

At the moment 103 of 143 issues have already been solved.
These issues belong to

• Domain Model,
• REST/AtomPub Binding,
• Schema,
• Web Services Binding
• or no components.

Here you can see the release notes for version 0.62 with the link to the explanation

Bug

• [CMIS-51] – Mention of unknown TypeDefinitionCollection
• [CMIS-82] – Property Definitions: A property definition should not ever say READONLY + REQUIRED
• [CMIS-83] – Schemas don’t allow setting minvalue/maxValue for Decimal property types
• [CMIS-84] – ContentStreamAllowed is modeled as a Property on a Document, NOT an attribute on an object type.
• [CMIS-87] – Type Id vs Query Name confusion
• [CMIS-88] – POST to Children resource is confusing
• [CMIS-89] – POST to Descendants is very confusing
• [CMIS-91] – getChildren type enum inconsistent
• [CMIS-93] – REST getChildren folderByPath argument is not well explained and is confusing.
• [CMIS-98] – There are CMIS properties that duplicate APP/ATOM information
• [CMIS-104] – Clarify the description of how to retrieve the service document.
• [CMIS-106] – Clarify types-children and types-descendants
• [CMIS-108] – Clarify getTypes URI
• [CMIS-115] – Make use of “OperationNotSupported” vs. “ConstraintViolationException” more consistent
• [CMIS-116] – TypeNotFoundException & notInFolderException — are these ever still used?
• [CMIS-118] – Methods other than “updateProperties” should include the changeToken as input
• [CMIS-119] – getProperties — do we still need Enum “returnVersion”?
• [CMIS-121] – Remove “offsetException”
• [CMIS-123] – deleteContentStream — should have an output param for documentId
• [CMIS-124] – cmisQueryType — rename some params to be consistent with other method terminology
• [CMIS-125] – Remove the “folderNotValid” exception type
• [CMIS-126] – Should “deleteAllVersions” have “continueOnFailure” semantics like “DeleteTree” does?
• [CMIS-127] – Cut-and-paste error: getRelationships method includes Boolean “includeRelationships”
• [CMIS-128] – Query result set AtomPub binding is ambiguous and implies object mapping, not row mapping
• [CMIS-130] – XML and HTML properties underspecified
• [CMIS-131] – contentCopied header
• [CMIS-134] – getContentStream and content-range support
• [CMIS-135] – createDocument & checkIn – Accept an optional contentStream input. How is this included and encoded?
• [CMIS-136] – CMIS-Core.xsd: cmisChoiceType
• [CMIS-144] – Full text search syntax and semantics
• [CMIS-145] – Missing Ex-Type.xml and Ex-FolderDescendants.xml examples
• [CMIS-147] – There’s still reference to FullText capability
• [CMIS-148] – IsLatestMajorVersion property gone missing
• [CMIS-152] – source link is overloaded between feeds and resources
• [CMIS-153] – The stream link on documents is uses interchangeably with the edit-media link.
• [CMIS-154] – Schema inconsistent with spec in several places.
• [CMIS-155] – Binding specific details found in CMIS-Core.xsd
• [CMIS-157] – Ex-ChangeLog.xml does not validate against schema
• [CMIS-158] – Ex-DocumentEntryWithChanges.xml does not validate
• [CMIS-159] – Ex-Service.xml does not validate
• [CMIS-160] – Document / Folder entry parents link
• [CMIS-161] – Clarify REST Query Paging
• [CMIS-162] – Add WS UpdateProperties to rtn changetoken
• [CMIS-164] – Usage of <content> across multiple implementations
• [CMIS-165] – Atom Upload of files [RFC 5023 section 9.6]
• [CMIS-166] – Link to parent collection
• [CMIS-168] – URL to id mapping
• [CMIS-169] – get object by id
• [CMIS-170] – get folder by path
• [CMIS-171] – Documents without content and getContentStream
• [CMIS-173] – Paging support in AtomPub Binding using rfc5005 is redundant
• [CMIS-174] – hasMoreItems element in schema is redundant
• [CMIS-175] – Fix query specification for CONTAINS()
• [CMIS-177] – How do the various comparison operators work with the various property types?
• [CMIS-178] – Clarify behavior and/or error handling of various Query Functions
• [CMIS-179] – Clarify behavior for a repository which may not be able to support the entire query grammar.
• [CMIS-180] – Clarify query escape behavior.
• [CMIS-184] – Add boolean and datetime literals to query grammar
• [CMIS-185] – Move binding-specific elements out of CMIS-Core.xsd
• [CMIS-186] – move atom:feed extensions before atom:entries
• [CMIS-187] – folders should always have the children relationship
• [CMIS-188] – Should it be optional to support “getDescendants” with an arbitrary “depth”?
• [CMIS-190] – moveObject should return the updated object ID
• [CMIS-191] – Add support for Unified Search proposal
• [CMIS-192] – REST/Atom: Why do we have “TypesChildren” and “Types Descendants” collections?
• [CMIS-193] – Property ‘required’ is now set to False for all properties except Name
• [CMIS-194] – Create relationship clarification is required
• [CMIS-195] – includeSubRelationshipTypes defaults to False
• [CMIS-197] – Clarify base type behavior in folder filing restrictions
• [CMIS-198] – getPropertiesOfMajorVersion and checkIn have the same argument spelled differently
• [CMIS-199] – enumRepositoryRelationship is an XSD enum – why?
• [CMIS-200] – Property Choice specification confusion
• [CMIS-202] – How does query work with descendent types?
• [CMIS-203] – Why specify URI’s to objects?
• [CMIS-204] – CMIS Version format needs to be specified.
• [CMIS-205] – Object Type Property Definition Schema is not complete in domain model and is duplicated in the spec.
• [CMIS-206] – Schema for Integer Object-Type Property Definitions error
• [CMIS-207] – Several Object-Type Property Definition attributes need clarification.
• [CMIS-208] – Document & Folder Object-Type Attribute “queryable” needs clarification.
• [CMIS-209] – 2.7.5 Schema Section – unclear what this refers to.
• [CMIS-210] – Clarify Query BNF called out in CONTAINS, IN_FOLDER and IN_TREE vs. the included BNF Grammar
• [CMIS-211] – CONTAINS qualifier object needs clarification.
• [CMIS-213] – Change log token acquisition needs clarification.
• [CMIS-214] – ChangeEvent section, ChangeType enum security description clarification
• [CMIS-215] – Property Filters can be ignored?
• [CMIS-216] – getRepositoryInfo specifies output schema which isn’t used by all protocol bindings
• [CMIS-218] – getFolderParent type enumeration – does this make sense?
• [CMIS-219] – getFolderParent – does it need a depth input?
• [CMIS-220] – Should moveObject’s sourceFolderId be required when the repo supports multi-filing?
• [CMIS-222] – Confusion in Atom Entry document for Atom Author Mapping
• [CMIS-224] – CMIS Link Relations Incomplete?
• [CMIS-228] – App:edited incorrectly specified as feed element.
• [CMIS-230] – deleteTree argument enumUnfileNonFolderObjects name is confusing
• [CMIS-231] – Atom Entry document – should it specify another property for LastModifiedDate?
• [CMIS-232] – CMIS Link Relations clarification
• [CMIS-233] – deleteTree notes clarification
• [CMIS-234] – Repository changes collection missing a collection name.
• [CMIS-235] – Repository Resource specifies links which should not be present if the repository doesn’t support the feature.
• [CMIS-236] – Should we document Atom Categories?
• [CMIS-237] – MediaTypes in resource description clarification
• [CMIS-238] – Atom Entry Links Clarification
• [CMIS-239] – The app edited element isn’t present in app.xsd
• [CMIS-240] – Types Descendents Collection needs to specify behavior when no base type is given, describe flat or nested feed structure.
• [CMIS-241] – Types Descendents Collection downtree is confusing.
• [CMIS-242] – Relationships Collection, via link needs clarification
• [CMIS-243] – Parents Collection feed structure needs clarification
• [CMIS-244] – Folder Children Collection description is confusing.
• [CMIS-245] – Folder Children Collection HTTP method description confusing.
• [CMIS-247] – Folder Descendents Collections
• [CMIS-249] – Document Entry need to differentiate getProeprties or getPropertiesOfLatestVersion
• [CMIS-250] – Need to elaborate the accept element for AtomPub Collections
• [CMIS-251] – Document Entry Links need description
• [CMIS-252] – Document PWC Entry Put – need to differentiate between checkIn and updateProperties
• [CMIS-254] – Content Stream description confusing
• [CMIS-256] – Rest Schema has extraneous entries.
• [CMIS-258] – Need to explain AllowableActions as they relate to AtomPub links
• [CMIS-259] – Need to explain flat and nested feeds in completion in the Rest binding
• [CMIS-262] – More Property Choice spec confusion for defaultValue.
• [CMIS-264] – Streaming handling for Folder Children Collection POST needs clarification.
• [CMIS-265] – Be explicit about optional rest-specific parameters – Folder Children Collection POST
• [CMIS-270] – Blanket Issue to track Domain Model Changes from 0.62a to 0.62b
• [CMIS-271] – Blanket Issue to track ReSTful AtomPub changes from 0.62a to 0.62b
• [CMIS-274] – deleteContentStream outputs
• [CMIS-281] – getCheckedoutDocs and others should be getCheckedOutDocs
• [CMIS-282] – AllVersions Collection description incorrect.
• [CMIS-283] – Relationships Collection operation createRelationship isn’t described.
• [CMIS-284] – latest-version link isn’t included in the link descriptions
• [CMIS-303] – Cardinality description: multi is “zero or more”

Improvement

• [CMIS-49] – Clarify need for “Encoding” in XML properties
• [CMIS-50] – Choice “name” vs “key”
• [CMIS-55] – Clarify deleteTree transactionality comment
• [CMIS-56] – Clarify query’s IncludeRelationships
• [CMIS-59] – Merge enumRelationshipDirection and enumIncludeRelationships, remove “none”
• [CMIS-62] – Information is scattered throughout the spec, cleanup needed.
• [CMIS-132] – Unifiy handling of type id between Atom and SOAP binding in Create* calls
• [CMIS-156] – Reconsider delete design
• [CMIS-181] – Naming of link relations
• [CMIS-182] – CLONE -various terminology issues
• [CMIS-312] – CLONE -Unifiy handling of type id between Atom and SOAP binding in Create* calls
• [CMIS-313] – CLONE -CLONE -Unifiy handling of type id between Atom and SOAP binding in Create* calls
• [CMIS-314] – CLONE -Reconsider delete design

New Feature

• [CMIS-112] – Expose display name with a property value and allow property name to be a technical name
• [CMIS-172] – Additional interface to query service via HTTP Get
• [CMIS-183] – Document thumbnail proposal
• [CMIS-272] – blanket issue to track changes to the Domain Model for the ACL-Proposal

Task

• [CMIS-129] – need to specify payload format for PATCH (when doing partial updates)
• [CMIS-141] – use of X-Method-Override sort of underspecified