␡
- XML Reference Guide
- Overview
- What Is XML?
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Table of Contents
- The Document Object Model
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- DOM and Java
- Informit Articles and Sample Chapters
- Books and e-Books
- Implementations
- DOM and JavaScript
- Using a Repeater
- Repeaters and XML
- Repeater Resources
- DOM and .NET
- Informit Articles and Sample Chapters
- Books and e-Books
- Documentation and Downloads
- DOM and C++
- DOM and C++ Resources
- DOM and Perl
- DOM and Perl Resources
- DOM and PHP
- DOM and PHP Resources
- DOM Level 3
- DOM Level 3 Core
- DOM Level 3 Load and Save
- DOM Level 3 XPath
- DOM Level 3 Validation
- Informit Articles and Sample Chapters
- Books and e-Books
- Documentation and Implementations
- The Simple API for XML (SAX)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- SAX and Java
- Informit Articles and Sample Chapters
- Books and e-Books
- SAX and .NET
- Informit Articles and Sample Chapters
- SAX and Perl
- SAX and Perl Resources
- SAX and PHP
- SAX and PHP Resources
- Validation
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Document Type Definitions (DTDs)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XML Schemas
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- RELAX NG
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Schematron
- Official Documentation and Implementations
- Validation in Applications
- Informit Articles and Sample Chapters
- Books and e-Books
- XSL Transformations (XSLT)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XSLT in Java
- Java in XSLT Resources
- XSLT and RSS in .NET
- XSLT and RSS in .NET Resources
- XSL-FO
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XPath
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XML Base
- Informit Articles and Sample Chapters
- Official Documentation
- XHTML
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XHTML 2.0
- Documentation
- Cascading Style Sheets
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XUL
- XUL References
- XML Events
- XML Events Resources
- XML Data Binding
- Informit Articles and Sample Chapters
- Books and e-Books
- Specifications
- Implementations
- XML and Databases
- Informit Articles and Sample Chapters
- Books and e-Books
- Online Resources
- Official Documentation
- SQL Server and FOR XML
- Informit Articles and Sample Chapters
- Books and e-Books
- Documentation and Implementations
- Service Oriented Architecture
- Web Services
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Creating a Perl Web Service Client
- SOAP::Lite
- Amazon Web Services
- Creating the Movable Type Plug-in
- Perl, Amazon, and Movable Type Resources
- Apache Axis2
- REST
- REST Resources
- SOAP
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- SOAP and Java
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- WSDL
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- UDDI
- UDDI Resources
- XML-RPC
- XML-RPC in PHP
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Ajax
- Asynchronous Javascript
- Client-side XSLT
- SAJAX and PHP
- Ajax Resources
- JSON
- Ruby on Rails
- Creating Objects
- Ruby Basics: Arrays and Other Sundry Bits
- Ruby Basics: Iterators and Persistence
- Starting on the Rails
- Rails and Databases
- Rails: Ajax and Partials
- Rails Resources
- Web Services Security
- Web Services Security Resources
- SAML
- Informit Articles and Sample Chapters
- Books and e-Books
- Specification and Implementation
- XML Digital Signatures
- XML Digital Signatures Resources
- XML Key Management Services
- Resources for XML Key Management Services
- Internationalization
- Resources
- Grid Computing
- Grid Resources
- Web Services Resource Framework
- Web Services Resource Framework Resources
- WS-Addressing
- WS-Addressing Resources
- WS-Notifications
- New Languages: XML in Use
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Google Web Toolkit
- GWT Basic Interactivity
- Google Sitemaps
- Google Sitemaps Resources
- Accessibility
- Web Accessibility
- XML Accessibility
- Accessibility Resources
- The Semantic Web
- Defining a New Ontology
- OWL: Web Ontology Language
- Semantic Web Resources
- Google Base
- Microformats
- StructuredBlogging
- Live Clipboard
- WML
- XHTML-MP
- WML Resources
- Google Web Services
- Google Web Services API
- Google Web Services Resources
- The Yahoo! Web Services Interface
- Yahoo! Web Services and PHP
- Yahoo! Web Services Resources
- eBay REST API
- WordML
- WordML Part 2: Lists
- WordML Part 3: Tables
- WordML Resources
- DocBook
- Articles
- Books and e-Books
- Official Documentation and Implementations
- XML Query
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XForms
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Resource Description Framework (RDF)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Topic Maps
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation, Implementations, and Other Resources
- Rich Site Summary (RSS)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Simple Sharing Extensions (SSE)
- Atom
- Podcasting
- Podcasting Resources
- Scalable Vector Graphics (SVG)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- OPML
- OPML Resources
- Summary
- Projects
- JavaScript TimeTracker: JSON and PHP
- The Javascript Timetracker
- Refactoring to Javascript Objects
- Creating the Yahoo! Widget
- Web Mashup
- Google Maps
- Indeed Mashup
- Mashup Part 3: Putting It All Together
- Additional Resources
- Frequently Asked Questions About XML
- What's XML, and why should I use it?
- What's a well-formed document?
- What's the difference between XML and HTML?
- What's the difference between HTML and XHTML?
- Can I use XML in a browser?
- Should I use elements or attributes for my document?
- What's a namespace?
- Where can I get an XML parser?
- What's the difference between a well-formed document and a valid document?
- What's a validating parser?
- Should I use DOM or SAX for my application?
- How can I stop a SAX parser before it has parsed the entire document?
- 2005 Predictions
- 2006 Predictions
- Nick's Book Picks
If you build a web service and nobody accesses it, have you really built anything?
In other words, once you have your web services built and ready for users, how do you let people know about it? The answer is the Universal Description, Discovery, and Integration (UDDI) Business Registry.
UDDI is a protocol and structure that enables business owners to register themselves, their companies, and their available services so that potential users can find them. A UDDI registry includes information on the "business entity", or company itself, as well as one or more contacts and any available services. For services, a UDDI registry includes a "technical model", also known as a tModel, which points to information a designer needs in order to build a client to access the service, as well as a separate "instance info" item, which might include information such as a WSDL file.
For example, if you sold widgets and you provided a widget lookup service and a widget purchase service via a SOAP web service, you could register your company with a UDDI registry. Users looking for widgets could then find your information and choose from the potential ways to contact you. They might use the business entity information to write to you, or choose a contact and call you, or look at the tModel and, discovering a WSDL file that describes the service, automatically generate a client.
A UDDI registry is useful because it enables users to find a service based on the company, the industry, or the type of service being offered.
When you're dealing with UDDI, it's important to understand which UDDI registry you're dealing with. "The" UDDI registry typically refers to the UDDI Business Registry, a group of global registries run by companies such as Microsoft and IBM. These are meant to be a single repository, and information is mirrored between these nodes at various intervals. To publicize your service to the world, this is where you'll want to list it.
On the other hand, UDDI can also be used locally. For example, it's been built into Microsoft Windows 2003 as an optional service, enabling you to publish and share web services easily within your organization.
Services are normally designed either for machine or for human access, but UDDI is interesting because you can easily do both. By visiting the UBR, you can enter information in a human-readable form explainign what information you're looking for. You can search by company name, by service, or by other information such as the companys D.U.N.S. number. Once you've located the company or the service, you can get more information, such as the WSDL file, if it's been added to the registry.
On the other hand, UDDI has been designed with an eye toward programmatic access. Both Java and C# have tools that enable you to easily access the database, as you can see in the resources. In fact, some tools, such as IBM's WebSphere Studio Application Developer (and its open-source version, Eclipse) and Visual Studio.NET, have been specifically designed to use UDDI, so you can easily integrate it into your web services strategy.
In other words, once you have your web services built and ready for users, how do you let people know about it? The answer is the Universal Description, Discovery, and Integration (UDDI) Business Registry.
UDDI is a protocol and structure that enables business owners to register themselves, their companies, and their available services so that potential users can find them. A UDDI registry includes information on the "business entity", or company itself, as well as one or more contacts and any available services. For services, a UDDI registry includes a "technical model", also known as a tModel, which points to information a designer needs in order to build a client to access the service, as well as a separate "instance info" item, which might include information such as a WSDL file.
For example, if you sold widgets and you provided a widget lookup service and a widget purchase service via a SOAP web service, you could register your company with a UDDI registry. Users looking for widgets could then find your information and choose from the potential ways to contact you. They might use the business entity information to write to you, or choose a contact and call you, or look at the tModel and, discovering a WSDL file that describes the service, automatically generate a client.
A UDDI registry is useful because it enables users to find a service based on the company, the industry, or the type of service being offered.
When you're dealing with UDDI, it's important to understand which UDDI registry you're dealing with. "The" UDDI registry typically refers to the UDDI Business Registry, a group of global registries run by companies such as Microsoft and IBM. These are meant to be a single repository, and information is mirrored between these nodes at various intervals. To publicize your service to the world, this is where you'll want to list it.
On the other hand, UDDI can also be used locally. For example, it's been built into Microsoft Windows 2003 as an optional service, enabling you to publish and share web services easily within your organization.
Services are normally designed either for machine or for human access, but UDDI is interesting because you can easily do both. By visiting the UBR, you can enter information in a human-readable form explainign what information you're looking for. You can search by company name, by service, or by other information such as the companys D.U.N.S. number. Once you've located the company or the service, you can get more information, such as the WSDL file, if it's been added to the registry.
On the other hand, UDDI has been designed with an eye toward programmatic access. Both Java and C# have tools that enable you to easily access the database, as you can see in the resources. In fact, some tools, such as IBM's WebSphere Studio Application Developer (and its open-source version, Eclipse) and Visual Studio.NET, have been specifically designed to use UDDI, so you can easily integrate it into your web services strategy.