Enterprise content management systems

• An enterprise content management (ECM) system is concerned with content, documents, details and records related to the organizational processes of an enterprise. The purpose is to manage the organization’s unstructured information content, with all its diversity of format and location.

Web content management systems

• A ‘web content management’ (WCM) system is a CMS designed to simplify the publication of Web content to Web sites, in particular allowing content creators to submit content without requiring technical knowledge of HTML or the uploading of files.

Mobile CMS

Component CMS

Incoming search terms:

• CMS TYPES
• types of CMS

Software as a Service:

• AspireCMS,
• Clickability,
• Knivis,
• Crownpeak,
• Hot Banana,
• Marqui and others

Enterprise:

• Sitecore,
• FatWire,
• Vignette,
• Interwoven,
• Documentum,
• MySource Matrix (Squiz),
• Alfresco,
• Oracle,
• IBM Web Content Management,
• SDL Tridion and others

Mid-market:

• Microsoft SharePoint,
• Kentico,
• Goss Interactive,
• Contrexx,
• Ektron,
• PaperThin,
• Ingeniux,
• Terapad,
• Cascade Server,
• Day Software,
• Logical CMS and others

Open source:

• Magnolia,
• Plone,
• Joomla,
• Drupal,
• Exponent CMS,
• Alfresco,
• Sensenet 6.0,
• MiaCMS,
• MMBase,
• TYPO3,
• MySource Matrix (Squiz),
• WordPress,
• DotNetNuke,
• MyWebPageStarterKit

Incoming search terms:

• dotnetnuke or terapad
• web system history

Plone is released under the GNU General Public License (GPL) and is designed to be extensible. Major development is conducted periodically during special meetings called Plone Sprints. Additional functionality is added to Plone with Products, which may be distributed through the Plone website or otherwise. The Plone Foundation owns and protects all copyrights and trademarks. Plone also has legal backing from the council of the Software Freedom Law Center.

The name Plone is an homage to the Warp Records band Plone, whose music is both simple and playful. The logo represents collaboration with three dots together in a group.

MediaWiki’s “Monobook” layout is based partially on the Plone style sheets.

History

The Plone project was begun in 1999, by Alexander Limi, Alan Runyan, and Vidar Andersen. It was made as a usability layer on top of the Zope Content Management Framework. The first version was released in 2001. The project quickly grew into a community, receiving plenty of new add-on products from its users. The increase in community led to the creation of the annual Plone conference in 2003, which is still running today. In addition, “sprints” are held, where groups of developers meet to work on Plone, ranging from a couple days to a week. In March 2004, Plone 2.0 was released. This release brought more customizable features in Plone, and enhanced the add-on functions. In May 2004, the Plone Foundation was created for the development, marketing, and protection of Plone. The Foundation has ownership rights over the Plone codebase, trademarks, and domain names. Even though the foundation was set up to protect ownership rights, Plone remains open source. In March 12, 2007, Plone 3 was released. This new release brought inline editing, an upgraded visual editor, and strengthened security, among many other enhancements. Up to September 2007, there have been over 200 developers contributing to Plone’s code. Plone won two Packt Open Source CMS Awards.

Design

Plone is built on the Zope application server, which is written in Python. Plone is made such that all information stored in Plone is stored in Zope’s built-in transactional object database (ZODB). Plone comes with installers for Windows, Mac OS X, and Linux, along with other operating systems. New updates are released regularly on Plone’s website. Plone is available in over 35 languages. Its interface follows the government standard WAI-AAA and U.S. section 508, which allows people with sight disabilities to properly access and use Plone. A major part of Plone is its use of skins and themes. When working with Plone, templates can be used to customize a website’s look. These templates are written with Cascading Style Sheets. In addition, Plone comes with a user management system called Pluggable Authentication Service. Introduced in Plone 2.5, “PAS” is used to properly sort actions from different users to their respective folders or accounts. PAS is also used to search for users and groups in Plone. Most importantly, PAS covers the security involved for users, requiring authentication in order to login to Plone. This gives users an increase in both security and organization with their content. A large part of Plone’s changes have come from its community. Since Plone is open source, the members of the Plone community regularly make alterations or add-ons to Plone’s interface, and make these changes available to the rest of the community via Plone’s website.

Community

