2008 National Meeting Technology Updates
From Exchange Network Wiki
The Exchange Network governance will significantly improve Exchange Network technology components in 2008. See below for the latest information on what to expect. And don't forget to Join the discussion. .
Contents |
NAAS 3.0
The Network Authentication and Authorization Service (NAAS) provides enterprise level security to Exchange Network Nodes. The service provides user identity management and a granular permissions scheme to ensure data security across the Exchange Network. Version 3.0 of the NAAS includes security enhancements and support for Node 2.0.
Impact of update to NAAS 3.0 on users: Although the interface to NAAS 3.0 is significantly different than NAAS 2.0, all Exchange Network user accounts will be available through both NAAS services. Node 2.0 implementations must use NAAS 3.0; however NAAS 2.0 will stay in operation until all Node 1.1 implementations have been upgraded to Node 2.0.
Anticipated Final Version Release Date: Roll-out of NAAS 3.0 is expected to occur in May 2008.
Header 2.0
The Exchange Network Header Specification v2.0 provides the capability to append descriptions and process instructions to a document without the need to change data schemas. It includes metadata to describe the contents of the payload, routing information for documents transferred across the Exchange Network, and additional information such as creator, timestamp, and description of the payload contents.
The Header 2.0 specification is a major update over the previous version, and it is not backwards compatible with previous versions. It will only be required on new exchanges through 2.0 Nodes.
Final Version Released: January 2008
Impact of update to Header 2.0 on users: Use of the Header is required for all Submit operations on the Network. Currently Header 1.1 is required. Header 2.0 will be required at next business-driven flow upgrade and in conjunction with the Node 2.0 implementation process. IPTs that are currently planning flows or in the early stages of schema development should plan to use Header 2.0. For all other payloads sent over the Exchange Network use of the Header is optional on a Service-by-Service basis. The FCD for each Data Exchange specifies whether partners are expected to use the Header.
Node 2.0
Node 2.0 is the newest version of the Network Node Specification (Specification) and Exchange Network (EN or Network) Protocol (Protocol) – the seminal technical definition of the Exchange Network. Node 2.0 defines an upgrade to the infrastructure of the Exchange Network improving upon version 1.1, adding new functionality, and ensuring that the EN remains current.
Proposed final version release date: June 2, 2008
The Node 2.0 Task Force, a body of the Exchange Network governance, is overseeing the development of Node 2.0. Below are the hand-outs distributed at the 2008 Exchange Network National Meeting.
- Presentation slides
- Agenda for presentation
- Node 2.0 Frequently Asked Questions
- Summary of the strategy for migrating Exchange Network flows
- Flow migration information for Exchange Network partners
- Get Services Schema
- Node 2.0 Factsheet
- Recipients Guidance for Flow Implementors
Need more information or want to share details on your Node implementation? The Network Nodes page has up-to-date information on existing and future Network Nodes.
Exchanging Geospatial Data on the Exchange Network
The Geospatial Task Force, a body of the Exchange Network governance, had their first meeting in February to work on developing demonstrations, refinements, and documentation needed to support adoption of GML on the Exchange Network. They will also identify and describe potential impacts on Network partners, infrastructure, and tools, and develop recommendations to address these impacts.
Proposed Final Version Release Date: TBD - Draft guidance on the exchange of geospatial data will be released the summer of 2008.
Impact on users: The new geospatial guidelines will improve the exchange of geospatial data on the Exchange Network as flow schema are modified. The Geospatial Task Force will consider how changing guidelines will affect current flows and current Exchange Network partners. Further information should be available in the summer of 2008. Flow implementers needing to make decisions now should contact the Geospatial Task Force through the National Meeting message board forum.
