For instance, let's take the classic example of the interface between a driver an a car. A spec might say that a car must have a steering wheel, breaks, and accelerator, and it would specify their location relative to the driver. The car may have a clutch and stick shift. The car may not have the driver's seat behind the passenger seat. And there are certain parameters that are open to individual interpretation, like the location of the headlight control.
Some servers support full-text searching.
We are just now to the point where we have enough experience and shared understanding of the interaction between web software components to submit specifcations to a formal standardization process. There are a few key characteristics of successful specifications that I'd like to discuss, and a few key properties of a standards process that has a proven record of producing them. First, a specfication must be complete to be successful. If significant aspects are left unspecified, then there is a possibility that independent projects or products will vary in their implementation of those aspects. And Murphy's law says that possibility should be considered a certainty.