[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Rendition AtomPub and domain model inconsistency
CMIS-630 was deferred from previous meetings. David C suggested we resolve it via email discussion, so here it is. For convenience, in the JIRA issue I wrote: 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. To fix this, we can add a cmisra:streamId attribute to the atom:link element, but this would require a spec change so I'd think it's logical to defer this to 2.0. In the meantime unofficially I would advise server vendors to use rendition links of the form http://...?streamId=foo which would help clients introspect these URIs and choose the correct one. What do you think? Florent -- Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]