List of rules:

rule name	ASAM_003 [3.9]
severity	error
runtime relevance	false
short description	Every SHORT-NAME must match the regular expression [a-zA-Z0-9_]+.
full description	A SHORT-NAME must only contain digits, letters and underscores '_'.

rule name	ASAM_004 [3.9]
severity	error
runtime relevance	true
short description	A DIAG-COMM must only reference COMPARAMs that reside in a COMPARAM-SPEC of the supported PROTOCOLs.
full description	A DIAG-COMM must only reference COMPARAMs that reside in a COMPARAM-SPEC of the supported PROTOCOLs. If PROTOCOL-SNREFS is set, all supported PROTOCOLs are listed there and no PROTOCOL is supported implicitly. If PROTOCOL-SNREFS is not set, then all PROTOCOLs within the current layer hierarchy are supported.

rule name	ASAM_005 [3.8]
severity	warn
runtime relevance	true
short description	SYNTAX within PROG-CODE must match one of the values 'JAVA', 'CLASS' or 'JAR'.
full description	SYNTAX within PROG-CODE must match one of the values 'JAVA', 'CLASS' or 'JAR'.

rule name	ASAM_006 [3.9]
severity	warn
runtime relevance	true
short description	If SYNTAX is neither 'JAVA' nor 'CLASS' ENTRYPOINT must be specified, otherwise it must not be set.
full description	If SYNTAX is neither 'JAVA' nor 'CLASS' ENTRYPOINT must be specified, otherwise it must not be set.

rule name	ASAM_007 [3.9]
severity	error
runtime relevance	true
short description	MATCHING-REQUEST-PARAM must refer to a byte position that is not outside the corresponding REQUESTs range.
full description	REQUEST-BYTE-POS added to BYTE-LENGTH must be less than or equal to the request byte length belonging to the same DIAG-COMM.

rule name	ASAM_008 [3.10]
severity	error
runtime relevance	true
short description	The PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP of a SYSTEM parameter must correspond to the SYSPARAM attribute.
full description	BASE-DATA-TYPE at PHYSICAL-TYPE of the referenced DOP of a SYSTEM parameter must be A_BYTEFIELD in case of SYSPARAM=TESTERID or SYSPARAM=USERID and A_UINT32 otherwise.

rule name	ASAM_009 [3.8]
severity	error
runtime relevance	true
short description	Value of BIT-LENGTH must be greater than 0.
full description	Value of BIT-LENGTH must be greater than 0.

rule name	ASAM_010 [3.8]
severity	error
runtime relevance	true
short description	Value of BIT-POSITION must be less than 8.
full description	Value of BIT-POSITION must be less than 8.

rule name	ASAM_011 [3.9]
severity	error
runtime relevance	false
short description	The attributes DISPLAY-RADIX and PRECISION of PHYSICAL-TYPE must only be set if the BASE-DATA-TYPE is A_UINT32 or respectively A_FLOAT32 or A_FLOAT64.
full description	The attributes DISPLAY-RADIX and PRECISION of PHYSICAL-TYPE must only be set if the BASE-DATA-TYPE is A_UINT32 or respectively A_FLOAT32 or A_FLOAT64.

rule name	ASAM_012 [3.9]
severity	error
runtime relevance	true
short description	MIN-LENGTH must be less than or equal to MAX-LENGTH.
full description	DIAG-CODED-TYPE/MIN-LENGTH must be less than or equal to DIAG-CODED-TYPE/MAX-LENGTH.

rule name	ASAM_014 [3.8]
severity	error
runtime relevance	true
short description	Ranges of SCALE-CONSTRs within a common INTERNAL-CONSTRS must not overlap.
full description	Ranges of SCALE-CONSTRs within a common INTERNAL-CONSTRS must not overlap.

rule name	ASAM_015 [3.9]
severity	error
runtime relevance	true
short description	MIN-NUMBER-OF-ITEMS must be less than or equal to MAX-NUMBER-OF-ITEMS.
full description	MIN-NUMBER-OF-ITEMS at END-OF-PDU-FIELD must be lower than or equal to MAX-NUMBER-OF-ITEMS.

rule name	ASAM_016 [3.8]
severity	error
runtime relevance	true
short description	For every CASE LOWER-LIMIT must be less than or equal to UPPER-LIMIT.
full description	For every MUX' CASE and DEFAULT-CASE LOWER-LIMIT must be less than or equal to UPPER-LIMIT.

rule name	ASAM_017 [3.8]
severity	error
runtime relevance	true
short description	The DOP referenced by DETERMINE-NUMBER-OF-ITEMS must have PHYSICAL-TYPE/BASE-DATA-TYPE set to A_UINT32.
full description	The DOP referenced by a DYNAMIC-LENGTH-FIELD/DETERMINE-NUMBER-OF-ITEMS must have PHYSICAL-TYPE/BASE-DATA-TYPE = A_UINT32.

rule name	ASAM_018 [3.8]
severity	error
runtime relevance	true
short description	Every TROUBLE-CODE must be unique inside of one DTC-DOP.
full description	Every TROUBLE-CODE must be unique inside of one DTC-DOP.

rule name	ASAM_019 [3.15]
severity	error
runtime relevance	true
short description	A PARAM, which is referenced by an ENV-DATA-DESC, must refer to a DATA-OBJECT-PROP or DTC-DOP with PHYSICAL-TYPE/BASE-DATA-TYPE set to A_UINT32.
full description	A PARAM, which is referenced by an ENV-DATA-DESC, must refer to a DATA-OBJECT-PROP or DTC-DOP with PHYSICAL-TYPE/BASE-DATA-TYPE set to A_UINT32.

rule name	ASAM_020 [3.10]
severity	error
runtime relevance	true
short description	ALL-VALUE must not occur more than once per ENV-DATA-DESC.
full description	Only one ENV-DATA with set ALL-VALUE element is allowed per ENV-DATA-DESC.

rule name	ASAM_021 [3.8]
severity	error
runtime relevance	true
short description	All DTC-VALUEs must be unique.
full description	Every ENV-DATA/DTC-VALUE must be unique inside one ENV-DATA-DESC.

rule name	ASAM_022 [3.9]
severity	error
runtime relevance	true
short description	The parameter referenced by COMM-RELATION via IN-/OUT-PARAM-IF-SNREF must exist at the referenced DIAG-COMM.
full description	The parameter referenced by COMM-RELATION via IN-/OUT-PARAM-IF-SNREF must exist at the DIAG-COMM which is also referenced by COMM-RELATION. If the referenced DIAG-COMM is a DIAG-SERVICE, the IN-PARAM-IF-SNREF must exist in the REQUEST referenced by DIAG-SERVICE and the OUT-PARAM-IF-SNREF must exist in one of the POS-RESPONSEs. If the DIAG-COMM is a SINGLE-ECU-JOB, then the IN-PARAM-IF-SNREF must exist among its INPUT-PARAMS and the OUT-PARAM-IF-SNREF among its OUTPUT-PARAMS.

rule name	ASAM_023 [3.12]
severity	warn
runtime relevance	true
short description	The parameter referenced by MATCHING-PARAMETER via OUT-PARAM-IF-SNREF must exist in all POS-RESPONSEs of the referenced DIAG-COMM.
full description	The parameter referenced by MATCHING-PARAMETER via OUT-PARAM-IF-SNREF must exist in all POS-RESPONSEs of the referenced DIAG-COMM.

rule name	ASAM_024 [3.8]
severity	error
runtime relevance	true
short description	ODXLINKs in a COMPARAM-SPEC must not use the DOCREF attribute.
full description	ODXLINKs in a COMPARAM-SPEC must not use the DOCREF attribute.

rule name	ASAM_025 [3.9]
severity	warn
runtime relevance	true
short description	The parameter referenced by MATCHING-COMPONENT must exist in the referenced DIAG-SERVICE or SINGLE-/MULTIPLE-ECU-JOB.
full description	If MATCHING-COMPONENT references a DIAG-SERVICE, the parameter referenced via OUT-PARAM-IF-SNREF must exist in all of its POS-RESPONSEs. If a SINGLE- or MULTIPLE-ECU-JOB is referenced, then the parameter must exist in its OUTPUT-PARAMS.

rule name	ASAM_027 [3.10]
severity	error
runtime relevance	true
short description	The target of a LOGICAL-LINK must be unambiguous.
full description	A LOGICAL-LINK that references a BASE-VARIANT which inherits from several PROTOCOLs (directly or indirectly from FUNCTIONAL-GROUPs) must also reference one of these PROTOCOLs or one of these FUNCTIONAL-GROUPs, so its target becomes unambiguous.

rule name	ASAM_028 [3.12]
severity	error
runtime relevance	true
short description	The parameter referenced by IDENT-DESC must exist.
full description	If IDENT-DESC references a DIAG-SERVICE the parameter referenced by OUT-PARAM-IF-SNREF must exist in all POS-RESPONSEs and if IDENT-DESC references a SINGLE-ECU-JOB it must exist in its OUTPUT-PARAMs.

rule name	ASAM_029 [3.9]
severity	error
runtime relevance	true
short description	LAYER-REF must only point to BASE- or ECU-VARIANT.
full description	Only BASE-VARIANT and ECU-VARIANT are valid targets for LAYER-REF in ECU-MEM-CONNECTOR.

rule name	ASAM_030 [3.8]
severity	warn
runtime relevance	true
short description	DOP-BASE elements defined in a MULTIPLE-ECU-JOB-SPEC must not set the IS-HIGHLOW-BYTE-ORDER attribute.
full description	Within a MULTIPLE-ECU-JOB-SPEC the attribute IS-HIGHLOW-BYTE-ORDER must remain unset for all DOP-BASE elements (=DATA-OBJECT-PROPs, all COMPLEX-DOPs, DTC-DOPs).

rule name	ASAM_031 [3.13]
severity	error
runtime relevance	true
short description	ODXLINK must only point to visible elements.
full description	ODXLINK must only point to elements that are visible from the current layer through inheritance or import.

rule name	ASAM_032 [3.9]
severity	error
runtime relevance	true
short description	Cyclic references are not allowed.
full description	No direct or indirect cycles must arise from the use of ODXLINKs.

rule name	ASAM_033 [3.10]
severity	error
runtime relevance	true
short description	ODXLINK must reference an existing element.
full description	ODXLINK must reference an existing element.

rule name	ASAM_035 [3.9]
severity	error
runtime relevance	false
short description	PHYSICAL-DEFAULT-VALUE VALUE must only exist if a DATA-OBJECT-PROP is referenced.
full description	PHYSICAL-DEFAULT-VALUE in PARAM of type VALUE must only exist if the referenced DOP-BASE element is a DATA-OBJECT-PROP.

rule name	ASAM_036 [3.9]
severity	error
runtime relevance	true
short description	A SHORT-NAME must not have more than 128 characters.
full description	A SHORT-NAME must not have more than 128 characters.

rule name	ASAM_038 [3.8]
severity	error
runtime relevance	true
short description	PHYSICAL-TYPE/BASE-DATA-TYPE of DTC-DOP must be A_UINT32.
full description	The BASE-DATA-TYPE of the PHYSICAL-TYPE of a DTC-DOP must always be set to A_UINT32.

rule name	ASAM_039 [3.9]
severity	error
runtime relevance	true
short description	Every DIAG-LAYER (except PROTOCOL and ECU-SHARED-DATA) must inherit from a PROTOCOL.
full description	At least one PROTOCOL must exist in the inheritance hierarchy of every DIAG-LAYER. For ECU-SHARED-DATA this rule does not apply.

rule name	ASAM_041 [3.10]
severity	error
runtime relevance	false
short description	REQUEST and RESPONSE must not have more than one PARAM with SEMANTIC=SERVICE-ID each.
full description	REQUEST and RESPONSE must not have more than one PARAM which has its SEMANTIC attribute set to SERVICE-ID.

rule name	ASAM_042 [3.8]
severity	error
runtime relevance	false
short description	IS-HIGHLOW-BYTE-ORDER must not be set, if the DIAG-CODED-TYPE is not of type LEADING-LENGTH-INFO-TYPE and BASE-DATA-TYPE is A_BYTEFIELD, A_ASCIISTRING or A_UTF8STRING.
full description	IS-HIGHLOW-BYTE-ORDER must not be set, if the BASE-DATA-TYPE of the DIAG-CODED-TYPE is A_BYTEFIELD, A_ASCIISTRING or A_UTF8STRING or else the DIAG-CODED-TYPE must be of type LEADING-LENGTH-INFO-TYPE.

rule name	ASAM_043 [3.9]
severity	error
runtime relevance	true
short description	INTERNAL-CONSTR is only allowed for ordered types.
full description	INTERNAL-CONSTR must only be specified if the BASE-DATA-TYPE of the DIAG-CODED-TYPE is an ordered type. Ordered types are A_BYTEFIELD, A_INT32, A_UINT32, A_FLOAT32 and A_FLOAT64.

rule name	ASAM_044 [3.9]
severity	error
runtime relevance	true
short description	The DIAG-CODED-TYPE of the DOP referenced by SWITCH-KEY must be a STANDARD-LENGTH-TYPE.
full description	The DIAG-CODED-TYPE of the DATA-OBJECT-PROP referenced by SWITCH-KEY in MUX must be of type STANDARD-LENGTH-TYPE.

rule name	ASAM_046 [3.8]
severity	error
runtime relevance	true
short description	If no CASES are specified in a MUX a DEFAULT-CASE must be given.
full description	If no CASES are specified in a MUX then a DEFAULT-CASE must be given.

rule name	ASAM_047 [3.9]
severity	error
runtime relevance	true
short description	COMPARAM-REFs within a common COMPARAM-REFS wrapper must be unique.
full description	COMPARAM-REFs within a common COMPARAM-REFS wrapper must not reference the same COMPARAM multiple times.

rule name	ASAM_048 [3.10]
severity	error
runtime relevance	false
short description	No DIAG-COMMs with IS-MANDATORY=true may be excluded with NOT-INHERITED-DIAG-COMM.
full description	No mandatory DIAG-COMMs (IS-MANDATORY=true) may be excluded from inheritance via NOT-INHERITED-DIAG-COMM.

