Network Technology Group Open Call February 2, 2006

1
Network Technology Group Open Call February
2, 2006
2
Introducing NTG Members
3
Exchange Network Governance
4
NTG Responsibilities

• We Are Building One Network
• To support the open standards and
  interoperability at the heart of the Exchange
  Network the NTG
• Oversees technical operation of the Network
• Example Network Security and NAAS
• Provides technical resources
• Documentation and guidance for developers
• Shepherds Flow Schema development
• Schema conformance review and guidance
• Evaluates new network technologies
• Provides technical vision for EN infrastructure

5
Agenda and participant feedback

• Todays Call
• Network Namespaces
• Exchange Network Discovery Service
• Other NTG Activities
• Participation
• Questions and Feedback on call about NTG
  activities
• Feedback to NTG on ongoing initiatives

6
Namespaces on the Exchange Network Tom Aten
Wisconsin DNR thomas.aten_at_dnr.state.wi.us
7
Network Namespaces
Target Namespace declaration in a schema file

• Network Namespaces are declarations in XML
  documents that govern the syntax for accessing
  tags from imported schema
• Proper use of namespaces simplifies schema and
  instance file development and prevents naming
  collisions. Schema reuse across flows makes a
  Network standard for namespaces even more
  important.

8
NTG Activities on Namespaces

• Version 1.10 was approved by NTG and NOB in
  January, 2006
• At next business-driven revision, schema should
  change namespaces to be URL-formatted.
• New standard format for namespaces
• http//www.exchangenetwork.net/schema/example/sube
  xample/version
• this link is an example and will not resolve

9
How does this affect the EN?

• New repository structure will be
• http//www.exchangenetwork.net/schema/
• Shared Schema Components will not declare a
  namespace so they can be included in schema
  (i.e., using include instead of import)
• A related requirement is to include an index.xsd,
  as the root schema
• This will improve access to schemas through the
  namespace structure

10
Namespace Resources

• Consult Namespace Use-Case Document
• http//www.exchangenetwork.net/dev_schema/index.ht
  m
• Network Namespace, Use-Case, Metadata available
• Questions or Comments on Namespace Recommendation
• Tom Aten
• atent_at_dnr.state.wi.us

11
Exchange Network Discovery ServiceGlen Carr
Oregon DEQcarr.glen_at_deq.state.or.us
12
EN Discovery Service

• Standards of the Exchange Network makes the
  Discovery Service possible
• Provides services to register and discover nodes
  and node services, making it easier for users to
  consume Network data
• 2 types of interfaces to the Discovery Service
  will be supported
• Node Web Service (machine interface)
• Web-enabled GUI (human interface)
• Functional Prototype hosted at Oregon DEQ

13
RegisterDiscoverConsume
Node Administrators can register their node
14
RegisterDiscoverConsume
Interested parties can determine what services
are available and which nodes offer them
15
RegisterDiscoverConsume
Interested parties can then use the information
retrieved from the Discovery Service to query one
or more nodes
16
Discovery Service NTG Activities

• A joint state/EPA Task Force was formed to work
  on the Discovery Service on behalf of the NTG.
• Final schema, Data Exchange Template, Flow
  Configuration Document, and instance file are
  under consideration for approval at version 1.3
• Task Force is planning for transition from
  prototype at Oregon DEQ to permanent node at CDX

17
Discovery Service Resources

• Questions or Comments for the Task Force can be
  sent to
• Steve Abercrombie
• steve.abercrombie_at_ross-assoc.com

18
Other NTG Activities
19
Other NTG Activities

• Revise Schema Review process
• Clarify and improve process steps for
• Developing a schema conformance report
• NTG reviews of conformance reports
• Create developer tools (checklists/templates)
• Explore additional NAAS authentication method for
  machine-to-machine transfers via a new Secure
  Authentication Key
• Unlike username/password, this credential will be
  tied to machine IP Address
• Improve Change Management on the Network
• NTG Task Force reviewing initial guidance from
  NOB
• Develop Network principles for Change Management,
  versioning, and developer-level guidelines

20
Other NTG Activities

• (continued)
• Managing updates to technical resources
• Shared Schema Components and guidance documents
• Design Rules and Conventions
• Future Activities
• Prioritized on Rolling Work plan (available from
  EN Website)

21
Questions or Feedback?

• Questions from call contact presenters
• Future feedback contact NTG Co-chairs
• Please provide any feedback related to the
  content of this call by February 22
• Feedback on pending issues before the NTG will be
  considered with other comments
• Feedback on decided issues/documents will be
  taken under consideration at the next revision of
  the decision/document

22
Resources

• Scott Totten
• scott.totten_at_dnr.mo.gov
• Connie Dwyer
• dwyer.connie_at_epa.gov
• Tom Aten
• atent_at_dnr.state.wi.us
• Glen Carr
• carr.glen_at_deq.state.or.us

• CSC Node Help Desk
• Hours 800am - 600pm (EST).
• Phone [phone]
• Email nodehelpdesk_at_csc.com
• Molly ONeill
• EN Coordinator
• Email moneill_at_sso.org

Operations page website http//www.exchangenetwork
.net/operations/index.htm Develop XML
Schema http//www.exchangenetwork.net/dev_schema/i
ndex.htm
23
Questions and Answers

• The following slides were not part of the Open
  Call presentation. They were questions from
  participants that were answered by NTG members.
  For additional information please contact the
  presenters or the NTG Co-Chairs.

24
Questions and Answers

• When using the EN Discovery Service to consume
  data from a node, what happens if someone does
  not have the proper security authorization?
• There are several potential scenarios - open data
  would be provided to the requester because there
  are no security constraints. If the requester
  didnt have proper NAAS security authorization to
  access data a message could be provided with
  phone number of node administrator so the
  requestor knew how to ask for authorization to
  view data.

25
Questions and Answers (cont.)

• Who reviews schema?
• The NTG is responsible for reviewing schema and
  overseeing the schema conformance review process.
• Has the current published schema review process
  changed?
• The NTG is modifying the schema conformance
  review process, but until guidance is released to
  the Network, flows should follow the current
  review process published on the EN website.

26
Question and Answers (cont.)

• Is there going to be an effort to synchronize
  internal EN guidance documents, and possibly
  documents outside of the EN?
• The NTG and guidance document developers always
  seek to maintain consistency between guidance
  documents. Current guidance document updates are
  listed along with other NTG activities on the
  groups rolling work plan. Please review the NTG
  work plan and provide us feedback if you know of
  specific conflicts in documents under development
  or revision. For documents not currently being
  revised, forward information about conflicting
  guidance to the NTG co-chairs.
• The EN Design Rules and Conventions (DRC) are
  currently undergoing revision, please contact
  Bill Rensmith from Windsor Solutions
  ltBill_rensmith at windsorsolutions.comgt with
  specific examples of conflicts in the DRC.

27
Questions and Answers (cont.)

• What is happening with synchronizing the
  Environmental Health Network and Exchange
  Network?
• EPA managers are involved in both efforts and
  attend meetings so there is visibility into
  current activities on both networks.