Since its release, many of Plone’s updates and add-ons have come from its community. Events called Plone “sprints” consist of members of the community coming together for a week and helping improve Plone. The Plone conference is also attended and supported by the members of the Plone community. In addition, Plone has an active IRC channel to give support to users who have questions or concerns. Up through 2007, there have been over one million downloads of Plone. Plone’s development team has also been ranked in the top 2% of the largest open source communities.

Strengths and weaknesses

Plone excels when compared to other content-management systems in standards conformance, access control, internationalization, aggregation, user-generated content, micro-applications, active user groups and value. It’s available on many different operating systems, due to its use of platform-agnostic underlying technologies such as Python and Zope. Plone’s Web-based administrative interface is optimized for standards, allowing it to work with most common web browsers, and uses additional accessibility standards to help users who have disabilities. All of Plone’s features are customizable, and free add-ons are available from the Plone website.

Plone has an excellent security record compared to other popular content management systems.

Plone’s weaknesses include Python and Zope experience requirements for those wishing to add or extend the feature set, making for a considerable learning curve for developers. Plone has been rated as lagging in repository services when compared to other major CMSs.

Features

These are some of the features available in Plone 3.0:

• Inline editing
• Working Copy support
• Link and reference integrity checking
• Automatic locking and unlocking
• Collaboration and sharing
• Versioning, history and reverting content
• Upgraded visual HTML editor
• Workflow capabilities
• Authentication back-end
• Full-text indexing of Word and PDF documents
• Collections
• Presentation mode for content
• Support for the search engine Sitemap protocol
• Support for multiple mark-up formats
• Wiki support
• Automatic previous/next navigation
• Rules engine for content
• Auto-generated tables of contents
• Portlets engine
• Support, development, hosting & training
• LiveSearch
• Multilingual content management
• Time-based publishing
• Human-readable URLs
• Powerful graphical page editor
• Navigation and updated site maps
• Resource compression
• Caching proxy integration
• Drag and drop reordering of content
• XML exports of site configurations
• Localized workflow configuration
• Adjustable templates on content
• Standard content types
• Content is automatically formatted for printing
• Standards-compliant XHTML and CSS
• Accessibility compliant
• RSS feed support
• Automatic image scaling and thumbnail generation
• Free add-on products
• Cross-platform
• Comment capabilities on any content
• Microformat support
• Installer packages for multiple platforms
• WebDAV and FTP support
• In-context editing
• Backup support
• Cut/copy/paste operations on content

Other Information

• Developed by  Alan Runyan, Alexander Limi, Vidar Andersen and the Plone Team
• Latest release  3.1.7 / #REDIRECT Template:Start date and age
• OS  Cross-platform
• Platform  Zope
• Type  Content management system
• License  GNU General Public License
• Website  http://plone.org/

MiaCMS is released under the terms of the GNU General Public License (GPL) Version 2. It is written with the PHP & JavaScript programming languages and uses the MySQL database. The official project site can be found at http://miacms.org, and an online demo of MiaCMS is available at Open Source CMS Demo.

Requirements

* A Web Server (ex) Apache (version 1.3.19 or above) or Windows IIS
* PHP 4.3.2+
* JavaScript
* MySQL 4.0+

MiaCMS is thoroughly tested on Linux, FreeBSD, Mac OS X and Microsoft Windows. Linux or one of the BSD’s are recommended, but anything else that can run the three pieces of software listed above should work just fine.

MiaCMS History

MiaCMS started as a fork of Mambo. Mambo is a Trademark of the Mambo Foundation, Inc. http://www.mambo-foundation.org. Mambo was originally developed by Miro International Pty Ltd in 2000. Mambo became Open Source software in April, 2001 under a GNU/GPL license. Miro assigned the copyright in Mambo to The Mambo Foundation in 2005 to ensure that Mambo remained free Open Source software owned and managed by the community. The rights to the Mambo CMS codebase, name and copyrights, are protected by the Mambo Foundation, a non-profit corporation formed to support and promote the Mambo Open Source project.

