paul spencer [email protected] using the ebxml registry for e-government schema management

Paul [email protected]

Using the ebXML Registry for e-Government Schema

Management

© 2004 Boynings Consulting boynings.co.uk

Topics

The need for a standards-based repository

Some existing repositories in Government

The requirementsThe OASIS eGov TC proof of

concept


The need

Large organizations need re-usable data items with known semantics

These components are required as XML Schema components

Components must be shared within and often outside the organization

Components may use external components such as code lists


The need

A registry/repository that stores both XML schema components and metadata

a standards-based approach to allow sharing


An early attempt

The UK Government Data Standards Catalogue pre-dated most of the standards work

An XML-based metadata catalogue linked to small XML schema documents

Schema documents can be imported into other schemas


UK GDSC


A slightly later version

The UK MOD already had a data dictionarySQL Serverseveral thousand data items

Now needed to add XML Schema components

Additional requirement was to assemble "message" schema documents from components


A slightly later version

Quick solution was to create a text file of componentsuse "id" attribute to link to data

dictionaryuse "mod:Version" attribute to

indicate component versionuse a self-describing assembly

mechanism


An MOD schema component

<xs:complexType name="NATOstockNumberStructure" id="5897" mod:Version="1.0"> <xs:sequence> <xs:element name="NATOsupplyClassificationCode" type="NATOsupplyClassificationCodeStructure" mod:Version="1.0"/> <xs:element name="NATOitemIdentificationNumber" type="NATOitemIdentificationNumberStructure" mod:Version="1.0"/> </xs:sequence></xs:complexType>


MOD DDR


Requirements

From these and other projects around the world, we can get requirements relating torepository populationschema assemblyschema useimport/export/federationrepository management


Registry requirements

Registry

break down tocomponents

and addmetadata

schemadocument

createcomponent

from metadata

create registryentry

population



Registry


and addmetadata

schemadocument

createcomponent

from metadata


assembly

assembleschema

documents

population



Registry


and addmetadata

schemadocument

createcomponent

from metadata


assembly

use

assembleschema

documents

browse andsearchSchema

developmenttool

WebDAVinterface

population

publish

FileSystem



Registry


and addmetadata

schemadocument

createcomponent

from metadata


manageapprovals(new andchanges)

register interest

managedeprecation

andobsolescence

assembly

use

assembleschema

documents

browse andsearchSchema

developmenttool

WebDAVinterface

population

management

publish

FileSystem



Registry

OtherRegistry

Tbreak down tocomponents

and addmetadata

schemadocument

createcomponent

from metadata


manageapprovals(new andchanges)

register interest

managedeprecation

andobsolescence

assembly

use

assembleschema

documents

browse andsearch

import / export /federation

Schemadevelopment

tool

WebDAVinterface

population

schemadocumentation

import / export

management

publish

FileSystem


OASIS eGov TC pilot project

Discussion of the MOD work exposed a great deal of interest in OASIS

eGov TC has approved a PoC / showcase

Aim is to create a registry/repository to meet

MOD/UK Gov and international government needs

define best practice for its use



Main teamPaul SpencerFarrukh Najmi, Sun MicrosystemsCarl Mattocks, CHECKMi

Many others involved from other organizations



Initial tasks are to map metadata requirements and build a registry

Aspects of the requirement necessitate ebXML Registry v2.5+

Will use open source freebXML (ebxmlrr) registry v3


Metadata Mapping

Different applications have different metadata requirements

Currently mapping UK e-GMS and MOD metadata to the ebRIM e-GMS is based on Dublin Core and forms the basis

of MiREG – the European e-Government metadata standard

MOD metadata is extended from e-GMS

Scope for further mappings Scope for semantic registry

ebXML Registry Semantic Content Management SC eGov Harmonising Taxonomies SC


Metadata Mapping

UK e-GMS Mapping to RIM Schema Docs

Schema Comps

Other

Contributor Association to Person (User for now) or Organization with associationType “Contributor”

MA

Coverage. Spatial Classification using chosen GEO ClassificationScheme RA Creator Association to Person (User for now) or Organization with

associationType “Creator” M

Date. Acquired <rim:Slot name="urn:gov:uk:egms:date:acquired" slotType="http://www.w3.org/2001/XMLSchema#date">

n/a

Date. Available <rim:Slot name="urn:gov:uk:egms:date:available" slotType="http://www.w3.org/2001/XMLSchema#date">

n/a


Registry Metadata, Repository Artifacts - Phase 1

Enter schemas and the associated metadata Enter schema components (global data types, elements

and attributes) and associated metadata Enter other document types with associated metadata Hold schema definitions in a syntax-independent

manner - sufficient information must be held in the registry to create the component from metadata

Metadata to be supported will vary according to the three document types (schema, schema component or other) and will be a subset of that defined in the UK e-GMS

Search on certain metadata information and extract all matching schemas, components or other documents

Construct schemas from components


Later Phases

Further metadata mappingsMore emphasis on semantic

contentThe ability for registries to inter-

operateConsideration of mapping data via

the ccRIMMore security features

paul spencer [email protected] using the ebxml registry for e-government schema management

Documents

external components

organization components

sharing slide

schemas slide

uk gdsc slide

uk government data standards

message schema documents

text file of components