[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-722) Annotation handling
[ http://tools.oasis-open.org/issues/browse/CMIS-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26208#action_26208 ]
Alexander Haag commented on CMIS-722:
-------------------------------------
As I tried to explain during the TC-call, another integration option using Rendition was not introduced since the specification of the Rendition must be changed and extended. ACL support for Annotation is repository specific and not a real problem for the most systems.
The problem is wich I see is that a Rendition cannot be deleted, changed/updated or created!
I my opinion most of the use cases for Annotation assume that delete, create or at least update capability exist.
Even if update and create capability would be add to the spec, the Rendition provides only an optional "renditionDocumentId".
These attribute must be also changed to required!
Would this make sense for thumbnails?
Do we want to have "special" Renditions objects?
(I mean to differ between thumbnail-Rendtion and Annotation-Rendition. If so, why not using the content type definitions?)
I had a possible proposal to use Rendition where not many changes need to be done, but it was quite dirty
cause I used the Rendition.streamId as ContentStream identifier and also as object identifier.
Regarding the ID problem which was raised, an ID in CMIS can be everything. So for non-unique native Annotation ID's:
cmis:annotation.cmis:objectId = <native Document ID> + <seperator> + <native Annotation ID>
Also the proposal could be changed again to have both parameters document ID and annotation ID,
which would then also require to create new methods for ACL handling, deleteObject and setContentStream/updateAnnotation.
> Annotation handling
> -------------------
>
> Key: CMIS-722
> URL: http://tools.oasis-open.org/issues/browse/CMIS-722
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: New Feature
> Components: Schema
> Affects Versions: Proposals for 2.0
> Reporter: James Michel
>
> Annotating provides the possibility to extend the document content information, without changing the content itself. With annotations it is possible to highlight a section of text, pinpoint a specific item in an image or simply provide a small note or comment during a particular stage within the process of the document's lifecycle.
> Currently most CMIS-compliant vendors support functionality for annotating, but unfortunately the support for this is repository-specific.
--
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]