DICT Building, C.P. Garcia Avenue, Diliman, Quezon City ...i.gov.ph/wp-content/uploads/2016/09/PeGIF_Framework_PeGIF_1.1... · Preface Interoperability is a key in realizing our goals

Version: 1.1Date: June 21, 2016

Philippine Electronic Government Interoperability Framework (PeGIF) version 1.1

Contents

Preface Introduction

Desired Outcomes Definition Coverage Principles

Key Technical Policies Managing the PeGIF

Development Implementation Monitoring and Evaluation Policy Updating Role of Agencies

Standards Catalog

Purpose

This document aims to define the common language, principles, and standards that national government agencies should use in the design of data and information systems to enable data exchange and reuse.

Scope

This document is limited to Technical Interoperability. Information Interoperability Framework shall be covered by another document.

Issuing Authority

This document has been developed and issued by the Policies and Standards Divisionunder the National ICT Governance Service of the Department Information and Communications Technology (DICT), subject to continuity, unless repealed.

Contact Information

Policies and associated publications under the DICT can be found at http://icto.dost.gov.ph/.

Queries, suggestions, and clarifications with regard to this policy may be forwarded to 920-0101 local 2622.

DICT Building, C.P. Garcia Avenue, Diliman, Quezon City 1101 Trunkline (+632) 920-0101

http://i.gov.ph/

Preface

Interoperability is a key in realizing our goals of improving the effectiveness and efficiency of national government agencies, creating a positive business environment and enhancing good governance and broadening public participation.

The Philippine eGovernment Interoperability Framework (PeGIF) seeks to enable data exchange and reuse among national government agencies. This specific document is about technical interoperability or matters relating to linking ICT systems and services, including interfaces, interconnection, data integration, data exchange, security, and presentation.

The PeGIF was developed by a special working group composed of members from the government and private sector. In producing the document, several consultation workshops with different stakeholders were also conducted. TheDICT is tasked with managing and monitoring the implementation of the PeGIF.

The PeGIF is one of the policy tools needed to implement seamless and effective technology-enabled governance. The DICT shall also work on a high-level government-as-a-whole architecture. With these policy tools, we hope to take a major stride toward effective, efficient, and empowering eGovernment in the Philippines.


Introduction

The Philippine eGovernment Interoperability Framework (PeGIF) defines a common language, principles, and standards that national government agencies should use in the design of data and information systems to enable data exchange and reuse.

1.1.Desired Outcomes

Interoperability is a tool to achieve the following:

1.1.1. Increased Efficiency of Government Services. The PeGIF will enable the government to design efficient and integrated services thatare responsive to citizens’ needs. Integration will reduce redundancies and inefficiencies in existing government processes. Through the PeGIF, agencies will be able to better collaborate in developing public policy and services.

This outcome will be achieved when the increased number of inter-agency systems leads to new ICT-enabled public services that better meet citizens' needs and hasten socio-economic growth.

1.1.2. Improved Decision-Making in Government. The PeGIF will improve decision-making through easier access to consolidated and processed data and information across government.

This outcome will be achieved when all NGAs use and rely on ICT-enabled decision support and business intelligence systems to deliver their mandate.

1.1.3. Reduced Costs and Increased Savings for Government. The PeGIF will allow information systems across agencies to exchange data seamlessly and reduce, if not remove, the need for middleware. The PeGIF will also prevent single-vendor lock-in, which can lead to cost-savings or more value gains for the same price.

The above would then lead to:

1.1.4. Increased Citizen Satisfaction in Transacting with Government. The PeGIF will help create interoperable eGovernmentsystems that would make possible trustworthy transactions with government anytime, anywhere.

This outcome will be achieved when secure government services are fully or partially delivered electronically and traditional service deliverychannels (e.g., over the counter, mail, and telephone) are enhanced by the use of ICT.


1.1.5. Enhanced Ability to Interoperate With Other Nations. The PeGIF will enable exchange of data and information across national boundaries.

