[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-705) Add support forexternal content references for 1.1
[ http://tools.oasis-open.org/issues/browse/CMIS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24839#action_24839 ]
David Choy commented on CMIS-705:
---------------------------------
The proxy object use case is certainly real. The challenge is what CMIS can/should do in support of this use case. If we introduce a standardized property, then we need to have a clear undertanding what this property means. IMHO this is what's missing here. Without clearly defined semantics, each repository would use it to represent something different. In that case, merely having a common property does not help. It may be better just let each repository define its own property then.
Specifically, this property is a reference stored in a document object pointing to an "external" object located outside of the current CMIS repository. Is referential constraint being maintained by the repository? Are there metadata associated with the external object? If yes, where and how to get them? Are the "state" of this document object and the "state" of the external object sychronized (whatever "state" means)? (For example, if this document cached some of the external object's metadata, does the repository attempt to keep the cached info up to date?) What is the role of this proxy document? Is the proxy document a passive representation of the external object, or is it an active object that controls the lifecycle and maybe even the accessibility of the external object? Or, is it merely a different "view" of the external object? If the proxy document contains certain info (e.g. metadata, rendition) that is not stored with the external object, should such info be considered an integral part of the external object? etc. etc. Many of these issues hinge on what "proxy" really means.
Of course, the richer the semantics we choose to define, the narrower its applicability will be. At the other extreme of the spectrum, if the property is
merely a URI for an external object, with no referential constraint and no specific semantics associated with it, then this reference only represents a
weak, generic relationship between the two objects, nothing specific to the proxy object use case.
On the other hand, I am less concerned with what a client application (e.g. a crawler) would/should do. Once the semantics of this property is clearly defined, it is up to an application to decide what it wants to do. A crawler that only looks for info stored in this repository may not want to follow this reference, whereas a more global crawler may want to.
> Add support for external content references for 1.1
> ----------------------------------------------------
>
> Key: CMIS-705
> URL: http://tools.oasis-open.org/issues/browse/CMIS-705
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: New Feature
> Components: Domain Model
> Affects Versions: V1.1
> Reporter: Jay Brown
> Priority: Minor
>
> I have written up a short proposal describing support for external content in CMIS 1.1.
> I will add the link for the proposal shortly and reference this record in the doc.
> This Jira issue is for discussion of this topic.
--
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]