Compliance tool failed about basyx-python-sdk

[s-heppner]

The compliance tool checks the compliance to the meta-model, based on our implementation. If the check fails, most likely the .aasx-files you tried are not valid, the output of the compliance tool should point you in the direction of where the issue with the files is. If you think, there is a bug in our implementation, please specify what you encountered.

[waleedshabbir1]

For example, I have a sample JSON file that is valid as json aasx and can be loaded in another aasx server as well.
But when I check with the compliance tool it fails.

Check the file in the attachment
FestoDemoAAS.zip

[s-heppner]

When I run the compliance tool on your provided AAS, it shows the following:

Validate file against official json schema
Status.FAILED
	<LogRecord: compliance_check, 40, <redacted>\venv\lib\site-packages\basyx\aas\compliance_tool\compliance_check_json.py, 103, "'asset' is a required property

Failed validating 'required' in schema['properties']['assetAdministrationShells']['items']['allOf'][2]:
    {'properties': {'asset': {'$ref': '#/definitions/Reference'},
                    'conceptDictionaries': {'items': {'$ref': '#/definitions/ConceptDictionary'},
                                            'type': 'array'},
                    'derivedFrom': {'$ref': '#/definitions/Reference'},
                    'security': {'$ref': '#/definitions/Security'},
                    'submodels': {'items': {'$ref': '#/definitions/Reference'},
                                  'type': 'array'},
                    'views': {'items': {'$ref': '#/definitions/View'},
                              'type': 'array'}},
     'required': ['asset']}

On instance['assetAdministrationShells'][0]:
    {'assetInformation': {'assetKind': 'Instance',
                          'billOfMaterial': [{'keys': [{'idType': 'Iri',
                                                        'type': 'Submodel',
                                                        'value': 'http://acplt.org/Submodels/Assets/TestAsset/BillOfMaterial'}]}],
                          'globalAssetId': {'keys': [{'idType': 'Iri',
                                                      'type': 'Asset',
                                                      'value': 'https://acplt.org/Test_Asset'}]}},
     'idShort': 'FestoDemoAAS',
     'identification': {'id': 'https://example.com/ids/aas/3235_8090_6012_8932',
                        'idType': 'Iri'},
     'modelType': {'name': 'AssetAdministrationShell'},
     'submodels': [{'keys': [{'idType': 'Iri',
                              'type': 'Submodel',
                              'value': 'https://example.com/ids/sm/1145_8090_6012_5097'}]},
                   {'keys': [{'idType': 'Iri',
                              'type': 'Submodel',
                              'value': 'https://example.com/ids/sm/4445_8090_6012_7409'}]},
                   {'keys': [{'idType': 'Iri',
                              'type': 'Submodel',
                              'value': 'https://example.com/ids/sm/2110_9090_6012_8448'}]},
                   {'keys': [{'idType': 'Iri',
                              'type': 'Submodel',
                              'value': 'https://example.com/ids/sm/5410_9090_6012_0950'}]},
                   {'keys': [{'idType': 'Iri',
                              'type': 'Submodel',
                              'value': 'https://example.com/ids/sm/2402_1191_1022_1090'}]}]}">

This tells us, that the attribute asset is missing in the AAS FestoDemoAAS with ID https://example.com/ids/aas/3235_8090_6012_8932.
According to the specification Details of the Asset Administration Shell Part 1 v2.0.1 page 58, this attribute is mandatory:

Because of that, the compliance check fails.

[waleedshabbir1]

I think the file I provided uses v3
Details of the Asset Administration Shell Part 1 v3

Does this means that compliance tool will only check the compliance with version 2 ?

[jkhsjdhjs]

The compliance tool uses the SDK, thus it only checks compliance with the version the SDK implements. The main branch currently implements DotAAS v2.0.1, a version for V3.0RC02 is currently in preparation, see #18.