Establishing a common language

Download Report

Transcript Establishing a common language

A Brave NEtWork World
Rob Willis, Ross & Associates
Node Mentoring Workshop
New Orleans, LA
February 28, 2005
Who is in the room
• In 2004, 32 State/Federal Partners
• Today, 47 Local/State/Federal/Tribal
/Non-governmental organization
Partners.
– More programmatic participants
• Why people said they came:
– Access to Expertise
– Learn from others
– Show others
Session Objective
• Establish a common vocabulary through
an illustrative description of the Network.
– By the end of the session you should be
able to:
• Identify the components of the Network.
• Understand the basic concepts and terms
associated with each of the components
• Be able to understand the relationship of
Web Services to the Network.
Partner Specificity
Business Logic
Infrastructure
and Transport
Administration
Information
Partner
Specificity
Network Components
•
•
•
•
Common exchange and access tools
Shared services and infrastructure
Data standards and shared formats;
Common business practices,
procedures and software for electronic
reporting and data collection;
• Shared strategy for environmental
Web services;
• Trading Partner Agreements
Common exchange and
access tools
Definition: Nodes, Clients, and their
associated software that Partners
employ to use the Network.
Information
Business Logic
Infrastructure
and Transport
Administration
• Guidance documents built around open
standards
• High-level of specificity
• Internet-based
Words you need to know
• XML, WSDL, SOAP
• Network Exchange Protocol (Protocol)
• Network Node Functional Specification
(Specification)
• Node
• Client
• Demonstrated Node Configuration
(DNC)
Protocol
/Specification
v 1.1
Network
WSDL
Network
Web
Methods
Node or
Client
XML SOAP
Node
Shared services and infrastructure
Definition: The common technical services and
infrastructure that support or enhance the
basic operation of a Flow. These services do
not, by themselves flow information, but they
materially support (sometimes in an essential
technical way) Partner Flows.
Business Logic
Infrastructure
and Transport
Administration
Information
Words you need to know
•
•
•
•
Shared Service
Registry
Repository
Network Authentication and Authorization
Server (NAAS)
– Authentication and Authorization
• Universal Description, Discovery, and
Integration (UDDI)
Protocol
/Specification
v 1.1
Registry/Repository
or
Shared Service
Network
WSDL
Network
Web
Methods
Node or
Client
XML SOAP
Node
Security/
e.g., NAAS
Data standards and shared formats
Definition: Documented agreements
among Partners on the names,
definitions, and formats for data.
Partners commonly use shared
formats, specifically XML schema.
Business Logic
Infrastructure
and Transport
Administration
Information
Words you need to know
• XML Schema
• Data Exchange Template (DET)
• Flow Configuration Document (FCD)
Protocol
/Specification
v 1.1
Schema
Registry/Repository
Data
or
Shared Service Standard
Network
WSDL
Network
Web
Methods
Node or
Client
XML SOAP
Node
Security/
e.g., NAAS
Schema
Design
Guidelines
Core
Reference
Model
Common business practices, procedures
and software for electronic reporting and
data collection
Definition: The set of related shared practices,
procedures and software used for electronic
collection of data from data-generating
sources, such as regulated entities,
laboratories, and field personnel and stations.
Business Logic
Infrastructure
and Transport
Administration
Information
Protocol
/Specification
v 1.1
Schema
Registry/Repository
Data
or
Shared Service Standard
Network
WSDL
Network
Web
Methods
Node or
Client
XML SOAP
Node
Security/
e.g., NAAS
Schema
Design
Guidelines
Core
Reference
Model
Business Logic
Infrastructure
and Transport
Administration
Information
Network Flows and Web Services
• Web Services are automated resources
accessed via the Internet.
– Standardized way of integrating Web-based
applications using the XML, SOAP, WSDL and UDDI
open standards.
• A Network Flow a documented grouping of
related data, their defined format, and the
requests and responses, as defined by the
Network Exchange Protocol and Network Node
Functional Specification.
– Documented in the Trading Partner Agreements,
Flow Configuration Documents, Data Exchange
Templates, Schema, Data Standards.
Shared Strategy for Environmental
Web Services
What a shared strategy means:
– Jointly developing and mounting shared
Web services that provide common,
compatible information among Partners and
allow its easy integration, aggregation and
access.
– Use Query or Solicit Web services as the
preferred approach when data publication is
(or could be) the right model for Partner
interactions; and
– Description of this components begins the
process of developing the strategy itself
Words you need to know
•
•
•
•
•
•
•
Traditional Flow
Regulatory Flow
Non-regulatory Flow
Data Publishing
FCD (mentioned above)
Web Services
Trading Partner Agreements
Challenge for the Network and its
Partners/Users
The key challenge facing the Network
is supporting Partners in designing
and managing the Flows that will
leverage the value of the Network,
and, in doing so, expand it.
Leveraging Communities of
Interest
• Emerging strategy to address the
challenge.
– Network Data Area Strategies.
• Premise behind the afternoon sessions.
Contact Information
Rob Willis
Ross & Associates
[email protected]
206.447.1805
Exchange Network Website:
http://www.exchangenetwork.net