Professional Documents
Culture Documents
John Borras
e-Government Unit, Cabinet Office, London UK
john.borras@e-envoy.gsi.gov.uk
Abstract: This paper provides an overview of the work currently being undertaken at an international
level by the OASIS e-Government Technical Committee on developing ICT standards for interoperability
to support the work of putting government services on-line. The work of the committee is on-going and
this paper provides a snapshot of current progress as at the date of this paper and assumes a certain
level of awareness on the part of the reader of the new set of Internet technologies.
this need the TC has published the achieve. Many Governments are or have
following Recommendation: developed taxonomies for use in e-service
“Governments are recommended to delivery, and this project aims to review
enhance interoperability among the scope for harmonising these
their networked systems by taxonomies. This harmonisation could
adopting a common search service. take a number of forms, eg linking them
The search service should be based together or producing a master one that all
on the ISO 23950 international governments use. The technical solution
standard that features a high degree is a secondary aspect, first there needs to
of interoperability across many be agreement on the business terminology
communities of practice and types and to that end a Glossary of Terms is
of data and information holdings. being produced. The next phase will be to
Governments should implement the analyse the content of a number of
search service as a supplement to government taxonomies to establish what
other search mechanisms, as these common content there is between them.
may be required for reasons other From this analyse a decision can then be
than broad scale interoperability.” made on the viability of either creating a
single master taxonomy or whether a
7.2 ebXML Messaging for use mapping of existing taxonomies is more
appropriate.
within e-Government
The initial ebXML Message Specification 7.4 Common Data Definitions
was designed primarily for Business-to-
Business communication, (see www.oasis- As with 7.3 above, there is a need to have
open.org/committees/ebxml-msg), common definitions of data so that when
therefore a number of Government data is exchanged in support of a process
specific service delivery requirements will both parties know exactly what the data is
not have been considered. The TC has and how it should be processed. For
produced a requirements document that example, there are a variety of formats for
identifies additional elements that will need the names and addresses of Taxpayers.
to be added to allow for complete This project will examine the Core
compliance with Government issues. With Components already defined as part of
these additional Government elements the UBL, (see www.oasis-
ebXML messaging specification can be open.org/committees/ubl), and either seek
used for: to refine them or identify new government
Citizen to Government components that need to be added to the
list.
Business ‘line of Business’
applications to Government
7.5 Use by Governments of
Agency to Agency Communications ebXML Registries
Agency to Government Common
Service Governments currently use a mixture of
data dictionaries, XML schema
Government to Government repositories and other registries to store
The requirements document has now information about the IT components they
been handed over to the ebXML use in the delivery of their e-services.
Messaging TC for them to include the There is a need for these all to be based
additional elements into the ebXML on the same standards and to inter-
Messaging Specification. operate to help governments meet their
interoperability aims both within their own
7.3 Harmonising Taxonomies jurisdictions and across boundaries.
One of the keys to successful sharing and
The TC is running a proof of concept /
interchange of information between showcase project to demonstrate how the
governments is the consistent use of ebXML registry, (see www.oasis-
terminology. For example, there are a
open.org/committees/regrep), with suitable
variety of terms used for the welfare and client applications, can meet the needs of
benefit payments functions. This is governments to store these components.
compounded in the international arena
The UK Government is hosting the trial
where translation into multiple languages site and using its corporate data dictionary
makes this consistency even harder to and that of the Ministry of Defence to show
7.6 Use by Governments of the This project aims to develop and record
the requirements and issues for records
eprXML Standard
management that are specific to the
This standard was developed by the context of e-Government, particularly long
Norwegian Government and covers term archiving. The focus is on when,
electronic processes (EPR). It is used to where and how (the right bits of) the
describe how data support can be information involved in e-style government
organized in a unified and standardised interactions (G2G, C2G, B2G) become
matter. This means that data support to formal records (an aspect of record
such different areas as health care and declaration); and identifying, & getting hold
housing construction can be modelled in of, all the right information to constitute an
the same way and use the same basic authentic record (aspects of capture).
components. The standard describes Following on from this initial requirements
how: definition the TC will seek to develop a
information is presented to the standard for use in this context.
users
tools and supporting materials are 7.9 Semantic Interoperability –
implemented Business Implementation
communication with legacy systems Guidelines
will take place XML has clearly proven itself as a
roles, processes and routines will be standard that enables syntactic
organised interoperability between information
general functions can be systems. However on its own it cannot
standardised improve and enable semantic
interoperability, i.e. systems that can talk
The TC is considering the use of this
to each other and understand each other.
standard to support the delivery of e-
In an effort to reap the benefits of an XML-
Government services.
centred and semantically interoperable
information architecture, this project will
7.7 Workflow Standards look to establish a set of Business
An increasingly important component of Guidelines that will help prepare
delivering e-Government services is the enterprises address the issues early and
need for a workflow system to underpin up-stream of any technology based
the e-service, particularly where the initiatives.
service needs input from across
organisational boundaries. From the 7.10 Naming and Design Rules for
customer perspective, i.e. the citizen or XML Schemas
business organisation, they will want to
enquire on-line at any point what the latest Many of the advantages of XML can only
situation is with their request for the be realized if common Naming and Design
service and who is currently dealing with it. Rules for use in XML schemas are
followed. This is not only a regional or a
To meet these needs Governments want national issue since services on the
products that support open, interoperable Internet are available to anyone. Therefore
standards to enable different workflow rules have to be developed in an
systems to work together and also international context. This project will set
interface with their e-service applications. out the standard set of naming and design
Currently there appears to be a number of rules to be used by governments.
standards in this category but with no clear
indication of which should be used for 8. Future Plans
what aspects and how they relate to each The work of the Technical Committee will
other. Within this project the TC will hope continue for some considerable time and
to clarify which standard(s) should be used this paper only gives a snap shot of work
and in what circumstances. to date. Further projects are already being
scoped and prioritised to cover the very
wide agenda of e-government. The