[OASIS Issue Tracker] Commented: (CMIS-106) Clarify types-childrenand types-descendants

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Florent Guillaume commented on CMIS-106:
----------------------------------------

TypesDescendants is necessary to model the answer to the getTypes method with a typeId parameter.

But I agree that the description of TypesDescendants in part II are probably a copy/paste error, the TypesDescendants feed should be described differently.


> Clarify types-children and types-descendants
> --------------------------------------------
>
>                 Key: CMIS-106
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-106
>             Project: OASIS Content Management Interoperability Services TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: Draft 0.50
>            Reporter: Ryan McVeigh
>            Assignee: Al Brown
>
> What is the difference between TypesChildren and TypesDescendants? The description of both says they are feeds containing all the types in the repository. If both resources contain all types, then what is the difference?
>    1. I suspect that either TypesDescendants is redundant and unnecessary, or
>    2. that the descriptions are wrong, and they should be returning feeds of types that are children/descendants of a given type.

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