[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=24536#action_24536 ]
Jay Brown commented on CMIS-705:
--------------------------------
Thanks for bringing this up Alexander. This is great feedback.
Since external content is outside of the control of the local CMIS repository there is always risk of any redundant information stored locally being stale or meaningless. Take the length of the content stream for example. One use case for external content is that the content is housed and continues to be used on a legacy system but just cataloged by the CMIS repository. This means that the size and other attributes may be constantly changing. Another case is where the external reference is a live stream. For example the CMIS document is metadata about the live camera stream for Camera X in Factory Y Floor Z. The external url is the actual live video stream, so length is meaningless here as well. The external content could also be to dynamic web resources (think of a an ATOM feed for example) which have similar issues.
Mime type:
I will admit that the mime type is less likely to be changing so your line of questioning has convinced me that the addition of that field would be useful here. (see updated design at the end of this comment)
cmis:contentStreamFilename and cmis:contentStreamMimeType
These fields are strictly for cmis (native) content streams and are to have no meaning pertaining to the external content I am suggesting. I do not intend to overload any legacy CMIS properties here with additional meaning. In addition I believe a externalContentStreamFilename (were we to create one) would not be necessary since the external stream is being permanently hosted somewhere else for a reason (i.e. you should not store it locally). The url for the external resource is (or at least should be) its only filename for all intents.
Your last question (4) about the security issues for the browser binding are outside the scope of this document, though I agree this might be an issue. What a client may do with that external content reference, or even how they might access it is not something I want to constrain or dictate here.
Updated model (proposal v0.2)
We will optionally define a new class (cmis:reference document) which would be the same as cmis:document but with two additional properties (to follow). If we chose to not have this whole new type then the following properties could just appear on cmis:document directly. (I would recommend a vote on this)
New properties for external content:
cmis:externalContent (type string) csrdinality (single)
cmis:externalContentMimetype (type string) cardinality (single)
Both of these properties would be optional. e.g. If they do not appear in the type definition for cmis:(reference)document , then they are not supported. This allows the feature to be defined with only the addition of the new names to the 1.1 spec.
> 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]