This outcome will be achieved when national government agencies regularly exchange and reuse data from their counterparts in other countries to protect and promote each government's national interest.

1.1.6. Better Informed and Active Citizenry. The PeGIF will help produce an informed and active citizenry by providing reliable and readily available government data and information as well as new electronic channels for citizen participation in governance.

This outcome will be achieved when government data and informationare readily available to all citizens via an Open Data portal and all national government agencies are able to provide electronic participation channels. These will enable Filipinos to participate in policy development and in the design and delivery of public services.

1.1.7. Improved Ecosystem for Competition and Innovation Among ICT Service Providers. The PeGIF will contribute to the improvement of market competition among ICT service providers by defining and sharing the standards for different providers competing for government accounts.

This outcome will be achieved when a diverse set of players in the market arise to compete for government accounts.

1.2. Definition

EGovernment Interoperability is defined as the ability to exchange and reusegovernment data and information in a uniform and efficient manner across multiple government ICT systems and agencies.

Interoperability has three domains.

1.2.1. Technical interoperability – All matters relating to linking ICT systems and services, including interfaces, interconnection, data integration, data exchange, security, and presentation.

1.2.2. Information interoperability – All matters relating to a common methodology, definition, and structure of information, along with shared services for its retrieval.

1.2.3. Business-process interoperability – All matters that deal with the common methods, processes, and shared services for collaboration, including workflow, decision-making, and business transactions.

Cross-cutting these three domains are:


1.2.4. Security - All aspects related to defining, achieving, and maintaining confidentiality, integrity, availability, non-repudiation, accountability, authenticity, and reliability of a system.

1.2.5. Best Practice - Aspects related to demonstrating the best uses of standards in the public and private sectors to achieve technical, information, and business process interoperability.

This document is limited to Technical Interoperability. Information Interoperability Framework shall be covered by another document.

1.3. Coverage

The use of PeGIF is mandatory for the Executive branch of government, including the National Government Agencies, Bureaus, and Offices (NGAs), Government-Owned and Controlled Corporations (GOCCs), Government Financial Institutions (GFIs), and State Universities and Colleges (SUCs).

PeGIF implementation shall be forward-looking. It shall guide the design, development, procurement, implementation, and evaluation of all new ICT systems (both software and hardware) in government. It shall also be used as ICT systems reach the end of their life cycles or as existing ICT systems are upgraded.

As the benefits of the PeGIF are not limited to the Executive branch of government, the Legislature, Judiciary, and other Constitutional bodies are invited to consider adopting the PeGIF. Likewise, Local Government Units (LGUs) are encouraged to adopt the PeGIF. The PeGIF is also open to use by:

1.3.1. non-government organizations1.3.2. the private sector (business community)1.3.3. the academe1.3.4. the public.

1.4.Tenets

The following tenets govern the PeGIF:

1.4.1. Openness and citizen engagement. The PeGIF facilitates transparency in government and enables citizen participation in governance.

1.4.2. Collaboration. The PeGIF allows national government agencies to work together to deliver better, more efficient public services.

1.4.3. Alignment with existing standards. The PeGIF draws from established international, regional, and national standards and notes opportunities from current industry developments.


1.4.4. Preference for open standards. The PeGIF is based on open standards. All PeGIF standards and guidelines must conform with open standard definitions, unless there are specific and compelling reasons against its use in specific agencies.

An open standard is a set of technical specifications that are usually published by formal standard-setting organizations, using an open decision-making process. These standards are generally available to the public on royalty-free terms without restrictions as to its use or redistribution of any of its implementations. The actual written specifications must be available for free or for a nominal fee.

1.4.5. Trust and security. The PeGIF will promote safety, resiliency, and confidence in eGovernment systems.

1.4.6. Inclusiveness. The PeGIF requires agencies to closely work with relevant sectors and communities of interest to define their interoperability needs.

Key Technical Policies

