PLAT-3 CMIS — What’s coming next?

CMIS – Whatʼs coming next?"Jeff Potts, Chief Community Ofﬁcer, Alfresco Software"

Agenda"•  What’s Happened?•  CMIS Refresher•  Coming Soon – CMIS 1.1•  What’s in the Future? – CMIS 2.0•  CMIS in Alfresco 4•  Questions?

Whatʼs Happening?"

Whatʼs Happened?" Development CMIS 1.0 Plug-‐Fest in May started by EMC, released for TC working on IBM & Microso@ public comment CMIS 1.1 2006 2008 2009 2010 2011 IniAal Proposal CMIS 1.0 SubmiEed to OASIS RaAﬁed in May and TC formed

Whatʼs Happened?"Original Goals and Scope •  Enable applications to target different ECM repositories uniformly" •  Provide a set of basic services enabling richer ECM applications and use cases" •  Allow for loose coupling of an ECM application and the underlying repository" •  Use popular protocol bindings" •  REST / AtomPub" •  Web Services / SOAP"Were we successful?

Whatʼs Happened?"Current State of the CMIS Ecosystem •  Implemented by every major ECM repository vendor" •  More than 50 CMIS applications" •  Alfresco is leading the charge" Providers Consumers

Some CMIS Producers"•  Adobe (Day Software) •  Microsoft SharePoint 2010 CRX) •  Nuxeo•  Alfresco! •  O3spaces•  Apache Chemistry! •  OpenIMS•  eXo Platform" •  OpenText•  Fabasoft" •  OpenWGA•  IBM FileNet, Lotus" •  Seapine Surround SCM•  ISIS Papyrus" •  Sense/Net•  KnowledgeTree" •  TYPO3

Some CMIS Client Applications"•  Adobe Drive" •  Drupal 6.x!•  Alfresco Mobile! •  Hippo CMS"•  Apache Chemistry! •  Liferay"•  cmislib! •  Wordpress•  cmis-php-client" •  Papyrus•  DotCMIS" •  WeWebU•  OpenCMIS! •  Open Workdesk"•  CMIS Spaces" •  Zero-Install Desktop"•  DITALabs" •  Zia Fresh Docs

Whatʼs Happened?" •  Highlighted as an open source option for provider and consumer implementers" •  Top-level Apache project" •  Client libraries / APIʼs" •  Java (OpenCMIS)" •  .NET (DotCMIS)" •  PHP (CMIS PHP Client)" •  Python (cmislib)" •  CMIS Workbench: graphical client, groovy console" •  OpenCMIS Server – interfaces to implement for a java provider"

Whatʼs Happened?"State of the CMIS Technical Committee (TC)" •  CMIS 1.0 errata – Vote just passed; Needs to be published" •  CMIS Technical Committee working on CMIS 1.1" •  Already talking about issues and ideas for CMIS 2.0"

CMIS Refresher"Domain Model •  Data Model" •  Services"Protocol Bindings •  RESTful AtomPub" •  Web Services"

CMIS Refresher"Repository •  Contains folders, documents and other objects" •  Must provide all basic services in the CMIS speciﬁcation" •  Must provide REST and SOAP bindings" •  Advertises capabilities through a service"

CMIS Refresher"Object Types •  Stricly-typed data model" •  Each object has an object type" •  Four base object types:" •  Document, Folder, Relationship & Policy" •  Base types may have sub-types"

CMIS Refresher"Properties •  All objects have properties" •  A property holds zero to many typed values" •  Property deﬁnitions have attributes" •  Common attributes e.g. ID, PropertyType, Cardinality" •  Property type speciﬁc attributes e.g. precision for decimals" •  Property data types" •  String, Boolean, Decimal, Integer, Datetime, Id, Uri and Html"

CMIS Refresher"Documents •  Instance of the document base type or sub-type" •  Documents have properties and optionally a content stream and renditions" •  Content streams are normally set and retrieved in separate operations" •  Documents may be versionable"

CMIS Refresher"Folders •  Folders can contain folders and documents" •  Any other kind of object that is declared to be ﬁleable" •  Folders cannot have more than one parent folder" •  Folders can decide what types they contain" •  A folder can specify it may only contain document of a given content type" •  Documents may optionally be unﬁled" •  Documents may optionally belong to multiple folders"

CMIS Refresher"Relationships •  A directional relationship between any two objects" •  An object can have any number of relationships including with itself" •  A relationship has a source and target but this ʻdirectionʼ has no CMIS-deﬁned semantics" •  Referential integrity is not enforced" •  When the relationship is created, both end-points must exist" •  Repository support for relationships is optional"

CMIS Refresher"Policies •  An administrative policy that can be enforced by a repository" •  Used to manage objects in ways that are, by themselves, outside the scope of CMIS" •  Such as records retention" •  policyText property contains the details of the policy" •  Policy text is opaque to the CMIS repository" •  Repository support for policies is optional"

