The deliverables of a A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard package consist of A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard documents and other files. A A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard package consists of at least one base A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard. Other deliverable items, as listed on this page, are optional.
Base Standard
A base A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.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 Unified Modeling Language (ISO Standard)UML or BNF. A base A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard is technology- and implementation-independent. Each ASAM A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard consists of one base A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.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 A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard in a reference-book style, and the User's Guide, which further specifies the application of the A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard.
All other A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard documents within a A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard package are associated to the base A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard, and are of one of the following types:
- Companion Standard
The notion of companion standard is typically used for application- or device-specific extensions of a base standard.
- Technology Reference
Technology references map the abstract specifications of the base standard to specific technologies, e.g. programming langages or data-base implementations.
- Transport Layer Specification
Transport layer specifications are similar to technology references, as they also provide a technology mapping. The notion of transport layer specification is used in the area of communication technologies. They provide a mapping of the base standard to specific protocol- or bus-technologies. The transport layer abstracts access of higher application layers to the lower layers of the communication system.
Model Files
Model files typically contain the object model of the A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard. A typical example of a model file in ASAM standards are Unified Modeling Language (ISO Standard)UML models created with the tool "Enterprise Architect" (.ea).
Schema Files
A formal definition of the structure and syntax of text files.Schema files define the formal structure and syntax of text files. They are used for automated A formal definition of the structure and syntax of text files.schema The process of determining that a system performs and meets the needs for identified end users.validation. Typical examples of A formal definition of the structure and syntax of text files.schema files are Extensible Markup Language (W3C Standard)XML definition files (.XML Schema Definition (W3C Standard)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 (.Interface Description Languageidl).
Example Files
Example files demonstrate a typical and A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard-compliant implementation of the A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.standard.