2.1. The following key policies are adopted:

2.1.1. Alignment with the Internet: the universal adoption of common specifications used on the Internet and World Wide Web for all public sector information systems.

2.1.2. Adoption of the browser as the key interface: all public sector information systems are to be accessible through browser-based technology; other interfaces are permitted but only in addition to browser-based ones. Browsers will not have active content so that users are not forced to reduce the browser’s security settings.

2.1.3. Addition of metadata to government information resources.

2.2. Standard Selection

The technical specifications adopted in the PeGIF are those that:

2.2.1. Enhance data/information exchange – Specifically, standards that are relevant to systems’ interconnectivity, data integration, presentation and interface, e-services access, and content management metadata.

2.2.2. Promote openness – Specifications that comply with the definition of open standards used in this document and contribute to open systems.


2.2.3. Conform with international practices – Preference will be given to standards with the widest applicability. When appropriate, international standards will take precedence over regional and national standards.

2.2.4. Adapt easily to scale – The standard should satisfy changed demands made on the system, such as changes in data volumes, number of transactions or number of users.

2.2.5. Have existing market base – The specifications selected are widelysupported by the market and leads to reduction of costs and risk for the government information system.

2.3. Sectoral Standards

The PeGIF recognizes the possible need for sectoral standards. These sectoral standards, however, should only be developed and adopted if existing national standards, identified in the standards catalogue, inhibit information exchange within the sector. Furthermore, sectoral standards should not prevent data and information exchange between sectors. Finally,sectoral standards should be selected using the PeGIF principles and selection process.

Managing the PeGIF

3.1.Development

The DICT managed the development and issuance of the PeGIF.

A PeGIF Task Group was organized to draft the PeGIF. The PeGIF Task Group was composed of ICT experts from government, private (business) sector, civil society and non-government organizations, and academe.

The draft PeGIF underwent a multi-channel national consultation involving stakeholders before it was finalized and adopted.

3.2. Implementation

An appropriate order shall be drafted and issued by the DICT to adopt and implement the PeGIF.

The DICT shall be responsible for the overall implementation of the PeGIF, including the development of the implementation plan and mechanisms and the integration of the PeGIF in all national government plans and processes (e.g. PDP, GPPB).

The DICT shall form a committee to oversee the implementation of the PeGIF, which will be assisted by a multi-stakeholder PeGIF Advisory Committee.


The DICT, shall assist this committee in PeGIF implementation.

3.3.Monitoring and Evaluation

The DICT shall develop tools to monitor PeGIF implementation.

The DICT, with the assistance of technical experts, shall issue yearly evaluation report of PeGIF implementation. These reports shall serve as inputs in updating the PeGIF.

3.4.Policy Updating

The PeGIF is a living document and will adapt to changing requirements overtime and will be maintained at a strategic level.

The PeGIF shall be reviewed a year after its implementation. Subsequent reviews shall be biennial. Specific standards in the catalog, however, can be updated after a Change Request, including use-case report, is submitted andaccepted by the DICT.

3.5.Role of Agencies

Interoperability requires a culture of collaboration and consistent use of the agreed standards between national government agencies.

Government Chief Information Officers (GCIOs), of NGAs, GFIs, GOCCs, and SUCs, or their equivalent, are primarily responsible for the success of the PeGIF. GCIOs shall ensure the adoption of the PeGIF as an agency policy and ensure that it is referenced in their ICT plans and procurement. GCIOs shall also raise awareness of the PeGIF within the agency and create an environment for officials to raise and act on interoperability issues.

GCIOs are encouraged to use the adoption of the PeGIF as an opportunity toreduce spending while improving the quality of services offered by their agencies.


Standards CatalogueTechnical Interoperability

Security

# Short Name

Full Standard Title

Latest Version Version URL Custodian

1ISO 27001

Information technology – Security techniques – Information security management systems -- Requirements

ISO/ IEC 27001:2013 2013

