Semantic Web, Webnodes, web cms
Norway-based content management provider Webnodes AS is out with version 4.5 of its .NET-based, semantic Web CMS platform. Enhancements include more options for load balancing, ontology merging, and content synchronizations between installations.

Last summer, Webnodes released version 4 of its Web CMSt. The company distinguishes its approach to content management with a core Semantic Content Engine, aligning the system with the growth of the semantic Web. The Semantic Content Engine allows a custom ontology, or content model, to be created for each project. The result is content that is structured by meaning, able to be shared in a presentation-agnostic format or used to create a website’s navigational structure based on meaning relationships rather than page relationships.

Flexible Load Balancing

A semantic CMS compares with a traditional page-centric CMS, where a hierarchy resembles files and folders on a computer. The main idea is that, while the second generation of websites separated content and presentation, the semantic Web separates meaning from content and from presentation.

This can lead to more accurate searching, more flexible content reuse, consistent content porting between sites, machine understanding of meaning, and other advantages. A semantically-tagged website, for instance, can understand which content describes a recipe’s ingredients, which is the name of the dish, and which describes the preparation.

The company said that the size and complexity of recent projects, such as ones involving online banking systems, indicated the need to provide better options for load balancing. Ole Gulbrandsen, Webnodes’ Chief Technical Officer, said in a statement that the load-balancing setup in 4.5 is "now easier and more flexible than ever," with eight core components that can each be installed on separate servers and multiplied if needed.

Those eight components are front-end servers for HTML, edit servers, background worker servers, query cache server, content cache server, content delivery, text indexing servers and database server. From an external perspective, all of the components act as one system.

OData, Updated Edit User Interface

A new content synchronization function allows syncing between identical versions of the website that are housed in separate environments, and between websites having different content and data models. If desired, synchronization can also occur between selections of content or data. Additionally, content synchronization can now be used to assist deployment to live sites from development and staging environments.

The newest version also features a revised ontology merging system. An ontology is a data model, and now content, code and data models can be more readily synchronized, even if they were originally different ontologies.

Webnodes also now supports all of the new functionality in version 3 of the OData protocol, a standard for creating data APIs that can be used for exchanging machine-readable data. Additionally, it supports SSL for OData services involving user names and passwords, as well as for forms authentication.

The edit user interface has been revised with SignalR technology, and the company said that an improved internal cache setting will result in performance improvements up to 50 percent as well as substantially reduced memory usage. PNG image compression now reduces the file size by as much as 70 percent, which Webnodes said is possible without visible differences.

Image courtesy of ALMAGAMI (Shutterstock)