You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After discussion at #832 and in #848 we have agreed the following:
JSON Schema ensures that CALM is structurally correct by enforcing the appropriate schema, however it does not necessarily meant that it is valid calm. Examples of this in calm include naming nodes in relationships is incorrect if the node is not in the architecture.
calm validate ensures that the appropriate business logic for CALM is enforced. Where the solution for ensuring valid JSON schema results in a more complex user experience, validating using calm validate is required.
In summary, a document is only valid CALM if it passes both JSON Schema validation and CALM validation via the CLI.
Support Question
Does Having a Valid JSON Schema mean that something is valid CALM?
A discussion for our office hours as we start to look at some changes that will challenge this question.
The text was updated successfully, but these errors were encountered: