e-government interoperability framework

109
E-Government Interoperability Framework 20 September 2004 e-Government Interoperability Framework Adrian Stevenson Jane Stevenson Amanda Hill

Upload: adrian-stevenson

Post on 15-May-2015

3.518 views

Category:

Business


2 download

DESCRIPTION

Review of the e-Government Interoperability Framework

TRANSCRIPT

Page 1: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-Government Interoperability Framework

Adrian Stevenson

Jane Stevenson

Amanda Hill

Page 2: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

An Introduction to the e-GIF

A Society of Archivists’ event, organised

by the EAD/Data Exchange Group

Given by MIMAS: Manchester Information

and Associated Services

Page 3: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Content

Section 1

– Introduction to e-GIF

Section 2

– XML - the Core of e-GIF

Section 3

– Implementing systems using XML technology

Page 4: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

JORUM Project

• JISC Online Repository for Learning and Teaching Materials

• Funded by the Joint Information Systems Committee (JISC)

• Advise on the interoperability requirements of the JISC Information Environment

• The JISC Information Environment requires the implementation of standards and specifications:– IMS Global Learning Consortium– IEEE– Advanced Distributed Learning (ADL)

Page 5: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Section 1

Introduction to e-GIF

Page 6: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Content

• Overview of e-GIF

• Components of e-GIF

• e-GIF Specification Drivers

• e-GIF Key Policies

• e-GIF Scope

• e-GIF Compliance / non-Compliance

Page 7: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-Government Interoperability Framework

• e-GIF version 6.0 (30th April 2004):

• “The e-Government Interoperability Framework (e-GIF) sets out the government’s technical policies and specifications for achieving interoperability… across the public sector.”

• “This approach is designed to be pragmatic and aims to reduce the costs and risk of operating information technology systems while keeping the public sector in step with the global internet revolution.”

http://www.govtalk.gov.uk/documents/e-gif-v6-0_.pdf

Page 8: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF importance

• Adoption of e-GIF is mandatory for the public sector

• It is the cornerstone policy of the e-Government strategy

• Details on e-Government strategy at:http://e-government.cabinetoffice.gov.uk/EStrategy/StrategicFramework/fs/en

Page 9: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Components of e-GIF

• Policy and Scope• Technical Policies• Implementation Support• Management Process• Change Management• Complying with the e-GIF

Page 10: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF architecture

• e-GIF contains:

• The Framework, which covers high-level policy statements, technical policies and management, implementation and compliance regimes

• The e-GIF registry, which covers XML schemas, technical standards, the e-Government Metadata Standard (e-GMS), the Government Category List (GCL), and a number of other elements

Page 11: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF Key Policies

• Alignment with the Internet – adoption of common standards used on Internet and WWW

• Adoption of XML as the primary standard for data integration

• The Web browser is the key interface• Addition of metadata to government resources• Development and use of the e-Government Metadata

Standard (e-GMS)• Develop and maintain the Government Category

List (GCL)

Page 12: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF specification drivers

• Interoperability – only specifications relating to interconnectivity, data integration, e-services access and content management metadata specified

• Market support – specifications have to be widely supported by the market

• Scalability – to changes in data volumes, number of users

• Openness – specifications available to the public

• International Standards – preferred to EU and UK standards

Page 13: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF Scope

• Information exchange between UK government and:– Citizens– Businesses both in the UK and overseas– UK government organisations– Other governments

• UK Government includes:– Central and local government departments– Devolved administrations– The wider public sector e.g. Non-departmental public bodies and

the NHS– HEFCE: universities as “independent autonomous bodies” classed

as being in the public sector

• You must use e-GIF for all new systems that fall in this scope

Page 14: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Open Source Software

• The e-GIF informs the Open Source Software (OSS) policy

http://www.govtalk.gov.uk/policydocs/consult_subject_document.asp?docnum=780

• OSS is software whose source code is openly published, and usually available at no charge– E.g. Linux operating system, Apache web server

• Open Source Software Policy:– Consider OSS alongside proprietary – choose best value for money– Seek to avoid vendor lock-in– Only use products that support open standards and specifications

Page 15: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF Technical Policies

• The Core technologies are divided into four technology areas:– Interconnection

– Data Integration

– Content Management Metadata

– e-Services Access and Channels

Page 16: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Interconnection Technologies

• The interconnection technologies are allstandard Internet technologies, such as– HTTP / FTP / IP / NNTP / SSL– SMTP / POP

• Web Services are part of this set oftechnologies:– SOAP, WSDL, and UDDI– Web Services are based around XML

Page 17: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Data Integration Technologies

• XML– XML and XML Schemas for data integration

