Method and System for Multi-tiered Abstract XML Content Services
Original Publication Date: 2009-Aug-27
Included in the Prior Art Database: 2009-Aug-27
Disclosed is an improved method for managing XML content services in a multi-tiered, heterogeneous, distributed architecture.
Ȉ ˇ ˄
A content management system (CMS), also known as a document management system (DMS), is an application that provides electronic data management capabilities. A CMS generally includes a wide range of functions such as content and metadata storage and retrieval, versioning, lifecycle management, security controls, indexing, and publishing. This invention focuses on the vital role of XML in the content management space. XML-aware content management systems can further provide powerful features such as the following:
structured authoring - the ability to incorporate metadata that is normally lost in traditional binary or proprietary formats such as Microsoft* Word
single source publishing and concurrent authoring - the ability to share fragments of data or to transform the data into different formats; the ability to pull together different fragments using assembly templates or XSLT
separation of content from presentation (e.g., via CSS or XSLT)
interoperability - the ability to utilize XML data across different systems or applications
intelligent storage - the ability to synchronize XML content with attributes in the CMS
Because of these key advantages, XML is growing in popularity as the preferred format for authoring and publishing. Oftentimes, a CMS does not provide enough functionality on its own to meet the demands of a particular industry or domain. For example, in the pharmaceutical industry the management of content is highly regulated by organizations such as the FDA and, therefore, requires pharmaceutical companies to implement additional features to facilitate compliance above and beyond what a typical CMS provides (e.g., such as auditing and controlled authoring/viewing, etc.). Applications that build on top of a core CMS can be referred to as "value-add" applications because they add the additional value or benefit needed for a particular domain. However, there are some issues that need to be looked at when using value-add applications. For instance, a value-add application, such as a regulatory compliance solution, may be designed to run on top of any number of core CMS applications by using an abstraction layer to insulate itself from the details of underlying core CMS's. This additional layer of abstraction is extremely beneficial for the value-add application as it allows the value-add application to be deployed in various environments without costly vendor lock-in. However, the additional function implemented above the abstraction layer is oftentimes specific to the value-add application and unknown to the core CMS.
Figure 1 depicts an architecture used in the prior art which adds additional XML content management features to the value-add application:
Ȉ ˇ ˄
Ȉ ˇ ˄ Ȉ ˇ ˄
˙ ˝˛ ˚ ~ !
However, there are a few...