A technical note is a non-normative document accompanying the UDDI Specification that provides guidance on how to use UDDI registries. The contents of these documents are not a part of the specifications. While technical notes represent the view of the OASIS UDDI Specification Technical Committee (TC) on some UDDI-related topic, they may be prospective in nature and need not document existing practice.

A best practice is a non-normative document accompanying a UDDI specification that provides guidance on how to use UDDI registries. Best practices not only represent the TC's view on some UDDI-related topic, but also represent well-established practice.  

A technical note may be written about a real implementation or application of UDDI to solve a business or technical problem, or it may be written to provide recommendations regarding interaction between UDDI and other technologies and/or standards where a widely adopted practice would benefit the Web services community.

A formal proposal to the TC is optional, but gives one the opportunity to present the idea for the submission without the need for investing the work necessary to prepare a completed work. A proposal may take the form of a simple abstract submitted to the TC mailing list, or may even be proposed as a topic of discussion at a TC meeting. The individual making the proposal may then gauge the support present in the TC for developing the work before proceeding to the next stage.

To be considered by the TC, a technical note submission must be based on a Committee Specification or OASIS Standard version of the UDDI specification. A technical note based on a future release of the UDDI specification may be created, but it will not be published until that version of the UDDI specification is released. The OASIS Intellectual Property Rights Policy applies for any submissions.

Individuals intending to submit proposals should use the official technical note template.