OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[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=26593#action_26593 ] 

James Michel commented on CMIS-722:
-----------------------------------

Following yesterday's TC meeting, I would like to summarize what was discussed:

The TC appeared to welcome our idea of scrapping the current annotations proposal in favor of a broader proposal "Associated Content".

It was also proposed that we should consider making Renditions a part of the Associated Content Proposal also, like annotations, bookmarks, etc..  This would also allow us to make Renditions writeable, which might also prove beneficial when connecting a Renditions engine to a CMIS-based document system.

It was again suggested that Associated Content could be represented through a special relationship, which defines a dependency between parent and child documents.  The problem here is that this special relationship must be defined with all its semantics, such as versioning, recursive deletion and updating. Nevertheless it is probably worth investigating further.

Questions to the TC:

- Does anyone object to introducing "Associated Content" types ?

- Would anyone have an issue with making Renditions a part of Associated Content ?

- Would it make sense to introduce a special relationship between child and parent documents as well ?

So far we have talked about the following as candidates for Associated Content:

- annotations
- bookmarks
- source documents
- signatures (electronic and digital)
- OCR data
- renditions
- document object references

Is there anything else that could be added to this list that would be of benefit to anyone?

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