[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=24840#action_24840 ]
Jay Brown commented on CMIS-705:
--------------------------------
Thank you for the comments David. Much appreciated. I agree this is a balance, and in this initial proposal I have started us out with a definition that is as loose as possible so we can tighten where necessary. (rather than starting tight and loosening)
Addressing some of your specific points:
Q:Is referential constraint being maintained by the repository?
A:No. RI for these references is outside the scope of the cmis server. Server should not even initially verify that the url is valid, but each implementation may do what it wants with respect to other metadata. However if it tries (and can't verify the link) I would suggest that it should not be allowed to throw an exception.
Q: Are there metadata associated with the external object?
A: Yes. In the case where the external content is present, the entire CMIS document is metadata about that external content. Specifically regarding metadata about the link itself, I agree that external_mimetype may also be useful.
Q: Are the "state" of this document object and the "state" of the external object sychronized (whatever "state" means)?
A: No. Again the CMIS repository implementation is to treat this url (or string) as an opaque address that is only to have meaning to CMIS clients or applications. Anytime we are talking about an external object, by definition we are talking about an object that is not under the control of the CMIS repository. Thus even if the repository verified the metadata they could be out of sync the very next second. It is as you suggested. '...a passive representation of an external object.'
On possible use case to consider. The external url represents a permanently stored (think archival) binary object that does not by itself carry associated metadata. (This may be a front end to a legacy system, fixed storage device, etc.)
Today we are currently planning CMIS systems with external references so my goal here is the have an official cmis:<prop name> to use for this string rather than something arbitrary.
> 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]