2 e-GIF standards
This section sets out the current and emerging standards required for e-GIF compliance and to facilitate interoperability.
- See Part 3, Section 3 Abbreviations for definitions of abbreviations and acronyms used in this section.
- See Part 3, Section 1.4 Change Log for a list of standards that are new, moved, removed, or changed in this version.
- Links in the list of standards to online resources, usually the standards themselves, explain more fully what each standard covers; see also Part 3, Section 2 URLs referred to in the e-GIF.
- Note that multiple standards may exist in any category; see Section 1.4 Choosing between standards.
2.1 Network layer
This section covers details of data transport, such as network protocols, which 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.
2.1.1 Network protocols
IP v4 Internet Protocol Version 4
Status Adopted
Comments Plan for migration to IP v6. New hardware should support IP v4 as well as IP v6.
IP v6 Internet Protocol Version 6
Status Recommended
Comments When implementing IP v6, configure routers to "ghost" IP v4.
2.1.2 Directory protocols
LDAP v3 Lightweight Directory Access Protocol Version 3
Status Recommended
Comments For access to directory services.
2.1.3 File transfer protocols
FTP File Transfer Protocol
Status Adopted for file transfers, where security is not required.
Secure File Transfer Protocols
Please note that secure file transfer protocols (such as Secure Copy and SSH File Transfer Protocol) are under review. Agencies considering products are advised to contact the ICT Branch.
Comments Use restart and recovery. Also FTP security extensions and FTP via Port 80 where applicable.
HTTP v1.1 HyperText Transfer Protocol Version 1.1
Satus Adopted
Comments Application level protocol. See Security layer for secure HTTP (HTTPS) and TLS usage.
WebDAV World Wide Web Distributed Authoring and Versioning
Status Future Consideration
Comments A set of extensions to HTTP v1.1 that allows users to collaboratively edit and manage files remotely but avoids access problems with NAT firewalls.
SCP Session Control Protocol
Status Future Consideration
Comments SCP is a simple protocol which lets a server and client have multiple conversations over a single TCP connection. The protocol is designed to be simple to implement, and is modelled after TCP.
2.1.4 Mail transfer protocols
SMTP Simple Mail Transfer Protocol
Status Adopted
Comments Host-to-host protocol. Beware of spoofing of email addresses. SMTP-TLS is used to protect mail headers.
2.1.5 Registry services
DNS Domain Name Server
Status Adopted
Comments Use DNS for Internet/Intranet domain to IP address resolution. DNS Security is critical. Omission from previous version.
LDAP v3 Lightweight Directory Access Protocol Version 3
Status Future Consideration
Comments Increasingly used for internal user authentication, and certificate registries. Not recommended for cross-domain purposes.
2.1.6 Time protocols
NTP v4 Network Time Protocol Version 4
Status Under Development
Comments De facto standard proposed for use in an all-of-government time standard. Best practice guidelines are being developed.
UTC (MSL) Universal Time Clock (Measurement Standards Laboratory)
Status Future Consideration
Comments De facto standard (accessed from Industrial Research Limited, MSL); proposed for use in an all-of-government time standard. Best practice guidelines are being developed.
2.1.7 Messaging transport
HTTP v1.1 HyperText Transfer Protocol Version 1.1
Status Adopted
Comments See File transfer and Security layer.
2.1.8 Messaging formats
MIME Multi-Purpose Internet Mail Extension
Status Adopted
Comments See also S/MIME and Security layer for secure mail attachments. Do not use Transport Neutral Encapsulation Formats (TNEF) for headers.
2.2 Data Integration layer
The Data Integration layer outlines standards in the realm of data exchange and processes.
2.2.1 Primary character set
ASCII American Standard Code for Information Interchange
Status Adopted
Comments Minimum set of characters for data interchange. Omission from previous version.
Status Deprecated
UTF-8 UCS Transformation Format (8-bit encoding)
Status Adopted
Comments UTF-8 is a variable length character encoding for Unicode. It can represent any character in the Unicode character set, yet is backwards compatible with ASCII.
2.2.2 Structured web document language
HTML v4.01 HyperText Markup Language Version 4.01
Status Adopted
Comments For web content. See New Zealand Web Standards and Recommendations v3.0
2.2.3 Schema definition languages
XML v1.0 Extensible Markup Language Version 1.0
Status Adopted
Comments Meta-language to create tags to define, transit, validate, and interpret data.
2.2.4 Document type definition
DTD Document Type Definition
Status Adopted
Comments Describes multiple elements and attributes for XML; see W3School's DTD Tutorial.
2.2.5 Structured data
XML v1.0 Extensible Markup Language Version 1.0
Status Adopted
Comments Preferred option for structured data transport.
2.2.6 Batch/bulk data
XML Extensible Markup Language Version
Status Adopted
Comments XML 1.0 is preferred for structured data transport. Parties must agree file header records before exchange.
CSV Comma-Separated Values
Status Deprecated
Comments Certain implementations of XML may fail in bulk/batch mode; in which case agencies may use deprecated standard of CSV. Parties must agree file header records before exchange. Omission from previous version.
2.2.7 File compression
ZIP v2.3 ZIP Version 2.3
Status Adopted
Comments Other products using the compression algorithm LZH are also acceptable, subject to the agreement of the exchanging parties.
GZIP GNU Zip
Status Adopted
Comments Not compatible with ZIP. Omission from previous version.
2.2.8 File archiving
TAR Tape Archiver
Status Adopted
Comments Omission from previous version.
2.3 Business Services layer
Business Services describe the services and data from a business point of view, i.e. mapping the technical components to useful business information.
2.3.1 Metadata (Discovery)
NZGLS v2.0 New Zealand Government Locator Service Version 2.0
Status Adopted
NZGLS Thesauri New Zealand Government Locator Service Thesauri
Status Adopted
RDF Resource Description Framework
Status Adopted
Comments An XML file format to describe metadata. RDF is used by RSS1.0 (see below).
2.3.2 Namespace
W3C schema definitions World Wide Web Consortium Schema Definitions
Status Adopted
Comments Use when other schemas customised for use by government agencies are not specifically identified (e.g. NZGMS, xNAL (nz), NZGLS).
OIDS Schema Object Identifiers
Status Recommended
Comments The ICT Branch of the State Services Commission maintains 2.16.544.101 as the Government OID Arc.
URN Uniform Resource Name
Status Under Development
Comments A way of unambiguously defining each element type and attribute name in an XML document. Working Group led by ICT Branch of the State Services Commission. See also RFC 4350.
2.3.3 Schemas
W3C schema definitions World Wide Web Consortium Schema Definitions
Status Adopted
Comments Use when other schemas customised for use by government agencies are not specifically identified (e.g. NZGMS, xNAL (nz), NZGLS).
2.3.4 Structured data description
XML v1.1 Extensible Markup Language Version 1.1
Status Adopted
Comments Erratum in previous version. (Note: "Structured data" refers to XML Schema v1.0.)
2.3.5 Name and address
xNAL v2 Extensible Name and Address Language Version 2
Status Adopted
Comments xNAL (OASIS) v3 being drafted; will be incorporated into e-GIF following a successful pilot.
Note: In 2006, NZ Post issued new requirements for addressing bulk mail.
xNAL (nz) schema Extensible Name and Address Language (New Zealand)
Status Recommended
Comments Agency User Group led by ICT Branch of the State Services Commission; xNAL (nz) will ultimately be replaced by xNAL (OASIS) v3.
2.3.6 Additional customer information
Data formats for identity records standard
Status Under Development
Comments The All-of-government Authentication project used schema fragments from xCIL to develop the Identity Records standard. This specifies data formats for a range of customer-information data elements that government agencies may use in customer identity records.
xCIL Extensible Customer Information Language
Status Future Consideration
Comments The superset of xNAL specifying formats for customer information elements such as phone and fax number, email address, date of birth, gender, etc. xCIL is already under consideration by several agencies and is being piloted in the web-based Change-of-Address Notification project.
2.3.7 Customer relationship
xCRL Extensible Customer Relationships Language
Status Deprecated
Comments Part of the xCIL and xNAL family of standards specifying formats for relationships between customers.
CIQ Customer Information Quality
Status Future Consideration
Comments XML Specifications for defining and managing Customer (also called "Party") information/profile (including customer/party relationships).
2.3.8 E-learning
ADL, SCORM , and IMS Advanced Distributed Learning, Shareable Content Object Reference Model, and Instructional Management System
Status Future Consideration
Comments Now under the auspices of the Education Sector ICT Connectivity sub-committee.
2.3.9 Business reporting
xBRL Extensible Business Reporting Language
Status Under Development
Comments Working Group underway, led by Inland Revenue.
2.3.10 Directory services
DSML Directory Services Markup Language
2.3.11 Statistical data and metadata
SDMX Statistical Data and Metadata Exchange
Status Future Consideration
Comments Statistics New Zealand leads this standard.
2.3.12 Geospatial
GML Geography Markup Language
Status Adopted
Comments Land Information New Zealand leads this standard.
WFS Web Feature Server
Status Adopted
Comments Land Information New Zealand leads this standard.
WMS Web Map Server
Status Adopted
Comments Land Information New Zealand leads this standard.
ESA Emergency Services in Government Administration
Status Recommended
Comments Land Information New Zealand leads this standard.
NZGMS New Zealand Geospatial Metadata Standard
Status Recommended
Comments Schema for identifying geospatial metadata. Land Information New Zealand leads this standard.
2.3.13 Registry services
ebXML RIM and RS v2.1 E-business Extensible Markup Language, Registry Information Model, and Registry Services Version 2.1
Status Adopted
Comments Open standard application for Registry Information and Records Services in an e-business context, as an alternative to Web Services.
ebXML RIM and RS v3.0 E-business Extensible Markup Language, Registry Information Model, and Registry Services Version 3.0
Status Future Consideration
Comments Open standard application for Registry Information and Records Services in an e-business context, as an alternative to Web Services.
2.3.14 Content syndication and channel feeds
RSS 1.0 RDF Site Summary
Status Recommended
Comments Note that this standard is required for agencies using the government portal news service, E-government Shared Services.
RSS 2.0 Really Simple Syndication
Status Future Consideration
Comments An alternative to RSS 1.0 that also enjoys wide support from the community.
2.3.15 Instant messaging
XMPP Extensible Messaging and Presence Protocol
Status Future Consideration
Comments XML protocol for real-time messaging. Taken from UK Technical Standards Catalogue Version 6.2.
2.3.16 Voice Over Internet Protocol (VOIP)
SIP Session Initiation Protocol
Status Future Consideration
Comments A protocol for initiating, modifying, and terminating an interactive user session that involves multimedia elements such as video, voice and instant messaging. Has greater take-up than H.323. Taken from UK Technical Standards Catalogue Version 6.2. Codec required.
RTP Real-time Transport Protocol
Status Future Consideration
Comments Defines a standardised packet format for delivering audio and video over the Internet and is frequently used in conjunction with RTSP, H.323 or SIP.
H.323 v2 H.323 Version 2
Status Future Consideration
Comments An umbrella recommendation from the ITU-T, which defines the protocols to provide audiovisual communication sessions on any packet network. Taken from UK Technical Standards Catalogue Version 6.2. Codec required.
Status Future Consideration
Comments An ITU-T standard for audio companding; primarily used in telephony.
Status Future Consideration
Comments An audio codec for voice that compresses voice audio in chunks of 10 milliseconds; is mostly used in VOIP applications for its low bandwidth requirement.
2.3.17 Digitisation
Archives Digitisation Standard
Status Under Development
Comments Archives New Zealand standard. Sets out the requirements for digitisation and disposal of paper or other analogue original source documents, and outlines best practice recommendations for digitisation processes.
2.4 Access and Presentation layer
This section presents standards and guidelines covering how business systems are presented and accessed by users.
2.4.1 Web site presentation
New Zealand Government Web Standards and Recommendations v3.0
Status Recommended
Comments See Web Standards and Recommendation for use of: HTML 4.01, XHTML, GIF 89a, JPG, PNG, SVG, and PDF. Proposed change to Adopted status in 2006.
2.4.2 Web design and maintenance
New Zealand Government Web Standards and Recommendations v3.0
Status Recommended
Comments See Web Standards and Recommendations for use of: HTML 4.01, XHTML, GIF 89a, JPG, PNG, SVG, and PDF. Proposed change to Adopted status in 2006.
2.4.3 Forms
Agencies considering products are advised to contact the Web Guidelines team at the ICT Branch.
2.4.4 Authentication standards
Note: Agencies wishing to implement any new systems where authentication of individuals or businesses is necessary must contact the ICT Branch of the State Services Commission for advice.
Guide to Authentication Standards for Online Services
Status Under Development
Comments An entry point and navigational tool for the suite of NZ e-GIF authentication standards
Status Under Development
Comments Specifies a business process for establishing the identity of government agency customers.
Authentication Key Strengths Standard
Status Under Development
Comments Specifies the requirements for the authentication keys and protections for the online authentication exchange.
Data Formats for Identity Records Standard
Status Under Development
Comments Specifies a set of identity-related data elements
that are presented in an agreed format, to provide a common approach
for agencies to systemise their identity management processes for users
of their services. The elements focus on who you are
(identity) rather than what you own/your role (attributes
of identity) or what you can do (authorisation).
Status Under Development
Comments Specifies the password requirements for online
services in the Low
Risk Category
Security Assertion Messaging Standard (NZSAMS)
Status Under Development
Comments Specifies a deployment profile of OASIS SAML v2.0 to communicate security assertions.
2.5 Web Services layer
Web Services is an emerging set of standardised applications to connect and integrate web-based applications over the Internet. The e-GIF identifies them separately, as they span multiple parts of the layer model. It is critical that agencies using web services agree on the implementation and semantics of data. The emergence of the WS-I Basic Profile 1.1 offers a starting point for a consensus on implementing web services across government.
The following standards apply where systems use web services architecture.
2.5.1 Discovery
UDDI v3 Universal Description, Discovery and Integration Version 3
Status Adopted
Comments An open standard for describing, publishing, and discovering network-based software components.
2.5.2 Description
WSDL v1.1 Web Services Description Language Version 1.1
Status Adopted
Comments Specifies the location of the service and the operations, or methods, the service exposes.
WSDL v2.0 Web Services Description Language Version 2.0
2.5.3 Access
SOAP v1.1 Simple Object Access Protocol Version 1.1
Status Adopted
Comments For Web Services Transport. E-GIF v3.0 recommends SOAP v1.2, but adopts SOAP v1.1 because of feedback from agencies that this is the version currently supported in many common development products.
SOAP v1.2 Simple Object Access Protocol Version 1.2
Status Recommended
Comments Previous versions of the e-GIF adopted SOAP v1.2. E-GIF v3.0 recommends SOAP v1.2, but adopts SOAP v1.1 because of feedback from agencies that this is the version currently supported in many common development products.
2.5.4 Messaging
ebXML MSG E-Business Extensible Markup Language Messaging Services
Status Future Consideration
Comments Also known as ebMS.
WSRM Web Services Reliable Messaging
Status Future Consideration
Comments WS-Reliability 1.1 provides a standard, interoperable way to guarantee message delivery to applications or Web services
AS2 Applicability Statement 2
Status Future Consideration
Comments A lightweight, open messaging transport for B2B messaging services. Comparable with ebXML MSG/ebMS.
2.5.5 Security
WSS Web Services Security
Status Recommended
Comments A technical foundation for implementing security
functions such
as integrity and confidentiality in messages implementing higher-level
Web services applications
WS-Securitypolicy Web Services Security Policy Language
Status Future Consideration
Comments This specification indicates the policy assertions
that apply
to Web Services Security: SOAP Message Security, WS-Trust, and
WS-SecureConversation.
WS-Trust Web Services Trust Language
Status Future Consideration
Comments Uses the secure messaging mechanisms of WS-Security to define additional primitives and extensions for security token exchange to enable the issuance and dissemination of credentials within different trust domains.
WS-Secon Web Services Secure Conversation Language
Status Future Consideration
Comments The Web Services Secure Conversation Language (WS-SecureConversation) is built on top of the WS-Security and WS-Policy models to provide secure communication between services.
SAML v1.1 Security Assertion Markup Language Version 1.0
Status Recommended
Comments Secure messaging and security token framework. See Access and Presentation layer. OpenSAML is an implementation of SAML.
SAML v2.0 Security Assertion Markup Language Version 2.0
Status Future Consideration
Comments Secure messaging and security token framework. A subset of SAML 1.1, elements are Under Development as part of the All-of-government Authentication project. See Access and Presentation layer. OpenSAML is an implementation of SAML.
xACML v2.0 Extensible Access Control Markup Language Version 2.0
Status Future Consideration
Comments XML Schema for creating policies and automating their use to control access to disparate devices and applications on a network.
Liberty ID-FF v2.0 Liberty Alliance ID-WSF 2.0
Status Future Consideration
Comments For consideration where app-to-app federated identity required and SAML V2.0 profiles not sufficient.
2.5.6 Compliance
WS-I Basic Profile v1.1 Web Services - Interoperability Organisation Basic Profile Version 1.1.
Status Future Consideration
Comments Profiles provide implementation guidelines for how related web services specifications should be used together for best interoperability. To date, WS-I has finalised the Basic Profile, Attachments Profile and Simple SOAP Binding Profile.
WSS-I Basic Profile v1.0 Web Services Security - Interoperability Organisation Basic Profile Version 1.0.
Status Future Consideration
Comments Draft 1.0 Basic Security Profile accepted by OASIS.
2.6 Security layer
Security is shown in the e-GIF as spanning all layers to reflect the fact that security needs to be designed into a system, not added as a layer on top. Security can be viewed in four main contexts:
- Confidentiality: Ensuring information is accessible only to those authorised to have access.
- Integrity [Note: "Integrity" here does not refer to "data integrity", which is beyond the scope of the e-GIF. These standards are responsible for the integrity of the transport but not necessarily the integrity of the data.] : Ensuring information has not been changed or altered without knowledge of this happening.
- Availability: Ensuring authorised users have access to information and associated assets when required.
- Accountability: A system's ability to keep track of who or what has accessed data, conducted transactions, or made changes to the system [Sourced from ISO17799: IT - Code of Practice for Information Security Management.] .
Agencies are encouraged to consider the security implications of interoperability projects using these contexts, and apply the appropriate policies and standards. The following list contains standards designed to offer different levels of security in the layers; the standards and policy statements in the NZSITs provide advice and direction on what levels may be required.
Contact the GCSB where one or more of the systems exchanging information is likely to be carrying classified information (RESTRICTED or greater).
2.6.1 Policy
GCSB NZSITs Government Communications Security Bureau New Zealand Security of Information Technology Publications
Status Adopted
Comments Refer to the GCSB for advice on hashing, key transport, signing and cryptographic algorithms, as described in the current versions of NZSIT 400.
SIGS Security in the Government Sector
Status Adopted
Comments A manual of policies, principles and procedures mandated by Cabinet in 2001, developed using AS/NZS ISO/IEC 17799:2001 - "Code of practice for information security management".
Page 8-20, paragraph 10 of SIGS requires use of an IS framework following AS/NZS ISO/IEC 17799:2001 for all systems processing classified, including IN-CONFIDENCE, information or hosting government services.
Agencies should decide how much protection is required using the principles of general risk analysis and risk management found in AS/NZS 4360:1999 - "Risk Management".
2.6.2 Network
HTTPS HyperText Transfer Protocol running over SSL
Status Adopted
Comments See SSL v3 below. Omission from previous version.
SSL v3 .0 Secure Sockets Layer Version 3
Status Adopted
Comments Use for encrypted transmission of any data quantity between web browser and web server over TCP/IP.
Used for HTTPS (HTTP in an SSL/TLS stream) to open a secure session on Port 443.
May also be used for secure TCP transport (e.g. VPN)
Note: TLS v1.0 is SSL v3.1
IPsec Internet Protocol Security
Status Adopted
Comments Authentication header standard taken from NZSIT/SIGS. Omission from previous version.
ESP IP Encapsulation Security Protocol for VPN
Status Adopted
Comments Requirements taken from NZSIT/SIGS. Omission from previous version.
S-HTTP Secure HyperText Transfer Protocol
Status Future Consideration
Comments For individual messages, created by SSL running under HTTP.
TLS v1.0 Transport Layer Security
Status Future Consideration
Comments RFC 2616 upgrade mechanism in HTTP 1.1; initiate Transport Layer Security over an existing TCP connection. Does not yet interoperate with SSL v3.
2.6.3 Data integration
XML - Enc XML-Encryption syntax and processing
Status Future Consideration
Comments Taken from UK Technical Standards Catalogue Version 6.2.
Status Future Consideration
Comments XML-Digital signature - syntax and processing as
defined by W3C, used in SAML implementations. OASIS Digital Signature
Services - developing an alternative implementation.
SAML v2.0 Security Assertion Markup Language Version 2.0
Status Future Consideration
Comments A subset of SAML v1.1, elements are Under Development as part of the All-of-government Authentication project. See Access and Presentation layer.
Security Assertion Messaging standard
Status Under Development
Comments All-of-government Authentication project standard Under Development. Expected to specify four specific messages from SAML for communicating authentication assertions.
2.6.5 Business services
SEE PKI Secure Electronic Environment Public Key Infrastructure
Status Recommended
Comments For agencies using the Secure Electronic Environment (SEE) e-government component. See Section 3 E-government Services for more details.
SEEMail Secure Electronic Environment Mail
Status Recommended
Comments A combination of procedures and standards already listed in the e-GIF, required to use the e-government component SEEMail service. See Section 3 E-government Services for more details.
S/MIME v3 0 Secure Multi-Purpose Internet Mail Extensions Version 3
Status Adopted
Comments Use MIME when security is not a concern. Use S/MIME encryption when not using the Messaging Transport protocols.
Status Under Development
Comments A draft RFC being developed by the ICT Branch of the State Services Commission, describing how to implement secure email between mail gateways using TLS.
2.6.6 Public Key Infrastructure (PKI)
RFC2527 Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework
Status Recommended
Comments Produced by the Public-Key Infrastructure X.509
group, or PKIX, a working group of the Internet Engineering Task Force
dedicated to creating RFCs and other standards documentation on issues
related to public key infrastructure (PKI) based on X.509
certificates.
Note: Agencies wishing to implement any new PKI system must contact
the ICT Branch of the State Services Commission for advice.
2.7 Best Practice layer
This section presents international standards and local conventions which support best practice, rather than the actual data exchange in interoperability. Agencies use these standards, not necessarily with direct dependence on the standards of other agencies with whom they interoperate, but to support interoperability in general.
2.7.1 Digital Rights Management (DRM)
Status Under Development
Comments Do not enable. See October 2004 paper on Trusted Computing. A Working Group is considering conventions for use across government.
2.7.2 Trusted computing
Status Under Development
Comments A Working Group has developed a set of government-wide principles and policies for the use of trusted computing and digital rights management (TC/DRM) technologies in New Zealand. See also SSC 2004 Report on Trust & Security.
2.7.3 Process
WS BPEL Web Services Business Process Execution Language
Status Future
Comments Lets users describe business process activities as web services and define how they can be connected to accomplish specific tasks.
FWSI Framework for Web Services Implementation
Status Future
Comments Defines methods and functional components for broad, multi-platform, vendor-neutral cross-industry implementation of Web services
CPPA ebXML Collaboration Protocol Profile and Agreement
Status Future
Comments Describing how trading partners engage in electronic business collaborations through the exchange of electronic messages
EBXML-BP ebXML Business Process
Status Future
Comments Providing a standards-based business process foundation that promotes the automation and predictable exchange of business collaboration definitions using XML
BPEL4WS Business Process Execution Language for Web Services
Status Deprecated
Comments Lets users describe business process activities as web services and define how they can be connected to accomplish specific tasks.
2.7.4 XML data transformation
XSLT eXtensible Stylesheet Language Transformations
Status Adopted
Comments A description vocabulary used by XSL to describe how an XML document is transformed into another XML document.
XPath eXtensible Stylesheet Language Transformations
Status Recommended
Comments XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.
2.7.5 Data modelling
Entity Relationship Diagrams
Status Adopted
Comments Useful for describing objects in a visual format.
UML Unified Modelling Language
Status Adopted
Comments Useful for describing objects in a visual format.
XMI XML Metadata Interchange
Status Recommended
Comments Enables easy interchange of metadata between odelling tools such as UML and remote metadata repositories.
UBL Universal Business Language
Status Future Consideration
Comments Naming and design rules for schema design.
2.7.6 Processing structured data
SAX Simple API for XML
Status Adopted
Comments Parser for large volume repetitious batch transfers. Open standard for navigating and updating XML documents.
DOM Document Object Model
Status Recommended
Comments Parser for transactional exchanges. SAX is a Java API for navigating XML documents.
XQuery 1.0 XML Query Language
Status Future Consideration
Comments A query language that can express queries across diverse data sources including structured and semi-structured documents, relational databases, and object repositories, whether physically stored in XML or viewed as XML via middleware.
XLink 1.0 XML Linking Language
Status Future Consideration
Comments A linking language that allows elements to be inserted into XML documents in order to create and describe links between resources.
2.7.7 Controlled Vocabulary or code Lists (CVLs)
Status Future Consideration
Comments Discussion on standardising CVLs. Research underway, led by the ICT Branch of the State Services Commission.
2.7.8 Health sector
HL7 Health Level 7
Status Under Development
Comments An international standard adopted by the health sector. Is converging on HL7 Version 2.4 for laboratory results and National Health Index (NHI).
2.7.9 Document file format
ODFOA v1.0 , Open Document Format for Office Applications
Version 1.0
DocBook, DocBook
Status Future Consideration
Comments Several candidates for agencies to save documents in an open, XML format.
2.7.10 Biometrics
ISO/IEC 19794 - Parts 2-6:2005 Information technology - Biometric data interchange formats
Status Future Consideration
Comments Applying to access control, ID systems and storage on databases. (Ref Mark Tesoriero at Customs for guidance).
Note that biometrics are specifically prohibited for transmission with an online transaction (Cabinet Minute EXG (03) 37 24th June 2003)
2.7.11 Evidence collection
HB 171-2003 Guidelines for the management of IT evidence
Status Future Consideration
Comments Provides useful guidelines for agencies in
management of evidence
held in computerised systems.
2.7.12 Business Transactions
UBL Universal Business Language
Status Future Consideration
Comments Defining a common XML library of business documents (purchase orders, invoices, etc.)
3 E-government Services
The following items comprise the E-government Services. They are actual implementations of useful functions that are:
- available for re-use by public sector agencies
- compliant with the e-GIF.
The items are:
- Metalogue: Services and
Document Description (metadata) Database
-
- Portal News Feed: News Syndication
-
- Uses NZ Government RSS to accept news items from government agencies for display on the Portal. This can also provide a feed of government news for use on agency websites.
- Authentication: Government to Individual and Government to Business online authentication
-
- The Government Logon Service (GLS) is currently available for implementation by agencies. It provides affordable access to high-quality authentication services. The GLS provides people with a common logon, such as a username and password or token, to access all online services provided by participating agencies.
- Shared Workspace:Online collaboration tool
-
- Workspace is available at a modest charge for agencies to run collaborative projects in an online environment. Workspace content-management functionality includes message threading, library and archiving, alerting and news/event announcements.
- Public Sector Intranet: All-of-Government online information repository
-
- The Public Sector Intranet was launched as a full production system, in June 2006. For more information, contact PSI@ssc.govt.nz
- SEEMail: New Zealand Government Secure Email system; SEEMail
-
- SEEMail is a gateway-gateway crypto layer running over public email, improving confidentiality and authentication. It is intended for use between government bodies (including local government). Note the next version of this service will not accept UUENCODE or TNEF message formats.
- Search Engine: Autonomy search engine (Deprecated)
-
- Please note that government agency web search capability is under review. Agencies considering products are advised to contact the ICT Branch.
- Government Shared Network: modular structured network that will enable government agencies to share information at higher speeds and more cost effectively
-
- The Government Shared Network is a secure network linking government agencies with high-speed Internet and telecommunications services. The initial set of services is being deployed by early adopting agencies at the end of 2006, with general release in early 2007. The Government Shared Network (GSN) features a fully managed infrastructure, with a 24 x 7 Service Desk. Contact gsn@ssc.govt.nz.
[ Previous ]
