[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-192) REST/Atom: Why do wehave "TypesChildren" and "Types Descendants" collections?
[ http://tools.oasis-open.org/issues/browse/CMIS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259#action_17259 ]
Al Brown commented on CMIS-192:
-------------------------------
JIRA Cleanup
> REST/Atom: Why do we have "TypesChildren" and "Types Descendants" collections?
> ------------------------------------------------------------------------------
>
> Key: CMIS-192
> URL: http://tools.oasis-open.org/issues/browse/CMIS-192
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Bug
> Components: REST/AtomPub Binding
> Affects Versions: Draft 0.62
> Reporter: Ethan Gur-esh
> Assignee: Al Brown
> Fix For: Draft 0.62
>
>
> In the CMIS domain model (Part I) and in the WS/SOAP binding, we said that there's a flat "types" collection returned by the getTypes method, and that the hierarchy of object types is not explicit (i.e. returned as a tree), but rather implicitly discoverable via the "ParentID" attribute of an object type.
> However, in the REST/ATOM binding, there's a "TypesDescendants" collection that returns an actual hierarchy of types.
> Why do we need/have this? If there's a use case for it, it should be part of the domain model & all bindings. If not, we should remove it from the REST/ATOM binding for consistency.
--
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]