http://www.iso.org/iso/home/standards/management-standards/iso27001.htm

International Organization for Standardization/ International Electrotechnical Commission

2S/MIME ESS

Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility

RFC 5035 v3

https://tools.ietf.org/html/rfc5751 Internet

Engineering Task Force

3 SAMLSecurity AssertionsMark-up Language(SAML) v2.0

V2.0 V2.0

https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=security

Organization for the Advancement of Structured Information Standards

4 TLSTransport Layer Security Protocol Version 1.2

RFC 5246 V1.2https://tools.ietf.org/html/rfc5246

Internet Engineering Task Force

5WS-Security v1.1.1

Web Services Security v1.1.1 OASIS 20040 V1.1.1

http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-UsernameTokenProfile-v1.1.1-os.html


6

WS-I - Basic Security Profile

Web Services- Interoperability Organization - Basic Security Profile v1

Up-to-date V1.0

http://www.ws-i.org/profiles/basicsecurityprofile-1.0.html

Web Services – Interoperability Organization (WS-1)

7 X.509 International standard for identity certificates RFC 6818 v3

https://tools.ietf.org/html/rfc6818

International Telecommunications Union

8 XML-DSIG

Extensible Markup Language – Signature Syntax and Processing

Xmldsig-core-20080610

2ndEdition

https://www.w3.org/TR/xmldsig-core World Wide Web

Consortium

9 PGP OpenPGP MessageFormat

RFC 5581 https://tools.ietf.org/html/rfc5581

Internet Engineering Task


Force

10 AES Advanced Encryption Standard

FIPS PUB 197http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf

National Institute of Standards and Technology

11 SHA2Secure Hash Algorithms

NIST FIPSPUB 180-4

http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf


12 SHA3Secure Hash Algorithms

FIPS PUB 202, August 2015

http://csrc.nist.gov/publications/drafts/fips-202/fips_202_draft.pdf

13 RSAAlgorithm for public key cryptography

IEEE 1363

http://grouper.ieee.org/groups/1363/

Institute of Electrical and Electronics Engineers Standards Association

14 DSA Digital Signature Algorithm

FIPS PUB 186 - 4

http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf

FIPS/ National Institute of Standards and Technology

15 ECDHElliptic curve Diffie-Hellman

SP 800-56 A Rev. 2 (2013)

http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar2.pdf


16 ECDSA

Elliptic Curve Digital Signature Algorithm

NIST FIPS PUB 186-3

http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf

American National Standards Institute

17 OAuthOpen Authentication Protocol

RFC 6749, 6750

*https://tools.ietf.org/html/rfc6749



18 OpenIDOpen ID Authentication Protocol

See OpenID Connect extension (Feb 2014)

V2.0

https://openid.net/specs/openid-authentication-2_0.html

Open ID Foundation

Discovery

# Name Full Standard Title

Latest Version VersionNumber

URL Custodian

1 DNS

Domain Names – Concepts and Facilities,Domain Names – Implementation and Specification

RFC 1034, 1035





2Dublin Core Standard

Simple and extensible metadata element set intended to facilitate discovery of electronic resources

Latest Verison May 2009

dublincore.org

Dublin Core Metadata Initiative

3ISO 19111

Geographic information – Spatial referencingby coordinates

Addition of ISO 19111-2:2009

ISO19111-2:2009

http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm

International Organization for Standardization

4 LDAP

Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map

RFC 4510



5 METSMetadata Object Description Standard

Latest Version May 2015 V3.6

http://www.loc.gov/standards/mods/

Library of Congress

7 MIX NISO Metadata forImages in SML

MIX Schema v2.0

V2.0 http://www.loc.gov/standards/mix/

Library of Congress

8

OAI Harvesting Protocol

Open Archives Initiative

Latest Version January 2015

V2.0

https://www.openarchives.org/OAI/openarchivesprotocol.html

Open Archives Initiative

9 ODRL Open Digital Rights Language

