Transparancy about validation (checkpoints)

foprs commented 7 months ago

I did some testing (AASX-File, Package Explorer V3.0 generated) with this great new service and got some questions.

1) A test failed due to missing concept description (no CD in the AASX). Is at least one CD mandatory? Is this specified somewhere? 2) I tested an AAS and got the protocol below

Is there a list of check points that are checkend by this service and that could be referenced in the protocol?
In the protocol there is not clear what the items are and what the problem is

I am aware that this is still in development. So this issue is just to give early feedback to you.

A transparent list with all checks that are performed would be helpful!

otto-ifak commented 5 months ago

Hello @foprs, thanks for reporting this issue.

A CD is optional, but if you provide one, it must not be empty (see https://github.com/admin-shell-io/aas-specs/blob/f4662a61cb7cdb180a779da38b409e7ead749628/schemas/json/aas.json#L584)
Multiple people reported similar problems, so we will address this in the next release

otto-ifak commented 5 months ago

Fixed by updating the underlying JSON schema library - you now get much more information when validating arrays.

admin-shell-io / aas-test-engines

Transparancy about validation (checkpoints) #4