The problem was, that with V3.0RC02, an Identifer is a string. Therefore
the distinction between File-Identifier and AAS-Identifier could not be
made anymore.
As a solution, remove the option to input the already hashed
File-Identifier.

implement global and model references
rename AASReference to ModelReference
add Reference/referredSemanticId
remove redundant definitions from XML schema (AAS and IEC61360)

rename SpecificAssetId/key to SpecificAssetId/name
change type of SpecificAssetId/externalSubjectId from Reference to GlobalReference

also make it an Iterable

make CONCEPT_DICTIONARY a private member since it has been removed
from the spec

… to Reference

reflect this change in the json/xml schemata
add missing comments to protected KeyTypes enum members

In V3.0RC02 DataTypeDef has been split into DataTypeDefRdf and
DataTypeDefXsd. Since DataTypeDefRdf only consists of rdf::langString
and currently isn't used anywhere in the DotAAS specification, just
rename DataTypeDef to DataTypeDefXsd.

In V3.0RC02 the attributes `allowDuplicates` and `ordered` were removed
from `SubmodelElementCollection`. Additionally the `semanticId` of
contained elements is no longer unique. Because of that, the extra
classes `SubmodelElementCollectionOrdered`,
`SubmodelElementCollectionUnordered`,
`SubmodelElementCollectionOrderedUniqueSemanticId` and
`SubmodelElementCollectionUnorderedUniqueSemanticId` aren't needed
anymore.

Also ignore two tests which will be modified and re-enabled later.

The `item_add_hook` is a function that is called whenever items are
added to the `NamespaceSet`, even on initialization. It is supplied
to the `NamespaceSet` on initialization and allows the model class
to check constraints whenever a new item is added.

In turn re-enable the unittests that were disabled in
639b4b9.

Improve/coverage/model.datatypes

…to improve/V30RC02

Due to missing calls to the initializer function (__init__) of parent
classes, not all superclasses were correctly initialized for classes
that inherit from multiple classes (e.g. Submodel, SubmodelElement).

https://stackoverflow.com/a/16310777/4780052

Rename supplementary_semantic_id to supplemental_semantic_id, as it's
named in the spec.

Use the official description of supplemental_semantic_id from the spec
in the docstrings.

Only implement the bare minimum of list functions for ConstrainedList.
Other functions such as `append()`, `pop()` and `remove()` are inherited
from MutableSequence and implemented via `__getitem__()`, `__len__()`,
`insert()`, and `__delitem__()`.

Document Constraint AASd-118 in HasSemantics docstring.

Change type of `supplemental_semantic_id` in `__init__()` of classes
that inherit from `HasSemantics`.
Optional[ConstrainedList[Reference]] creates an ambiguity between None
and an empty list, which both correspond to no supplemental semantic ids
being present. Insead, initialize the set with an empty iterable.
Also, instead of a ConstrainedList[Reference], use Iterable[Reference]
as we don't want the users of this SDK to worry about ConstrainedList,
it should be an implementation detail.

Add item_set_hook to ConstrainedList. Similar to item_del_hook, it is
actually not necessary for the HasSemantics constraint, but I only
noticed that later when I re-read the HasSemantics constraint.

Instead of raising a ValueError when a constraint is violated, raise an
AASConstraintViolation, which is a special class of this SDK for exactly
this purpose.

Clean up the tests a bit, e.g. use pythons unittest assertion functions
instead of raising a ValueError on error. Also split the tests by
functionality in separate functions.

Improve the ConstrainedListTest by verifying which values are passed to
the hook functions.

- Use a dictionary called mapping that maps each object type to its corresponding serialization method.

annotation->in JSON: annotations

inputVariable->in JSON: inputVariables
outputVariable->in JSON: outputVariables
inoutputVariable->in JSON: inoutputVariables

externalAssetIds->specificAssetIds
thumbnail->defaultThumbnail

externalAssetIds->specificAssetIds

subjectId->externalSubjectId