– XSLT for data transformation

– UML, RDF and XML for data modelling and description

• All of the above with the exception of UML

are based upon XML

Page 18: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

CALM

Page 19: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

ADLIB

Page 20: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Content Management metadata

• Adopt e-GMS, based on Dublin Core for information management and retrieval needs– e-GMS is a ‘superset’ of metadata elements - unlikely that any

single system will require all

• Organisations encouraged to develop sector specific standards, removing elements not required and adding local constraints

• Policy covers the development and maintenance of the Government Category List (GCL)

Page 21: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 22: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GMS

Page 23: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Government Category List

• The GCL is a structured list of categories

• Use with the ‘Subject.category’ element of the e-GMS

• GCL consists of approximately 400 controlled vocabulary categories

• GCL will be fully integrated into applications

Page 24: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-Services access technologies

• Systems designed to be accessible through browser-based technology

• Provide services via a range of delivery channels and devices

• Information content should be separate from the delivery channel

• Systems designed so essential information accessible via delivery channels with limited capability

• Plug-ins must be easy to download and without a licensing fee

Page 25: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-Services delivery channels

• Access technologies vary depending upon the form of access– Digital TV– PC based Web browser– Mobile Phones– Video conferencing systems over IP– PDAs and other devices

• Personalisation technologies can be employed to support service delivery– content filtered to match device display capabilities

Page 26: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF Implementation Support

• There are also a number of predefined XMLschemas to be used where appropriate– Address and personal details– Property information– Archives and Records Management

• Many others are in draft– Education– Local government services

Page 27: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Govtalk Schema Library

Page 28: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML Schemas Production

• Schemas developed by specialist groups or by open submission to the GovTalk website

• The Government Schemas Group will manage the acceptance, publication and change requests

• Accepted schemas published at: http://www.govtalk.gov.uk/schemasstandards/agreedschema.asp

Page 29: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

www.govtalk.gov.uk

• GovTalk website forms a fundamental part of the e-GIF implementation strategy

• GovTalk provides implementation support through the production of agreed, freely available XML schemas that can be re-used throughout the public sector

Page 30: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Management Processes

• Outlines the roles and responsibilities of central government and the public sector

• The e-Government Unit (EGU) is the lead authority for implementing and maintaining the e-GIF

• EGU provides the management infrastructure to support the processes

• Public sector organisations need to ensure that compliance is a fundamental part of their organisational IT strategies

Page 31: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Change Management

• e-GIF specifications inevitably change – reviewed annually and updated as necessary

• Change management process must ensure that e-GIF is up to date and aligned to new technology and market developments

• Inclusive Internet-based consultation process that will encourage participation and innovation:– Organisations consulted– Comments and suggestions encouraged– Drafts published with Request for Comments (RFC)

Page 32: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Change Management: XML Schemas

• Changes to XML schemas have to be carefully assessed, as can have a high impact

• Estimated that it can take some organisations a year to implement changes to a core schema

• Changes to agreed XML schemas need to be managed carefully – schemas undergo test programs

Page 33: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Change Management

Page 34: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF Compliance

• System compliance to the e-GIF specification means that the system will:

- Provide a browser interface for access- Use XML as the primary means for data integration- Use Internet and World Wide Web standards- Use metadata for content management

• Ultimate test for interoperability is the coherent exchange of information and services between systems

Page 35: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Compliance Timetable

• All new systems will provide interfaces that conform to the e-GIF specifications by default

• Legacy systems need to provide compliant interfaces on demand or through replacement– Except for those systems linking to Directgov or the Knowledge

Network – these should follow their respective timetables

• Compliance came into force when e-GIF version 1 was announced in the House of Commons in October 2000

Page 36: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Results of non-compliance

• Projects will not get funding from– The e-Government Unit (formerly the Office of the

e-Envoy)– HM Treasury– Within your own organisation

• Systems will not be able to connect with– Directgov (formerly UK Online)– The Knowledge Network– The Government Gateway

Page 37: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Directgov

Page 38: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

The Knowledge Network

Page 39: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Government Gateway

Page 40: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Compliance Responsibility

• Responsibility for compliance rests with the system’s senior responsible owner or sponsor

• Compliance is by self-regulation

• Final arbiter on all questions relating to e-GIF compliance is the e-Government Unit

Page 41: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Compliance: Public Sector

• Compliance rules apply to all public sector bodies

• Public sector includes communities that exchange information with their own members, e.g. Using Z39.50

• Any specialised data interchange must be in addition to, and must not conflict with, the e-GIF interoperability requirements

Page 42: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF assessment service