rule name	ASAM_049 [3.10]
severity	error
runtime relevance	false
short description	A final DIAG-COMM must not be overwritten.
full description	A DIAG-COMM which has its IS-FINAL attribute set to true must not be overwritten.

rule name	ASAM_050 [3.8]
severity	error
runtime relevance	true
short description	DIAG-LAYERs must establish only allowed inheritance relationships.
full description	DIAG-LAYERs must establish only permitted inheritance relationships. Permitted relationships are: Every DIAG-LAYER type except ECU-SHARED-DATA may inherit from arbitrary number of ECU-SHARED-DATAs. A FUNCTIONAL-GROUP may inherit from an arbitrary number of PROTOCOLs. A BASE-VARIANT may inherit from an arbitrary number of FUNCTIONAL-GROUPs and PROTOCOLs. An ECU-VARIANT may inherit from exactly one BASE-VARIANT.

rule name	ASAM_052 [3.8]
severity	error
runtime relevance	true
short description	A COMPU-METHOD of CATEGORY TAB-INTP must have a numerical LOWER-LIMIT and no UPPER-LIMIT in every COMPU-SCALE.
full description	A COMPU-METHOD of CATEGORY TAB-INTP must have a numerical LOWER-LIMIT and no UPPER-LIMIT in every COMPU-INTERNAL-TO-PHYS//COMPU-SCALE.

rule name	ASAM_053 [3.8]
severity	error
runtime relevance	true
short description	A COMPU-METHOD of CATEGORY COMPUCODE must have a PROG-CODE in COMPU-INTERNAL-TO-PHYS.
full description	A COMPU-METHOD of CATEGORY COMPUCODE must have a PROG-CODE in COMPU-INTERNAL-TO-PHYS.

rule name	ASAM_054 [3.9]
severity	error
runtime relevance	true
short description	A UNIT must be specified completely.
full description	If a UNIT specifies one of the elements PHYSICAL-DIMENSION-REF, FACTOR-SI-TO-UNIT and OFFSET-SI-TO-UNIT, then the remaining two must be specified too.

rule name	ASAM_055 [3.8]
severity	error
runtime relevance	true
short description	No DIAG-LAYER must inherit from another DIAG-LAYER and simultaneously import it.
full description	No DIAG-LAYER must inherit from another DIAG-LAYER and simultaneously import it.

rule name	ASAM_056 [3.17]
severity	error
runtime relevance	true
short description	SHORT-NAMEs must be unique within their specified NAMESPACES.
full description	SHORT-NAMEs must be unique within their specified NAMESPACES. This rule also applies for elements that are imported via ODXLINK in a proxy wrapper. Proxy wrappers are: DIAG-COMM-PROXY, DTC-PROXY, ENV-DATA-PROXY, DIAG-VARIABLE-PROXY and TABLE-ROW.

rule name	ASAM_057 [3.11]
severity	error
runtime relevance	true
short description	Each SCALE-CONSTR must fit into the corresponding INTERNAL-CONSTR.
full description	Each range of SCALE-CONSTR must fit into the INTERNAL-CONSTR range.

rule name	ASAM_058 [3.10]
severity	error
runtime relevance	true
short description	The DIAG-COMM, referenced by ACCESS-LEVEL, COMM-RELATION, DIAG-SERVICE or MATCHING-PARAMETER must be visible.
full description	ACCESS-LEVEL, COMM-RELATION, DIAG-SERVICE and MATCHING-PARAMETER may only reference a DIAG-COMM which resides in the enclosing layers inheritance hierarchy.

rule name	ASAM_059 [3.9]
severity	error
runtime relevance	true
short description	BASE-DATA-TYPE of DIAG-CODED- and PHYSICAL-TYPE of a DATA-OBJECT-PROP with COMPU-METHOD/CATEGORY=IDENTICAL must be identical.
full description	BASE-DATA-TYPE of DIAG-CODED-TYPE and PHYSICAL-TYPE of a DATA-OBJECT-PROP must be identical if COMPU-METHOD/CATEGORY is IDENTICAL. String types are an exception to this rule - they are regarded compatible among each other.

rule name	ASAM_060 [3.9]
severity	error
runtime relevance	true
short description	The BASE-DATA-TYPEs of DIAG-CODED- and PHYSICAL-TYPE must be suitable for the COMPU-METHOD/COMPU-CATEGORY.
full description	BASE-DATA-TYPEs of DIAG-CODED-TYPE and PHYSICAL-TYPE must be numeric if COMPU-METHOD/COMPU-CATEGORY is LINEAR, SCALE-LINEAR, TAB-INTP, RAT-FUNC or SCALE-RAT-FUNC.

rule name	ASAM_061 [3.9]
severity	error
runtime relevance	true
short description	PHYSICAL-TYPE/BASE-DATA-TYPE must be A_UNICODE2STRING if COMPU-CATEGORY is TEXTTABLE.
full description	PHYSICAL-TYPE/BASE-DATA-TYPE must be A_UNICODE2STRING if COMPU-CATEGORY is TEXTTABLE.

rule name	ASAM_062 [3.10]
severity	error
runtime relevance	true
short description	DIAG-CODED-TYPE/BASE-DATA-TYPE must be A_INT32, A_UINT32, A_UNICODE2STRING, A_ASCIISTRING, A_UTF8STRING or A_BYTEFIELD if COMPU-CATEGORY is TEXTTABLE.
full description	DIAG-CODED-TYPE/BASE-DATA-TYPE must be A_INT32, A_UINT32, A_UNICODE2STRING, A_ASCIISTRING, A_UTF8STRING or A_BYTEFIELD if COMPU-CATEGORY is TEXTTABLE.

rule name	ASAM_063 [3.9]
severity	warn
runtime relevance	false
short description	If COMPU-METHOD/CATEGORY is IDENTICAL, then no conversion method must be defined.
full description	Neither COMPU-INTERNAL-TO-PHYS nor COMPU-PHYS-TO-INTERNAL must be defined if COMPU-METHOD/CATEGORY is IDENTICAL.

rule name	ASAM_064 [3.9]
severity	error
runtime relevance	true
short description	No more than one COMPU-SCALE is allowed if CATEGORY is LINEAR or RAT-FUNC.
full description	No more than one COMPU-SCALE is allowed if CATEGORY is LINEAR or RAT-FUNC.

rule name	ASAM_068 [3.11]
severity	error
runtime relevance	false
short description	OUT-PARAM-IF-SNREF inside an IDENT-DESC must refer to a DATA-OBJECT-PROP.
full description	OUT-PARAM-IF-SNREF inside an IDENT-DESC must refer to a DATA-OBJECT-PROP.

rule name	ASAM_069 [3.9]
severity	error
runtime relevance	false
short description	TYPE of all IDENT-VALUES in a common IDENT must be identical.
full description	The value of the TYPE attribute of all IDENT-VALUES in a common EXPECRED-IDENT must be identical.

