Sjoerd Visscher -- Everyone with an interest in easily connecting to XML needs to look at Xopus. Q42 doesn't have a marketing department, and their Xopus site looks daunting.
All actions in Xopus are schema controlled. If the schema doesn't allow it, the user can't do it. This doesn't stop with structural actions, like 'can you add one or more Authors to a Book', but markup is also restricted by the schema. Can a user only add bold and italic, or also lists and tables? And if the user can add links, is he then allowed to add a target attribute? This is a big issue for CMSs, where the site designers want to give the site a consistent look and feel, but where the editors keep messing things up.
Xopus provides the standard Word-like interface, like toolbars, context-menus, and some dialogs. But a user must do more than edit some XHTML. For example, the University of Groningen allows teachers to edit course descriptions and other course related data using Xopus. The two options they had before were either teach the teachers to use an XML editor, or build huge amounts of html forms more or less by hand.
The teacher doesn't even have to know the storage structure of the CMS. If he wants to edit his course, he fires up his browser and he surfs to the webpage of the course. And because the system can recognise the teacher, an extra link appears to edit the course. When clicked, the Xopus toolbar slides in and the course data becomes editable.
|
|