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: RE: [cmis] Copying documents


Also, any one particular choice of semantics can be doable, but not all repositories a) have copy and b) implement the semantics differently. As such by including copy we make the life harder for repository vendors.

With respect to the rest atompub binding, how would copy be implemented and how would it be differentiated from addobjecttofolder or create? The Rest binding has a de-facto copy, retrieve the resource, remove the id, and post to the folder you want (actually same process as create except starting from an existing resource). File is the same scenario, except you leave the id in place.

-Al

Al Brown
Emerging Standards and Industry Frameworks
CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home
Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home

Office 714 327 3453
Mobile 714 263 6441
Email albertcbrown@us.ibm.com
CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.

Inactive hide details for Ethan Gur-esh ---03/05/2009 04:55:56 PM---Florent,Ethan Gur-esh ---03/05/2009 04:55:56 PM---Florent,


From:

Ethan Gur-esh <ethang@exchange.microsoft.com>

To:

Florent Guillaume <fg@nuxeo.com>, CMIS TC List <cmis@lists.oasis-open.org>

Date:

03/05/2009 04:55 PM

Subject:

RE: [cmis] Copying documents





Florent,

I'd agree with you that adding a copy method to CMIS wouldn't be especially difficult/complex from a spec perspective. The main reason we didn't do this initially was that we were concerned that the underlying semantics of the "copy" operation would be repository-specific.

For example:
- Does the new copy share the same "created date/by" metadata values as the original object?
- Do the policies/ACLs of the original object get copied to the new copy?
- What about the values of read-only properties generated by the repository?

That said, I'm not convinced that any of these problems are insurmountable -- and if you'd like to draft a proposal for a copy method, I'd be happy to have the group consider/review it. :)

- Ethan.

-----Original Message-----
From: Florent Guillaume [
mailto:fg@nuxeo.com]
Sent: Wednesday, March 04, 2009 10:03 AM
To: CMIS TC List
Subject: [cmis] Copying documents

Hi all,

As David Caruana pointed out on Twitter, there is no API to copy a document.
I'm sure it was considered before, so could people knowledgeable explain the reason why it was not felt that this primitive was necessary?

I understand that in theory copying can be done by the client by reading data and then writing it back into a new document, but this is horribly inefficient in many cases and as soon as you have big content streams.

What are the problems with introducing a copy primitive? I'm sure very few repositories don't have it natively, and furthermore if a client can do it then the repository's CMIS bindings themselves can do it as well, so why put that weight on the client and the network?

BTW copying folders (and their subtree of documents) would be needed to IMHO.

Thanks,
Florent

--
Florent Guillaume, Head of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]