OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oasis-charter-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: CMIS Revised Charter

The following revised charter has been submitted by the Convener on behalf
of the co-proposers of the OASIS Content Management Interoperability
Services (CMIS) Technical Committee. The Call for Participation will be
issued on Monday, 6 October 2008.


1A Name of the TC: 

Content Management Interoperability Services (CMIS) Technical Committee

1B Statement of Purpose: 

Historically content management systems were purchased for specific
application uses and this led to islands of incompatible systems.  The lack
of a standard interface to content management systems made it difficult to
integrate content from multiple repositories into a single application such
as a portal, CRM system, or office desktop.  It also made it difficult for
Independent Software Vendors (ISVs) and integrators to build applications
that supported multiple content management systems consistently or easily.  

The purpose of the Content Management Interoperability Services (CMIS) TC
will define a domain model including a data model and abstract capabilities
for Content Management (CM) and a set of bindings that can be used by
applications to work with one or more Content Management
Repositories/systems and that can be implemented by content repositories and
enable interoperability across repositories for the set of use cases below.
These capabilities and interfaces will not match every existing content
management system and may require some level of change to existing products,
at least in terms of conforming existing interfaces to those defined here.
However, it is an explicit goal that CMIS Domain Model and Bindings will NOT
require major product changes or significant data model changes in existing
major CM repositories.

As such, the CMIS TC should define a domain model and bindings that are
designed to be layered on top of existing Content Management systems and
their existing programmatic interfaces. This TC should not prescribe how
specific features should be implemented within those Enterprise Content
Management (ECM) systems. This TC is intended to define a generic/universal
set of capabilities provided by an ECM system and a set of services for
working with those capabilities.  

1C Scope of work:

The TC will accept as input Version 0.5 of the CMIS specification as
published by EMC, IBM and Microsoft on September 10th, 2008. The
specification is located at:
* http://community.emc.com/community/labs/cmis
* http://www.microsoft.com/sharepoint/capabilities/ecm/cmis.mspx 

Other contributions and changes to the input documents will be accepted for
consideration without any prejudice or restrictions and evaluated based on
technical merit in so far as they conform to this charter.  

The initial set of deliverables will be targeted for the following use
* Collaborative Content Applications
* Portals leveraging Content Management repositories
* Mashups
* Searching a Content Repository

The following use cases should be able to be supported by CMIS Domain Model
and Bindings, but are not primary drivers:
* Workflow and Business Process Management (BPM)-centric applications
utilizing Content
* Archival Applications
* Compound and Virtual Documents
* Electronic and Legal Discovery
The following use cases are out of scope for the initial set of
* Records Management (RM) and Compliance
* Digital Asset Management (DAM)
* Web Content Management (WCM)
* Subscription and Notification Services

Also, this TC will engage in maintenance of the specifications produced by
this TC.

The tasks of the TC include:
* To articulate the principles of the interoperable content management
through formal specifications 
* To assess the relationship of CMIS to other related standards and industry
efforts.  These include Java Content Repository (JCR) (JSR-170, JSR-283),
WebDAV and its related specifications including DASL, Search Web Services
TC, and other relevant standards.
* To define appropriate specifications for interoperable content management 
  o Including schemas, such as XML Schema Definition (XSD)
  o Including service definitions, such as Web Service Definition Language
* To standardize the common types of entities and capabilities in CM
* To encourage cooperation within and between the various topical domains
and groups

After the first set of deliverables, the TC will continue to work on the
next versions of the specification.  Specific functional content of the next
versions will be determined by a TC vote.  The next versions may address the
following use cases:
•	Core ECM Repository capabilities 
•	Collaborative Content Applications 
•	Portals leveraging Content Management repositories 
•	Mashups utilizing Content 
•	Workflow and BPM-centric applications utilizing Content 
•	Content Archival Applications 
•	Compound and Virtual Documents applications
•	Electronic and Legal Discovery of Content applications
•	Records Management and Compliance 
•	Digital Asset Management  Applications
•	Web Content Management Applications
•	Information Rights Management applications
•	Desktop Integration of Content Management repositories 