rule name	ASAM_070 [3.10]
severity	error
runtime relevance	false
short description	The TYPE of all IDENT-VALUEs of an IDENT which is referenced by an IDENT-DESC must match the PHYSICAL-TYPE/BASE-DATA-TYPE of the DOP referenced by IN-/OUT-PARAM-IF-SNREF.
full description	The datatype which is specified by the TYPE attribute of IDENT-VALUE must match the BASE-DATA-TYPE of the PHYSICAL-TYPE of the DOP belonging to the parameter which is referenced via IN-/OUT-PARAM-IF-SNREF by an IDENT-DESC for all IDENT-VALUEs of an IDENT which is also referenced by the IDENT-DESC (in ECU-MEM-CONNECTOR).

rule name	ASAM_071 [3.9]
severity	error
runtime relevance	false
short description	The START-ADDRESS of an ADDRDEF-PHYS-SEGMENT must be less or equal to END-ADDRESS.
full description	The START-ADDRESS of an ADDRDEF-PHYS-SEGMENT must be less or equal to END-ADDRESS.

rule name	ASAM_072 [3.9]
severity	error
runtime relevance	false
short description	SOURCE-START-ADDRESS in CHECKSUM must be less or equal to SOURCE-END-ADDRESS.
full description	SOURCE-START-ADDRESS in CHECKSUM must be less or equal to SOURCE-END-ADDRESS.

rule name	ASAM_073 [3.9]
severity	error
runtime relevance	false
short description	FILTER-START in ADDRDEF-FILTER must be less or equal to FILTER-END.
full description	FILTER-START in ADDRDEF-FILTER must be less or equal to FILTER-END.

rule name	ASAM_074 [3.9]
severity	error
runtime relevance	false
short description	SOURCE-START-ADDRESS in SEGMENT must be less or equal to SOURCE-END-ADDRESS.
full description	SOURCE-START-ADDRESS in SEGMENT must be less or equal to SOURCE-END-ADDRESS.

rule name	ASAM_075 [3.10]
severity	error
runtime relevance	false
short description	The values of SECURITY-METHOD, FW-CHECKSUM, VALIDITY-FOR, FW-SIGNATURE, CHECKSUM-RESULT, IDENT-VALUE and ENCRYPT-COMPRESS-METHOD must conform to their TYPE attributes.
full description	The values of SECURITY-METHOD, FW-CHECKSUM, VALIDITY-FOR, FW-SIGNATURE, CHECKSUM-RESULT, IDENT-VALUE and ENCRYPT-COMPRESS-METHOD must be interpretable as values of the datatype specified in the corresponding TYPE attribute.

rule name	ASAM_076 [3.10]
severity	error
runtime relevance	false
short description	Ranges of SEGMENTs within the same DATABLOCK may not overlap.
full description	Ranges of SEGMENTs within the same DATABLOCK may not overlap.

rule name	ASAM_077 [3.10]
severity	error
runtime relevance	false
short description	Ranges of FILTERs within the same DATABLOCK may not overlap.
full description	Ranges of FILTERs within the same DATABLOCK may not overlap.

rule name	ASAM_078 [3.10]
severity	error
runtime relevance	false
short description	SEGMENTs must be in the FILTER range of their DATABLOCK.
full description	Every SEGMENT must be completely in a range defined by one ore more FILTERs of the same DATABLOCK.

rule name	ASAM_079 [3.9]
severity	error
runtime relevance	false
short description	FILTER-SIZE inside SIZEDEF-FILTER must be greater than zero.
full description	FILTER-SIZE inside SIZEDEF-FILTER must be greater than zero.

rule name	ASAM_080 [3.9]
severity	error
runtime relevance	false
short description	UNCOMPRESSED-SIZE inside CHECKSUM must be greater than zero.
full description	UNCOMPRESSED-SIZE inside CHECKSUM must be greater than zero.

rule name	ASAM_081 [3.9]
severity	error
runtime relevance	false
short description	UNCOMPRESSED-SIZE inside SEGMENT must be greater than zero.
full description	UNCOMPRESSED-SIZE inside SEGMENT must be greater than zero.

rule name	ASAM_082 [3.9]
severity	error
runtime relevance	false
short description	SIZE inside SIZEDEF-PHYS-SEGMENT must be greater than zero.
full description	SIZE inside SIZEDEF-PHYS-SEGMENT must be greater than zero.

rule name	ASAM_083 [3.9]
severity	error
runtime relevance	false
short description	Ranges of PHYS-SEGMENTs within the same PHYS-MEM may not overlap.
full description	Ranges of PHYS-SEGMENTs within the same PHYS-MEM may not overlap.

rule name	ASAM_084 [3.9]
severity	error
runtime relevance	false
short description	If LATEBOUND-DATAFILE in DATAFILE is false the content of DATAFILE must not use wildcards ('*', '?').
full description	If LATEBOUND-DATAFILE in DATAFILE is false the content of DATAFILE must not use wildcards ('*', '?').

rule name	ASAM_085 [3.9]
severity	error
runtime relevance	true
short description	KEY-DOP-REF inside TABLE must refer to a DATA-OBJECT-PROP.
full description	KEY-DOP-REF inside TABLE must refer to a DATA-OBJECT-PROP.

rule name	ASAM_086 [3.10]
severity	error
runtime relevance	true
short description	The value of each KEY must match the KEY-DOPs PHYSICAL-TYPE.
full description	The value of each KEY in TABLE-ROW must be interpretable as a value of the datatype specified by the PHYSICAL-TYPE/BASE-DATA-TYPE of the KEY-DOP.

rule name	ASAM_087 [3.12]
severity	error
runtime relevance	true
short description	TABLE-KEY must reference a TABLE if it lies in a RESPONSE.
full description	TABLE-KEY must reference a TABLE (not a TABLE-ROW) if it lies in a RESPONSE. This rule is also applied if the TABLE-KEY is not directly defined inside a RESPONSE, but somewhere in its deeper structure.

rule name	ASAM_089 [3.9]
severity	error
runtime relevance	true
short description	TABLE-KEY-REF must reference a TABLE-KEY inside the REQUEST/RESPONSE/STRUCTURE where the referencing TABLE-STRUCT lies.
full description	TABLE-KEY-REF must reference a TABLE-KEY inside the REQUEST/RESPONSE/STRUCTURE where the referencing TABLE-STRUCT lies.

rule name	ASAM_090 [3.9]
severity	error
runtime relevance	true
short description	Parameters of type TABLE-ENTRY must only occur in STRUCTUREs which are referenced by a TABLE-ROW.
full description	Parameters of type TABLE-ENTRY must only occur in STRUCTUREs which are referenced by a TABLE-ROW.

rule name	ASAM_091 [3.10]
severity	error
runtime relevance	false
short description	The shortnames of the FUNCT-CLASSes referenced via FUNCT-CLASS-REF in DIAG-COMM must be unique among each other.
full description	The shortnames of the FUNCT-CLASSes referenced via FUNCT-CLASS-REF in DIAG-COMM must be unique among each other.

