2 How to read the standards

Each table includes protocols, standards and conventions (defacto standards), with version numbers where applicable, a status, review cycle, and comments. Note that in computing, protocols are generally used to define real-time communications behaviour, while standards are used to govern the structure of information committed to long-term storage.

This section explains how to read the tables.

2.1 Layer model

Layer models are widely used to classify functions within IT systems. The intent is to simplify systems by segregating system functions into levels and disentangling the complexity and variations of each level. Components normally communicate only with others at neighbouring levels, and in standardised ways.

The model for this version of the e-GIF is illustrated and described below.

Figure 1: e-GIF v3 Layer Model

The four basic structural components (layers) of this model are:

• Network - Covers details of data transport such as network protocols. This is a crucial area for interoperability. Without agreement on networking standards, it is hard or impossible to make systems communicate. The e-GIF uses a subset of the widely proven Internet Protocol suite.
• Data Integration - Facilitates interoperable data exchange and processing. Its standards allow data exchange between disparate systems and data analysis on receiving systems.
• Business Services - Supports data exchange in particular business applications and information contexts. Some of the standards in this layer are generic, covering multiple business-information contexts; others work with data-integration standards to define the meaning of the data, mapping it to usable business information. For example, an agency will format a stream of name-and-address data in XML (Data Integration) using the business rules of xNAL (Business Services) to create a commonly agreed representation of name-and-address information.
• Access and Presentation - Covers how users access and present business systems. Most of the standards in this layer are in the Government Web Guidelines.

Applying to all of the structural layers are:

• Security - Crosses all layers, to reflect the fact it needs to be designed into a system, not added as a layer on top. The e-GIF contains standards at the various levels designed to offer different levels of security as appropriate. It also refers to a series of standards and policy statements (the NZSITs) which provide advice and direction on the levels required.
• Best Practice - New category to help readers of the e-GIF distinguish published standards from Best Practice, Codes of Practice, and other general or sector-focussed guidance. Published standards alone do not ensure interoperability - they merely offer a common approach to managing and understanding the context of the information exchange.
• E-government Services - These are actual implementations of IT infrastructure made available by the ICT Branch for use by public-sector agencies. (See Part I, Section 4, E-government services)
• Web Services - An emerging set of standardised applications to connect and integrate web-based applications over the Internet. Web Services connect services together. Using Best Practice implementations, agencies can agree a common approach to interoperable service delivery to customers.

Underpinning all layers are:

• Management - See Part II, Managing the e-GIF.
• Governance - See Part II, Managing the e-GIF and Part II, Governance Principles. An e-GIF Governance overview paper is also available from the SSC ICT Branch. Please email e-GIF@ssc.govt.nz for access to this document.

2.2 Compliance status levels

The status level of an e-GIF standard indicates its maturity relative to other standards. In 2004, the e-GIF Management Committee agreed revised status levels for e-GIF standards. The Committee renamed Mandatory and Recommended levels and extended them to include: Adopted, Recommended, Under Development, and Future Consideration. The revised statuses broadly align with the levels used in the UK e-GIF [The criteria for status levels have been adapted from the UK e-GIF Interoperability Working Group draft paper "Criteria for TSC standards V1.doc".] . The requirement for an additional category, Deprecated, became self evident in 2005.

The e-GIF does not require a standard to pass through each successive stage of development. When the Committee publishes an e-GIF standard, they give it an appropriate status. When the standard matures, the Committee can consider recommendations to alter its status.

2.3 Current e-GIF compliance statuses

The current e-GIF standard compliance status levels are illustrated and described below.

Figure 2: e-GIF Compliance Status Levels

The compliance statuses in this version of the e-GIF are:

• Future Consideration (F): - not yet reviewed, customised, nor having any successful, documented implementation in the New Zealand government; yet probably necessary for public-sector IT systems. Included mainly to introduce to IT developers. F-level standards are:
  • possibly required for interoperability of IT systems in the public sector;
  • open or demonstrating the intention of being open once published;
  • not overruled by an existing international standard; and
  • not clashing with or rival to a standard already listed.
