See: https://github.com/RESOStandards/transport/blob/a99fb6ca307208280ac51bca1f573e89cb67b202/proposals/web-api-validation-expression.md
There was a revised specification created from RCP-19 with the goal of being more streamlined and easier to read. There were also some out-of-date examples in the original spec.
There were some additional discussions about adding more rules examples as well as improving the grammar to fix a legacy issue with () not being able to be used as an empty list due to a collision in terminals. Providers should be using LIST() and SET() accordingly to avoid parsing ambiguity. These items will be addressed as part of separate improvements in the future.
See: https://github.com/RESOStandards/transport/blob/a99fb6ca307208280ac51bca1f573e89cb67b202/proposals/web-api-validation-expression.md
There was a revised specification created from RCP-19 with the goal of being more streamlined and easier to read. There were also some out-of-date examples in the original spec.
There were some additional discussions about adding more rules examples as well as improving the grammar to fix a legacy issue with
()not being able to be used as an empty list due to a collision in terminals. Providers should be usingLIST()andSET()accordingly to avoid parsing ambiguity. These items will be addressed as part of separate improvements in the future.