Skip to main content

New background-introduction

I went through my intro and have started to rewrite the whole thing. Posting it here to show A. The difference is that this intro takes a more top-down, basical approach.

Background

The last ten years have seen revolution after revolution within information technology and telecommunications. The rise of the Internet, the success of the World Wide Web, the availability of personal computers and server performance, more recently the circulation of mobile devices and the distribution of broadband Internet are all trends of the new technological infrastructure which supports the world of modern assets which is electronical or digital data and information.


As to illustrate the increase in digital capability in containing data, one might consider the fact that the information estimated lost in the burning of the Great Library of Alexandria would fit on one single DVD. As storage space has grown, and network bandwidth has widened, the mass of digital information has exploded, both internally on intranets, and on the Internet. Users of the Internet have been most significantly effected by the increase in e-mail traffic and the amount of documents and pages available on the World Wide Web.


The value of information is only equal to that of its use. To use information, it must be found, recovered, formatted and presented. Information which is stored but never used is worthless. Digital information is enabled by the use of Information Systems. Before one can define the particular kind of Information System referred to as the Content Management System, one needs to define content itself, and seperate it from data and information.


Definitions

Data, information. content and knowledge are four ambigous concepts which are regularly applied in Information Systems. If allowed to delimit the definition to digital representation, we leave out the definition of knowledge for now, focusing on the other three. These terms have various meanings, and are potential candidates for extensive ontological discussion. To avoid confusion, the meanings of these terms as used in this paper are defined as follows:


Data

The basic unit of digital representation which can be used to construct information and content with more value for the consmer. Data is raw and granular. It does not inherently have any meaning, meta-data is not self-contained.


Data is a set of symbols, ranging from a numeral value to a string of words, or even a large series of encoded symbols that compose a binary value representing sound or picture. One often mentions data processing, feeding data as input to a program or algorithm, the output being either new data, information or content. Imagine calculating the mean of a hundred numerical values into one number. Data has been processed, but no meaning has been added. Had the value been wrapped with the context that this is the average temperature for the last three months, it could have been considered information.


Information

One definition of information is data with meaning (Davenport and Prusak, 1998 [fix]). The same information can be conveyed with different data. Pieces of data combined with meta-data to form a package of meaning that can be conveyed. Bob Boiko includes all the common forms of recorded communication. Liz Orne ([Boiko 2002]: Orna, E (2004) Information Strategy in Practice, Aldershot: Gower, p. 7). describes it as knowledge transformed into a transportable format, visible or audible.


Content

This is perhaps the vaguest term which we must define. Ideas include


  • Information put to use [boiko 2002]

  • Information with human meaning and context [wikipedia]

  • Information with an intended consumer, artificial or real [personal note]

  • Information with a purpose (the now disbanded ContentWatch organization's definition [Boiko 2002, p. 8]) .


The definition used in this paper is streamlined for how content can be handled by an Information System. A collection or subset of information intended for a given audience or non-human consumer with a context of location, period and situation.


Content management

Now that the definition is in place, the segment of Information Systems known as Content Management Systems can be defined. Note that in the industry of content management, the use of the term is indeterminate. Some CMS vendors claim their services feature knowledge management or enterprise content management. On the other side of the scale, many lightweight web applications claim to do content management when they actually are providing what is by most percieved as web content management, or perhaps merely weblog or wiki functionality.


Content management means different things for different actors. The basic lifecycle of content is production and consumption. For the producer, the processes of content management includes creation, formatting, structuring and integration of content. For the consumer, it includes search, export, and display. The sum of these processes make out content management. A content management system (CMS) is a suite of tools designed to assist and support these processes.


Web content management

As pointed out earlier, the explosion of digital information has been most significant on the World Wide Web. To manage this mass of online content and use, a new breed of information systems has evolved; the Web Content Management System (WCMS). The responsibility of such a system is similar to that of the CMS, only it is delimited to content which consumption is done by way of the World Wide Web. [See “Why only a web content management system” to see how WCMS has become detached from the CMS].

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password...

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config...