What do different "orderable" attributes cause in getChildren/getCheckedOutDocs ?

[Tomoyuki Hayashi <tomoyuki.hayashi@aegif.jp>]

Hello,

According to 2.1.3.3.2, if two property definitions belong to different object types,

these property definitions can have different values for the attributes other than id, property type, query name and cardinality.

On the other hand, “orderable” is used in “orderBy” parameter in getChildren or getCheckedOutdDocs.

2.2.1.2.7 shows an example of orderable, like

"cmis:baseTypeId,cmis:contentStreamLength DESC,cmis:name”

They don’t have an object type, though, it is likely that getChildren or getCheckedOutDocs returns different type’s objects.

Some objects might have orderable = true type and other objects not. If orderable = false, the property is ignored in sorting.

In this case, how can I know the way of sorting within CMIS specification? Is it repository-specific?

(Fortunately, secondary type property's query name has its type as prefix, but there are still problems with other types, including CMIS base types and also their children types.)

linzhixing