Skip to content.
|Networking government in New Zealand.
You are here: Home » Standards » Interoperability (e-GIF) » cvl-discussion-200408 » Purpose and Context

Purpose and Context

2 Purpose and context of this proposal

2.1 Purpose

The purpose of this document is to provide a backdrop for an initiative to advance a common strategy for CVL management by XML programmers in public and private sectors throughout the New Zealand Government agencies. The document will:

  • outline the problems associated with not having a common strategy,
  • provide background to further debate, study, and inputs to a Working Group and Terms of Reference,
  • propose a Working Group format to begin looking into the issue.

This proposal aims to give sufficient background and justification for the e-Government Interoperatiblity Framework (e-GIF) Custodian to seek public consultation and, through the formation of a Working Group, to report progress to the e-GIF Management Committee.

The ultimate aim is to have a consensus strategy for pan-agency XML-schema CVL-management, wrapped up in a best-practice document associated with the e-GIF.

2.1.1 What is the e-GIF?

The e-Government Interoperability Framework (e-GIF) is a document containing a set of policies, standards, guidelines, and a governance approach to technical components and data—and ways of linking them. Its purpose is to define the way in which integrated electronic services for e-government in New Zealand will be delivered. All people and organisations that make use of the e-government facilities of the New Zealand Government will use this platform.

2.2 Target audience

Given that this proposal, if ratified, may ultimately be published in full or in part, the intended audience is aimed at Information Technology (IT) strategists, data administrators, and solution architects whose remit involves complying with e-GIF.

This document discusses a technical subject, assuming some understanding of information architecture and schema development.

2.3 Scope

The scope of this document does not cover:

  • guidelines for programmers defining terms for schema coding,
  • a deep analysis of the alternative options for managing CVLs (although they are noted as a basis for discussion and later study by the Working Group).

2.4 Definitions

See Appendix A, Glossaries.


[ Previous | Next ]