rule name	ASAM_092 [3.9]
severity	error
runtime relevance	false
short description	The shortnames of all FLASH-CLASSes referenced via FLASH-CLASS-REF in SESSION-DESC must be unique among each other.
full description	The shortnames of all FLASH-CLASSes referenced via FLASH-CLASS-REF in SESSION-DESC must be unique among each other.

rule name	ASAM_093 [3.10]
severity	error
runtime relevance	true
short description	COMPU-METHODs of DOPs used in a REQUEST must be invertible.
full description	COMPU-METHODs of DOPs used in a REQUEST must be invertible. COMPU-METHODs of CATEGORY RAT-FUNC and SCALE-RAT-FUNC must not be used in a REQUEST. COMPU-METHODs of CATEGORY LINEAR and TAB-INTP are always invertible. COMPU-METHODs of CATEGORY LINEAR are invertible if VN1 != 0 (VN1 is the coefficient of x^1 in the numerator) or COMPU-INVERSE-VALUE is specified. COMPU-METHODs of CATEGORY SCALE-LINEAR are invertible if the functional characteristics at their intersections match and the requirements for invertibility for COMPU-METHODs of CATEGORY LINEAR are met for every single scale. A COMPU-METHOD of CATEGORY TEXTTABLE is invertible if it is deterministically invertible or COMPU-INVERSE-VALUE is specified. COMPU-METHODs of CATEGORY COMPU-CODE are invertible if COMPU-PHYS-TO-INTERNAL is defined.

rule name	ASAM_096 [3.10]
severity	error
runtime relevance	true
short description	PROTOCOL-SNREFS must only occur in DIAG-COMMs that do not reside in a PROTOCOL themselves.
full description	PROTOCOL-SNREFS must only occur in DIAG-COMMs that do not reside in a PROTOCOL themselves.

rule name	ASAM_097 [3.8]
severity	error
runtime relevance	true
short description	For every CASE LOWER- and UPPER-LIMIT must correspond to the SWITCH-KEY.
full description	For every MUX' CASE and DEFAULT-CASE the values of LOWER-LIMIT and UPPER-LIMIT must correspond to the PHYSICAL-TYPE/BASE-DATA-TYPE of the SWITCH-KEYs DOP.

rule name	ASAM_098 [3.11]
severity	error
runtime relevance	true
short description	LOWER-LIMIT and UPPER-LIMIT in MUX/CASE must be the same if their datatype is A_UNICODE2STRING.
full description	LOWER-LIMIT and UPPER-LIMIT in MUX/CASE must be the same if their datatype is A_UNICODE2STRING.

rule name	ASAM_099 [3.9]
severity	error
runtime relevance	true
short description	Every TABEL-ROWs KEY must be unique inside the containing TABLE.
full description	Every TABEL-ROWs KEY must be unique inside the containing TABLE.

rule name	ASAM_100 [3.12]
severity	warn
runtime relevance	false
short description	If a DIAG-COMM is referenced by a MATCHING-PARAMETER its DIAGNOSTIC-CLASS must be VARIANTIDENTIFICATION.
full description	If a DIAG-COMM is referenced by a MATCHING-PARAMETER its DIAGNOSTIC-CLASS must be VARIANTIDENTIFICATION.

rule name	ASAM_103 [3.9]
severity	error
runtime relevance	true
short description	PARENT-REFs xsi:type attribute must conform to the actually referenced DIAG-LAYERs type.
full description	PARENT-REFs xsi:type attribute must conform to the actually referenced DIAG-LAYERs type. E.g. if a PROTOCOL is referenced xsi:type must be a PROTOCOL-REF.

rule name	ASAM_104 [3.9]
severity	error
runtime relevance	true
short description	Only one DIAG-COMM may exist for each of the DIAG-CLASS-TYPEs STARTCOMM and STOPCOMM.
full description	Only one DIAG-COMM may exist for each of the DIAG-CLASS-TYPEs STARTCOMM and STOPCOMMs.

rule name	ASAM_105 [3.10]
severity	warn
runtime relevance	true
short description	Only one DIAG-COMM with SEMANTIC = DEFAULT-FAULT-READ may exist.
full description	Only one DIAG-COMM with SEMANTIC = DEFAULT-FAULT-READ may exist.

rule name	ASAM_107 [3.9]
severity	error
runtime relevance	true
short description	A SESSION may reference a DATABLOCK only once.
full description	A SESSION may reference a DATABLOCK only once.

rule name	ASAM_108 [3.9]
severity	error
runtime relevance	true
short description	MATCHING-REQUEST-PARAM and DYNAMIC must only be used in a RESPONSE.
full description	MATCHING-REQUEST-PARAM and DYNAMIC must only be used in a RESPONSE.

rule name	ASAM_110 [3.14]
severity	error
runtime relevance	true
short description	The parameter referenced by MATCHING-PARAMETER/OUT-PARAM-IF-SNREF must exist.
full description	If DIAG-COMM-SNREF of MATCHING-PARAMETER inside a BASE-VARIANT references a DIAG-SERVICE, then the parameter referenced by OUT-PARAM-IF-SNREF must exist in at least one of its POS-RESPONSEs or respectively among one of the OUTPUT-PARAMS if DIAG-COMM-SNREF references a SINGLE-ECU-JOB.

rule name	ASAM_112 [3.10]
severity	error
runtime relevance	true
short description	PHYSICAL-TYPE/BASE-DATA-TYPE must be numeric if DATA-OBJECT-PROP references a UNIT with FACTOR-SI-TO-UNIT or OFFSET-SI-TO-UNIT.
full description	PHYSICAL-TYPE/BASE-DATA-TYPE must be numeric if DATA-OBJECT-PROP references a UNIT with FACTOR-SI-TO-UNIT or OFFSET-SI-TO-UNIT.

rule name	ASAM_113 [3.9]
severity	warn
runtime relevance	true
short description	No two PROG-CODEs with same SYNTAX may reside in the same SINGLE-ECU-JOB/MULTIPLE-ECU-JOB.
full description	No two PROG-CODEs with same SYNTAX may reside in the same SINGLE-ECU-JOB/MULTIPLE-ECU-JOB.

rule name	ASAM_114 [3.9]
severity	error
runtime relevance	true
short description	If BASE-DATA-TYPE of DIAG-CODED-TYPE is numeric then xsi:type must be STANDARD-LENGTH-TYPE or PARAM-LENGTH-INFO-TYPE.
full description	If BASE-DATA-TYPE of DIAG-CODED-TYPE is numeric then xsi:type must be STANDARD-LENGTH-TYPE or PARAM-LENGTH-INFO-TYPE.

rule name	ASAM_115 [3.10]
severity	error
runtime relevance	true
short description	LENGTH-KEY-REF must reference only LENGTH-KEY parameters inside the same PDU.
full description	LENGTH-KEY-REF must reference only LENGTH-KEY parameters inside the same PDU.

rule name	ASAM_116 [3.10]
severity	error
runtime relevance	true
short description	LENGTH-KEY must reference a simple DOP with PHYSICAL-TYPE/BASE-DATA-TYPE = A_UINT32.
full description	LENGTH-KEY must reference a simple DOP with PHYSICAL-TYPE/BASE-DATA-TYPE = A_UINT32.

