incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "ChemistryProposal" by DavidNuescheler
Date Mon, 20 Apr 2009 16:31:35 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by DavidNuescheler:
http://wiki.apache.org/incubator/ChemistryProposal

The comment on the change is:
clarifications and added myself

------------------------------------------------------------------------------
  
  === Abstract ===
  
- Apache Chemistry is a generic Java language implementation of the upcoming [http://www.oasis-open.org/committees/cmis
OASIS CMIS] standard.
+ Apache Chemistry is a generic Java language implementation of the upcoming [http://www.oasis-open.org/committees/cmis
OASIS CMIS] specification.
  
  === Proposal ===
  
- Apache Chemistry is to provide a Java implementation of the CMIS standard, consisting of
a high-level API for developers wanting to manipulate documents, a low-level SPI close to
the CMIS protocol for developers wanting to implement a client or a server, and default implementations
for all of the above. Chemistry aims to cover both the !AtomPub and SOAP bindings defined
by the CMIS specifications.
+ Apache Chemistry is to provide a Java (and possibly others, like JavaScript) implementation
of an upcoming CMIS specification, consisting of a high-level API for developers wanting to
manipulate documents, a low-level SPI close to the CMIS protocol for developers wanting to
implement a client or a server, and default implementations for all of the above. Chemistry
aims to cover both the !AtomPub and SOAP bindings defined by the CMIS specifications.
  
  === Background ===
  
  The CMIS (Content Management Interoperability Services) defines a domain model and set of
bindings, such as AtomPub and SOAP that can be used by applications to work with one or more
Content Management repositories and systems. The standard aims to help providing vendor-neutral
formats to share information across Internet.
- The standard was originally promoted by three big ECM vendors (EMC, IBM and Microsoft) and
has been adopted by some other Content Management projects, both commercial and Open Source.
It is now in an early definition phase (started in September 2008); improvement of specifications
and compatibiliy among existing implementations are the short term goals for CMIS.
+ The submission of the specification was originally proposed by seven CMS vendors and since
that a number of other vendors have joined the OASIS TC, both commercial and Open Source.
It is now in an early definition phase (started in September 2008); improvement of specifications
and compatibility among existing implementations are the short term goals for CMIS.
  
  === Rationale ===
  
@@ -27, +27 @@

  The above mentioned pieces are able to make the development activity, towards a CMIS implementation,
easier and more successful.
  Having an healthy ecosystem will ensure a smoother implementation process, more compliant
products  and, ultimately, a wider adoption of the standard.
  
- The CMIS ecosystem has been successful in creating and documenting the basic standard, yet
it might potentially lack two very important components, that is a Reference Implementation
(RI) and a Technology Compatibility Kit (TCK). As much as such artifacts can be developed
independently by any CMIS proponent, the value of having a  neutral party as a steward of
actual code is to be considered. The Apache Software Foundation has been playing this kind
of role for many years, and can provide the perfect environment to foster contributions on
the CMIS theme with a great amount of expertise.
+ The CMIS ecosystem has been successful in creating and documenting early drafts the basic
standard, yet it might potentially lack two very important components, that is a Reference
Implementation (RI) and a Technology Compatibility Kit (TCK). As much as such artifacts can
be developed independently by any CMIS proponent, the value of having a  neutral party as
a steward of actual code is to be considered. The Apache Software Foundation has been playing
this kind of role for many years, and can provide the perfect environment to foster contributions
on the CMIS theme with a great amount of expertise.
  
  === Initial Goals ===
  
@@ -135, +135 @@

  || St├ęphane Lacoin          || slacoin@nuxeo.com             || ...              ||
  || Sun Seng David Tan       || stan@nuxeo.com                || ...              ||
  || Gabriele Columbro        || columbro@gmail.com            || ...              ||
+ || David Nuescheler         || uncled@apache.org             || ...              ||
  
  == Affiliations ==
  
@@ -144, +145 @@

  || St├ęphane Lacoin          || Nuxeo             ||
  || Sun Seng David Tan       || Nuxeo             ||
  || Gabriele Columbro        || Alfresco          ||
+ || David Nuescheler         || Day               ||
+ 
  
  == Sponsors ==
  
@@ -155, +158 @@

  
   * Jukka Zitting
   * Felix Meschberger
+  * David Nuescheler
   * ...
  
  Sponsoring Entity

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message