« Content Interpreter IV: Content Management | Main | How to get you personal email on your corporate blackberry »

Content Interpreter V: The Definition

In the case of XML, a Content Interpreter is an architecture that consists of an XML database that stores and indexes XML, with a business layer application that provides business intelligence and content transformation capabilities.

These specialized functions are not mature features within ECMS or DAMS. To gain these advantages it is necessary to look for a 3rd party package to integrate into the ECMS or DAMS. In the market, there exists a number of mature XML Database solutions including but not limited to Mark Logic and the open-source eXist.

The key points of implementing a Content Interpreter are:

1. Integration with the content repository.

It is imperative to draw a hard line between the functions that the ECMS and the Content Interpreter are responsible for. For ex. the ECMS should “publish” to the Content Interpreter.

2. Scalability.

The Content Interpreter should be able to handle an enterprise’s full structured content set.

3. Speed.

The Content Interpreter must be able to execute queries in real time and can be quickly extended to create new ways of searching and grouping content.

4. Configuration.

The Content Interpreter should not be a black box but rather a transparent collection of modules that can be configured to meet new requirements.

5. Lightweight.

The Content Interpreter should be relatively portable, and not requisite of an advanced engineering degree to manage and operate.


To meet these five key points of implementing a Content Interpreter, a sophisticated programming language that is simple and lightweight is required. Since the architecture is comprised of an XML Database and a business logic layer, the natural choice is XQuery (XML Query Language). XQuery is a natural fit because its inherent capabilities are to execute tasks such as combining, searching and comparing data.

The Content Interpreter’s layers

The implementation of a Content Interpreter is more an exercise in setting up the appropriate architecture and sticking to a key set of rules as opposed to what tools and technologies are used. Looking at the Content Interpreter from the bottom up, the following outlines its four logical layers:

1. XML or structured content layer – the physical content.
2. ECMS or DAMS layer – the management of the content.
3. XML Database layer – the indexing and searching of the content.
4. Content Interpreter layer - the business application layer.

TrackBack

TrackBack URL for this entry:
http://www.geekoutsummit.com/mt/mt-tb.cgi/31

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)