1 How to read the standards

The e-GIF standards [In the e-GIF, protocols and standards are both referred to as "standards". Note that protocols are sometimes distinguished as a specific type of standard — seehttp://en.wikipedia.org/wiki/Protocol_%28computing%29 and http://en.wikipedia.org/wiki/Communications_protocol.] are categorised using a "layer model".

Each protocol, standard or convention (de facto standard) is listed with a version number, where applicable, a status level and any relevant 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 list of standards.

1.1 Layer model

Layer models are widely used to classify functions within IT systems. They are used 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, or 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

• Security: Crosses all layers, to reflect the fact that security 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: This is a 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 which the ICT Branch of the State Services Commission makes available for public sector agencies to use. (See Section 3E-government Services).
• Web Services: Web Services connect services together. They are an emerging set of standardised applications to connect and integrate web-based applications over the Internet. Using Best Practice implementations, agencies can agree a common approach to interoperable service delivery to customers.

Underpinning all these layers are:

• Management: See Part 2, Section 1.4 Managing the e-GIF.
  
• Governance: See Part 2, Section 1.4 Managing the e-GIF and Section 3.4 Governance Principles. An e-GIF Governance Overview paper is also available from the ICT Branch of the State Services Commission. Please email e-GIF@ssc.govt.nz.

1.2 Compliance status levels

The status level of an e-GIF standard shows 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 the following levels: Adopted, Recommended, Under Development, and Future Consideration. The revised status levels broadly align with those 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 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, it gives it an appropriate status. When the standard matures, the Committee can consider recommendations to change its status.

1.3 Current e-GIF compliance status levels

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

Figure 2: e-GIF Compliance Status Levels

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

• Future Consideration (F): Not yet reviewed, customised, or having any successful, documented implementation in the New Zealand government; yet probably necessary for public sector IT systems. Included mainly to introduce these standards 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
  • not clashing with or rival to a standard already listed.
  
  
• Under Development (U): Actively under assessment by more than one government agency, e.g. 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
  • 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:
• • open
  • scaleable
  • not overruled by an existing international standard
  • not clashing with or rival to a standard already listed
  • complete and published
  • showing clear indication of market support
  • likely to be required for interoperability of IT systems in the public sector.
  
  
• Adopted (A): Mandatory and 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:
• • required for interoperability of IT systems in the public sector
  • 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
  • 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.

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

1.4 Choosing between standards

Given the need to maintain the e-GIF so that it keeps pace with changing technology, multiple standards may be available for a 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 agencies whose functions and services relate to your own (your likely interoperability partners)
• then, together, agree a standard, considering the compliant status levels:
• • Use Recommended (R) standards if you can; they are generally newer and less subject to obsolescence than other standards.
  • If you cannot use R, then use an Adopted (A) standard. An A standard is the default; but an R standard is preferable if it exists.
  • If you cannot use R or A standards, use any applicable Future Consideration (F) or Under Development (U) standards. Notify the ICT Branch of the State Services Commission for Working Group 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 Deprecated (D) standards.

Note 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 they will be taking part in its development.

1.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 explain them more fully. If you are using a hard copy version of this document, see Part 3, Section 2 URLs referred to in the e-GIF.

1.6 Comments

The comments in the list of standards provide 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.

1.7 Changes from previous version

The following elements in the list of standards are new to e-GIF v3.0:

• Status levels: Version 2.1 standards were either Mandatory or Recommended; this version uses the scheme described in Section 1.3.
• Standards listing: The list of standards now notes the status level of each standard and includes relevant comments.
• Web Services section: Includes standards specifically related to web services implementation that do not strictly fit into the layer model.
• Best Practice section: Includes standards that do not strictly fit into the layer model but rather apply only in a particular context.
• Added, moved, removed, revised standards: See Part 3, Section 1.4 Change Log. Note there are a number of new standards in the e-GIF v3.0; many of these were considered necessary to implement existing e-GIF standards.