rule name	ASAM_117 [3.9]
severity	error
runtime relevance	true
short description	LOWER-LIMIT and UPPER-LIMIT of COMPU-SCALEs in a COMPU-METHOD of category TEXTTABLE must be identical.
full description	LOWER-LIMIT and UPPER-LIMIT of COMPU-SCALEs in a COMPU-METHOD of category TEXTTABLE must be identical.

rule name	ASAM_118 [3.9]
severity	error
runtime relevance	true
short description	CODED-VALUE and DIAG-CODED-TYPE within RESERVED must be specified either both together or none of them.
full description	CODED-VALUE and DIAG-CODED-TYPE within RESERVED must be specified either both together or none of them.

rule name	ASAM_119 [3.10]
severity	error
runtime relevance	true
short description	DYN-DEFINED-SPEC must only reference TABLEs that have unique TABLE-ROW/KEYs regarding their SEMANTIC attribute.
full description	DYN-DEFINED-SPEC must only reference TABLEs that have unique TABLE-ROW/KEYs regarding their SEMANTIC attribute.

rule name	ASAM_120 [3.9]
severity	error
runtime relevance	true
short description	No SHORT-NAME must start with GEN3D_.
full description	No SHORT-NAME must start with GEN3D_ because this prefix is reserved for SHORT-NAMEs that are autogenerated by the runtime system.

rule name	ASAM_122 [3.9]
severity	error
runtime relevance	true
short description	LOWER-LIMIT in INTERNAL-CONSTR, SCALE-CONSTR und COMPU-SCALE must be less or equal to UPPER-LIMIT.
full description	LOWER-LIMIT in INTERNAL-CONSTR, SCALE-CONSTR und COMPU-SCALE must be less or equal to UPPER-LIMIT.

rule name	ASAM_123 [3.12]
severity	error
runtime relevance	true
short description	The value of PHYSICAL-DEFAULT-VALUE must be applicable for the PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP.
full description	The value of PHYSICAL-DEFAULT-VALUE must be interpretable as a value of the datatype specified by the PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP.

rule name	ASAM_124 [3.11]
severity	error
runtime relevance	true
short description	The value of PHYSICAL-DEFAULT-VALUE must be in the range of the referenced DOPs INTERNAL-CONSTR.
full description	The value of PHYSICAL-DEFAULT-VALUE must after its reverse calculation into an internal value be in the range of the INTERNAL-CONSTR defined by the referenced DOP.

rule name	ASAM_125 [3.10]
severity	error
runtime relevance	true
short description	The value of PHYSICAL-CONSTANT-VALUE must be applicable for the PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP.
full description	The value of PHYSICAL-CONSTANT-VALUE must be interpretable as a value of the datatype specified by the PHYSICAL-TYPE/BASE-DATA-TYPE of the referenced DOP.

rule name	ASAM_126 [3.12]
severity	error
runtime relevance	true
short description	The value of PHYS-CONSTANT-VALUE must be in the range of the referenced DOPs INTERNAL-CONSTR.
full description	The value of PHYS-CONSTANT-VALUE must after its reverse calculation into an internal value be in the range of the INTERNAL-CONSTR defined by the referenced DOP.

rule name	ASAM_127 [3.9]
severity	error
runtime relevance	true
short description	A LONG-NAME must have at most 255 characters.
full description	A LONG-NAME must have at most 255 characters.

rule name	ASAM_128 [3.9]
severity	error
runtime relevance	true
short description	SYSPARAM in SYSTEM may only carry a valid, enumerated value.
full description	SYSPARAM in SYSTEM may only carry one of these values: TIMEZONE, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, TESTERID, USERID, CENTURY and WEEK.

rule name	ASAM_129 [3.9]
severity	error
runtime relevance	true
short description	STRUCTUREs referenced by a CASE must set IS-VISIBLE = false.
full description	The STRUCTURE referenced by a CASE must have its IS-VISIBLE attribute set to false.

rule name	ASAM_130 [3.9]
severity	error
runtime relevance	true
short description	LOWER-LIMIT in COMPU-SCALE must be specified.
full description	LOWER-LIMIT in COMPU-SCALE must be specified except if COMPU-CATEGORY is LINEAR. If no UPPER-LIMIT is given, then the INTERVAL-TYPE of LOWER-LIMIT must be CLOSED.

rule name	ASAM_131 [3.11]
severity	error
runtime relevance	true
short description	CLEAR-DYN-DEF-MESSAGE-REF, READ-DYN-DEF-MESSAGE-REF und DYN-DEF-MESSAGE-REF must point to a DIAG-SERVICE with suitable DIAGNOSTIC-CLASS.
full description	CLEAR-DYN-DEF-MESSAGE-REF, READ-DYN-DEF-MESSAGE-REF und DYN-DEF-MESSAGE-REF must point to a DIAG-SERVICE with suitable DIAGNOSTIC-CLASS.

rule name	ASAM_132 [1.9]
severity	warn
runtime relevance	false
short description	Values of attributes with extendable value set shall have one of the predefined values.
full description	Values of attributes with extendable value set shall have one of the predefined values.

rule name	ASAM_133 [1.4]
severity	error
runtime relevance	true
short description	Parameters referenced by a COMM-RELATION shall not be contained within a FIELD.
full description	Parameters referenced by a DIAG-VARIABLE/COMM-RELATION shall not be indirectly contained within a FIELD.

rule name	ASAM_134 [1.5]
severity	error
runtime relevance	true
short description	The parameter referenced by MATCHING-PARAMETER, MATCHING-COMPONENT and IDENT-DESC shall not be contained within a FIELD.
full description	The parameter referenced by OUT-PARAM-IF-SNREF in MATCHING-PARAMTER, MATCHING-COMPONENT and IDENT-DESC shall not be (indirectly) contained within a FIELD.

rule name	ASAM_135 [1.4]
severity	error
runtime relevance	false
short description	It is prohibited to define elements with the same shortname like an object of the same type that has been excluded from inheritance by a parent layer.
full description	DIAG-COMMs and DIAG-VARIABLEs can be excluded from inheritance via NOT-INHERITED-DIAG-COMM or NOT-INHERITED-VARIABLE. If this is used to completly eliminate an element in a more specialized layer it must not be redefined.

rule name	ASAM_136 [1.9]
severity	error
runtime relevance	false
short description	DIAG-COMMs that are marked MANDATORY must not be excluded from inheritance.
full description	If a DiagLayer contains a mandatory (@IS-MANDATORY="true") DIAG-COMM it must not be excluded from inheritance by a more specialized layer. Exception: If a DiagLayer inherits from several other DiagLayers containing mandatory DIAG-COMMs with the same shortname, then all except one of these DIAG-COMMs must be excluded from inheritance, so that it is clear which inheritance path is to be chosen.

rule name	ASAM_137 [1.5]
severity	error
runtime relevance	false
short description	A layer must not inherit two objects of the same type and with the same shortname from several layers of the same specialisation level.
full description	A layer must not inherit two objects of the same type and with the same shortname from several layers of the same specialisation level.