The TC MAY define other bindings explicitly listed below after the first
•	Web Services 


Once the TC has completed work on a deliverable and it has become an OASIS
standard, the TC will enter "maintenance mode" for the deliverable.

The purpose of maintenance mode is to provide minor revisions to previously
adopted deliverables to clarify ambiguities, inconsistencies and obvious
errors. Maintenance mode is not intended to enhance a deliverable or extend
its functionality.

The TC will collect issues raised against the deliverables and periodically
process those issues. Issues that request or require new or enhanced
functionality shall be marked as enhancement requests and set aside. Issues
that result in the clarification or correction of the deliverables shall be
processed. The TC shall maintain a list of these adopted clarifications and
shall periodically create a new minor revision of the deliverables including
these updates. Periodically, but at least once a year, the TC shall produce
and vote upon a new minor revision of the deliverables.

1D List of Deliverables:

The initial set of deliverables and projected duration: 
* CMIS Domain model specification (September 2009)
* CMIS SOAP-based Web Services binding specification (September 2009)
* CMIS REST/Atom-based Web Services binding specification (September 2009)

1E IPR Mode: 

The IP mode for the TC will be RF on RAND.

1F Audience for the TC:  

The primary audience for the final output of this TC includes ECM and BCS
application architects and ECM repository architects and implementers.

1G The language in which the TC shall conduct business:


2 – Non-normative information
2A identification of similar or applicable work that is being done in other
OASIS TCs or by other organizations:
	WebDAV: Not targeting ECM and does not provide a CM domain model
	JCR: Java based specification and does not specify a protocol

2B Date, time and place of the first TC meeting: 
* 12PM EST/9AM PST, 11/10/2008, conference call

2C On-going meeting schedule:
The CMIS TC will meet by telephone every other week at Monday 9AM PST.  The
time, date and recurrence of the periodic phone call will be confirmed at
the first TC meeting.  The meetings will last no more than two hours.  The
CMIS TC will hold face-to-face meetings 3 times a year for three days
* 1/26/2009 (Redmond, Washington, hosted by Ethan Gur-esh, Microsoft)

2D Names and email addresses of members (minimum three):
Albert Brown, albertcbrown@us.ibm.com
Cornelia Davis, Davis_Cornelia@emc.com
Craig Randall, Randall_Craig@emc.com
Derek Carr, dwcarr@us.ibm.com
David Caruana, david.caruana@alfresco.com
David Choy, Choy_David@emc.com
Dustin Friesenhahn, dustinfr@microsoft.com
Paul Goetz, paul.goetz@sap.com
Ethan Gur-esh, ethang@microsoft.com
Martin Hermes, martin.hermes@sap.com
Jens Hόbel, jhuebel@opentext.com
Ryan McVeigh, ryan.mcveigh@oracle.com
Gregory Melahn, melahn@us.ibm.com
Pat Miller, patmill@microsoft.com
Florian Mόller, fmueller@opentext.com
John Newton, john.newton@alfresco.com
Norrie Quinn, quinn_norrie@emc.com
Steve Roth, steve.roth@oracle.com	
Dennis Hamilton, dennis.hamilton@acm,org
David Nuescheler, david@day.com

2E Convener
Al Brown, IBM, albertcbrown@us.ibm.com

2G Input Specifications
CMIS Part I – Domain Model v0.5
CMIS Part II – Web Services Binding v0.5
CMIS Part II – REST-Atom Binding v0.5
CMIS -- Appendices v0.5 

(Available at:
* http://community.emc.com/community/labs/cmis  
* http://www.microsoft.com/sharepoint/capabilities/ecm/cmis.mspx   )

2I Proposed Specification Title
Content Management Interoperability Standard, Domain Model
Content Management Interoperability Standard, Web Service Binding
Content Management Interoperability Standard, REST/Atom Binding

Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org  
web: www.oasis-open.org
phone: 1.603.232.9090

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]