Implementation and Management Approach
Development
The largest problem by developing the CVDR was to keep in touch with the local Civil servants. A big issue in the Netherlands is to keep all different governments aligned. Especially when the central government develops services and applications for the local governments. Aim was to keep the central developments in line with the wishes, needs and desires of the local governments. To achieve this the selected project manager was an experienced local legal professional. Also there was a group of peers selected from the local governments which were regularly consulted during the building and development of the CVDR. Finally just before delivery of the CVDR two extensive user tests had been held. All these efforts were aimed to make the CVDR as user friendly as possible.
To shorten lines between the the builder, the project manager and the Executive. The methods of Prince2 where used as project management tools.
Implementation
After the completion of the build the further implementation by local government is done by an specific team consisting of an legal advisor, an account manager, a technical advisor and a product manager. For the support of the local government while implementing the CVDR consists of an designated help desk, an Internet community with E learning facilities and a workshop in which the legal surroundings and the working of the CVDR are explained. To further support the local government by implementing the CVDR an extra service is developed. This extra service consists of making the start collection in the CVDR for the local governments when they don't have the time to do that themselves.
Community of interest
For the further developments of the CVDR a community of local legal professionals is assembled to make decisions about the development strategy, change management, legal question surrounding legislation etc. The intellectual ownership of the CVDR is in the process of handing it over from the project manager to this group of legal professional. This form of ownership is in line with the paradigm that the CVDR is owned by all governments together. This community of interest is also facilitated with a community website were all Dutch civil servants can get access to the required knowledge for working with the CVDR, participate in a forum download information and relevant documentation and have access to an e learning application.
Costs
The CVDR is completely free of charge for local governments because all the Dutch governments combined own the system.
Â
Technology solution
The CVDR technology consists of several components.
(the system architecture can be seen in the Powerpoint Presentation in the appendix)
The entry module:
A web application has been chosen because it is much easier to manage than a desktop application. In this project with over 500 local users throughout the Netherlands, this is a huge benefit. On the other hand, the technical capabilities and speed of browsers is very limited. This made it difficult meet the CVDR’s requirements:
The entry module needed to comply with the following requirements:
- Users must be able to convert their Word documents to the required XML format
- The entry module must be very user friendly as users/authors do not need to have any affinity with technology.
- The legislation must be made available in valid XML in the Dutch Law XML scheme.
- All functions to publish legislation must be integrated in the entry module and users must not need extensive knowledge of E-publication or CMS systems to put legislation on the Internet.
There are different ways to comply with all these requirements. One of them is to choose an HTML editor but this means a conversion from HTML to XML. A conversion always includes the risk of loss of information. Word and Open Office are also options, as nowadays they can also produce XML. The problem however is that the XML produced does not validate against the Dutch law XML Schema. In developing a conversion, it quickly becomes clear that this XML, in the same way as HTML, does not include enough meaningful information.
The choice for a regular XML editor seems obvious. But then validation remains a problem as these type of editors are developed for expert users and only validate the XML at the author’s request. If the document contains errors then the editor will indicate a validation error and the author must solve the problem in the XML. However, this cannot be expected of the CVDR target group.
The selected XML editor, Xopus, solves this validation problem by switching off all options in the interface that could make the document non-valid. This technique is called prevalidation (as opposed to postvalidation as in regular XML editors). Prevalidation helps to create a friendly environment in which the author cannot make errors and does not encounter cryptic error messages. Additionally, Xopus is a browser-based application (Xopus is an HTML page with JavaScript) which supports the XML Schema and other standards. This means the editor offers a good basis for the CVDR process interface.
A bit of WYSIWYM
User-friendliness is very important in the CVDR project. A WYSIWYG (What You See Is What You Get) editor is the normal way of achieving such user friendliness. In this case WYSIWYG also can also cause confusion. This confusion occurs because the structure of the text is not shown. A WYSIWYM (What You See Is What You Mean : the interface shows the structure and the meaning of the XML and not only the presentation) editor can be an alternative. A WYSIWYM interface does require that the author clearly indicates the structure in the text and tries to imagine the end result. However we could not expect the user group to have a clear idea of the text structure. That is why a fully WYSIWYM interface is not suited for the CVDR user group.
In cooperation with a specialized communication bureau Eden design, a solution was found in the form of a hybrid between WYSIWYG and WYSIWYM. The document is displayed virtually identically during processing as during the on line publication. The structure is shown in the left margin. In this way the interface provides a visual aid for users, and at the same time provides a simple way via which to adjust the document structure.
Restructuring
Regulations have been made for many years, and this process has been modernized many times. From Word Perfect or Word Star files to Word. The current generation of regulations is almost completely stored in local system using unstructured Word files. In order to make these legacy documents suited for the CVDR, a specialized E-publishing bureau STIPP developed a state of the art converter that produces XML, which is valid according to the CVDR schema. However, in some cases this conversion of structures requires adjustments. A separate interface has been specially created for this. With the help of a clear interface and with just limited insight in the structure, the author is able to create a good structure for the text of the regulation.
The second component the web service
Some local governments already had systems to put legislation on the Internet. This done on a voluntary basis. With the arrival of the CVDR these governments had a problem because most of them didn't want to change their technologies. To make it possible for these government to connect with the CVDR an Web service module was added. The local software connect in a push pull combination with the CVDR and send the legislation in the correct XML over to the CVDR. It is also possible to connect with the CVDR and extract the legislation through the same Web services. In this way it is possible to change from working with the entry module and local software without losing the content. Or using both systems at the same time. This makes it possible for local governments to freely chose between software suppliers or change from supplier to the CVDR if they want it. Without the hassle of data migration or conversion.
Â
