Interoperability Standards Rationale for PAPI. Sean McGrath Technical Lead Pan African Parliamentary Interoperability Framework Initiative

Transcription

1 Interoperability Standards Rationale for PAPI Sean McGrath Technical Lead Pan African Interoperability Framework Initiative 1

2 Why Pan-African Interoperability? All Parliaments face very similar IT problems Drafting legislation Debating/voting/tracking changes to documents Recording chamber debate/committees etc. Producing working documents such as committee briefs, amendment lists etc. 2

3 Why Pan-African Interoperability? Significant scope for sharing information artifacts such as legislation Significant scope for avoiding reinventing the wheel in creating electronic representations of bills, debate record, order papers etc. Significant scope for improving inter-parliament information retrieval and citation through use of common metadata and common document naming conventions. 3

4 Why Pan-African But Interoperability? Individual Parliaments/jurisdictions require local features, local customisations Many, many similarities in the workings of Parliaments but also many differences that need to be respected 4

5 Why Pan-African Interoperability? Question: How to allow seamless sharing of documents between Parliaments while retaining local extensibility? Answer: Create an Interoperability Framework 5

6 What is Interoperability? The ability to share electronic data and electronic processing between cooperating entities such that differences in underlying IT systems are irrelevant. 6

7 Layers Of Interoperability Organisational Interoperability Semantic Technical EPAN egovernment Working Group 7

8 Layers of Interoperability Interoperability Naming Organisational PDR ACT BILL POP XML Semantic Technical Metadata Web PAPI EPAN egovernment Working Group perability.pdf 8

9 PAPI In Practice Hub notation Parliament A Parliament B PAPI Framework Parliament D Parliament C 9

10 PAPI Deployment Options Direct Parliament A Users PAPI-Based System Parliament B PAPI Framework Parliament D Parliament C 10

11 PAPI Deployment Options Extended Parliament A Users Extended PAPI-Based System PAPI Import/Export Filter Parliament B PAPI Framework Parliament D Parliament C 11

12 PAPI Deployment Options Compatibility Parliament A Non-PAPI System Users PAPI Import/Export Filter Parliament B PAPI Framework Parliament D Parliament C 12

13 PAPI Citation and Search Model Web Browser Website Parliament A Website Parliament A PAPI Framework PAPI Web Spider & Search Engine Website Parliament A Website Parliament A Front-end Integration Back-end Integration 13

14 PAPI Metadata Critical for inter- information retrieval/search Extensible Metadata Model based on naming conventions Eurovoc Africa Dublin Core 14

15 Eurovoc Africa Eurovoc Multilingual thesaurus developed by EU 15 Languages (including English, French & Portuguese) Over 6,000 descriptors Eurovoc Africa A planned extension to Eurovoc to incorporate required African descriptors 15

16 PAPI Hypertext Naming convention for information assets critical for inter- hyperlinking Meaningful identifiers no need for lookup registries Can know what the resource will be called in PAPI before the resource even exists Variety of hypertext resolution mechanisms supported 16

17 Main components XML Document models for legislation, debate record etc. (in a variety of schema languages) Sample documents Extensible naming convention for documents and metadata Extensible naming convention for hypertext management Extensible framework for expressing business rules to validate the structure of documents 17

18 Main components Profiles of XML and related standards for use in PAPI (Unicode, W3C XML schema etc.) Extensible framework for schema management and evolution 18

19 Status and Roadmap Framework has been baselined Sample documents, schemas, validators etc. available Full documentation available Governance structure under discussion Comments and contributions welcome 19