• Web-based e-GIF Compliance Assessment Service

• http://www.e-GIFcompliance.org/

• Benchmarks your activities against the Framework

• There is a charge for the service

Page 43: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Summary

• Overview of e-GIF

• Components of e-GIF

• e-GIF Specification Drivers

• e-GIF Key Policies

• e-GIF Scope

• e-GIF Compliance / non-Compliance

Page 44: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

EGU Contact

Colette Coles

Interoperability Policy Advisor

e-Government Unit

tel: 020 7276 3091

Email: [email protected]

Page 45: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Section 2

XML

Page 46: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML

eXtensible Markup Language

• Define XML

• XML syntax and rules

• why use XML?

• XML Schemas

• XSLT

Page 47: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

What is XML?

• a technology for the management, display and organisation of data

• a programming language• a markup language • a markup language used to describe the

structure of data• not really a language• a standard for creating languages that meet

the XML criteria

Some possible definitions?

Page 48: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

So, what is XML?

• XML is a grammatical system for creating languages… a meta-language

• Use XML to design your own markup language, consisting of meaningful tags that describe the data they contain

• Create a language for describing…anything

Page 49: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Something to remember about XML

• XML does not do anything itself. It is pure information wrapped in XML tags.

• You must use other means to send, receive or display the data

Page 50: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML: elements

<language> English </language>

<tag> </tag>content

Page 51: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML attributes

• Attributes are simple name/value pairs associated with an element

<tag attribute_name=“attribute_value”>content</tag>

<language>English<language>

<language langcode=“eng”>English</language>

<date normal=“2004”>20 Sept 2004</date>

Page 52: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML example

<archdesc level="fonds"><did>

<repository>John Rylands University Library of Manchester</repository><unitid countrycode="GB" repositorycode="0133">GB 0133 NCN</unitid><unittitle>Papers of Norman Nicholson</unittitle><unitdate normal="1899-1987">1899-1987</unitdate><physdesc>

<extent>0.44 cu.m; 1,201 items</extent></physdesc><langmaterial>

<language langcode="eng">English</language></langmaterial><origination>Nicholson, Norman Cornthwaite, 1914-1987</origination><note>Created by the John Rylands Library archivist</note>

</did>…..</archdesc>

Page 53: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML must be well-formed

• a root element is required

<ead>

…..all your tags and content…

</ead>

• closing tags are required

Page 54: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML must be well-formed (2)

• elements must be properly nested <physdesc><extent>10 boxes</extent></physdesc>

<physdesc><extent>10 boxes</physdesc></extent>

Page 55: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML must be well-formed (3)

• case matters

• attribute values must be enclosed in quotation marks, e.g. langcode=“fre”

• element names must obey some basic rules, e.g. cannot start with numbers or punctuation characters, cannot contain spaces

Page 56: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Exchanging recipies

Page 57: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Valid XML (1)

• Valid XML: rules specify elements and attributes used and how used

• Valid XML provides consistency and facilitates the exchange of data

• Valid XML is important for displaying, processing and exchanging XML in a wider environment

Page 58: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Valid XML (2)

• Must conform to a Document Type Definition (DTD) or Schema

• Archives: Encoded Archival Description - EAD version 1; EAD 2002

• e-learning: IEEE Learning Object Metadata Schema (LOM)

Page 59: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML example

<archdesc level="fonds"><did>

<repository>John Rylands University Library of Manchester</repository><unitid countrycode="GB" repositorycode="0133">GB 0133 NCN</unitid><unittitle>Papers of Norman Nicholson</unittitle><unitdate normal="1899-1987">1899-1987</unitdate><physdesc>

<extent>0.44 cu.m; 1,201 items</extent></physdesc><langmaterial>

<language langcode="eng">English</language></langmaterial><origination>Nicholson, Norman Cornthwaite, 1914-1987</origination><note>Created by the John Rylands Library archivist</note>

</did>…..</archdesc>

Page 60: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

HTML vs. XML (1)

• HTML is ONLY for display in a browser

• HTML tags do not describe the content

• HTML cannot easily be extracted

HTML: <h1> Papers of Peter Rowe </h1>XML: <title> Papers of Peter Rowe </title>

HTML: <b> 21 May 2004 </b>XML: <date> 21 May 2004 </date>

Page 61: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

HTML vs. XML (2)

• XML is for display…anywhere

• XML tags are self-describing

• XML tags can be specified by anyone

• XML is user and machine readable

HTML: <table> [data table] </table>

XML: <table> ??? </table>

Page 62: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Why use XML?

• Because everyone else is!

• International standard, supported by the W3C

• XML is open, licence free and platform neutral