• April 2008: Four former Mambo core developers fork Mambo and form MiaCMS. The founding members are Chad Auld, Ozgur Cem Sen, Richard Ong, and Al Warren. The reasons behind the fork can be found on the project’s main site here. The initial fork is based on a Mambo 4.6.3 SVN snapshot just prior to their 4.6.4 release.
• May 2008: The first release, MiaCMS 4.6.4, is launched. It’s code name is Flourish. Here are the release notes for 4.6.4.
• June 2008: The 2nd release, MiaCMS 4.6.5, is launched. It’s code name is Eclipse. Here are the release notes for 4.6.5. The project also launches it official site designs and creates the official logo.
• August 2008: A security patch was released to deal with some XSS issues in the 4.6.5 release.
• September 2008: Version 4.6.5 SP1 was released. This version was the 4.6.5 release prepacked with the SP1 patch so users would not have to install and then immediately patch. MiaCMS is also selected as a finalists in the Packt Publishing 2008 Open Source CMS Awards competition under the “Most Promising Open Source CMS” category. Another former Mambo core developer, Neil Thompson, has joined the MiaCMS core development team.
• October 2008: MiaCMS ties for 3rd place in the Packt Publishing 2008 Open Source CMS Awards competition under the “Most Promising Open Source CMS” category. One of the teams core developers, Chad Auld, is also named in Packt Publishing’s 2008 list of “Most Valued People from Open Source Content Management Systems”.

Other Information

• Developed by  The MiaCMS Team
• Latest release  4.6.5 SP1 Latest releases
• Written in  PHP & JavaScript
• OS  Cross-platform
• Type  Content management system
• License  GNU General Public License v2
• Website  http://miacms.org

CMS Made Simple provides a mechanism for the website administrator to create and manage “pages”, their layout, and their content. CMS Made simple is unobtrusive…. You can create a table based layout, or a fully validating XHTML/CSS layout.

CMS Made Simple makes managing the navigation in your website a breeze… you can re-organize your pages any way you want, and navigations are automatically created from your page hierarchy. This tool makes creating numerous different navigations with the entire page hierarchy, or a subset of it “simple”.

CMS Made Simple separates layout code from content code, so that editors can manage content without having to know much about how websites work, so that layouts can be easily edited and take effect on numerous pages, and can be easily shared. With CMS Made Simple you design once, and easily use that same design over and over again. Smarty (a php based templating engine) is used to provide most of the caching, templating, and logic capabilities. This basic building block also provides the ability for website administrators to virtually eliminate any duplication of code or content.

The Core package provides the ability to manage news articles, search functionality a contact form, a WYSIWYG editor (for your customers or editors) and numerous other built in functions. Additionally, there are hundreds of third party add-on tools that are quickly and easily installable to allow building websites with many different capabilities.

CMS Made Simple is built in PHP, and allows you to integrate many existing PHP scripts or PHP snippets into your website… Though you definately don’t need indepth knowledge of PHP to use CMS Made Simple.

Who should use CMS Made Simple?

If you’re an experienced web developer. If you have found that sometimes creating a simple corporate or organization website is difficult in some of the other content management systems. If you have found that other CMS’s are sometimes “overkill” for what you need. If you want to be able to hand off the content management to editors. If you want complete control over the layout and appearance of the site, and you know how to do it… If you want a simple, easy to use, yet expandable tool – then CMS Made Simple is probably for you.

CMS Made Simple is not a replacement for packages that build static websites like Dreamweaver or FrontPage, etc. These packages don’t use databases, provide little in the way of dynamic content, and usually content cannot be edited by customers.

Is CMS Made Simple really “simple”?

Yes it is. Many of our experienced users find it a simple tool for building many websites. However, that does not mean that there isn’t some learning to be done. You will at the least need to learn our vocabulary, explore the package and it’s options, play around a bit, and probably do considerable learning. Did you jump right in to HTML and learn how to do professional websites in 30 minutes. Probably not, and CMS packages (including this one) are similar. There are a few things you will need to learn.
5. What knowledge do I need?

To take advantage of CMS Made Simple, you should have at a minimum a basic understanding of:

• Creating Databases, and backing up / restoring databases.
• Working with, and transferring files to a remote host
• Manipulating permissions on remote hosts
• A basic understanding of HTML and CSS
• Diagnosing errors:

From time to time, with different hosts, problems do occur in any online application. When working with these, you need a basic understanding of how they work, and how to diagnose some problems, so that you can assist the support personnel, or perhaps identify and solve the problem on your own. This includes:

• Finding your website error logs and access logs
• The ability to understand some of the error messages or access log lines
• The ability to find, identify and to some level diagnose Javascript errors
• An ability to learn independently, and do some research on your own.

