[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=26169#action_26169 ]
Jay Brown commented on CMIS-722:
--------------------------------
Comment on version 0.3 (15 June 2011)
It just occurred to me that since there is a hard constraint on these objects that they must not exist without a parent document then they are starting to sound like 'dependent' objects here. (i.e. Not independently persistable objects with a id that is unique within the scope of a repository) This is not the case for IBM/FileNet, but I would imagine in some repositories these might be modeled underneath as a truly dependent (on their parent document) object.
Are there any repositories where this is the case? If so please speak up now! If not, then I will withdraw this comment, and there is no need to read further. But if there are, then to accommodate them, it might be safer if we always referred to annotations as a pair/tuple of ids (document id + annotation id)
The implications of this would be (among others) that there should be no operations on Annotations formed as if they were independent as suggested for deleteObject, getContentStream and setContentStream in the proposal. For example the object services would include a new deleteAnnotation as follows:
deleteAnnotation(repositoryId, documentObjectId, annotationId)
which would seem to be in symmetry with the already suggested createAnnotation() method.
> 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]