• XML is human and machine readable

• XML documents are text documents

Page 63: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

More reasons to use XML

• Separation of content and presentation- With proprietary systems content is

inextricably

bound up with format

• XML does not determine the presentation of the data - You can use CSS (stylesheets) or XSLT

(Extensible Style Sheet Language for Transformations) to present XML data

Page 64: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

..and even more reasons

• Hierarchical structure- XML documents are hierarchical in nature –

with one top-level root element, and hence XML is an excellent choice for setting out hierarchical data in an easy-to-read fashion

• The ability to manipulate and customise- data can be shaped and additions made as the author wishes

Page 65: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

and for data exchange

• XML is the main basis for defining data exchange languages

- e-GIF

• Meaningful tags facilitate extraction – data can be manipulated as required

• Text based - highly portable

Page 66: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF mandates XML

• XML and schemas for data integration

• XSL for data transformations

Page 67: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Document Type Definitions

• A Document Type Definition defines the building blocks of an XML document

• It specifies elements and attributes and defines how they can be used

• People can agree to use a common DTD for interchanging data

• You can include a DTD in your XML source file, or point to an external DTD

Page 68: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF specifies Schemas

• Schemas perform the same task as DTDs

• Schemas use XML syntax

• Schemas support complex data types

• Schemas are extensible

• One XML document can point to more than one schema

Page 69: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML Schemas

• W3C Schema is the standard grammar which is mandated by e-GIF

• Schemas will be developed by specialist groups or by open submission

• Eventually there will be schemas for all services

Page 70: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

A simple XML document

<?xml version="1.0"?>

<note>

<to>Rachel</to>

<from>John</from> <heading>Reminder</heading> <body>Don't forget the concert!</body>

</note>

Page 71: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Example of a simple Schema

<?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

targetNamespace="http://www.w3schools.com" xmlns="http://www.w3schools.com" elementFormDefault="qualified">

<xs:element name="note"> <xs:complexType>

<xs:sequence> <xs:element name="to" type="xs:string"/> <xs:element name="from" type="xs:string"/> <xs:element name="heading" type="xs:string"/> <xs:element name="body" type="xs:string"/>

</xs:sequence> </xs:complexType> </xs:element> </xs:schema>

Page 72: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

e-GIF Schemas

• You are mandated to use the e-GIF schemas

where available

• You can also get involved in the development of new schemas for e-GIF

• e-GIF Schemas are listed at

http://www.govtalk.gov.uk/schemasstandards/xmlschema.asp

Page 73: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 74: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 75: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 76: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 77: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 78: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 79: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Displaying XML

• XML technologies – for displaying, retrieving, transforming, manipulating

• DOM, SAX, XForms, XLink, XPointer

• XSL FO – Extensible Stylesheet Language Formatting Objects

• XSLT – Extensible Stylesheet Language for Transformations

Page 80: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Transformation of XML

• Transformation involves the reading in of an XML file and an XSLT file to a processor,which can then generate some output – typically HTML

XSLT

XML

processor HTML output

Page 81: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

XML in the Archives Hub

• Records displayed in HTML but the data is held as XML

• Plan to use XSLT stylesheet for display

• A stylesheet has been developed as part of a project to evaluate the use of XMLSPY, an XML editor

Page 82: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 83: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 84: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 85: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 86: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 87: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 88: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Summary

• XML is simple, flexible and great for data exchange

• XML must be well-formed and valid

• e-GIF specifies and lists schemas

• XML is used with other XML technologies

• XSLT can transform XML

Page 89: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Section 3

Web Services and other e-GIF protocols

Page 90: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Aims of this section

• To explain…• what Web Services are• the standards that are used

• To illustrate the technology with some examples

• To briefly mention other e-GIF protocols

Page 91: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Web Services

• A web service is an online application that can be accessed by other applications

• Web services use XML to achieve this interoperability– SOAP

– WSDL– UDDI

Page 92: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Creating a web service

• Web services can be created for existing applications

– e.g. zetoc service at MIMAS

• Key element is an XML file with details of how to interact with the service – the WSDL (Web Services Description Language) file

Page 93: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Locating the Service

• Information about the location of the WSDL file is placed with a registry service

• Potential users of the web service can then discover its location and how to interact with it (from the information in the WSDL file)

Page 94: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Web services architecture

Registry

Web Service

User

3. Accesses

1. Publishes details of service

2. Discovers available services

Page 95: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Web services architecture

Registry

Web Service

User

3. Accesses

1. Publishes details of service

2. Discovers available services

Described in WSDL file

Page 96: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

zetoc WSDL extract

…<complexType name="JournalRequest"> <sequence> <element ref="srw:startRecord" minOccurs="1" maxOccurs="1"/> <element ref="bath:any" minOccurs="1" maxOccurs="1" nillable="true"/> <element ref="dc:title" minOccurs="1" maxOccurs="1" nillable="true"/> <element ref="dc:creator" minOccurs="1" maxOccurs="1" nillable="true"/> <element ref="oujnl:jtitle" minOccurs="1" maxOccurs="1" nillable="true"/> <element ref="oujnl:issn" minOccurs="1" maxOccurs="1" nillable="true"/> <element ref="oujnl:volume" minOccurs="1" maxOccurs="1" nillable="true"/> <element ref="oujnl:issue" minOccurs="1" maxOccurs="1" nillable="true"/> <element ref="oujnl:spage" minOccurs="1" maxOccurs="1" nillable="true"/> <element ref="dcterms:issued" minOccurs="1" maxOccurs="1" nillable="true"/> </sequence> </complexType>…

Page 97: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Interacting with a service

• Once the client application knows how to interact with the service, client and service communicate using messages encoded in XML

• These messages use the SOAP schema and are often passed over HTTP

Page 98: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

SOAP

• A way of packaging XML information and passing it from one system to another

• Allows one system to make requests of another and to process the reply

• Systems can be completely different, running on different software

Page 99: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Sample zetoc search values

Property Value

dc:creator apps

oujnl:jtitle materialia

oujnl:issn 1359-6462

oujnl:volume 48

oujnl:issue 5

oujnl:spage 475

dcterms:issued 2003

Page 100: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

SOAP request

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<zetoc:JournalRequest>

<dc:creator>apps</dc:creator><oujnl:title>materialia</oujnl:title><oujnl:issn>1359-6462</oujnl:issn><oujnl:volume>48</oujnl:volume>…

</zetoc:JournalRequest>

</soap:Body>

</soap:Envelope>

Page 101: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Sample full record response

Property Valuesrw:numberOfRecords 1dc:identifier RN125218404zetoc:type J (ie. journal)dc:title Phase compositions in magnesium-rare earth alloys containing

yttrium, gadolinium or dysprosiumdc:creator Apps, P. J.; Karimzadeh, H; King, J. F.; Lorimer, G. W.zetoc:dewey 669zetoc:lccn TT273oujnl:jtitle SCRIPTA MATERIALIAoujnl:issn 1359-6462zetoc:volissue VOL 48; NUMBER 5oujnl:pages 475-481dcterms:issued 2003dc:publisher Great Britain : Elsevier Science B.V., Amsterdam.zetoc:frequency Fortnightly: 15-30 issues per yeardc:language Englishzetoc:shelfmark8212.970000

Page 102: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

SOAP Response

HTTP/1.1 200 OKContent-Type: text/xml

<soap:Envelope > <soap:Body> <zetoc:IdentifierSearchResponse >

<srw:numberOfRecords>1</srw:numberOfRecords><dc:identifier>RN125218404</dc:identifier><zetoc:type>J</zetoc:type><dc:title>Phase compositions in magnesium-rare earth alloys containing yttrium, gadolinium or dysprosium</dc:title> …

</zetoc:IdentifierSearchResponse > </soap:Body></soap:Envelope>

Page 103: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Registries

Registry

Web Service

User

3. Accesses

1. Publishes details of service

2. Discovers available services

Page 104: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Publishing to a registry

• UDDI – Universal Description, Discovery and Integration

• A way of describing a service provider and its services (in XML)

• With a mechanism for publishing the descriptions (maintained by IBM and Microsoft)

Page 105: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Issues with registries

• How do you judge the quality of the services described?

• Private registries could be the answer: e.g. JISC’s Information Environment Service Registry – quality-assured services for JISC’s target audience (www.iesr.ac.uk)

Page 106: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Page 107: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

SOAP service description

Page 108: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Other protocols

• e-GIF approves other protocols for information transfer, including:

– Metadata harvesting: OAI-PMH version 2.0– Content syndication: RSS version 1.0– Context-sensitive linking: OpenURL 0.1(migrating to 1.0)– Distributed searching: Search/Retrieve Web Service (SRW)

• All these services can be described in a registry such as the IESR

Page 109: e-Government Interoperability Framework

E-Government Interoperability Framework20 September 2004

Conclusion

• This seminar has introduced you to

– What eGIF is all about• a set of complementary technologies that you must use

• What XML is all about• the core technology of eGIF

• How XML can be used to implement systems• How different XML technologies can be used together

• To access this presentation online visit:• www.archiveshub.ac.uk/arch/egif