Learn what constitutes an ASAM standard.
The deliverables of a Standard package consist of Standard documents and other files. A Standard package consists of at least one base Standard. Other deliverable items, as listed on this page, are optional.
A base Standard contains all fundamental specifications such as abstract object models, syntax definitions and functional behavior descriptions. It uses a problem- or task-oriented notation, such as UML or BNF. A base Standard is technology- and implementation-independent. Each ASAM Standard consists of one base Standard document. Some base standards at ASAM are split-up into two documents, which is the Reference Guide, which contains all formal specifications of the Standard in a reference-book style, and the User's Guide, which further specifies the application of the Standard.
All other Standard documents within a Standard package are associated to the base Standard, and are of one of the following types:
Model files typically contain the object model of the Standard. A typical example of a model file in ASAM standards are UML models created with the tool "Enterprise Architect" (.ea).
Schema files define the formal structure and syntax of text files. They are used for automated Schema Validation. Typical examples of Schema files are XML definition files (.XSD) or Google protocol buffers definition files (.proto).
Interface Definition Files
Interface definition files define programmatic interfaces, such as APIs (Application Programming Interface). They are used for automatic code generation of the standardized interface for specific programming languages. A typical example of an interface definition file is the Interface Description Language file (.IDL).
Example files demonstrate a typical and Standard-compliant implementation of the Standard.