RackML Schema v1.0.0 Namespace: http://rackml.org/schema/1-0-0 RackML is an XML vocabulary for describing rack-mounted IT infrastructure: racks, appliances, slots, components, ports, and connections. A conforming document has either a single <rack> root element (full rack layout) or a single appliance root element (standalone appliance library entry). All linear measurements are in millimetres unless stated otherwise. Angles are in degrees. Copyright (c) 2024-2026 Logistic Support Alliance, LLC. All rights reserved. Licensed under the Apache License, Version 2.0. A numeric value with an optional unit suffix for linear dimensions. Bare numbers are interpreted as millimetres. Supported suffixes: mm — millimetres (explicit, same as bare number) m — metres (1 m = 1000 mm) u — rack units (1 u = the rack's U value, default 44.45 mm) Examples: "440", "440mm", "1u", "0.8m", "44.45mm" Decimal value representing an angle in degrees. No unit suffix; the value is always in degrees. Physical face of an appliance or rack enclosure. Mounting orientation of an appliance within the rack. "front" means rails face the front of the rack; "rear" means the appliance is flipped 180 degrees. Positioning mode for an appliance inside a rack. "mounted" — snapped to a U-slot on the rail. "absolute" — free-positioned via explicit x/y/z coordinates. Abstract base type that carries the attributes common to every RackML element: human-readable name, bounding-box size, local position offset, SKU string, and weight. Extended by every concrete element type in the schema. Document-unique identifier. When present, other elements can reference this element via xs:IDREF attributes. Human-readable label for this object (e.g. "switch-01"). Names are not required to be unique but SHOULD be within their parent scope to allow unambiguous path references. Width of the bounding box (X axis). Accepts unit suffixes. Height of the bounding box (Y axis). Accepts unit suffixes. Depth of the bounding box (Z axis). Accepts unit suffixes. X-axis offset from parent origin. Accepts unit suffixes. Y-axis offset from parent origin. Accepts unit suffixes. Z-axis offset from parent origin. Accepts unit suffixes. Vendor stock-keeping unit or part number. Weight in kilograms. Bezel depth (front faceplate thickness). Accepts unit suffixes. Bezel width. Accepts unit suffixes. Top-level element describing a single equipment rack. Contains zero or more appliances, connections, and annotations. When used as the document root, represents a complete rack layout that can be rendered, analysed, or exchanged. Schema version that this document targets (e.g. "1.0.0"). Processors SHOULD check this value before parsing the remainder of the document. Number of rack units (U) in this rack. Common values: 12, 24, 42, 48. Horizontal distance between the inner edges of the front mounting posts (mm). Horizontal distance between the centres of the front mounting holes (mm). Horizontal distance between the outer edges of the front mounting posts (mm). Overall depth of the rack enclosure (mm). Physical height of one rack unit in millimetres. The EIA-310-E standard defines 1U = 44.45 mm. Omit to use the standard value. A piece of equipment installed in a rack: server, switch, UPS, patch panel, blank, etc. May also appear as the document root for appliance library entries. When used as a standalone root, the element describes a single appliance template that can be imported into a rack. Schema version (used when appliance is the document root for a library entry). Which rack face the appliance is mounted against. Positioning mode: "mounted" snaps to a U-slot; "absolute" uses explicit x/y/z coordinates. Appliance category (e.g. "server", "switch", "ups", "patch-panel", "pdu", "blank"). Rotation around local X axis in degrees. Rotation around local Y axis in degrees. Rotation around local Z axis in degrees. A receptacle inside an appliance that can accept a single component (e.g. a drive bay, expansion slot, or PSU bay). The "accepts" attribute names the component type this slot is designed for, enabling drag-and-drop compatibility checks. Component type this slot accepts (e.g. "psu", "hdd", "pcie", "fan"). Which appliance face this slot is visible from. Rotation of the slot (and its child component) around the Z axis in degrees. A removable part installed inside a slot: a power supply module, hard drive, expansion card, fan tray, etc. Components may expose their own ports (e.g. a NIC in a PCIe slot exposes network ports). Component category (e.g. "psu", "hdd", "ssd", "pcie-card", "fan"). A physical connector on an appliance or component face. Ports are the endpoints referenced by connection elements. Common port types include: Network — rj45, rj45_f, sfp, sfp+, qsfp, fiber, ethernet Power — c13, c14, c20, power, pdu Console — console, serial, management Video — hdmi, displayport, vga, dvi Other — usb, audio, coax, bnc Implementations SHOULD accept additional type values to support new connector standards without a schema revision. Connector type identifier (see element-level documentation for the list of well-known values). Appliance face this port is mounted on. When omitted, inherited from the parent slot's face. Rotation around the Z axis perpendicular to the mounting face, in degrees. A logical or physical cable connection between two ports. "from" and "to" use slash-delimited path notation to address ports (e.g. "server-01/eth1" or "switch-01/port24"). Source port path (e.g. "server-01/eth1"). Destination port path (e.g. "switch-01/port24"). Cable or medium type (e.g. "Cat6", "OM4", "Direct", "DAC"). Free-form string to accommodate the wide range of cable standards. A text annotation attached to an enclosing rack element (rack or appliance). Annotations are stored in the project and displayed in the properties panel when the parent object is selected. Unlike xs:annotation, this element carries user-authored notes rather than schema documentation. Optional document-unique identifier for this annotation. The annotation body text. Plain text; no markup. Name or identifier of the person who wrote the annotation. ISO 8601 timestamp when the annotation was created (e.g. "2026-03-15T14:30:00Z"). Set by the client at creation time.