What are the system requirements?

• Web server with PHP 4.3+ (Linux/Unix, Windows 2000/XP/ME/2003, OS X)
  • (CMS Made Simple does not officially support PHP safe mode)
  • At least 16mb of available memory for PHP (This should work fine for most small to medium sized websites. However, as your site grows, or you utilize other addon modules, your memory requirements may increase.)
  • PHP tokenizer support enabled
  • At least one of ImageMagick or GD enabled
  • MySQL 3.23 or 4.0+ or PostgreSQL 7 +
  • Enough access to your server to upload files and change some permissions

Where can I get help/support?

There are numerous forms of support available for CMS Made Simple:

• The default content: – The well documented content pages, templates and stylesheets that are displayed with a new installation of CMS Made Simple are an invaluable way of introducing yourself to the package and getting to know how the package works. We encourage you to read all of this thoroughly and save this information for future reference while building your website.
• The Documentation
• Built in Help: -   Each module and tag installed in a CMS Made Simple website includes basic help and examples to assist in utilizing the the functionality.
• Public/Community support

The CMS Made Simple forum is an invaluable way of finding out information about the CMS Made Simple core, and the add-ons. There are thousands of posts by the development team and members of our community that describe the various problems our users have encountered, and how they were solved.

We attempt to keep the forum clean from distracting posts, or posts that are not directly and specifically relevant to CMS Made Simple. Additionally, in order to expedite support, we ask that all users spend the time to research, and accurately describe their issues. Therefore please read and follow the forum rules when posting.

• Commercial Support: – Paid support is available to those people with an important project that are concerned about the turn-around time that may be related to getting an issue solved. Additionally, if you would like to have somebody to call for problems that you just can’t fix, upgrade issues, backups, or any other concern, then commercial support may be an option for you.
• Paid Development: – So you’ve got the tool up and running, and you like what you see…. but your project requires some functionality that isn’t yet available for CMS… or doesn’t quite work the way you want it to. For that, the CMS Made Simple Development Team offers independent contracting services. Our in-depth knowledge of the tool, and experience in building the package and its add-on modules can ensure that you get a working, well fitting, quality tool.

Other Information

• Developer:  Ted Kulp
• Current version:  1.5.1 “San Juan”(04 December 2008)
• Operating system:  all LAMP systems, Windows and Mac
• Category:  Content Management System
• License:  GPL (free software)

Links

• Official Website
• Theme
• Modules
• Tags and Plugins
• Download

Incoming search terms:

• cms made simple remove powered by

Enterprise level applications are not cheap. In particular, enterprise content management systems can send an organization’s budget plans through the roof. Unless, of course, you are implementing an open source enterprise cms. So the story goes.

According to open source enterprise cms provider Alfresco, they are the alternative with a scalable, easy to use platform at a fraction of the price.

We read their Total Cost of Ownership for Enterprise Content Management whitepaper. The whitepaper walks you through the licensing and hardware costs associated with several propertiery ECMs and shows how clearly open source is the more inexpensive option.

But the story of project costs is not just a tale of license price. There’s a lot more money to spend implementing an Enterprise CMS.

Go to Source

• Community web portals
• Discussion sites
• Corporate web sites
• Intranet applications
• Personal web sites or blogs
• Aficionado sites
• E-commerce applications
• Resource directories
• Social Networking sites

Drupal is ready to go from the moment you download it. It even has an easy-to-use web installer! The built-in functionality, combined with dozens of freely available add-on modules, will enable features such as:

• Content Management Systems
• Blogs
• Collaborative authoring environments
• Forums
• Peer-to-peer networking
• Newsletters
• Podcasting
• Picture galleries
• File uploads and downloads and much more.

Drupal is open-source software distributed under the GPL (“GNU General Public License”) and is maintained and developed by a community of thousands of users and developers. If you like what Drupal promises for you, please work with us to expand and refine Drupal to suit your specific needs.

General features

