PowerPoint Presentation


Published on

PowerPoint Presentation

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • When SQL was introduced the CEVA use case enabled the growth of enterprise business software like ERP
  • PowerPoint Presentation

    1. 1. Breaking down contentsilos with CMISBas PetersOpen Source Conference 2011
    2. 2. Bas PetersUvA, Information ScienceUL, Dutch Language and LiteratureStarted career in academic publishingWorked for large consultancy firm and for manycustomers in publishing, government, retailbanking, industryCurrently Solutions Architect focusing onECM, Alfresco and open source at Incentro
    3. 3. Breaking down content silos with CMISINTRODUCTION
    4. 4. ECMEnterprise Content ManagementCapture, manage, store, preserve, anddeliver content and documents related toorganizational processesAllow the management of an organizationsunstructured information, wherever thatinformation exists
    5. 5. Content as a service CMS Implementation Document Collaboration & Web Content Records E-mailManagement Social Media Management Management Archive
    6. 6. Improve ECM interoperability
    7. 7. CMIS goalsEnable applications to target different ECMrepositories uniformlyProvide a set of basic services enabling richer ECMapplications and use casesAllow for loose coupling of an ECM application andthe underlying repositoryUse popular protocol bindings REST / AtomPub Web Services / SOAP
    8. 8. Some say that...“CMIS is as important to contentmanagement applications as thestandardization of SQL was todatabase applications in the late1980’s and early 1990’s”
    9. 9. OASISOASIS was founded under the name "SGML Open" in 1993Organization for the Advancement of StructuredInformation StandardsNot-for-profit consortium that drives thedevelopment, convergence and adoption of openstandards for the global information societyStandards: Darwin Information Typing Architecture (DITA) DocBook v5.0 ebXML Business Process OpenDocument Format for Office Applications SWS (Search Web Services)
    10. 10. CMIS timelineCommittee members includedMicrosoft, EMC, IBM, SAP, Alfresco, Oracle, Day andOpenText http://www.slideshare.net/alfresco/cmis-spec-uncovered
    11. 11. Providers ConsumersVendor support
    12. 12. Breaking down content silos with CMISUSE CASES
    13. 13. Use CasesLaurence Hart compiled a list of CMIS usecases: Repository-to-Repository (R2R) Application-to-Repository (A2R) Federated Repositories
    14. 14. Repository-to-Repository (R2R)Managing Records centrally that are storedin other repositoriesPublishing content from one repository toanother CMIS
    15. 15. Application-to-Repository (A2R)SharePoint or Alfresco Share as a front-endEnterprise Software Applications(BPM, CRM, Capture)Content Enabled Vertical Applications(CEVA)Productivity applications (Office integration) CMIS
    16. 16. Federated RepositoriesFederated Search CMIS Client searches multiple repositories CMIS Client crawls multiple repositoriesFederation instead of migration CMIS
    17. 17. Breaking down content silos with CMISTHE STANDARD
    18. 18. PartsDomain modelServicesQuery languageProtocol bindings REST / AtomPub Web Services / SOAP
    19. 19. Breaking down content silos with CMISDOMAIN MODEL
    20. 20. Domain modelCopyright ©2011 Alfresco Software Inc.
    21. 21. Base object type properties
    22. 22. Custom typesCustom types can extend the CMIS types Copyright ©2011 Alfresco Software Inc.
    23. 23. Folder hierarchyDocument objects live in a folder hierarchyCopyright ©2011 Alfresco Software Inc.
    24. 24. VersionsDocument Objects are the only object typethat can be versioned Copyright ©2011 Alfresco Software Inc.
    25. 25. Content accessDocument Objects provide access to contentstreams and enable retrieval of renditions Document Rendition  Mime Type  Kind  Mime Type Content Stream  Stream Id
    26. 26. Policy objectA policy object represents an administrativepolicy that can be enforced by a repository ACL (Access Control Lists) Retention policies Aspects in Alfresco
    27. 27. Breaking down content silos with CMISCMIS SERVICES
    28. 28. CMIS services
    29. 29. Create folderhttp://localhost:8080/alfresco/s/cmis/p/children Content-Type: application/atom+xml Request Body:
    30. 30. Breaking down content silos with CMISQUERY LANGUAGE
    31. 31. Query languageBased on SQL 92, with ECM extensions andsupport for metadata and full text SELECT with a target list FROM with the object types being queried JOIN to perform a join between object types WHERE with the predicate IN and ANY to query multi-value properties CONTAINS to specify a full-text qualification IN_FOLDER to search children within a folder IN_TREE to search within a folder hierarchy ORDER BY to sort the results
    32. 32. Queryhttp://localhost:8080/alfresco/s/cmis/queries Content-Type: application/cmisquery+xml Request Body:
    33. 33. Non-strict queriesRetrieve aspects in AlfrescoSELECT d.*, t.*, a.* FROM cmis:document AS dJOIN cm:titled AS t ON d.cmis:objectId = t.cmis:objectIdJOIN cm:author AS a ON d.cmis:objectId = a.cmis:objectIdWHERE IN_FOLDER(d, 40312a4b-7767-4586-a58b-18d050ffe0ca)AND CONTAINS(d,sample)
    34. 34. Breaking down content silos with CMISPROTOCOL BINDINGS
    35. 35. RequirementsNeutral Any Programming Language Any Operating System Any EnvironmentRequired Web Service Client Library HTTP Client Library There are client libraries available in all general languages including Java, PHP, .NET, JavaScript and Python
    36. 36. Web Services /SOAP bindingService-oriented bindingCMIS-specified XML schemaCapable for system-to-system accessUse MTOM to transfer content streamRecommend Basic Authentication and WSSecurity UsernameTokenTransactional Applications
    37. 37. REST / AtomPub bindingResource-based bindingAtomPub format with OpenSearch and CMISextensionsBrowse-able by standard Atom feed readersSuitable for RESTful-style application-to-system accessRecommend HTTP Basic AuthenticationWeb-based Applications
    38. 38. Breaking down content silos with CMISFUTURE DIRECTIONS
    39. 39. Future directionsBrowser binding (1.1)Secondary Object Types (1.1)Type Mutability (1.1)Retention policiesAnnotations
    40. 40. Browser bindingSimplify uploading documents from abrowser application (e.g. using HTML Form)Simplify parsing (e.g. using JSON instead ofXML)Does not require a JavaScript librarySimplify construction of required objectmetadata (e.g. constructing links)
    41. 41. Secondary object typesAdditional metadata has to be attachedafter the document has been created.Some common and crosscutting conceptssuch as tags, comments and ratings can beimplemented with secondary types.Properties of secondary types can alsoreveal the status of an object.
    42. 42. Type mutabilityCMIS Application needs to install its own metadataand uninstall if removed.CMIS Repository migration application would notonly migrate documents from one repository toanother; but would be able to migrate andpreserve the metadata as well.General purpose Administration applications thatallow administrators to author metadata for newsystems.
    43. 43. Retention policiesThe rules for retention policies on invoices are maintainedin the ERP systemWhen a fax image is attached to the invoice data in the ERPsystem, the ERP system Creates the appropriate CMIS Policy for the retention if it does not already exist Applies the CMIS Policy for the retention to the CMIS Document with the fax image CMIS
    44. 44. AnnotationsAbility to create and retrieve annotationsassociated to documents: To highlight a section of text Pinpoint a specific item in an image Provide a small note or comment during a particular stage within the process of the documents lifecycle
    45. 45. ConclusionCMIS is a well designed standardIt supports relevant use casesAll big vendors are involved, although opensource seems to be leadingIt remains to be seen if it will become as bigas SQL
    46. 46. Breaking down content silos with CMISQUESTIONS?