rule name	ASAM_138 [1.1]
severity	error
runtime relevance	false
short description	Multiple COMPU-SCALEs of the same TEXTTABLE, that map to the same physical value, must have identical COMPU-INVERSE-VALUEs.
full description	If multiple COMPU-SCALEs of a COMPU-METHOD with COMPU-CATEGORY 'TEXTTABLE' map to the same physical value (COMPU-CONST/VT), then these COMPU-SCALEs must have identical COMPU-INVERSE-VALUEs.

rule name	ASAM_139 [1.1]
severity	error
runtime relevance	false
short description	A LOGICAL-LINK can reference a BASE-VARIANT and/or a PROTOCOL or a FUNCTIONAL-GROUP and a PROTOCOL.
full description	A LOGICAL-LINK can either reference a BASE-VARIANT alone or a PROTOCOL alone or a PROTOCOL and a BASE-VARIANT or a PROTOCOL and a FUNCTIONAL-GROUP. All other combinations are invalid.

rule name	ASAM_140 [1.3]
severity	error
runtime relevance	false
short description	COMPU-SCALEs of a DOP must cover the valid ranges of the INTERNAL-CONSTR.
full description	The COMPU-SCALEs of a DATA-OBJECT-PROP must cover at least the valid ranges (SCALE-CONSTR[@VALIDITY)="VALID") of the corresponding INTERNAL-CONSTR.

rule name	ASAM_142 [1.1]
severity	error
runtime relevance	false
short description	DIAG-SERVICEs with ADDRESSING="FUNCTIONAL" must not be defined in a BASE-VARIANT or an ECU-VARIANT.
full description	DIAG-SERVICEs with ADDRESSING="FUNCTIONAL" must not be defined in a BASE-VARIANT or an ECU-VARIANT.

rule name	ASAM_143 [1.1]
severity	error
runtime relevance	false
short description	The SESSION referenced by SESSION-DESC must exist.
full description	The SESSION referenced by ECU-MEM-CONNECTOR//SESSION-DESC via SESSION-SNREF must exist in the ECU-MEM which is referenced by ECU-MEM-CONNECTOR/ECU-MEM-REF.

rule name	ASAM_144 [1.1]
severity	error
runtime relevance	false
short description	The DIAG-COMM referenced by SESSION-DESC must exist.
full description	The DIAG-COMM referenced by SESSION-DESC in ECU-MEM-CONNECTOR must exist in all ECU-VARIANTs and BASE-VARIANTs that are referenced by the ECU-MEM-CONNECTOR.

rule name	ASAM_145 [1.0]
severity	error
runtime relevance	true
short description	BIT-LENGTH at DIAG-CODED-TYPE must match the bit-length of the float data type.
full description	In case if DIAG-CODED-TYPE is A_FLOAT32 the BIT-LENGTH must be equal to 32. In case of A_FLOAT64, the BIT-LENGTH must be equal to 64. That means that the DIAG-CODED-TYPE must be of type STANDARD-LENGTH-TYPE if BASE-DATA-TYPE is set to a float data type.

rule name	ASAM_146 [0.0]
severity	error
runtime relevance	true
short description	The wildcards '*' and '?' can only be used in CODE-FILE if attribute LATEBOUND-CODE-FILE equals 'true'.
full description	The wildcards '*' and '?' can only be used in CODE-FILE if attribute LATEBOUND-CODE-FILE equals 'true'.

rule name	ASAM_149 [1.0]
severity	error
runtime relevance	true
short description	IDENT-IF-SNREF must reference to a IDENT-IF that exists within the namespace of the ECU-MEM referenced by the ECU-MEM-CONNECTOR the IDENT-DESC is contained in.
full description	IDENT-IF-SNREF must reference to a IDENT-IF that exists within the namespace of the ECU-MEM referenced by the ECU-MEM-CONNECTOR the IDENT-DESC is contained in.

rule name	ASAM_151 [1.0]
severity	error
runtime relevance	true
short description	Each range of COMPU-SCALE must not overlap any other range.
full description

rule name	ASAM_154 [1.0]
severity	error
runtime relevance	true
short description	PHYSICAL-DEFAULT-VALUE or PHYS-CONSTANT-VALUE must match with an entry of the corresponding texttable.
full description	In case of DOP/COMPUMETHOD/TEXTTABLE the values of PHYSICAL-DEFAULT-VALUE or PHYS-CONSTANT-VALUE must match case-sensitively with an entry of the corresponding texttable.

rule name	ASAM_156 [1.0]
severity	warn
runtime relevance	true
short description	BYTE-SIZE must not be less than the total size of the included parameters. If the STRUCTURE has any dynamic components the BYTE-SIZE must not be specified.
full description	BYTE-SIZE must not be less than the total size of the included parameters. If the STRUCTURE has any dynamic components (e.g. MUX or any FIELD with dynamic length) the BYTE-SIZE must not be specified.

rule name	ASAM_157 [1.0]
severity	error
runtime relevance	true
short description	DOCREF and DOCTYPE must be specified either jointly or not at all.
full description	DOCREF and DOCTYPE must be specified either jointly or not at all.

rule name	VAX_001 [1.5]
severity	error
runtime relevance	false
short description	Check of shortnames
full description	Check of shortnames

rule name	VAX_002 [1.4]
severity	error
runtime relevance	true
short description	Check of longnames
full description	Check of longnames

rule name	VAX_003 [1.4]
severity	error
runtime relevance	true
short description	Check if IDs are unique and correct coded.
full description	Check if IDs are unique and correct coded.

rule name	VAX_004 [1.3]
severity	error
runtime relevance	true
short description	The protocol layer must contain the DOP "DOP_NRC"
full description	The protocol layer must contain the DOP "DOP_NRC"

rule name	VAX_005 [1.3]
severity	error
runtime relevance	true
short description	Usage of COMPU-SCALEs and COMPU-DEFAULT-VALUE at COMPU-METHODs except for IDENTICAL and COMPUCODE
full description	Usage of COMPU-SCALEs and COMPU-DEFAULT-VALUE at COMPU-METHODs except for IDENTICAL and COMPUCODE: 1). ERROR: COMPU-METHOD must contain at least one COMPU-SCALE, 2). ERROR: In case of STRING and BYTEFIELD the COMPU-DEFAULT-VALUE must be defined, 3). ERROR: The value range must be calculatable (not calculatable e.g. in case of FLOAT32 with BitLength != 32), 4). WARN: COMPU-DEFAULT-VALUE is redundant, if COMPU-SCALEs cover the whole internal data range

rule name	VAX_006 [1.4]
severity	error
runtime relevance	true
short description	Check of the existance of the layer referenced via PARENT-REF or IMPORT-REF
full description	Check of the existance of the layer referenced via PARENT-REF or IMPORT-REF

rule name	VAX_007 [1.5]
severity	error
runtime relevance	false
short description	Check if file name complies with Shortname + Version (3-digit number)
full description	Check if file name complies with Shortname + Version (3-digit number)

rule name	VAX_008 [1.4]
severity	error
runtime relevance	true
short description	The file referenced by CODE-FILE must exist in the PDX archive.
full description	The file referenced by CODE-FILE must exist in the PDX archive.

