[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-117) getDescendants method-- mis-match between Schemas & Domain model
[ http://tools.oasis-open.org/issues/browse/CMIS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10659#action_10659 ] Ethan Gur-esh commented on CMIS-117: ------------------------------------ Yes, it was already gone from the domain model. > getDescendants method -- mis-match between Schemas & Domain model > ----------------------------------------------------------------- > > Key: CMIS-117 > URL: http://tools.oasis-open.org/issues/browse/CMIS-117 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Components: Domain Model, Schema > Affects Versions: Draft 0.50 > Reporter: Ethan Gur-esh > Assignee: Ethan Gur-esh > Priority: Minor > > Currently, the CMIS schema & domain model are inconsistent in the following ways for the definition of the "getDescendants" method. > Inputs: > - includeRelationships: > -- Domain model says: It's an enum with values "source", "target", "both", "none" (default) > -- Schemas say its a boolean. > (Note: includeRelationships is also defined this way for getChildren,getFolderParent, getObjectParents, getCheckedoutDocs, getProperties). > - orderBy: > -- Domain model says it's a string that is a valid "ORDER BY" statement in CMIS-SQL (just like query). > -- Schemas don't include it. -- 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]