1. 1 Exchange Network Node 2.0 Open Conference Call for Node Builders June 21 st, 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 Today’s presenters: Connie Dwyer and Glen Carr

3. 3 Conference call agenda Provide an detailed description of the proposed technical changes from Node 1.1 to Node 2.0, and the process for finalizing Node 2.0 Discuss how you can participate in Node 2.0 development and testing Discuss the expected timelines for vendors/ Network partners developing Node 2.0 implementations Collect your comments and concerns about Node 2.0

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 Before we get started: When can I see the draft WSDL? We will use the e-mail requests from this call to establish a WSDL distribution list Draft 0.7 of the WSDL will be distributed next week, after the next Task Force meeting Task Force will be managing the distributions closely to ensure there is not confusion about versions, and especially about what is final/draft. Final Version 1.0 is expected in September

6. 6 Questions to consider during this presentation Initial feedback/questions on the indicated changes: Hold detailed questions until you have the WSDL in hand. What feedback or questions do you have on the Node 2.0 timeline? Are you interested in developing a Node 2.0 implementation? If so, what Web Service implementation will you use? What type of information/communications are you interested to receive as Node 2.0 development proceeds?

7. 7 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 Early 2003: several more 1.1 Nodes in production Late summer 2006: NTG work group starts discussing Node 2.0 Present: Node 2.0 WSDL, Specification, and Protocol under development

8. 8 Current State of Node 1.1 SOAP 1.1 is no longer supported in many standard toolkits (mainly Java and.NET) Node 1.1 WSDL = RPC/Encoded Standard, but inconsistent implementation due to differing encoding type definitions Node 1.1 uses DIME for payloads Functional Never an integrated solution No longer supported by Java or MS.NET WS toolkits

9. 9 Boundaries of Node 2.0 development The NTG is using the guidelines below to bound the Node 2.0 development effort: Continue single EN WSDL for all Nodes Continue using the basic EN Methods established in Node 1.1 (Query, Solicit, Submit, Download) Focus changes on: upgrading technologies fixing identified Node 1.1 bugs expanding features where the need and opportunity is clear and the costs are acceptable Pay attention to, and balance implications/costs of changes on current implementations, especially at the flow level: But also recognize that it is “now or never” for many of these changes/upgrades Ensure all changes are based on testable/verifiable use cases

10. 10 Notes to WSDL Reviewers What feedback and questions do you have on the WSDL? Are there any comments or questions on the WSDL Technology Changes? Are there any comments or questions on the WSDL Method Changes? Pay attention to enumerated lists they are still working drafts: your input on them is welcome 0.8 version of WSDL will contain firmer versions of those Please consider and explain the USE CASES behind your comments There are thousands of design options and we are trying to ground any changes in real (or real possible) USE CASES.

11. 11 What’s New in Node 2.0: Technologies 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

12. 12 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.

13. 13 Examples of What’s New in Draft Node 2.0: WSDL Authenticate – Future support for federated security model Download - Specify downloads by unique DocumentID or TransactionID Query Parameters sent as explicit pairs of names/values Now better supports paged results GetServices – Returns ENDS compliant service description that includes parameters GetStatus – Returns flow level status error code and description Lower-level, audit information will be provided through a standard, optional, “GetAuditDetails” Query Candidate New Methods Process: A combination of Solicit and Submit. A r equest that the Node perform some named, parameter driven operation, on an attached payload and return a result. Invoke: Provides a generic, open ended EN interface to any external (web) service. Allows clients to consume these services using constructs defined in the Specification.

14. 14 Opportunities for you to participate in Node 2.0: Development The NTG is asking for comments, suggestions and proposals on every aspect of Node 2.0 WSDL Protocol and Specification Support Materials Exchange Network Guidance 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.

15. 15 Opportunities for you to participate in Node 2.0: Testing Vendors, States, and Tribes are encouraged to participate in the Node 2.0 development process If you are interested in developing beta implementations or assisting with testing, please let us know! In addition, the NTG target is to have three fully tested implementation available by this time next year CDX will have one Several current EN vendors have indicated intention of developing implementations We are looking for vendors (or other Network Partners) to code additional Nodes, including:.NET, Java and an Open Source Node Alternate Web Service Implementations

16. 16 Node 2.0 Timeline Late June: Version 0.7 WSDL document completed and distributed for comment July: Beta Node 2.0 coding begins on testing servers August: Unit Method testing and flow process testing Mid August: Protocol and Specification updated and Version 0.95 document distribution to Node 2.0 developers, for final review and testing September: Final CDX/Vendor Node testing Final NTG/NOB decision point: go/no go with rollout November: Distribution/Availability of Final version Node 2.0’s and Protocol/Specification. Winter 07: User Test Bed Available: Early adopter implementations Spring 08: Building 2.0 Nodes

17. 17 Receiving the Draft WSDL The NTG is distributing the current 0.7 draft WSDL for comment If you are interested in receiving the WSDL, please email: Node2.0@exchangenetwork.net Please provide comments on any part of the WSDL by July 2.

18. 18 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

19. 19 Questions for Vendors and Network Partners Developing Node implementations Are you interested in developing a Node 2.0 implementation? If so, what Web Service implementation will you use? What type of information/communications would you like to receive as Node 2.0 development proceeds?

20. 20 Feedback for the NTG? What feedback and questions do you have on the WSDL? Are there any comments or questions on the WSDL Technology Changes? Are there any comments or questions on the WSDL Method Changes? What feedback or questions do you have on the Node 2.0 timeline?

21. 21 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/mb/exnet?forum=83874 http://www.websitetoolbox.com/tool/mb/exnet?forum=83874 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