18.01.2015 Views

Content Management Interoperability Services (CMIS) Version 1.1

Content Management Interoperability Services (CMIS) Version 1.1

Content Management Interoperability Services (CMIS) Version 1.1

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Classification<br />

Fileplan<br />

Retention Schedule<br />

Doc 1<br />

Finance<br />

Retention Rule 1<br />

Doc 2<br />

Travel<br />

Retention Rule 2<br />

Incidents<br />

Retention Rule 3<br />

Doc 3<br />

Audits<br />

Retention Rule 4<br />

Retention Rule 5<br />

Doc 4<br />

Reports<br />

Retention Rule 6<br />

Doc 5<br />

Requests<br />

Retention Rule 7<br />

Inspections<br />

Retention Rule 8<br />

Doc 6<br />

Figure 2.7: Classification<br />

Support for Repository Managed Retentions is optional. A repository that does not support Repository Managed<br />

Retentions will not expose a file plan via the secondary type hierarchy. Repositories that support<br />

Repository Managed Retentions MUST expose the categories of the file plan as a subtype of the <strong>CMIS</strong> defined<br />

secondary type cmis:rm_repMgtRetention. The secondary type cmis:rm_repMgtRetention<br />

does not require any properties. A repository MAY add repository specific properties. A secondary type hierarchy<br />

for Repository Managed Retentions could look like this (white boxes are <strong>CMIS</strong> defined types, orange<br />

boxes are repository specific):<br />

<strong>CMIS</strong>-v<strong>1.1</strong>-csprd01<br />

Standards Track Work Product<br />

Copyright © OASIS Open 2012. All Rights Reserved.<br />

18 August 2012<br />

Page 116 of 331

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!