A design/product specification does not necessarily prove that a product is correct or useful in all contexts. An item can be checked to meet a specification or stamped with a specification number: this does not mean that the item is suitable for other unredified uses. People who use the article (engineers, unions, etc.) or the article (building rules, government, industry, etc.) have a responsibility to take into account the choice of available specifications, to indicate the correct specifications, to impose compliance and to use the article correctly. Qualification validation is required. Specifications can be either “performance-based,” the term limiting the text to the indication of the performance that must be obtained by the work done, “normative” when the qualifier indicates specific criteria, such as the standards for the designation of the article, or “owner,” the qualifier indicating certain products, suppliers and even contractors that are acceptable for each volume of work. In addition, specifications can be made possible with a specific list of products “closed” or “open” to substitutions by the contractor. Most design specifications are a combination of performance-based and decency-based types that identify acceptable manufacturers and products, while defining certain design standards and criteria that need to be met. If z.B. use two applications to share Unicode data, but use different normal forms or use them incorrectly, compatible or without sharing a minimal set of interoperability specifications, errors and data loss can occur.
For example, Mac OS X has many components that only prefer or need disassembled characters (therefore, only Unicode encodings disassembled with UTF-8 are called “UTF8-MAC”). In one case, the combination of OS X errors in the processing of composite characters and file-sharing software and samba printers (letters broken down by assembled letters replaced by assembled letters when copying file names) created confusing and data-destroying interoperability problems.   Specification standards may be provided by government agencies, standards bodies (SAE, AWS, NIST, ASTM, ISO, CEN, DoD, etc.), professional associations, businesses and others. As far as specifications are concerned, UK standards are as follows: The development of formal specifications for food and drug data, with the necessary clarity and precision and sufficient for use by digital computer systems, began by some government authorities and standards bodies: the US Food and Drug Administration has issued specifications for a label of structuring products that drug manufacturers must use by warrant to electronically transmit information on a drug label.  ISO has recently made some progress in the area of food and pharmaceutical standards and formal specifications for controlled substance data, by publishing ISO 11238.  A requirement specification is a documented requirement or a series of documented requirements that must be met by a material, design, product, service, etc.  This is a traditional part of product design and development processes in many areas. Although there is a tendency to think that the “specifications of a drawing” deviate from the drawings in the event of a discrepancy between the text document and the drawings, the actual intent must be explicitly stated in the contract between the owner and the contractor.
The Standard AIA (American Institute of Architects) and the EJCDC (Engineering Joint Contract Documents Documents Committee) stipulate that the drawings and specifications are complementary and together provide the information necessary for a complete installation.