CMIS Refresher"Access Control •  Permission" •  An allowed action (read, write, all)" •  Mapping to allowed actions is repository speciﬁc and discoverable" •  Principal – a user or a group" •  Access Control Entry (ACE)" •  One or more permissions granted to a Principal" •  Access Control List (ACL)" •  A collection of ACEʼs" •  Can be assigned to an object and can be propagated" •  Repository support for Access Control is optional"

CMIS Refresher"Versioning •  A document may be versioned as indicated by the type deﬁnition" •  Versions represent the properties and content of a document at a given point in time" •  All versions of a document collectively deﬁne its Version Series" •  CheckOut creates a Private Working Copy which can be edited and checked in"

CMIS Refresher"Query •  Based on well known standard – SQL-92" •  With ECM extensions added" •  Each type is treated as a logical relational table" •  Joins may be supported" •  Either inner, or both inner and outer joins" •  Repository speciﬁc behavior" •  Query supports metadata and/or full-text" •  Repository support for full-text search is optional"

CMIS Refresher"Services •  Eight sets of services:" •  Repository, Object, Discovery, Navigation, Versioning, Relationship, Policy and ACL" •  Support for create, read, update and delete operations for various types" •  Some examples:" •  Repository Services: getRepositories, getRepository, getTypeDeﬁnition" •  Navigation Services: getChildren, getFolderParent, getObjectParents" •  Object Services: createDocument, createFolder, getObject, getObjectByPath, getContentStream, deleteObject" •  Versioning Servcies: checkOut, cancelCheckOut, checkIn, getAllVersions"

CMIS Refresher"Protocol Bindings •  Providers must implement RESTful AtomPub and SOAP"RESTful AtomPub •  Feeds, entries & links" •  GET, POST, PUT, DELETE" •  Example: createDocument by POST to parent folderʼs collection" •  Recommend HTTP Basic Authentication"Web Services •  SOAP" •  WSDL and XSD are deﬁned in the speciﬁcation" •  Recommend Basic Authentication and WS Security UsernameToken"

Coming Soon to CMIS" Credit: Mo Morgan

Coming Soon – CMIS 1.1"Browser Binding – CMIS-719 •  Designed to allow developers to build browser based applications" •  Use already understood technologies including" •  HTML, HTML Forms, JavaScript and JSON" •  Does not require a JavaScript library" •  Optimized for use in a browser, also useful for HTTP based bindings for other application types"

Coming Soon – CMIS 1.1"Browser Binding – CMIS-719 •  HTTP Protocol" •  Predictable URLʼs" •  JSON Data Representation" •  Described by orderly: http://orderly-json.org" CMIS JSON String string Boolean boolean Decimal number Integer number DateAme number (milliseconds since 1970/01/01, UTC) Uri string Id string Html string

Coming Soon – CMIS 1.1"Browser Binding – CMIS-719 •  Uses HTTP GET and POST exclusively" •  HTML forms used to POST content must include “cmisaction” to describe the action to perform e.g. createDocument, createFolder, etc." •  Various controls speciﬁed per operation" •  Details here:" •  http://bit.ly/tlACld"

Demo!"Browser Binding in Alfresco •  More efﬁcient than Web Services and the AtomPub binding" •  Try it! http://cmis.alfresco.com/" •  JSONView Firefox extension" •  Alfresco Community 4.0b"

Coming Soon – CMIS 1.1"Type Mutability – CMIS-669Use Cases •  CMIS Application needs to install its own metadata and uninstall if removed" •  CMIS Repository migration application would not only migrate documents from one repository to another; but would be able to migrate and preserve the metadata as well" •  General purpose Administration applications that allow administrators to edit metadata for new systems"

Coming Soon – CMIS 1.1"Type Mutability – CMIS-669Requirements •  Must be optional and backward compatible with 1.0" •  Must be implemented in a way such that is it obvious to someone familiar with CMIS 1.0 how these operations would be implemented" •  POST to the ʻTypes Childrenʼ collection creates a new type, etc." •  Must allow an application to setup new types with associated new properties" •  Optionally allows an application to delete types it has created" •  Exposed schema changes will be conﬁned to a small footprint" •  A Type Mutability aware CMIS 1.1 client MUST work ﬁne with a CMIS 1.0 (non Type Mutability) aware server"

Coming Soon – CMIS 1.1"Type Mutability – CMIS-669 •  Discoverable Optional Capability exposed on a type" •  cmisTypeMutabilityCapabilitiesType enum" •  create (new child types), update, delete" •  New services: createType, updateType and deleteType" •  Details here:" •  http://bit.ly/v9zeYg"

Coming Soon – CMIS 1.1"Secondary Object Types – CMIS-713 •  Aspects!"Use Cases •  Additional metadata has to be attached after the document has been created" •  Adding a new set of properties is necessary for some business cases" •  Some technical metadata derived from the content can only be added after the repository has analyzed the content" •  Some common and crosscutting concepts such as tags, comments and ratings can be implemented with secondary types." •  Secondary types and their properties can reveal and control the status of an object. Examples are legal holds, workﬂows, storage/ archiving information, publishing information, etc."

