The Interoperability Framework for E-Government

The Interoperability Framework for E-Government

Office of the Government Chief Information Officer The Interoperability Framework for e-Government [S18] Version: 19.0 December 2020 The Government of the Hong Kong Special Administrative Region of the People’s Republic of China COPYRIGHT NOTICE © 2020 by the Government of the Hong Kong Special Administrative Region Unless otherwise indicated, the copyright in the works contained in this publication is owned by the Government of the Hong Kong Special Administrative Region. You may generally copy and distribute these materials in any format or medium provided the following conditions are met – (a) the particular item has not been specifically indicated to be excluded and is therefore not to be copied or distributed; (b) the copying is not done for the purpose of creating copies for sale; (c) the materials must be reproduced accurately and must not be used in a misleading context; and (d) the copies shall be accompanied by the words “copied/distributed with the permission of the Government of the Hong Kong Special Administrative Region. All rights reserved.” If you wish to make copies for purposes other than that permitted above, you should seek permission by contacting the Office of the Government Chief Information Officer. INTEROPERABILITY FRAMEWORK FOR E-GOVERNMENT DISTRIBUTION AND RELEASE Distribution of Controlled Copy Copy No. Holder 1 Government-wide Intranet (itginfo.ccgo.hksarg) 2 Internet (www.ogcio.gov.hk) Prepared By: Interoperability Framework Coordination Group Document Effective Date: 1 March 2021 i-1 INTEROPERABILITY FRAMEWORK FOR E-GOVERNMENT AMENDMENT HISTORY Amendment History Change Revision Description Pages Revision Date Number Affected Number Major updates to version 18.1 issued in 19.0 December February 2020 are as follows: 2020 1. Add “OpenAPI v3.0” as a recommended 7-2 standard to the interoperability area “Simple functional integration in an open environment” under Application Integration Domain. 2. Remove “ISO/TS 15000-2:2004” from name 7-3 of the Recommended Standard “ebMS v2 (ISO/TS 15000-2:2004)” from the interoperability area “Reliable message exchange between application systems in an open environment for business document- oriented collaboration” under Application Integration Domain. 3. Add “PDF/A-1a (ISO 19005-1 Level A)” and 7-4 “PDF/A-1b (ISO 19005-1 Level B)” as the recommended standards to the interoperability area “Document file type for receiving documents under ETO” under Information Access & Interchange Domain. 4. Update the remarks of interoperability area 7-7 “Removable storage media for receiving documents under the ETO” under Information Access & Interchange Domain. 5. Add “MPEG-4 (ISO 14496)” as a 7-8 recommended standard to the interoperability area “Audio / video streaming” under Information Access & Interchange Domain 6. Update the version of “GeoTIFF”of the 7-9 interoperability area “Digital Geographic Data Format” under Information Access & Interchange Domain 7. Update the version of “ISO 19111” of the 7-9 interoperability area “Digital Geographic Data Format” under Information Access & Interchange Domain ii-1 INTEROPERABILITY FRAMEWORK FOR E-GOVERNMENT AMENDMENT HISTORY Amendment History Change Revision Description Pages Revision Date Number Affected Number 8. Add “Geography JavaScript Object Notation 7-9 (GeoJSON - RFC 7946)” as a recommended standard to the interoperability area “Digital Geographic Data Format” under Information Access & Interchange Domain. 9. Add “S/MIME v4” as a recommended 7-10 standard to the interoperability area “Attachment of digital signature to electronic documents received under ETO” under Security Domain. 10. Add “S/MIME v4” as a recommended 7-10 standard to the interoperability area “E-mail security” under Security Domain. 11. Add “STIX v2.1” as a recommended standard 7-13 to the interoperability area “Cyber threat information sharing standards” under Security Domain. 12. Add “TAXII v2.1” as a recommended 7-13 standard to the interoperability area “Cyber threat information sharing standards” under Security Domain. 13. Remove the version of the standard “CTAP” 7-14 from the interoperability area “Authentication and authorisation with distributed identity” under Security Domain. 14. Add “HTTP/2” as a recommended standard to 7-14 the interoperability area “Hypertext transfer protocol” under Interconnection Domain. 15. Add “HTTP/2” as a recommended standard to 7-14 the interoperability area “File transfer” under Interconnection Domain. 16. Update the “Are the specifications relevant to 7-14 submissions under ETO ?” of interoperability area “File transfer” under Interconnection Domain. ii-2 INTEROPERABILITY FRAMEWORK FOR E-GOVERNMENT AMENDMENT HISTORY Amendment History Change Revision Description Pages Revision Date Number Affected Number 17. Add “Data Distribution Service (DDS)” as an 7-16 under observation standard (or emerging standard) to the interoperability area “Asynchronous message exchange between application systems” in the Application Integration Domain. 18. Remove the version of the standard “WS- 7-16 Addressing” from the interoperability area “Transport-neutral mechanisms to address Web Services and messages” under Application Integration Domain. 19. Remove the version of the standard “WS- 7-16 Policy” from the interoperability area “Grammar for expressing the capabilities, requirements, and general characteristics of entities in an XML Web Services-based system” under Application Integration Domain. ii-3 INTEROPERABILITY FRAMEWORK FOR E-GOVERNMENT CONTENTS TABLE OF CONTENTS 1.EXECUTIVE SUMMARY ............................................................................................... 1-1 2.PURPOSE AND STRUCTURE OF DOCUMENT ........................................................ 2-1 3.OVERVIEW OF THE INTEROPERABILITY FRAMEWORK ................................ 3-1 3.1 THE NEED FOR AN INTEROPERABILITY FRAMEWORK .................................. 3-1 3.2 SCOPE OF THE INTEROPERABILITY FRAMEWORK ......................................... 3-1 3.3 IMPACT OF THE INTEROPERABILITY FRAMEWORK ....................................... 3-3 4.MANAGEMENT OF THE INTEROPERABILITY FRAMEWORK ........................ 4-1 4.1 KEY REQUIREMENTS FOR MANAGEMENT MECHANISM .............................. 4-1 4.2 MANAGEMENT OF TECHNICAL SPECIFICATIONS ........................................... 4-1 4.3 MANAGEMENT OF COMMON SCHEMAS ............................................................ 4-2 4.4 CHANGE MANAGEMENT ........................................................................................ 4-2 5.COMPLIANCE ................................................................................................................. 5-1 5.1 THE USE OF TECHNICAL SPECIFICATIONS AND COMMON SCHEMAS ....... 5-1 5.2 COMPLIANCE POLICY ............................................................................................. 5-1 5.3 COMPLYING TO NEW VERSIONS OF THE INTEROPERABILITY FRAMEWORK ...................................................................................................................................... 5-2 5.4 WHO NEEDS TO UNDERSTAND COMPLIANCE .................................................. 5-3 5.5 RESPONSIBILITIES .................................................................................................... 5-3 5.6 PROCEDURES FOR EXEMPTION FROM COMPLIANCE .................................... 5-3 6.PRINCIPLES UNDERLYING THE RECOMMENDATION OF TECHNICAL STANDARDS .............................................................................................................. 6-1 6.1 PRINCIPLES TO BE OBSERVED BY PROJECT TEAMS WITH REGARD TO THE USE OF THE IF TECHNICAL STANDARDS ........................................................... 6-1 6.2 PRINCIPLES FOR INCLUDING INTEROPERABILITY AREAS UNDER THE IF 6-2 6.3 PRINCIPLES FOR SELECTING TECHNICAL STANDARDS UNDER THE IF .... 6-3 7.SPECIFICATIONS UNDER THE INTEROPERABILITY FRAMEWORK ............ 7-1 7.1 OVERVIEW ................................................................................................................. 7-1 7.2 APPLICATION INTEGRATION DOMAIN ............................................................... 7-2 7.3 INFORMATION ACCESS AND INTERCHANGE DOMAIN .................................. 7-3 7.4 SECURITY DOMAIN ................................................................................................ 7-10 7.5 INTERCONNECTION DOMAIN ............................................................................. 7-14 7.6 OTHER SPECIFICATIONS UNDER OBSERVATION ........................................... 7-16 8.ABBREVIATIONS AND ACRONYMS ......................................................................... 8-1 iii-1 INTEROPERABILITY FRAMEWORK FOR E-GOVERNMENT EXECUTIVE SUMMARY 1. EXECUTIVE SUMMARY The Interoperability Framework (IF) supports the Government’s strategy of providing client-centric joined-up services by facilitating the interoperability of technical systems between Government departments, as well as between Government systems and systems used by the public (including citizens and businesses). The IF defines a collection of specifications aimed at facilitating the interoperability of Government systems and services. By bringing together the relevant specifications under an overall framework, IT management and developers can have a single point of reference when there is a need to identify the required interoperability specifications that should be followed for a specific project. By adopting these interoperability specifications, system designers can ensure

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    46 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us