This standard specifies the AT Attachment Interface betweenhost systems and storage devices. It provides a common attachment interface for systems manufacturers, system integrators, software suppliers, and suppliers of intelligent storage devices. The application environment for AT Attachment Interface is any host system that has storage devices contained within the processor enclosure. This standard defines the connectors and cables for physical interconnection between host and storage device, as well as the electrical and logical characteristics of the interconnecting signals. It also defines the operational registers within the storage device, and the commands and protocols for the operation of the storage device. This standard maintains a high degree of compatibility with the AT Attachment with Packet Interface - 5 standard (ATA/ATAPI-5), NCITS 340-2000, and while providing additional functions, is not intended to require changes to presently installed devices or existing software.
[NOTE - ANSI INCITS 172-2002 is published in HTML format. The file you will download is a .ZIP file containing all the necessary files. To view the standard, please unzip all of the files and place them into the same folder, then open the HTML file 'ANSDIT.HTM.'. This file provides links to the other sections of the standard.] ANSI INCITS 172-2002 contains concepts used in information technology. In general, concepts or terms found in an everyday non-technical dictionary are not included. Also, concepts and terms that are: a) from specialized areas of information technology, b) still in development, and c) of a parochial nature, are not necessarily incorporated in this standard. Inevitably, the rapid growth of the field of information technology precludes the standard from being exhaustive and final.
Associated with the provision and operation of a Trusted Third Party (TTP) are a number of security-related issues for which general guidance is necessary to assist business entities, developers and providers of systems and services, etc. This includes guidance on issues regarding the roles, positions and relationships of TTPs and the entities using TTP services, the generic security requirements, who should provide what type of security, what the possible security solutions are, and the operational use and management of TTP service security.
This Technical Report gives mechanisms for formally specifying the syntax of XML-based languages. For example, the syntax of XHTML 1.0 can be specified in RELAX.Compared with DTDs, RELAX provides the following advantages:?Specification in RELAX uses XML instance (i.e., document) syntax, ?RELAX provides rich datatypes, and ?RELAX is namespace-aware.The RELAX specification consists of two parts, RELAX Core and RELAX Namespace. This part of the Technical Report gives RELAX Core, which may be used to describe markup languages containing a single XML namespace. Part 2 of this Technical Report gives RELAX Namespace, which may be used to describe markup languages containing more than a single XML namespace, consisting of more than one RELAX Core document.Given a sequence of elements, a software module called the RELAX Core processor compares it against a specification in RELAX Core and reports the result. The RELAX Core processor can be directly invoked by the user, and can also be invoked by another software module called the RELAX Namespace processor.RELAX may be used in conjunction with DTDs. In particular, notations and entities declared by DTDs can be constrained by RELAX.This part of the Technical Report also gives a subset of RELAX Core, which is restricted to DTD features plus datatypes. This subset is very easy to implement, and with the exception of datatype information, conversion between this subset and XML DTDs results in no information loss.