The Use of Standards in SOA
Peter Roden
Director of Technology Development
The 2nd Service Oriented
Architecture (SOA) and Web
Services Best Practices
OPEN STANDARDS
What is an Open Standard?
■
An is:
●
publicly available in stable, persistent versions
●
developed and approved under a published,
transparent process
●
open to public input: public comments, public
archives, no Non-Disclosure Agreements (NDA)
●
subject to explicit, disclosed (Intellectual Property
Rights) IPR terms
■
●
That's not a pejorative, it's a description
●
Using a single company's method, or joint work
from several companies, may be fine: but it has a
different set of risks and qualities than the official
output from a genuine open standards process
Standards ROI
■
Normalizing data, processes and users costs
time and money
■
ROI can come from operational savings and
outweigh the costs, ! those savings are "
and
■
This requires:
●
Established versioning
●
Reliable, fixed terms of availability (some
protection against withdrawal or “embrace-and
extend”)
●
#$%&'%&(% standards
●
#)%&*#* standards
Regulatory case for Open Standards
■
Increasingly, it matters to government
regulators and implementers whether
standards are developed under an
!+,- process.
●
WTO Technical Barriers to Trade Agreement
■
http://www.wto.org/english/docs_e/ legal_e/final_e.htm
●
United States criteria
■
http://www.whitehouse.gov/omb/circulars/a119/ a119.html)
■
Industry users care about the same issues
