[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=35933#action_35933 ]
Jay Brown commented on CMIS-722:
--------------------------------
Per a discussion that Florian, Scott and I had at IOD 2 weeks ago:
An Annotation solution 100% compatible with CMIS 1.1 -------------------
Add a new secondary type to indicate objects that are dependent on another independent object (e.g. An object marked with this secondary type will be automatically deleted by the repository when/if its parent is deleted)
This secondary type (e.g. cmis:dependent) would have a required ID property indicating the object's dependency parent. (e.g. cmis:dependencyParent )
note this secondary type marker can then be re-used for a variety of other dependent objects like comments, etc. (will discuss comments in another record - see cmis extension example below)
Once that secondary type is defined we can create Annotations in a variety of ways based on our current cmis:document type. One suggestion below.
(e.g.) Define a subclass of cmis:document (named cmis:annotation or cmis:associatedContent ) which when created would have the cmis:dependent secondary type added to make it dependent to a particular document. Making this a subclass of cmis:document (as opposed to using cmis:document directly) will allow the repository to place additional constraints on this new type; like not permitting versioning, etc.
Unlimited Annotations:
This would allow for us to have an unlimited amount of Annotations for any document and the clients would be able to get a paged view of them via the CMIS 1.1 query syntax we have today.
e.g. (pseudo syntax) SELECT * from cmis:annotation WHERE (dependencyParent == someDocId)
CMIS extension example:
Note that everything described here could be defined in a CMIS 1.1 extension feature since all of the components it uses are already present in CMIS 1.1.
This would have the following benefits:
1)Would serve as a good sample since we don't yet have a model of what an actual CMIS 1.1 extension feature should look like. (We may propose another one of these for comments)
2)CMIS servers and clients could begin using Annotations much sooner (as soon as we came to an agreement on how the extension should look) since recommendations for extensions are not subject to the normal OASIS approval process
(For discussion Monday 11/18) David are there any restrictions on the TC doing something like this? This would be a TC recommendation of a usage pattern that is outside of the normative spec. )
Note1: This might need to be a combination of 2 cmis extensions. 1 for the cmis:dependent secondary type (since this will be reused for other features) and a second one to define the annotation class that uses (1).
Note2: All names used here are just place holders. Not sure if we can even use cmis: for extension features and if we did we should limit doing to to extensions specifically recommended by the TC.
> 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]