<font face="Verdana">[This introduc
tion is not part of IEEE Std 1226.3-1998, IEEE Standard for Software Inte
RFace for Resource Management<br/>for A Broad-Based Environment for Test (ABBET).]<br/>In the course of developing IEEE Std 1226-1993, A Broad-Based Environment for Test (ABBET), it was<br/>determined that multiple standards would be required to define the various ABBET functions and interfaces.<br/>These standards consist of the Overview and Architecture Standard, numbered 1226, and a set of related<br/>component standards, numbered 1226.1 through 1226.x. This component standard, numbered 1226.3, documents<br/>the software interfaces defined by ABBET to test equipment configuration information.<br/>At the February, 1991, ABBET meeting, it was decided to document the automatic test equipment (ATE)<br/>system and instrument control in a single component standard. Deliberations subsequent to that meeting,<br/>however, revea
LED that combining the groups of interfaces into a single component standard would force<br/>implementations of the instrumentation interfaces to conform to a subset of that standard. Therefore, it was<br/>concluded that the interface groups should be documented in separate component standards, and that these<br/>standards would naturally divide at the interface between Test Equipment Description Language (TEDL)<br/>and Resource Description Language (RDL). At the Scottsdale, Arizona, meeting in May, 1991, this decision<br/>was changed, as it was decided to create three component standards for the ATE system layer: one for the<br/>resource management interfaces (referencing TEDL and RDL), one for the instrument interfaces (referencing<br/>SCPI, CIIL, etc.), and one for the instrument control bus interfaces (referencing IEEE 488, VXI, Ethernet,<br/>etc.).<br/>This standard is intended to document the interfaces to services to ATE descriptive information that would<br/>allow bridging the gap between an ABBET ATLAS level test procedure and an ATE (referred to in this standard<br/>as “ATE interface services”).</font><br/>
0