1. 1 Exchange Network Node 2.0 Open Conference Call October 18 th, 2007

2. 2 Introductions This conference call is hosted by the Network Technology Group (NTG), which is the technical work group of the Exchange Network (EN) governance NTG members present: Connie Dwyer, EPA OEI (EPA Co-chair) Glen Carr, Oregon DEQ (State Co-chair) Tom Aten, Wisconsin DNR Dennis Burling, Nebraska DEQ Chris Clark, EPA OEI

3. 3 Conference call agenda Provide a detailed description of the proposed technical changes from revision 7 (June 2007) to draft 8 (October 5, 2007) Update on revised Node 2.0 Timeline and Testing Collect your comments on the revised draft 8 WSDL and Spec Q&A

4. 4 Conference call basics Feel free to ask questions at any time during the presentation: before, during, or after! Please put your phone on mute when you’re not asking questions (if your phone has a mute function) Please don’t put this call on hold if your hold function plays music This web conference has a chat feature. Please feel free to send questions or comments to the meeting organizers at any time during the call.

5. 5 The journey from Node 1.1 to Node 2.0 October 2000: Network Blueprint defines a Network Node 2001-2002: Alpha and Beta node projects conducted Fall 2002: Node 1.0 project completed; Node 1.1 Specification and Protocol released Late 2002: first Node in production with CDX Late summer 2006: NTG work group starts discussing Node 2.0 June 2007: Node 2.0 revision 7 WSDL, Specification release to EN for comment June – Present: continued development of WSDL, Specification October 5: Node 2.0 Draft 8 WSDL, Specification released

6. 6 Basic changes in Node 2.0 Three major changes to Node technologies SOAP 1.2 Doc/Literal WSDL MTOM Changes primarily driven by vendor support issues These changes will be mostly transparent but are important for other reasons: Bring the Exchange Network up-to-date with current standards for web services This means that the same platform (e.g. SOAP 1.2 handler) that runs Node 2.0 can easily be adapted to inter-operate with other Web services networks

7. 7 What’s New in Node 2.0: SOAP 1.2 and Doc/Lit WSDL Soap 1.2/MTOM SOAP 1.1 is no longer supported by Java or MS.NET WS toolkits. SOAP 1.2 utilizes MTOM (now a W3C standard) to attach binary messages which has a unified infoset, is simple to design and implement, and is the new standard for WS payloads over SOAP. Doc/Literal WSDL The Node 1.1 WSDL is RPC/Encoded. Standard, but inconsistent implementation due to encoding type definitions. Doc/Literal allows WSDL types to be defined like normal XML schema.

8. Node 2.0 Draft 8 Specific Changes Parameters –Parameters are now defined as an element/attribute pair. –Includes ability to specify unique type for each parameter. All nodes must accept ‘string’ typed parameters Additional parameter types are optional, but encouraged (XML specifically) 8

9. Node 2.0 Draft 8 Specific Changes Query Paging –Expanded from Node 1.1 –Return result set based on rowID, maxRows –Still outstanding challenges: Some DBs do not support this functionality Setting sort order? –The NTG will be testing implementation of query paging to determine required level of support in final Node 2.0 Specification. 9

10. Node 2.0 Draft 8 Specific Changes Synchronous Status Response –Immediate status returned with submit and solicit responses –At minimum, must return ‘received’ –NTG expects increased adoption/support over time Realize that many Nodes may not support this level of granular status response immediately 10

11. Node 2.0 Draft 8 Specific Changes Expanded status information –Two parts of status information: Status Code –Enumerated list (expanded from Node 1.1) Status Detail –Placeholder for Node/Flow specific return message –Potential use for Flows to send detailed status information on business processes 11

12. Node 2.0 Draft 8 Specific Changes Automatic Email/Node notification –Via the new ‘notificationURI’ parameter –Ability to supply either a valid email URI or Node URI –Automatically receive a notification message when a transaction status changes –NTG will be testing variations of the notificationURI array Different levels of granular notification 12

13. Node 2.0 Draft 8 Specific Changes Dynamic submission routing –Via the new ‘recipients’ parameter –Specify either a Node URI or email URI Nodes receive a forwarded submission Emails receive transactionID. –Creates ability to create ‘ad hoc’ dataflows – i.e. dynamic submissions 13

14. Node 2.0 Draft 8 Specific Changes Notify method –Updated to provide granular detail Documents Events Transactions –Enhanced machine-to-machine communications GetServices method –GetServices now includes detailed service information Parameter level service description Allows Node self description 14

15. Node 2.0 Draft 8 Specific Changes Execute method –Expandable interface for services: Future EN Services Outside Web Services Legacy Node 1.1 applications –This method will be optional for nodes to fully implement 15

16. 16 Node 2.0 Timeline October – December 2007 –Collect comments on Node 2.0 Draft 7 WSDL/Specification –Conduct tests as defined in the Node 2.0 Testing Plan (finish by 12/31/2007) –Implement Node 2.0 Test tool February 2008 –Modification/revisions to the WSDL, specification, and protocol process Task force discussion on any issues that arise during testing NTG review and acceptance of modification and revisions March 2008 –Node 2.0 WSDL and Specification Draft 9 made available to the user community and for comment April 2008 –Modification/revisions to the Node 2.0 WSDL and Specification –NTG review and acceptance of modification and revisions May 2008 –Finalize Node 2.0 WSDL, Protocol, Specification and supporting documentation –Release all Node 2.0 items (Specification, WSDL, and Protocol) June 2008 –Start Node 2.0 implementations and operations

17. 17 Opportunities for you to participate in Node 2.0: Development The NTG is asking for comments and suggestions on every aspect of Node 2.0 Draft 8 WSDL and Specification Support Materials Exchange Network Guidance Please submit comments on Draft 8 documents by October 26. For more specific information on technical Node 2.0 materials, please visit the Node 2.0 page at: www.exchangenetwork.net/node The NTG will consider and attempt to respond to all feedback/comments submitted

18. 18 Opportunities for you to participate in Node 2.0: Testing NTG has an initial list of EN partners interested in testing, Please let us know if you are interested in helping test! Testing will begin in November 2007 Two phases of testing: Unit testing individual methods Functional Testing basic exchange scenarios The NTG is still looking for vendors (or other Network Partners) to code additional Nodes, including:.NET, Java and an Open Source Node Alternate Web Service Implementations

19. 19 How do I stay connected? Updates on Node 2.0 will be posted to the Node page on Exchange Network website: www.exchangenetwork.net/node www.exchangenetwork.net/node Slides from this call will be posted shortly NTG will use Network Alerts to inform you of key updates on Node 2.0 and to announce future open calls NTG will contact those vendors/Network partners who express an interest in coding a Node implementation to discuss a communications process

20. 20 How to communicate on Node 2.0 The Exchange Network Message Board has a forum set up for you to ask questions and collaborate with other Network partners: http://www.websitetoolbox.com/tool/post/exnet/vpost?id=22 12821 http://www.websitetoolbox.com/tool/post/exnet/vpost?id=22 12821 To contact the NTG directly: E-mail questions to: node2.0@exchangenetwork.net node2.0@exchangenetwork.net OR Contact the NTG co-chairs: Connie Dwyer, EPA Co-chair EPA OEI Dwyer.connie@epa.gov (202) 566-1691 Glen Carr, State Co-Chair Oregon DEQ carr.glen@deq.state.or.us (503) 229-5062