• Collaborative Book – Our unique collaborative book feature lets you setup a “book” and then authorize other individuals to contribute content.detailed information
• Friendly URLs – Drupal uses Apache’s mod_rewrite to enable customizable URLs that are both user and search engine friendly.
• Modules – The Drupal community has contributed many modules which provide functionality that extend Drupal core.detailed information
• Online help – Like many Open Source projects, we can’t say that our online help is perfect but have built a robust online help system built into the core help text. Available to you on your own site.detailed information
• Open source – The source code of Drupal is freely available under the terms of the GNU General Public License 2 (GPL). Unlike proprietary blogging or content management systems, Drupal’s feature set is fully available to extend or customize as needed.detailed information
• Personalization – A robust personalization environment is at the core of Drupal. Both the content and the presentation can be individualized based on user-defined preferences.
• Role based permission system – Drupal administrators don’t have to tediously setup permissions for each user. Instead, they assign permissions to roles and then group like users into a role group.screenshot . detailed information
• Searching – All content in Drupal is fully indexed and searchable at all times if you take advantage of the built in search module.

User management

User authentication – Users can register and authenticate locally or using an external authentication source like Jabber, Blogger, LiveJournal or another Drupal website. For use on an intranet, Drupal can integrate with an LDAP server.detailed information

Content management

• Polls – Drupal comes with a poll module which enables admins and/or users to create polls and show them on various pages.detailed information
• Templating – Drupal’s theme system separates content from presentation allowing you to control the look and feel of your Drupal site. Templates are created from standard HTML and PHP coding meaning that you don’t have to learn a proprietary templating language.detailed information
• Threaded comments – Drupal provides a powerful threaded comment model for enabling discussion on published content. Comments are hierarchical as in a newsgroup or forum.detailed information
• Version control – Drupal’s version control system tracks the details of content updates including who changed it, what was changed, the date and time of changes made to your content and more. Version control features provide an option to keep a comment log and enables you to roll-back content to an earlier version.screenshot

Blogging

• Blogger API support – The Blogger API allows your Drupal site to be updated by many different tools. This includes non-web browser based tools that provide a richer editing environment.detailed information
• Content syndication – Drupal exports your site’s content in RDF/RSS format for others to gather. This lets anyone with a News Aggregator browse your Drupal sites feeds.detailed information
• News aggregator – Drupal has a powerful built-in News Aggregator for reading and blogging news from other sites. The News Aggregator caches articles to your MySQL database and its caching time is user configurable.detailed information
• Permalinks – All content created in Drupal has a permanent link or “perma link” associated with it so people can link to it freely without fear of broken links.

Platform

• Apache or IIS, Unix / Linux / BSD / Solaris / Windows / Mac OS X support – Drupal was designed from the start to be multi-platform. Not only can you use it with either Apache or Microsoft IIS but we also have Drupal running on Linux, BSD, Solaris, Windows, and Mac OS X platforms.detailed information
• Database independence – While many of our users run Drupal with MySQL, we knew that MySQL wasn’t the solution for everyone. Drupal is built on top of a database abstraction layer that enables you to use Drupal with MySQL and PostgreSQL. Other SQL databases can be supported by writing a supporting database backend containing fourteen functions and creating a matching SQL database scheme.detailed information
• Multi-language – Drupal is designed to meet the requirements of an international audience and provides a full framework to create a multi-lingual website, blog, content management system or community application. All text can be translated using a graphical user interface, by importing existing translations, or by integrating with other translation tools such as the GNU gettext.detailed information

Administration and analysis

• Analysis, Tracking and Statistics – Drupal can print browser-based reports with information about referrals, content popularity and how visitors navigate your site.screenshot . detailed information
• Logging and Reporting – All important activities and system events are captured in an event log to be reviewed by an administrator at a later time.screenshot . detailed information
• Web based administration – Drupal can be administered entirely using a web browser, making it possible to access it from around the world and requires no additional software to be installed on your computer.screenshot

Community features

• Discussion forums – Full discussion forum features are built into Drupal to create lively, dynamic community sites.detailed information
  Performance and scalability

Caching – The caching mechanism eliminates database queries increasing performance and reducing the server’s load. Caching be tuned in real time and many high-traffic sites have performed very well under load.detailed information.

Other Information

• Initial release  January 2001 (2001-01)
• Latest release  6.8 / 11 December 2008; 10 days ago
• Written in  PHP
• OS  Cross-platform
• Type  Content management framework, Content management system, Community and Blog software
• License  GPL

Links

• Drupal News
• Download Drupal 6.8
• Download Drupal 5.14
• Visit drupal.org

Overall Winner