Latest Version March 2015

V2.1 https://www.w3.org/community/odrl/

IPR Systems

10 RDFResource Description Framework

RDF 1.1 Concepts and Abstract SyntaxW3C Recommendation 25 February 2014

RDF 1.1

https://www.w3.org/standards/techs/rdf#w3c_all

World Wide Web Consortium

11 UDDI v2UDDI Version 2 OASIS Standard

Latest Version October 2004 V3.0

https://www.oasis-open.org/committees/uddi-spec/


12WSDL v2.0

Web Services Description Language (WSDL)

W3C Recommendation 26 June 2007

V2.0https://www.w3.org/TR/wsdl


13 XrML Extensible Rights Markup Language

Latest Version May 2002

V2.0 http://www.xrml.org/ ContentGuard

Interconnection




URL Custodian

1 BGP4A Border Gateway Protocol 4 RFC 4271



2 IPv4

Internet Protocol: DARPA Internet Program Protocol Specification

RFC 791



3 IPv6Internet Protocol, Version 6 Specification

RFC 2460https://tools.ietf.org/html/rfc2460


4 HTTP/1.1Hypertext TransferProtocol – HTTP/1.1

Obsoleted by RFCs: 7230, 7231, 7232, 7233, 7234, 7235


5 HTTP/2Hypertext TransferProtocol – HTTP 2

RFC 7540 (Published May 15, 2016)



6HTTPS: TLS

A secure version ofHTTP implementedusing the secure sockets layer(Transport Layer Security Protocol Version 1.2)

RFC 5246



7

Multiprotocol Extensions for BGP-4 and Extensions for IPv6Inter-Domain Routing

Multiprotocol Extensions for BGP-4 and Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-DomainRouting

RFC 4760, 2545


*https://tools.ietf.org/html/rfc2545 Internet


8SOAP v1.2

Simple Object Access Protocol

W3C Recommendation 27 April 2007

https://www.w3.org/TR/2001/WD-soap12-20010709/


9 JMS Java Message Service

JSR343 (JMS 2.0) V2.0

https://www.jcp.org/aboutJava/communityprocess/mrel/jsr343/index.html

Java Community Process

10 TCPTransmission Control Protocol Congestion Control




11WS-I Basic Profile

Web Services Interoperability Profile

Latest Version Nov 9, 2010 V2.0

http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html

Web Services Interoperability Organization

12

WS-I Simple SOAP Binding Profile

Defines use of XML envelopes for transmitting messages and places certain constraints on their use

Up-to-date V1.0

http://www.ws-i.org/profiles/simplesoapbindingprofile-1.0.html Web Services

Interoperability Organization

13

WS-I Attachments Profile 1.0

Defined MIME multipart structurefor packaging attachments with SOAP messages

Up-to-date V1.0

http://www.ws-i.org/profiles/attachmentsprofile-1.0-2004-08-24.html

Web Services Interoperability Organization

14 JSON

The application/ json Media Type for JavaScript Object Notation

RFC 7159



15 SSHThe Secure Shell Protocol Architecture

RFC 4250 to 4254

*https://tools.ietf.org/html/rfc4250*https://tools.ietf.org/html/rfc4251





16 WebDAV

HTTP Extensions for Web Distributed Authoring and Versioning

RFC 4918



17SIP SIP: Session

Initiation Protocol RFC 3261https://tools.ietf.org/html/rfc3261


18ITU-T H.323

Terminals and other entities that provide multimediacommunication services over Packet-Based Networks

Amendment 1 March 2013 V7.0

https://www.itu.int/rec/T-REC-H.323/en

International TelecommunicationUnion


19 XMPP

Extensible Messaging and Presence Protocol:Core, Extensible Messaging and Presence Protocol:Instant Messaging and Presence, Extensible Messaging and Presence Protocol:Address Format

RFC 6120, 6121,7622





Data Exchange

#Name Full Standard

TitleLatest Version Version

