Get documents about "Workshop Template - Download as PowerPoint
Document Sample
S1 Welcome and
Introduction
S2 State Preliminary Design CVISN DESIGN WORKSHOP
Review
S3 State Work/Discussion
Sessions
S4 General Discussion of
issues and questions
Session 4b
S5 Birds of A Feather design
discussions Discussion -
S6 State Program Phase Charts
Review
S7 State Work Sessions
EDI, XML, Web
S8 State Presentations
S9 Feedback & Next Steps
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 1
Session 4b Discussion - Outline
EDI, XML and the Web: CVISN Interface Design
• CVISN Interface Designs
• Alternatives for Electronic Credentialing
• Strategy for CVISN Interfaces
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 2
Session 4b Discussion - Background Material
EDI, XML and the Web: CVISN Interface Design
• Comparison of Electronic Credentialing Alternatives
• Simplified Comparison of Person-to-Computer & Computer-to-
Computer Interfaces
• Simplified Comparison of Alternatives for Computer-to-Computer
Interfaces: EDI or XML
• More on the Technologies
• What is EDI?
• What is XML?
• When Should You Use XML?
• What Activities Are Ongoing?
• Terminology
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 3
Session 4b:
EDI, XML and the Web: CVISN Interface Design
• The Interface: Defines the exchange of business
information between trading partners. In CVISN,
the interfaces that exchange data are grouped as
carrier-to-state, state-to-CVISN Core
Infrastructure systems, and within-state systems.
• The Design: Must consider State’s business
needs as well as long term plans for technology
upgrades and services in other areas. The design
is related to the types of entities that exchange
data.
• The Technologies: Must be appropriate to
support the design and business needs.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 4
CVISN Guidelines for Interface Design
Interface Design Technology
Choices
Computer-to-Computer: Open standard(EDI);
Carrier-to-State • CAT to CI exploring XML
• Fleet Mgmnt System to CI
Person-to-Computer: WWW and Internet
• Carrier to Web Site standards; HTML or XML
Computer-to-Computer:
• CVIEW to SAFER Open standard(EDI)
State-to-Core • ASPEN/SAFETYNET to
Infrastructure SAFER Custom format
• LS/CI to IRP Clearinghouse Custom format
• LS/CI to IFTA Clearinghouse Open standard(EDI)
Computer-to-Computer:
Within-State • CI to legacy systems Open standard (EDI), XML,
• Legacy system/ roadside to or custom interface
CVIEW
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 5
A state Web site approach provides a
person-to-computer interface.
Carrier State
Credentialing
Systems with
Web Site
World Wide Web
Web HTML or XML, HTTP
Browser Web standards;
no credentialing
standards used
States can provide electronic credentialing using a web site. The carrier
would access the web site using a commercial browser (e.g., Netscape)
and manually enter the required data.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Comparison of E-Credentialing Approaches
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 6
A stand-alone CAT (PC CAT) provides a
computer-to-computer interface.
Carrier State
Or Service Bureau
Stand-alone Credentialing
Internet,
CAT Systems
Dial-up, or VAN
EDI credentialing
standards exist. Stand-alone
XML credentialing CAT
standards could be Optional use for
developed. state branch offices
A carrier would enter vehicle information using the stand-alone CAT,
where it would be stored locally. The stand-alone CAT would
exchange credentialing information with the state using standards.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Comparison of E-Credentialing Approaches
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 7
A CAT module could be integrated into
existing fleet management systems to provide a
computer-to-computer interface
Carrier State
Fleet
Management Credentialing
System Internet, Systems
(including CAT Dial-up, or VAN
Module)
EDI credentialing
standards exist.
XML credentialing
standards could be
developed.
CAT credentialing capabilities are integrated in carrier Fleet
Management Systems (FMS) that already contain carrier and vehicle
related information needed for credentialing and use EDI for financial
information. The CAT module in the FMS would exchange credentialing
information with the state using standards.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Comparison of E-Credentialing Approaches
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 8
Dual Interface: A state could implement both
a Web site and a computer-to-computer interface.
Carrier 1 State
Credentialing
Systems with
World Wide Web Web Site
Web
Browser
HTML or XML, HTTP
E-mail or FTP
Carrier 2
PC CAT or EDI / XML /
CAT Module other file format
This approach gives carriers a choice of options. It provides the
benefits of both interface types, at additional cost to the state.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Comparison of E-Credentialing Approaches
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 9
Hybrid Interface: A Web site approach could incorporate
a one-way computer-to-computer element.
Carrier State
Credentialing
Systems with
World Wide Web Web Site
Web
Browser HTML or XML, HTTP
E-mail or FTP
FMS
Database EDI / XML /
other file format
Transactions are submitted via the web, but the user could request a computer
processable response from the state that would enable the carrier to update
their database. This may provide many of the benefits of a full computer-to-
computer interface at reduced cost.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Comparison of E-Credentialing Approaches
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 10
Web-Enabled CI System Design Firewall 1
MD Systems
Carrier Web
MD Files
Credentialing
Browser Web
Internet Site
Data DMZ
Base
Firewall 2
MVA DB
(stored procedures)
Stand-Alone
Core CI
CAT VISTA/RS
IRP backend
MD (future)
IRP CSR CI UI
CVIEW CAT Legend:
Client blue arrows indicate access
through firewall
Keep the same “back end” processes, regardless of
the external interfaces for credentialing
State Systems
Web & XML-
Stand-Alone Enabled
CAT Credentialing IRP
Interface
C
Terminal
A EDI I/F
Terminal Server
T IFTA
Client XML I/F Reg
Credentialing
Web Site
Fleet Web Database IFTA
Management Tax
System Filing
Core CI
Browser Database
CVIEW
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 12
Data interface choices imply
communications protocol choices
State Systems
Web & XML-
Stand-Alone Mail protocol: Enabled
CAT SMTP/POP3 IRP
Credentialing
Interface
C
Terminal
A EDI I/F
Terminal Server
T IFTA
Terminal protocol: XML I/F
Client Telnet
Reg
Credentialing
Web Site
Fleet File transfer: Web Database IFTA
FTP
Management Tax
System Filing
Web protocol:
Core CI
HTTP
Database
Browser CVIEW
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 13
Strategy for Carrier-to-State Interface (1 of 2)
• FMCSA currently
• requires an ANSI X12 EDI computer-to-computer
interface
and also
• recommends a person-to-computer (i.e., a web site)
interface
• In cooperation with states and other stakeholders,
FMCSA is evaluating this policy to determine the need
for change.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 14
Strategy for Carrier-to-State Interface (2 of 2)
• It has been recommended that FMCSA:
• Require states implement either a computer-to-
computer interface or a person-to-computer
interface. The state should be able to supply
evidence that their customers support this choice.
• Recommend states implement both a person-to-
computer and computer-to-computer solution.
• Recommend carriers and states use X12 EDI for
computer-to-computer interfaces unless the state has
evidence that customers support another format.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Summary
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 15
Strategy for State-to-Core Infrastructure Interface
• The interface for exchanging snapshot data between the
State CVIEW (or CVIEW equivalent) and SAFER is an
open standard (EDI) computer-to-computer interface
• The interface between the State and the IRP
Clearinghouse is a custom interface as defined in IRP
Clearinghouse Jurisdiction System Specification V1.6
• The interface between the State and the IFTA
Clearinghouse is EDI
• The interfaces between FMCSA-developed safety-related
systems (ASPEN and SAFER, ASPEN and CVIEW,
SAFER and SAFETYNET, SAFER and MCMIS, SAFER
and Licensing and Insurance) are based on custom
interface agreements defined by the system developers
and endorsed by FMCSA
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 16
Strategy for Within-State Interfaces
• The CVISN architecture does not specify the types of
interfaces to be used among in-state systems. The
state may choose computer-to-computer or person-to-
computer solutions to support their business needs.
The state may choose any technology that supports
their design choices.
• Computer-to-computer solutions: Custom interface,
EDI or XML.
• Person-to-computer solutions: Web-site (HTML, XML)
• The State should consider interface choices that will
minimize redundancy of effort and maximize
maintainability
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 17
Comparison of Electronic Credentialing Alternatives
• Simplified Comparison of Person-to-Computer &
Computer-to-Computer Interfaces
• Simplified Comparison of Alternatives for
Computer-to-Computer Interfaces: EDI or XML
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 18
A Simplified Comparison of Alternative Interfaces:
Person-to-Computer vs. Computer-to-Computer
Technical Carrier State Federal
Approach Perspective Perspective Perspective
Web Site Probably meets all needs of small to State must provide Does not satisfy all CVISN
mid-size carriers. Useful to even large web-site. State has architecture requirements.
carriers for individual transactions. control over software. Simpler to test the functionality.
Implementations across states
may be very different.
Stand Alone CAT
Offers mid-size & larger carriers
efficiencies when batch updating many
transactions. Requires maintaining a
separate software package. State must provide FMCSA should continue to
computer-to-computer facilitate interface standards
CAT Module For carriers with a high level of
interface. Will incur development and
automation, it offers potential for tighter
additional cost over maintenance. More complex
integration with carrier legacy
web site solution. to test.
databases. Potential for higher degree
of process automation & improved
efficiencies. May be a separately
priced option.
Dual Interface State must provide
This is the current CVISN
Allows a larger carrier to choose from Web-site and computer-
architecture
all 3 above alternatives to fulfill needs. to-computer interfaces.
recommendation.
Will incur cost of both.
Hybrid Interface FMCSA should facilitate
State must provide
If the state provides a computer- interface standards
Web-site and computer-
processable update to the carrier at the development and maintenance
to-computer interfaces.
end of a Web credentialing session, for the state-to-carrier
Will incur cost of both,
then many of the benefits of the Web response. Interoperability
but c-to-c interface is
and stand-alone CAT/CAT Module testing should involve both the
one-way, rather than
alternatives are available. Web-site tests and the state-to-
two-way.
carrier tests.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 19
A Simplified Comparison of Alternatives for
Computer-to-Computer Interfaces: EDI or XML
Technical Carrier State Federal
Approach Perspective Perspective Perspective
EDI Many carriers (& their EDI is new to most state EDI standards &
software suppliers) have credentialing agencies. implementation guides
used EDI for decades to Need to invest in have been developed.
interface to customers & translators and know- EDI has been deployed
suppliers. Proven how. in several states.
standards & guides exist. FMCSA must support
EDI standards & guides
maintenance.
XML Will avoid the cost of an Will avoid the cost of an FMCSA must provide
EDI translator but may EDI translator but may (or at least facilitate)
not be cheaper. Not all not be cheaper. Not all XML interface
necessary standards and necessary standards standards development
implementation guides and implementation and maintenance.
exist. “Hot” new guides exist. “Hot” new
technology may be wave technology may be
of the future, or may not wave of the future, or
live up to promise. may not live up to
promise.
With either EDI or XML:
• Developers need to map data from the legacy format to the interface, and back
again.
• All data users need to be able to interpret data coding in a standard way. (e.g., do
we abbreviate Quebec as QC or PQ?)
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 20
More on the Technologies
• What is EDI?
• What is XML?
• When Should You Use XML?
• What Activities Are Ongoing?
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 21
What is EDI?
• Electronic Data Interchange
• EDI is the electronic exchange of business information in a
standard format that permits computer generation and
processing of the message.
• ANSI X-12 EDI standards and user implementation guides
define the structure and meaning of computer-to-computer
messages passed between trading partners. EDI transaction
sets describe data structure, data type, data
interdependencies and data usage.
• X-12 EDI is a standard for data exchange based on a 20 year
history of consensus on data semantics.
• EDI is often implemented via the Internet. By using the
Internet to transmit EDI documents instead of VANs,
companies can save 60 to 90 percent on communications
costs.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 22
How Would EDI Work in CVISN Design?
• An EDI application consists of: EDI Standard +
Implementation Guide + EDI translator + Custom Software
• EDI standards and IGs are available
• Commercial translators are available
• EDI cost is reduced by using the Internet to send and
receive data
• EDI is well understood by the e-commerce business
community
• EDI is the open standard of choice for CVISN external
interfaces
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 23
What is XML?
• XML is a metalanguage for creating a customized mark-up
language to describe the structure and content of
documents. It is an outgrowth of document publishing and
display technologies which is becoming popular in WWW
applications. It is a method, not a standard, for data
interchange.
• Similar to HTML, XML uses a set of “tags” to describe
document content. Where HTML describes document format,
XML describes document content.
HTML Example: <tab> means tab over here on the page
XML Example : <name> John </name>
• What an XML document does NOT tell you about the data
exchanged: data type, data relationships/dependencies, data
meaning
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 24
Other XML Technologies and Languages
• Document Type Definition (DTD): Provides rules for using XML to
represent documents of a certain type. Defines the tags used.
• Schema: Goes beyond the DTD and describes meaning, usage,
and relationships of data elements. Schemas are likely to
replace DTDs in XML applications within a year or two, but
standards are still being developed and tools are not available.
• XML Parser: Checks for well-formed XML document (matching
tags, proper nesting). A validating parser checks that document
conforms with associated DTD.
• Style sheet: Describes how document is presented or displayed.
• XML Query Language: Notation for addressing and filtering the
elements of XML documents.
• XML Pointer and XML Linking Language: Describes how to
address a resource and how to associate two or more resources.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 25
How Do You Get XML to Work?
• For XML to work, you need mutually defined tags
for data exchange, as well as industry-specific
schemas to give the data meaning.
• Schemas are critical to data verification and
processing and are currently under development.
• Of note, regardless of the technologies used. . .
• To exchange information, developers need to map
data from the existing (legacy) format to the interface,
and back again.
• You still need custom software to extract and insert
data into your applications.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 26
How Would XML Work in CVISN Design?
• An XML application consists of: XML Standards + XML Document +
DTD or Schema + XML parser + Custom Software
• XML standards and many industry schemas are under development
• XML translators and parsers are inexpensive or free; more
sophisticated and expensive tools are also available
• XML for within-state (custom application) may be a reasonable
choice
• Properly designed XML solution will promote client-side processing,
more efficient use of server resources, faster response time
• XML is not necessarily “easier” for the developer
• XML may be the best thing since sliced bread when it fully matures
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 27
When Should You Use XML?
Situation Solution
Data consist of simple pages and graphics HTML
Data remain relatively static HTML
Data primarily multi-media- sound and/or video HTML
Data viewed on a variety of different platforms XML
Data require advanced searching XML
Data interfaced between different machines or XML
database engines
Users not finding data they need XML
Source: Pitts-Moultis, XML Black Book. The Coriolis Group, 1999. ISBN: 157610284X
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 28
When Should You Use XML?
Situation Solution
Trading Partners EDI enabled EDI
High-volume batch-processing EDI
XML standards and specifications do not support EDI
process
Trading Partners do not have application/database XML
Trading Partners want to use the web XML
Agency moving to web architecture XML
Real-time processing XML
Data used for both user-to-machine and machine-to- XML
machine
Source: Pitts-Moultis, XML Black Book. The Coriolis Group, 1999. ISBN: 157610284X
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 29
What Activities Are Ongoing? (1 of 3)
• Standards organizations and industry experts are
working to combine the rich data semantics from 20
years of EDI history with the emerging XML
technology for data and document exchange.
• The ebXML initiative is endorsed by leading industries
and the ANSI X12 Committee. Draft standard due out
within the year.
• States are implementing Web-based credentialing.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 30
What Activities Are Ongoing? (2 of 3)
• FMCSA is exploring the use of XML in computer-to-
computer applications for CVISN
• XML interface for IRP credentialing in Maryland
• XML interfaces to SAFER
• Tracking technology development and industry efforts to
define data repositories and schemas
• If the prototypes are fruitful, the architecture may be
changed.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 31
What Activities Are Ongoing? (3 of 3)
• FMCSA has just completed a survey of carriers,
service providers, states, and fleet management
system vendors to try to assess the market/need for
standardized computer-to-computer interfaces
between carriers and states.
• The survey results shaped the recommendations to
FMCSA, described under “Strategy for Carrier-to-State
Interfaces”, for the changes to the architecture.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 32
Terminology
• CVISN
• Electronic Credentialing
Terminology
• Computer-to-computer interface
• Person-to-computer interface In order to get accurate
information from the
• Open Interface Standard
survey, it is important that
• EDI (Electronic Data Interchange) we use common
• Proprietary Interface terminology. Definitions
• Local Area Networks (LANs) are included in the
• Wide Area Networks (WANs) Terminology section after
• Value-Added Networks (VANs) this slide. Please review
the definitions of any terms
• The Internet
unclear to you and ask for
• The World Wide Web (WWW or The clarification from the
Web) interviewer.
• HTML (Hypertext Markup Language)
• XML (eXtensible Markup Language)
• EDI Over the Internet
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Refresher - Terminology
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 33
Terminology -- CVISN
• Commercial Vehicle Information Systems and Networks
(CVISN, pronounced “see vision”)
Refers to the ITS information system elements that support
Commercial Vehicle Operations. CVISN includes information
systems owned and operated by governments, carriers, and other
stakeholders.
• CVISN focuses on three major capability areas
• Safety Information Exchange
• Credentials Administration
• Electronic Screening
• Electronic Credentialing
The process which allows carriers, owners, and drivers to apply
for, pay for, and receive credentials electronically.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Refresher - Terminology
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 34
Terminology -- Interfaces
• Computer-to-computer interface
How two (or more) computers exchange information.
The computers can be programmed to automatically
exchange information electronically. The computers
generate, send, receive, and process data with no (or
limited) involvement by a person.
• Person-to-computer interface
How a person and a computer exchange information.
Today, this is typically through a graphical user
interface (GUI) in which information is shown to a user
on a video monitor in an easy-to-follow way. GUIs
also collect inputs from users through a keyboard and
mouse.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 35
Computer-to Computer Interface Using Open Standards
MOTOR CARRIER Open standards and STATE
supporting documentation
allow motor carriers,
Motor Carrier states, and other trading State
Applications partners to exchange Applications
safety and credentialing
information.
Application Application
Database An open standard interface Database
can be added to existing
systems through some
custom coding and,
Custom Data perhaps, a commercial-off- Custom Data
Extract/Insert the-shelf translator. Extract/Insert
Commercial Commercial
Translator Translator
Open
Standard(s)
Open Communications Open
Standard Standard
Networks
(e.g., the Internet)
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Comparison of E-Credentialing Approaches
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 36
Terminology -- Standards
• Open Interface Standard
An interface definition that has been developed and adopted by
a standards development organization (SDO) such as ANSI or
IEEE, and that is published and available to the public for use.
• EDI (Electronic Data Interchange)
Often used as a shorthand for American National Standards
Institute (ANSI) Accredited Standards Committee (ASC) X12
EDI. EDI is an example of an open interface standard that is
widely used for the electronic exchange of business information
in a format that permits computer generation, exchange, and
processing of messages.
EDI standards and user implementation guides define the
structure and meaning of computer-to-computer messages
passed between trading partners.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Refresher - Terminology
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 37
Terminology - EDI Over the Internet
• EDI transactions can now be sent over the Internet
instead of over a VAN.
• VANs were the common method of EDI transmission
until the past few years.
• Internet EDI has attracted a lot of attention because of
its ability to dramatically lower the cost of EDI
communications. By using the Internet instead of VANs
to transmit standardized EDI transaction sets,
companies can save 60 to 90 percent on
communications costs.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Refresher - Terminology
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 38
Terminology -- Proprietary Interface
• Proprietary Interface
An interface definition that has been developed by one
or more companies for use in their private or
commercial systems and is not available for public
use.
Use of a proprietary interface can cause a customer to
be “locked in” to a specific vendor.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 39
Terminology -- Networks
• Local Area Networks (LANs)
Networks designed for geographically local areas, such as a
building or a campus.
• Wide Area Networks (WANs)
Networks consisting of LANs of various protocols, supporting
myriad media and architectures, and spanning cities, countries,
and continents.
• Value-Added Networks (VANs)
VANs often bundle other services with wide area network
(WAN) connectivity. Services can include automatic error
detection and correction; protocol conversion (for example,
from EDI format to legacy system format); or message storing
and forwarding. AAMVANET is an example of a VAN.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 40
Terminology -- The Internet and the Web
• The Internet
Worldwide public, cooperative, self-sustaining system of computer
networks. The Internet can support both computer-to-computer and
person-to-computer interfaces.
• The World Wide Web (WWW or The Web)
All the resources and users on the Internet that are using the
Hypertext Transfer Protocol (HTTP). The Web is the most widely
used part of the Internet.
A browser is an application program that provides a way to look at
and interact with all the information on the World Wide Web. A Web
browser uses the Hypertext Transfer Protocol (HTTP) to make
requests of Web servers throughout the Internet on behalf of the
browser user. Two widely used browsers are Netscape Navigator
and Internet Explorer.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Refresher - Terminology
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 41
Terminology -- Web Languages
• HTML (Hypertext Markup Language)
The set of "markup" symbols or codes inserted in a file
intended for display on a World Wide Web browser. The
markup tells the Web browser how to display a Web page's
words and images for the user.
• XML (eXtensible Markup Language)
A flexible way to create common information formats and
share both the format and the data on the World Wide Web,
intranets, and elsewhere.
Particular applications are defined through three elements:
Document Type Description (comparable to a data base
schema), Stylesheets (to explain how to present
information to the user), and Links between resources (for
example, between index and content).
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 42
Terminology -- Web Languages (concluded)
• Similarities
Both XML and HTML contain markup symbols to describe
the contents of a page or file.
• Differences
HTML, however, describes the content of a Web page
(mainly text and graphic images) only in terms of how it is to
be displayed and interacted with. XML describes the
content in terms of what data is being described. XML is
"extensible" because, unlike HTML, the markup symbols
are unlimited and self-defining.
CVISN Design Workshop Session 4b - Discussion - EDI, XML, Web Refresher - Terminology
The Johns Hopkins University Applied Physics Laboratory 8/18/2010 2:26 AM Design Page 4b - 43
Related docs
