Library not consistent with V1.1.0 specification

[jomo02]

Describe the bug
The library is (at some parts) not consistent with the V1.1.0 specification.

Examples I have found so far:

• Optional State field information should be called informations and be mandatory
• Enum values of ErrorLevel should be fatal and warning instead of FATAL and WARNING
• NodePosition field allowedDeviationXy should be called allowedDeviationXY

This is the V1.1.0 specification I'm referring to.

[jomo02]

I found out that this library is probably implemented against the JSON Schema as 'single source of truth' as mentioned in the PDF above.
Meaning that my remarks regarding information, ErrorLevel and allowedDeviationXy can be ignored since they fit with the schema.

However, the actionStatus differs: The schema contains lower case and the library upper case enums. Also paused is missing.

[ghost]

Thanks for pointing out some of the inconsistencies between VDA 5050 specs and schemas. Yes, I followed the "single source of truth" principle specified in chapter 6 of VDA 5050 v1.1.0 PDF.

You are correct in that casing in enum ActionStatus is wrong in my implementation and that "PAUSED" is part of my schema but the official one is missing a "paused" value. Regarding the missing "paused" value I assume this is an error in the original schema as all VDA 5050 specification versions describe a PAUSED ActionState and its associated logic in their PDF documents. My library implementation is also relying on the Paused state.

I have decided to keep my current JSON schema and implementation "as is" as long as the official VDA 5050 PDF spec and JSON schema are a complete mess regarding consistency. For example, this issue states a decision taken on 2023-03-09 to rename AllowedDeviationXy to AllowedDeviationXY in the schema which contradicts the "single source of truth" principle.

You may open an issue on the official VDA 5050 repo to clarify the missing Paused state.