NumberURL Custodian

1

PhilippineStandard IndustrialClassification

Guide for classifying industries by economic activity

Latest Version 2009

http://nap.psa.gov.ph/activestats/psic/default.asp

2 ebXML v2.0

ebXML Message Service Specification v2.0

OASIS 200204/ ISO 15000-1 to 5

V2.0

http://docs.oasis-open.org/ebxml-bp/2.0.4/OS/spec/ebxmlbp-v2.0.4-Spec-os-en-html/ebxmlbp-v2.0.4-Spec-os-en.htm

Organization for the Advancement of Structured Information Standards/International Organization for Standardization

3 eBMXL v3.0

OASIS ebXML Messaging Services Version 3.0

OASIS Standard1 October 2007

V3.0

http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/cs02/ebms_core-3.0-spec-cs-02.html

Organization for the Advancement of Structured Information Standards/International Organization for Standardization

4 ISO/IEC 11179

Information Technology --Metadata Registries – Part 1 Framework

11179-1 3rd edition – Under Development

3rdEdition

http://metadata-standards.org/11179/


5ISO15022

Data Field Dictionary ISO 20022

ISO20022

http://www.iso15022.org/ International Organization for Standardization

6 MIME Multipurpose Internet Mail Extensions (MIME)Part One to Part Five

RFC 2045, 2046,2047, 2049, 4289 & 6838







*https://tools.ietf.org/html/rfc4289*https://tools.ietf.org/html/rfc6838

7 SMTPSimple Mail Transfer Protocol RFC 5321



8 UNICODEUnicode Format for Network Interchange



9XBRL Meta Model

Extensible Business ReportingLanguage (XBRL 2.1)

Up-to-date V2.1

http://www.xbrl.org/specification/abstractmodel-primary/pwd-2012-06-06/abstractmodel-primary-pwd-2012-06-06.html

XBRL

10 XMI v 2.0.1

XML Metadata Interchange Specification

ISO/IEC 19503

http://www.omg.org/spec/XMI/


11 XML 1.0 Extensible Markup Language (XML) 1.0 Fifth Edition

W3C Recommendation 16 August 2006

https://www.w3.org/TR/xmldsig-core/ World Wide Web

Consortium

12 XSL v1.1

Extensible Stylesheet Language Version 1.0

W3C Recommendation 05 December 2006

https://www.w3.org/TR/xsltWorld Wide Web Consortium

13 XSLTv2.0 XSL Transformations

Latest Version Nov 2015

V3.0 https://www.w3.org/TR/xslt20/


14 XSD v1.1XML Schema Definition Language

W3C Recommendation 5 April 2012

https://www.w3.org/TR/xmlschema11-1/ World Wide Web

Consortium

15 EML v7.0Election Markup Language v7.0

EML 7.0 (October 2011) V7.0

http://docs.oasis-open.org/election/eml/v7.0/eml-v7.0.html



16GML Geography Markup

LanguageLatest Version Feb 2012 V3.3

http://www.opengeospatial.org/standards/gml

Open Geospatial Consortium

17 POP3

Post Office Protocol – Version 3/Using TLS with IMAP, POP3, and ACAP

RFC 1939/2595




18 IMAP4

Internet Message Access Protocol – Version 4rev1/Using TLS with IMAP, POP3, and ACAP

RFC 3501/2595




Presentation Encoding Formats

# NameFull Standard Title


URLCustodian

1 BWFSpecification of theBroadcast Wave Format (BWF)

V2May 2011 V2.0https://tech.ebu.ch/docs/tech/tech3285.pdf

European Broadcast Union

2 GIFGraphic Interchange Format

Up-to-datehttp://giflib.sourceforge.net/ Compuserve

3HTML V4.01 (ornewer)

Hypertext Markup Language 4.01 Specification (or newer)

Latest Version May 2001

V5.0

https://www.w3.org/TR/html4/ World Wide Web

Consortium

4 JPEGJoint PhotographicExperts Group ISO/IEC 10918

http://www.iso.org/iso/catalogue_detail.htm?csnumber=18902

Joint Photographic Experts Group

5 MPEG-1

Coding of moving pictures and associated audio for digital storage media at up to about 1.5 Mbit/s

ISO/ IEC 11172:1993


Moving Picture Experts Group/ International Organization for Standardization/ International Electrotechnical Commission

6 MPEG-2

Generic coding of moving pictures and associated audio information

ISO/IEC 13818-1: 2015

http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=67331



7 MPEG-4 Coding of audio-visual objects

ISO/ IEC 14496:1998

http://mpeg.chiariglione.org/


8 MPEG-7Multimedia contentdescription interface

ISO/ IEC 15938:2002



9 MPEG-21 Multimedia framework

ISO/ IEC 21000:2001

http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=40611


10 MXFMaterial Exchange Format

Amendment 1 (2012)

http://www.digitalpreservation.gov/formats/fdd/fdd000013.shtml

Pro-MPEG Forum and SMPTE

11 PDF Portable DocumentFormat

V 1.7ISO 32000-1

V1.7

http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf


12 PDF/A

Document management – Electronic document file format for long-term preservation – Part 1: USE of PDF 1.4 and Part 2: Use of ISO 32000-1

-ISO 19005-2 PDF 1.7 (ISO 32000-1:2008) -2011-ISO 19005-3 PDF 1.7 (ISO 32000-1:2008) –2012

V1.7

http://www.digitalpreservation.gov/formats/fdd/fdd000318.shtml


13 PNGPortable Network Graphics Specification Version 1.0

W3C Recommendation 01 October 1996

V1.0

https://www.w3.org/TR/REC-png-multi.html World Wide Web

Consortium

14 SVG V1.1Scalable Vector Graphics

W3C Recommendation 16 August 2011

https://www.w3.org/TR/SVG/ World Wide Web

Consortium

15 TIFF Tagged Image File Format

Revision 6 V6.0 https://partners.adobe.com/public/developer/en/tiff/TI

Adobe Systems


FF6.pdf

16XHTML v1.0

Extensible Hypertext Markup Language

Latest Version October 2014 V1.1.1

https://www.w3.org/TR/xhtml1/


17 HTML5

Hypertext Markup Language 5: A vocabulary and associated APIs forHTML and XHTML

W3C standard as of October 2014

https://www.w3.org/TR/html5/ World Wide Web

Consortium

18ECMA Script 262

Standard ECMA-262: ECMAScript Language Specification Edition 5.1 (June 2011)

Latest Version June 2015

6thEdition

http://www.ecma-international.org/ecma-262/5.1/ ECMA

International

19 CSS Cascading Style Sheets, level 1

CSS 2.1 (June 2011)CSS 2.2 (being drafted)

V2.1

https://www.w3.org/TR/CSS21/ World Wide Web

Consortium

20 DOM v1.0

Document Object Model Level 2 Style Specification

W3C Recommendation 13 November 2000

https://www.w3.org/TR/DOM-Level-2-Style/ World Wide Web

Consortium

21 OGG VORBIS

Audio format specification and software implementation forlossy audio compression

Updated March 2015

V1.3.5

http://www.vorbis.com/

Xiph.org Foundation

22OGG THEORA

Lossy video compression format

Updated October 2009 V1.1.1

https://www.theora.org/ Xiph.org Foundation

Document Format



URLCustodian

1 .rtf Rich Text Format Up-to-date V1.9.1 Microsoft

2 OOXML Information technology – Document description and processing languages – OfficeOpen XML File Formats – Part 1: Fundamentals and Markup Language

ISO/ IEC 29500-1: 2012




Reference

3ODF v1.1and v1.2

Open Document Format for Office Applications (OpenDocument)

ODF v1.1 and v1.2

V1.1 &V1.2

https://www.oasis-open.org/committees/office/


