[OASIS Issue Tracker] Commented: (CMIS-630) Rendition AtomPub anddomain model inconsistency

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

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

Florent Guillaume commented on CMIS-630:
----------------------------------------

This issue is invalid as actually the AtomPub requests never expose the <rendition> tags therefore aren't able to get to the streamId in the first place.
See CMIS-645 for further work in 2.0.

> Rendition AtomPub and domain model inconsistency
> ------------------------------------------------
>
>                 Key: CMIS-630
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-630
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model, REST/AtomPub Binding
>    Affects Versions: Committee Draft 06
>            Reporter: Florent Guillaume
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> There is a slight inconsistency between the domain model and the AtomPub way of exposing renditions.
> In the domain model a rendition has a unique id and a non-unique kind. This is exposed through <cmis:rendition>.
> But in the AtomPub rel=alternate links only cmisra:renditionKind is exposed.
> So, given a just rendition id, if there are several renditions of the same kind, an AtomPub client has no way of choosing which rendition link to use.

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