1. Drupal – Drupal is a free software package that allows an individual or a community of users to easily publish, manage and organize a wide variety of content on a website, Tens of thousands of people and organizations are using Drupal to power scores of different web sites, including
   
2. Joomla! – Joomla is an award-winning content management system (CMS), which enables you to build Web sites and powerful online applications. Many aspects, including its ease-of-use and extensibility have made Joomla the most popular Web site software available. Best of all, Joomla is an open source solution that is freely available to everyone..
3. DotNetNuke - DotNetNuke is an open source web application framework written in VB.NET for the ASP.NET framework. The application’s content management system is extensible and customizable through the use of skins and modules, and it can be used to create, deploy, and manage intranet, extranet, and web sites.

Most Promising Open Source CMS

1. SilverStripe – SilverStripe is a free and open source programming framework and content management system (CMS) for creating and maintaining websites. The CMS provides an intuitive web-based administration panel, allowing any person to maintain their website without knowledge of markup or programming languages.
2. CMS Made Simple – CMS Made Simple is an open source (GPL) package, built using PHP that provides website developers with a simple, easy to use utility to allow building small-ish (dozens to hundreds of pages), semi-static websites. Typically our tool is used for corporate websites, or the website promoting a team or organization, etc. ..
   
3. ImpressCMS
4. MiaCMS

Best PHP Open Source Content Management System

1. Drupal
2. Joomla!, CMS Made Simple

Best Other Open Source Content Management System

1. Plone
2. dotCMS
3. DotNetNuke

Packt Publishing

Accepting nominations since mid-July, Packt Publishing announced this week the finalists for its 2008 Open Source CMS Awards. Final voting began on Sept. 1 and runs through Oct. 20.

This is the third year for the awards, which are designed to “encourage, support, recognize, and reward” popularity and quality in open source content management systems. The finalists for each of the four main categories are as follows:

Overall Open Source CMS Award Finalists

• DotNetNuke
• Drupal
• Joomla
• Plone
• TYPOlight

Most Promising Open Source CMS Finalists

• CMS Made Simple
• ImpressCMS
• MiaCMS
• MemHT
• SilverStripe

Best PHP Open Source CMS Finalists

• CMS Made Simple
• Drupal
• eZ Publish
• Joomla
• Xoops

Best Other Open Source CMS Finalists

• dotCMS
• DotNetNuke
• mojoPortal
• Plone
• Umbraco

In addition to awards for the systems themselves, an Open Source CMS MVP Award will be given to an outstanding individual contributor. The winners in each category will be determined by a panel of four judges whose votes will be combined with those from the public. Announcements of the winners will be staggered:

Oct. 27: Open Source CMS MVP
Oct. 28: Best Other (non-PHP based) Open Source CMS
Oct. 29: Best PHP Open Source CMS
Oct. 30: Most Promising Open Source CMS
Oct. 31: Overall Open Source CMS Award

The project team for the overall winner gets a prize of $5,000, with an additional $15,000 in prizes going to winners and runners-up other categories.

To learn more about each of the projects and cast your vote, visit Packt Publishing’s finalist page.

The specification, called Content Management Interoperability Services (CMIS), establishes how content management systems (CMSs) can use a set of Web services interfaces, as well as the REST and Atom protocols to link with other repositories. The vendors announced that it plans to submit the specs to the Organization for the Advancement of Structured Information Standards (OASIS), the standards body that oversees many Web services standards today.

“Historically content management systems were purchased for specific application uses and this led to islands of incompatible systems,” the specification states in the introduction. “The objective of the CMIS standard is to define a common content management Web services interface that can be implemented by content repositories and enable interoperability across repositories.”

It is expected that existing vendors of content management systems will implement the specification, so that when their customers need to move a set of data from one repository to another, they will have an easy set of commands to carry out the work. Not every feature in every content management system will be replicated, and some systems will have to be retrofitted to talk with the new features, the document warns.

SMIS is built on an object model. In the parlance of CMIS Version 1, a content repository has four basic entities, called objects: Documents, folders, relationships and policies. All the objects are extensible, meaning they can be extended with new attributes. CMIS offer specifications for creating, reading updating and deleting objects. Services are also defined for filing documents, navigating the repository and querying documents within the repository

Issuing commands and transferring information across repositories will be conducted by using the Simple Object Access Protocol. A subscription service, where users can be notified when a document changes, will be carried out using the Representational State Transfer protocol.