OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (CMIS-655) Folder Children(restrict acceptable values for OrderBy)



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

Al Brown commented on CMIS-655:
-------------------------------

I'd like to keep getFolderChildren() simple.  I do think this should be clarified either as reduced scope and explicit repository capability defined by modes.

I would think the modes would be: None, cmis-common-properties (probably recommended option), custom-properties

I personally am not sure how to handle custom properties since documents or folders of any type can be in the listing.  This raises issues on how to handle properties across multiple types that might or might not have the property.

Query only exposes the properties on the type and not on the sub-types. So this would be the first instance of CMIS supporting that functionality.

> Folder Children (restrict acceptable values for OrderBy)
> --------------------------------------------------------
>
>                 Key: CMIS-655
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-655
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Domain Model
>    Affects Versions: Committee Draft 06
>         Environment: n/a
>            Reporter: Jay Brown
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> Since folder getChildren is basically a specialized query against two different tables, supporting all orderBy values for all possible orderable properties becomes prohibitively difficult for some repositories.
> In some repositories, the underlying query against all documents (and sub classes of document) may not permit sorting by a field that only may be present on a subclass of document.     But the scope of this call implies all cmis:document subclasses and all cmis:folder subclasses. 
> An example of a case that may be difficult to correctly service is the following: 
> A subclass of cmis:document named invoicedoc exists that has a an orderable property value of 'foo'.
> A folder getchildren is then reqested for a folder with an orderBy parm set to "foo".

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