rule name	VAX_009 [1.5]
severity	error
runtime relevance	false
short description	Check whether COMPARAM-SPEC and PROTOCOL exist within the pdx package
full description	Check whether COMPARAM-SPEC and PROTOCOL exist within the pdx package

rule name	VAX_010 [1.5]
severity	error
runtime relevance	false
short description	For every DIAG-LAYER ADMIN-DATA, LONG-NAME and DESC must be set. For every ODX-CATEGORY except DIAG-LAYER-CONTAINER ADMIN-DATA and DESC must be set. For every ODX-CATEGORY LONG-NAME must be set.
full description	For every DIAG-LAYER ADMIN-DATA, LONG-NAME and DESC must be set. For every ODX-CATEGORY except DIAG-LAYER-CONTAINER ADMIN-DATA and DESC must be set. For every ODX-CATEGORY LONG-NAME must be set.

rule name	VAX_011 [1.3]
severity	error
runtime relevance	true
short description	Response codes in the DOP "DOP_NRC" must contain only entries froms the predefined list (defined in VAX_NRCs.xml).
full description	Response codes in the DOP "DOP_NRC" must contain only entries froms the predefined list (defined in VAX_NRCs.xml).

rule name	VAX_012 [1.4]
severity	error
runtime relevance	false
short description	Checking of SDGs at DTC
full description	Checking of SDGs at DTC

rule name	VAX_013 [1.3]
severity	error
runtime relevance	false
short description	Every ADMIN-DATA element must have at least one DOC-REVISION.
full description	Every ADMIN-DATA element must have at least one DOC-REVISION.

rule name	VAX_014 [1.6]
severity	warn
runtime relevance	false
short description	TI attributes should only contain values from a predefined list.
full description	TI attributes should only contain values from a predefined list.

rule name	VAX_015 [1.4]
severity	error
runtime relevance	true
short description	Each DIAG-COMM (service or job) must be assigned to at least one session
full description	Each DIAG-COMM (service or job) must be assigned to at least one session

rule name	VAX_016 [1.3]
severity	error
runtime relevance	true
short description	Check of the existance of the COMPARAM-SPEC referenced by a PROTOCOL
full description	Check of the existance of the COMPARAM-SPEC referenced by a PROTOCOL

rule name	VAX_017 [1.3]
severity	error
runtime relevance	true
short description	DISPLAY-TROUBLE-CODE must not be empty.
full description	DISPLAY-TROUBLE-CODE must not be empty.

rule name	VAX_018 [1.4]
severity	error
runtime relevance	true
short description	Every DTC in ECU- and BASE-VARIANT must have a LEVEL. If defined the LEVEL must have a value between 1 and 9.
full description	Every DTC in ECU- and BASE-VARIANT must have a LEVEL. If defined the LEVEL must have a value between 1 and 9.

rule name	VAX_019 [1.2]
severity	error
runtime relevance	true
short description	V and VT elements must not be empty.
full description	V and VT elements must not be empty.

rule name	VAX_020 [1.3]
severity	error
runtime relevance	true
short description	AUDIENCE/IS-AFTERMARKET and AUDIENCE/IS-AFTERSALES of an OBD-Service must not be false.
full description	AUDIENCE/IS-AFTERMARKET and AUDIENCE/IS-AFTERSALES of an OBD-Service must not be false.

rule name	VAX_021 [1.2]
severity	error
runtime relevance	true
short description	Each DIAG-LAYER-CONTAINER must contain exactly one DIAG-LAYER
full description	Each DIAG-LAYER-CONTAINER must contain exactly one DIAG-LAYER

rule name	VAX_022 [1.2]
severity	error
runtime relevance	true
short description	ECU-SHARED-DATA must not be referenced by PARENT-REF
full description	ECU-SHARED-DATA must not be referenced by PARENT-REF

rule name	VAX_023 [1.2]
severity	error
runtime relevance	true
short description	Elimination of services and variables is only allowed for BASE-VARIANTs and ECU-VARIANTs
full description	Elimination of services and variables is only allowed for BASE-VARIANTs and ECU-VARIANTs

rule name	VAX_024 [1.3]
severity	error
runtime relevance	true
short description	Overwriting of objects is only allowed for BASE-VARIANTs and ECU-VARIANTs
full description	Overwriting of objects is only allowed for BASE-VARIANTs and ECU-VARIANTs

rule name	VAX_025 [1.3]
severity	error
runtime relevance	true
short description	An ECU-VARIANT is not allowed to use objects from another ECU-VARIANT
full description	An ECU-VARIANT is not allowed to use objects from another ECU-VARIANT

rule name	VAX_026 [1.3]
severity	error
runtime relevance	true
short description	An ECU-VARIANT-PATTERN must be unique for each ECU-VARIANT
full description	An ECU-VARIANT-PATTERN must be unique for each ECU-VARIANT

rule name	VAX_027 [1.6]
severity	error
runtime relevance	false
short description	SHORT-NAME is generated from the LONG-NAME using guidelines
full description	SHORT-NAME is generated from the LONG-NAME using guidelines

rule name	VAX_028 [1.3]
severity	error
runtime relevance	true
short description	Check if each DIAG-COMM is assigned to at least one functional class
full description	Check if each DIAG-COMM is assigned to at least one functional class

rule name	VAX_029 [1.5]
severity	error
runtime relevance	false
short description	Shortname of DTCs must comply with the following pattern: "DTC_" + TROUBLE-CODE
full description	Shortname of DTCs must comply with the following pattern: "DTC_" + TROUBLE-CODE

rule name	VAX_030 [1.4]
severity	error
runtime relevance	true
short description	If the KEY-DOP owns a Compu-Method of type TEXTTABLE, the VTs of the Compu-Scales must be unique and all KEYs must be defined in the TEXTTABLE.
full description	If the KEY-DOP owns a Compu-Method of type TEXTTABLE, the VTs of the Compu-Scales must be unique and all KEYs must be defined in the TEXTTABLE.

rule name	VAX_031 [1.4]
severity	error
runtime relevance	true
short description	Checks if the V elements are of the correct type
full description	Checks if the V elements of COMPU-METHODs are of the correct type. E.g. 0.01 is not allowed if the calculation type is INT.

rule name	VAX_032 [1.3]
severity	error
runtime relevance	true
short description	In case of TEXTTABLE as KEY-DOP at each TABLE-ROW the KEY must be equal to the LONG-NAME
full description	In case of TEXTTABLE as KEY-DOP at each TABLE-ROW the value of KEY must be equal to the value of LONG-NAME

rule name	VAX_033 [1.1]
severity	error
runtime relevance	true
short description	At TABLEs with KEY-DOP of type TEXTTABLE for each TABLE-ROW/KEY exactly one COMPU-SCALE with appropriate text must exist and vice versa
full description	At TABLEs with KEY-DOP of type TEXTTABLE for each TABLE-ROW/KEY exactly one COMPU-SCALE with appropriate text (VT) must exist and vice versa, i.e. for each COMPU-SCALE of the KEY-DOP exactly one TABLE-ROW must exist with the same value of KEY