Coming Soon – CMIS 1.1"Secondary Object Types – CMIS-713 •  New base type: cmis:secondary " •  Other base types have new attribute: cmis:secondaryObjectTypeIds " •  Added to updateProperties and checkIn services" •  Properties are returned via query operations" •  Can be ﬁltered using property ﬁlter syntax" •  Details here:" •  http://bit.ly/syhlzW"

Coming Soon – CMIS 1.1"Approved •  CMIS Repository Extensions (CMIS-693)" •  Allow Creation of Unﬁled Documents with AtomPub (CMIS-711)" •  Description Property for all Base Types (CMIS-712)" •  Retention & Hold (CMIS-714)" •  Currently proposed to split these into separate proposals"

Coming Soon – CMIS 1.1"Under Consideration •  External Content Reference (CMIS-705)" •  Batch Operations (CMIS-727)" •  Is PWC the latest version? (CMIS-728)" •  Query Wildcard Clariﬁcation (CMIS-729)"

Whatʼs in the Future? – CMIS 2.0"•  Pessimistic Locking (CMIS-196)•  Multiple Content Streams on Documents (CMIS-432)•  Remove base64 content stream encoding (CMIS-466)•  Reconsider Renditions Implementation (CMIS-645)•  Annotations (CMIS-722)•  Tagging (CMIS-726)

CMIS Technical Committee Info"All work publicly accessibleTC Wiki •  http://bit.ly/t1IUCw"All OASIS JIRA Issues •  http://bit.ly/vEHttJ"

Whatʼs new with CMIS in Alfresco 4?"

CMIS implementation is based on OpenCMIS"Why has it been re-implemented? • OpenCMIS is used by several CMIS repositories.  Alfresco automatically benefits from all bug fixes and improvements." • One code base for the AtomPub and the Web Services binding   (and the Browser Binding)." • Better CMIS specification compliance." • Better performance, less memory consumption,   handling of big documents."

CMIS implementation is based on OpenCMIS"How does this affect CMIS clients? •  New URLs…" • The old implementation and URLs will be available but are deprecated." • Speciﬁcation compliant, generic CMIS clients shouldnʼt see a difference." •  Aspects and the Alfresco OpenCMIS Extension work as before." •  If the CMIS Client make any assumptions about the format the object id, it has to change! (See next slides.)"

CMIS Document IDs in Alfresco 4"Alfresco 3.X Object Ids: • Current version document id: "node ref  workspace://SpacesStore/e5787fce-7583-4b74-8836-8dcc94df4493! • Version document id: current version node ref + “;” + version label  workspace://SpacesStore/e5787fce-7583-4b74-8836-8dcc94df4493;1.0! • The creation of a new version doesnʼt change the current version document id.  Not spec compliant!! • A client must not assume that a document id always represents the current version!"

CMIS Document IDs in Alfresco 4"Alfresco 4.X Object Ids: • Current version document id: "node ref + “;” + version label  workspace://SpacesStore/e5787fce-7583-4b74-8836-8dcc94df4493;1.1! • Version document id: current version node ref + “;” + version label  workspace://SpacesStore/e5787fce-7583-4b74-8836-8dcc94df4493;1.0! • The creation of a new version changes the current version document id.  Spec compliant!! • General advice: Treat the object id as an opaque string."

OpenCMIS client available in web scripts"Use case examples: • Alfresco Share mashups and federated queries" • Synchronize documents between repositories" • Publishing scenarios" • Simple migration scenarios"

OpenCMIS client available in web scripts"New JavaScript top level object: cmis •  This object manages connections to CMIS servers." •  Three connection types:" •  Current Alfresco server (uses OpenCMIS local binding if possible)" •  Preconﬁgured connection" •  Web script conﬁgured connection" var cmisConnection = cmis.getConnection(myConnectionId); var cmisSession = cmisConnection.getSession(); model.folder = cmisSession.getRootFolder(); model.children = model.folder.getChildren().iterator();

Demo!"Share Extras JavaScript console + cmis root object

Resources"OASIS CMIS TC • http://www.oasis-open.org/committees/cmis" • http://tools.oasis-open.org/issues/browse/CMIS"Live CMIS server • http://cmis.alfresco.com"Apache Chemistry • http://chemistry.apache.org"Florianʼs Tech Talk Live Session on CMIS" • Recorded webex http://bit.ly/tTW9ZX" • Slides: http://slidesha.re/uL8IKI"

Questions? jeff.potts@alfresco.com  @jeffpotts01 http://ecmarchitect.com"

PLAT-3 CMIS — What’s coming next?

by Alfresco Software on Nov 14, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

PLAT-3 CMIS — What’s coming next? — Presentation Transcript