This schema document describes the XML namespace, in a form suitable for import by other schema documents.
See http://www.w3.org/XML/1998/namespace.html and http://www.w3.org/TR/REC-xml for information about this namespace.
Note that local names in this namespace are intended to be defined only by the World Wide Web Consortium or its subgroups. The names currently defined in this namespace are listed below. They should not be used with conflicting semantics by any Working Group, specification, or document instance.
See further below in this document for more information about how to refer to this schema document from your own XSD schema documents and about the namespace-versioning policy governing this schema document.
denotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited. This name is reserved by virtue of its definition in the XML specification.
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility.
See BCP 47 at http://www.rfc-editor.org/rfc/bcp/bcp47.txt and the IANA language subtag registry at http://www.iana.org/assignments/language-subtag-registry for further information.
The union allows for the 'un-declaration' of xml:lang with the empty string.
denotes an attribute whose value is a keyword indicating what whitespace processing discipline is intended for the content of the element; its value is inherited. This name is reserved by virtue of its definition in the XML specification.
denotes an attribute whose value provides a URI to be used as the base for interpreting any relative URIs in the scope of the element on which it appears; its value is inherited. This name is reserved by virtue of its definition in the XML Base specification.
See http://www.w3.org/TR/xmlbase/ for information about this attribute.
denotes an attribute whose value should be interpreted as if declared to be of type ID. This name is reserved by virtue of its definition in the xml:id specification.
See http://www.w3.org/TR/xml-id/ for information about this attribute.
denotes Jon Bosak, the chair of the original XML Working Group. This name is reserved by the following decision of the W3C XML Plenary and XML Coordination groups:
In appreciation for his vision, leadership and dedication the W3C XML Plenary on this 10th day of February, 2000, reserves for Jon Bosak in perpetuity the XML name "xml:Father".
, are installed in a secure, hidden location within your vehicle by a certified dealer .
: For those performing ISO compliance testing or software resilience training, the tool can intentionally corrupt Error Correction Code (ECC) data to simulate "bad" sectors. Modify Device Status
To run the utility portably, execute the binary from an . Note that ATATool requires a direct connection to a native PATA or SATA controller; it cannot pass low-level ATA commands through standard consumer USB-to-SATA bridge cables. Command Action Syntax Example List Connected Drives ATATOOL /LIST View HPA & DCO Status ATATOOL /INFO \\.\PhysicalDriveX Restrict Capacity via HPA ATATOOL /SETHPA10GB \\.\PhysicalDriveX Restrict Capacity via DCO ATATOOL /SETDCO10GB \\.\PhysicalDriveX Corrupt ECC (Simulate Bad Sector) ATATOOL /BADECC0 \\.\PhysicalDriveX
is a specialized, command-line utility used by digital forensics professionals, law enforcement, and security researchers to inspect, modify, and test low-level Advanced Technology Attachment (ATA) hard disk configurations from a Windows environment. Primarily designed by Data Synergy, ATATool is famous for its unique ability to manipulate hidden storage sectors—specifically the Host Protected Area (HPA) and Device Configuration Overlay (DCO) . atatool portable
The versatility of the Atatool portable power station makes it suitable for a wide range of activities. Camping and RVing
Outputs comprehensive, low-level ATA string data from the controller.
Standard SATA / Legacy PATA Controllers (USB-to-SATA bridges are strictly unsupported due to command blocking) , are installed in a secure, hidden location
Atatool Portable is a self-contained, portable version of Atatool that can be run from a USB drive or any other portable storage device. It does not require installation and can be used on any Windows machine without leaving any footprint.
If a drive contains an active file system, altering or removing a DCO/HPA will shift block layouts and potentially corrupt partition geometry. Always test workflows on non-production, disposable media first.
: In digital investigations, ATATool is used to check for data hidden in HPAs, which can be a common tactic for concealing information from standard forensic imaging tools. Target Audience and Accessibility Note that ATATool requires a direct connection to
Resets factory maximum sector settings modified by overlay profiles. /FREEZELOCKDCO \\.\PhysicalDrive1
Artificially create disk errors for software stress testing. ATA Information
Unlike standard partition managers or diagnostic software that interface only with volumes exposed by the operating system, ATATool sends commands directly to the drive controller. This grants access to areas of a hard disk drive (HDD) or solid-state drive (SSD) that are normally invisible to both Windows and the end-user.
refers to the standalone deployment format of Data Synergy ATATool , a specialized command-line utility used to view and modify hard drive firmware configurations directly from a Microsoft Windows environment . Unlike mainstream hard drive diagnostics, ATATool provides deep, low-level access to hidden hard drive structures like the Host Protected Area (HPA) and Device Configuration Overlay (DCO). Because it requires no installation, the portable version can run directly from a USB triage drive, making it a critical asset for digital forensics, hardware security research, and data recovery operations. Core Technical Capabilities
In keeping with the XML Schema WG's standard versioning policy, this schema document will persist at http://www.w3.org/2009/01/xml.xsd.
At the date of issue it can also be found at http://www.w3.org/2001/xml.xsd.
The schema document at that URI may however change in the future, in order to remain compatible with the latest version of XML Schema itself, or with the XML namespace itself. In other words, if the XML Schema or XML namespaces change, the version of this document at http://www.w3.org/2001/xml.xsd will change accordingly; the version at http://www.w3.org/2009/01/xml.xsd will not change.
Previous dated (and unchanging) versions of this schema document are at: