Re: [cmis] CMIS Extension Proposal: Content Hash Property

hi Florian,

Great idea to add a hash!

One thought I had on the hash proposal was that it may make sense for this to be a multi-value property, to support more variety in the client's choice of hash which not always match the server's one choice.

The behaviour of hash when using appendContentStream should be described. Probably it ends being a server implementation choice whether to recompute the hash on each chunk or only when isLastChunk=true. While appending is happening (until isLastChunk=true) the value of cmis:contentStreamHash may then become "not set".

I assume when deleteContentStream happens, the value of cmis:contentStreamHash becomes "not set"?

Instead of the structured format {<hash algorithm>}<hash value>, could we instead adopt some JSON object format like {<hash algorithm>:<hash value>}. Or would that be too weird for AtomPub clients?

One thought on the process for extensions is to always have a jira ticket for the proposal and then we can use Jira commenting instead of the list?

tx!

Greg

On 6 December 2013 06:47, Mr. Florian Mueller <florian.mueller02@sap.com> wrote:

Hi,

I've uploaded a proposal [1] for a CMIS feature extension (as defined in the CMIS 1.1 specification).
I would like to discuss it for two reasons. First of all, it would be good to have an optional property that provides the hash value of the document content. But I would also like to use this proposal to start a discussion about a template for such feature extension specifications.

Thanks,

Florian

[1] https://www.oasis-open.org/apps/org/workgroup/cmis/download.php/51648/cmis-extension-content-hash.pdf

Greg Melahn | Principal Software Architect
o +1 919 656 9717 | m +1 919 656 9717 | skype gregory.melahn

cmis message