Created by the Storage Networking Industry Association (SNIA), XAM facilitates the exchange of data among content-addressed storage (CAS) systems, which store archive and compliance data (often in an immutable form). XAM assigns a unique identifier (UID) and user-defined metadata to each object. Because the metadata never changes, content can still be identified if it is migrated or even moved to another system.Content Continues Below
The XAM standard is composed of three sections:
- XAM Part 1: Architecture. Document used by application programmers using the XAM application program interface (API) to create, access, manage and query reference content, as well as by storage system vendors creating vendor interface modules (VIMs) that translate XAM requests into device-specific action.
- XAM Part 2: C API. Reference document for C application development using the XAM API.
- XAM Part 3: Java API. Reference document for Java application development using the XAM API.
See also: object storage