• Under Development (U): - actively under assessment by more than one government agency; for example, having an active working group, a proof of concept, or a pilot implementation with associated documentation. Active or starting within three months of publication. U-level standards are:
  • required for interoperability of IT systems in the public sector;
  • open or demonstrating the intention of being open once published;
  • not overruled by an existing international standard;
  • not clashing with or rival to a standard already listed; and
  • published or very soon to be published.
• Recommended (R): - emerging from the development, review, or working-group process with implementation documentation and evidence of successful interoperability and data exchange. Recommended standards are generally more recent, founded upon newer technologies or standards. R-level standards are:
  • required for interoperability of IT systems in the public sector;
  • open;
  • scalable;
  • not overruled by an existing international standard;
  • not clashing with or rival to a standard already listed;
  • complete and published; and
  • showing clear indication of market support.
• Adopted (A) - mandatory; normally upgraded from Recommended status (only in exceptional circumstances can a standard enter the e-GIF as Adopted without first completing a successful period as Recommended). A-level standards are:
  • meeting or surpassing all criteria from the previous status levels;
  • well established in public-sector ICT systems;
  • having complete supporting documentation and processes for implementation; and
  • proven effective for interoperability.

Note: The main difference between Recommended and Adopted is the maturity, which can be equated with well-understood software version models.

• A standard that is Adopted has widespread use and industry acceptance. It is the default standard in use, and is not expected to become Deprecated within twelve months. There is no immediate onus on existing interoperability agreements to migrate to the newer Recommended standard.
• Where a standard is Recommended, there is growing industry adoption. New interoperability initiatives are more likely to use this standard.

• Deprecated (D) - a standard or practice that has been abandoned for or superseded by a better solution in the Adopted or Recommended levels. Agencies should plan to migrate away from solutions assigned with this designation as soon as practical. New use of this standard is discouraged.

2.4 Choosing between standards - agency considerations

Given the need to maintain the e-GIF, to keep pace with changing technology, multiple standards may be available for an particular application. Agencies collaborating on interoperability projects may need to either agree one standard or use mapping technologies to achieve interoperability.

When choosing a standard:

• first consult with agencies whose functions and services relate to your own (your likely interoperability partners);
• then together agree a standard, considering the compliant statuses:
  • Use R (recommended) standards if you can; they are generally newer and less subject to obsolescence than A standards.
  • If you cannot or do not wish to use R, use A if you can (an A standard is the default; but if an R standard also exists, you are encouraged to use it).
  • If you cannot use R or A standards, use any applicable F or U standards and notify the SSC ICT Branch for Working Grouping information and to document your implementation as part of the standards-development process.
  • If no current standards apply, or you wish to propose a new standard, first please contact the ICT Branch for Working Group information.
  • Avoid new use of D.

Note that there may be circumstances where agencies agree to use a more mature standard (e.g., A) over one that is likely to have a longer life cycle (e.g., R). They may also accept the risk of a newer standard (e.g., F or U) instead, with the understanding that that they will be participating in its development.

2.5 Links

Standards included in the e-GIF that are blue and underlined have links to an RFC or other resources on the Internet, which more fully explain them. If you are using a hard-copy version of this document, see Part III, URLs Referenced In This Document.

2.6 Comments

The comments column provides additional information on the background, circumstances of use, or anecdotal feedback that may help agencies in their decision to use or implement the applicable standard.

2.7 Changes from previous version

The following elements of the standards tables are new to e-GIF version 3.0:

• Statuses - version 2.1 standards were either Mandatory or Recommended; this version uses the scheme described above.
• Columns - tables now include columns for Status, and Comments.
• Web Services Section - standards specifically related to Web Services implementation that do not strictly fit into the layer model.
• Best Practice Section - standards that do not strictly fit into the layer model but rather apply in a particular context only.
• Added, moved, removed, revised standards - see the Change Log in Part III.. Note that there are a number of new standards in version 3.0 of the e-GIF; many of were deemed necessary to implement existing e-GIF standards.