To all on the dam-cmis-profile-discuss@ mailing list:
The efforts of the participants on the list led to a draft Technical Committee charter that you will find appended below. OASIS and the proposers are now soliciting comments on the charter prior to starting this new initiative. The comment period remains open until 23:59 UTC on 16 September 2014.
If you have questions or comments on the draft charter, please feel free to share them here. Once the TC is formally announced, I will be closing this list.
Our congratulations and thanks to all who helped define and launch this effort.
—- TC Charter
(1)(a) TC Name
OASIS Content Management Interoperability Services for Digital Asset Management (CMIS4DAM) Technical Committee
(1)(b) Statement of Purpose
The Content Management Interoperability Services for Digital Asset Management (CMIS4DAM) TC aims to resolve interoperability challenges facing Digital Asset Management (DAM) solution providers and their end users by leveraging the existing CMIS standard already adopted by the Enterprise Content Management sector.
CMIS is a comprehensive standard, however the specification’s scope and scale sometimes makes it difficult for DAM vendors to benefit from adopting it; many require only small subsets of CMIS capabilities, and many have limited time and staff resources to devote to understanding CMIS in sufficient detail to identify and implement those parts they can use. This is unfortunate because for each type of vendor, elements of the CMIS standard can enable important, needed interoperability capabilities.
Further, the range of alternative metadata standards used by the rich media stored inside DAM solutions also requires a more adaptable framework that can share the common elements of a widely adopted standard like CMIS while leaving open the opportunity to expand its scope on a case-by-case basis. For example, a photo management solution may need to interoperate with general CMIS Enterprise Content repositories as well as with photo-specific metadata standards such as IPTC or PLUS, while a video-focused media asset management application might substitute the latter for audio-visual standards such as PBCORE. The range and significance of each of these associated endeavors and the necessity for a given solution provider to integrate with them cannot be accurately predicted and will change over time.
In addition to enabling metadata interoperability, a further objective of CMIS4DAM is to define a series of common operations which compliant DAM solutions will respond to in a predictable and consistent fashion. As with metadata, the range and scope of these is intended to be flexible and extensible, such that individual applications can support certain functions to a greater or lesser extent according to areas in which each specializes. A core or baseline series of operations will be defined as part of this activity.
CMIS4DAM is intended to offer a layer of abstraction between CMIS and a range of external metadata classification protocols, together with common operations used within the DAM domain, especially as they relate to individual classes of rich media assets such as images and video. The purpose is to assimilate these models and to use CMIS as the conduit to enable interoperability between them. The goal of CMIS4DAM is to enhance the cohesion between different DAM solutions and provide a more flexible protocol that is easier for a wider range of participants to engage with than the core CMIS standard alone offers.
CMIS4DAM needs to provide a flexible and structured framework which can be rapidly implemented at a basic level to enable widespread participation, while at the same time enabling a wide-ranging series of related standards to be connected into it on an as-needs basis. It is anticipated, therefore, that a major element of the work of the Committee will be education oriented to meet the first objective, and the second may need to be accommodated with Subcommittees to address the specific needs of individual standards and the characteristics necessary to facilitate their integration into CMIS4DAM. The scope of this TC is to provide a framework rather than to prescribe a finite list of external metadata standards that should be adopted.
The TC will develop example CMIS mappings targeted at DAM applications to assist DAM solution developers to rapidly access assets (represented as documents) in existing CMIS-compliant repositories.
The TC will propose an initial list of candidate external standards (with a specific interest in those relating to asset metadata) which will be included in the first iteration of the standard documentation.
The TC will reach out to bodies responsible for additional external standards that may be utilized by DAM with the aim of encouraging their participation.
The TC will solicit opinions from DAM vendors, industry associations, and journals to define a baseline set of operations or functions which compliant DAM solutions should support.
The TC will define protocols that allow the baseline operations to be extended on a selective basis by system developers while still allowing them to maintain a compliant solution.
The TC will develop a documented procedure for incorporation of new DAM-related metadata standards so that this process can become more efficient and incorporate best practice methods (as well as any subsequent refinement of these same procedures).
* A document describing the specific use cases of CMIS4DAM that the TC plans to address in its work product
* Introductory core CMIS implementation models intended for managers and technical practitioners that explain how to implement CMIS4DAM at a basic level
* Advanced implementation models and frameworks that expand upon the introductory items to include coverage of any initial metadata standards encompassed by CMIS4DAM
* Terminology guidelines and glossary (to be integrated with the DAM Glossary being developed at damglossary.org
* Documentation describing core operations and instructions for extending them to support specialized functionality in a compliant manner
(1)(e) IPR Mode
DAM solution providers and end users
Enterprise Content Management (ECM) solution providers who have implemented CMIS and wish to integrate with a broader range of DAM solutions
Section 2: Additional Information
(2)(a) Identification of Similar Work
DCMI (Dublin Core Metadata Initiative) – A series of core metadata elements used to describe both digital and physical resources - http://dublincore.org/
IPTC (International Press Telecommunications Council) Photo Metadata Standard – A standard which defines a range of metadata fields for use with photos (often stored within the image file itself) - http://www.iptc.org/site/Photo_Metadata/Overview/
(2)(b) First TC Meeting
The first meeting of the TC will be held 28 October 2014 at 12pm ET. The first meeting will be held by teleconference. Daydream will sponsor the first meeting and provide the conference call facilities.
(2)(c) Ongoing Meeting Schedule
The TC will meet biweekly on a schedule to be determined at the first meeting. Hosting of the meeting will rotate through the TC members.
(2)(d) TC Proposers
(2)(e) Primary Representatives' Support
- I, John Newton <email@example.com
>, as Alfresco's primary representative, support the proposed CMIS4DAM charter and intend to participate in the Technical Committee. I can confirm the participation of our employee Ray Gauss as a member.
- I, Mark Davey <firstname.lastname@example.org
>, as the DAM Foundation's Primary Representative, support the proposed CMIS4DAM charter and intend to participate in the Technical Committee.
I believe the DAM (and all associated acronyms) industry needs an interoperability standard that works for end users, integrators and vendors alike. We need to move this needle as complexity grows. I would like to see and help OASIS bring the CMIS4DAM into being.
- I, Ken Baclawski <email@example.com
>, as Northeastern University's Primary Representative, support the proposed CMIS4DAM charter and intend to participate in the Technical Committee.
I am especially interested in the metadata feature of DAM as this could provide important new functionality beyond that provided by CMIS.
- I, Sascha Homeier <firstname.lastname@example.org
>, as Merle+Mueller's Primary Representative, support the proposed CMIS4DAM charter and intend to participate in the Technical Committee.
I think this work is worth doing because I really value the parent standard CMIS and its benefits and during my work on implementing a CMIS server and several CMIS clients I noticed that CMIS does not cover some points which we, at Meyle+Mueller as DAM vendor, would like to address. This mainly includes services to get previews (proxy images/renditions) and workflow support.
Provided that such a profile gets widely adopted I personally think it offers good prospects in respect to interoperability. This also was the main reason why we decided to integrate CMIS: Our DAM can easily ‘speak’ with other systems.
(2)(f) TC Convener
(2)(g) OASIS Member Section
(2)(h) Anticipated Contributions
(2)(i) FAQ Document
(2)(j) Work Product Titles and Acronyms
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information societyhttp://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393