'value' is not required in Schema

'value' is optional in Schema

- Add `kind` attribute to Qualifier class
- Init QualifierKind enum class
- remove "modelType" in json de-/serialisation for Qualifier

…mentList`

Removed since V30RC02

param kind was missing

Add missing attr "supplemental_semantic_id"

- Implement `HasDataSpecification` and make it as ancestor of  `AssetAdministrationShell`, `Submodel`, `SubmodelElement`, `ConceptDescription`, `AdministrativeInformation`,  (conform to V30RC02)
- Move `AdministrativeInformation` down, as we want it to be defined after its parent `HasDataSpecification`
- Remove `IEC61360ConceptDescription` and move `IEC61360DataType`, `IEC61360LevelType` to base.py
- Implement `DataSpecificationIEC61360`, `DataSpecificationPhysicalUnit` and its de-/serialization

Value format in IEC 61360 refers to the way a particular data element's value is represented, but not its type.

We can use it later in tests

As the DotAAS meta model does not require value_type, make it optional

…modelElementList`"

This reverts commit 2362f26.
It's better to always serialize the value instead of having multiple
places where the default value is specified.

It's better to always serialize optional values instead of specifying
their default value in multiple locations.
See also: 0a735db

This saves us a 'type: ignore' comment.

Class names: PascalCase
Attribute names: snake_case

Since a LangStringSet can't be empty, it must be optional here.

…and schema

Changes:
- fix bugs in XML/JSON schema by copying some sections from the V3.0 schema
- remove `ABAC.xsd` and `IEC61360.xsd` (not needed anymore, now unified in a single schema)
- adapter.json: fix `HasDataSpecification` (de-)serialization
- adapter.xml: add `HasDataSpecification` (de-)serialization
- move XML namespace definitions to `adapter._generic`
- remove `ConceptDescriptionIEC61360`
- remove `example_concept_description.py` (as it only contained `ConceptDescriptionIEC61360`)
- fix some minor issues in `AASDataChecker` (type hints, error messages, etc.)
- add `HasDataSpecification` support to `AASDataChecker`
- add `EmbeddedDataSpecifications` to example data
- add `__repr__()` to `EmbeddedDataSpecification`, `DataSpecificationIEC61360` and `DataSpecificationPhysicalUnit`
- remove `value_id` attribute from `DataSpecificationIEC61360`
- rename attribute accesses of `DataSpecificationPhysicalUnit` that were missed in 6cc19c6
- update tests and compliance tool example files in accordance to the changes

Furthermore, check `Qualifier.kind` with `AASDataChecker` and add
examplary values to example files.

…Pair`

…ationIEC61360`

…ng to `String`

2373167 and
9da564c changed the default
`value_format` and `value_type` of `DataSpecificationIEC61360` and
`ValueReferencePair` to `String`.
This commit adjusts the JSON/XML adapters accordingly.

The security model wasn't implemented and isn't part of the new V3.0
schemata. The (de-)serialization functions weren't used since the
removal of the security attribute from `AssetAdministrationShell` in
1c45c3c.

In turn, also remove security (de-)serialization functions from JSON/XML
adapters.
Remove ABAC XML namespace definition as it isn't used.

Update the implementation to V3.0RC02

Rename AASReference to ModelReference in `test_base.py`

---------

Co-authored-by: David Niebert <d.niebert@plt.rwth-aachen.de>
Co-authored-by: s-heppner <s.heppner@plt.rwth-aachen.de>

Renamed `model.KeyElements` to `model.KeyTypes` as defined for V3.0RC02 and V3.0. Adapted to new constructor of `model.Key`

…test_resolve()`

Multiple ModelReferences had the same Index. Fixed `mypy basyx test` errors

…TimeStamp"

This reverts commit 8fee1c5.
This commit was for V3.0RC02 only, it is reverted for V3.0
compatibility.

This commit adjusts the following commits to work on V3.0 of the SDK:
f45ae7f
7289de0