7.
CMIS
• Has SOAP and REST bindings
• REST binding deﬁned as extension to Atom
but tightly coupled to data model with
“protocol extensions that tunnel the Web
Services interface through fake-Atom and
fake-HTTP” (Roy Fielding)
• Has hype, buzz and industry support (try a
Google search and see EMC, Alfresco ads)

8.
CMIS REST:
Is It Any Good?
• Roy Fielding
• “I am getting tired of big companies
making idiotic claims about REST and
their so-called RESTful architectures. The
only similarity between CMIS and REST is
that they both have four-letter acronyms”
• http://roy.gbiv.com/untangled/2008/no-
rest-in-cmis

9.
CMIS REST:
Is It Any Good?
• Roy Fielding con’t
• “...unless you expect blogging clients and
syndication feeds to be the primary
application of CMIS, it would make a lot
more sense to deﬁne the representations
in a microformat of HTML, JSON,YAML,
or whatever else best ﬁts the data...”

13.
AtomPub WSGI App?
• Idea: Atom Publishing application living in a
Repoze ecosystem
• Aggregate content from several Plone,
Grok, etc. sites
• Get around the lack of PUT/DELETE in
Plone - act as a middleman
• Use zgeo.atom as starting point

14.
Atom For Now
• Focus on providing read-only Atom
representations
• Atom browser view that would apply to
any folderish object
• Start at the root of the Plone site and
discover all the Atom publishable objects by
following the Atom links

16.
Conclusion
• Implementing RESTful web services will be
a large and complex project, given the
limitations of the Zope2 publisher
• Not realistic to expect it to get done in a
sprint or even a series of sprints
• Most likely scenario: a customer needing
support for CMIS (after all!)