4

ECMA-262/ JavaScript

Language used forclient-side scripting on the web

Updated June 2015

6thEdition

http://www.ecma-international.org/publications/standards/Ecma-262.htm

ECMA International

5 ZIP

Archive file format that supports lossless data compression

Updated October 2014

V6.3.4

https://support.pkware.com/display/PKZIP/APPNOTE PKWARE

6 GNU gzip

Software application for file compression and decompression

RFC 1952

https://tools.ietf.org/html/rfc1952 GNU GPLv3

7 GNU tar Create tar archives Updated July 2014

V1.28 https://www.gnu.org/software/tar/

GNU

Metadata for Process and Data Description


Latest VersionVersionNumber

URL

Custodian

1 BPEL4WS

Business Process Execution Language for Web Services

V1.1 V1.1

http://www.daml.org/services/swsl/materials/bpel11.pdf

IBM, Microsoft et.al Industry Consortium

2WSBPEL v2.0

Web Services Business Process Execution Language v2.0 TC

Up-to-date V2.0

https://www.oasis-open.org/committees/wsbpel/


3ER Diagrams

Entity-RelationshipDiagrams Up-to-date

http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.123.1085

4 ISO/ IEC 11179

Information technology – Metadata registries– Part 1: Framework

revised by ISO/ IEC 11179-1: 2015

ISO/ IEC11179-1:

2015




5 XML Schema

XML Schema

- Latest Version April 2012:* W3C XML Schema Definition Language (XSD)1.1 Part 1: Structures * W3C XML Schema Definition Language (XSD)1.1 Part 2: Datatypes

V1.1

https://www.w3.org/standards/xml/schema


6 UML

Information technology – OpenDistributed Processing -- Unified Modelling Language (UML) Version 1.4.2

Latest Version: June 2015 v2.x

http://www.uml.org/ International Organization for Standardization/ International Electrotechnical Commission

7 DFD Data Flow Diagram

Naming

# Name Full StandardTitle


URL Custodian

1 URIUniform Resource Identifier: Generic Syntax



2 URL Uniform Resource Locators (URL)

RFC 4248, 4266




Sectoral Standards



URLCustodian

1 CAP

Common Alerting Protocol - Electronic data exchange in disaster risk sector

Latest Version: July 2010

https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html OASIS

2 GTFS

General Transit Feed Specification - Electronic data exchange in transportation sector

Latest Version: February 3, 2016

https://developers.google.com/transit/gtfs/reference

Google Developers


3 UACS

Unified Accounts Code Structure - Released by PFM Committee of DBM/ DOF/ COA

Latest Version: November 7, 2014

http://www.uacs.gov.ph/resources/issuances/95/unified-accounts-code-structure-uacs

Unified Accounts Code Structure

4 HL7

Provide a framework (and related standards) for the exchange, integration, sharing, and retrieval of electronic health information

Latest Version 2015 V3.0

http://www.hl7.org/

HL7

5 LOINC

Logical Observation Identifiers, Numbers and Codes

Latest Version December 2015 V2.54

loinc.org Logical Observation Identifiers, Numbers and Codes

6 DICOM

Standard for handling, storing, printing, and transmitting information in medical imaging.

Base Standard –2016b

http://dicom.nema.org/

7 PSGCPhilippine Standard Geographic Code

Latest Version April 2016

http://nap.psa.gov.ph/activestats/psgc/


PeGIF Members

Chair: Denis F. VillorenteCo-Chair: Vladimir Dennis B. Reyes, PhD

Usec. Richard Moya Reynaldo Joseph Callao Jonathan F. Cuevas Dr. Alvin B. Marcelo William Emmanuel S. Yu, PhD


Documents

DICT Building, C.P. Garcia Avenue, Diliman, Quezon City ...i.gov.ph/wp-content/uploads/2016/09/PeGIF_Framework_PeGIF_1.1... · Preface Interoperability is a key in realizing our goals