- 04 Mar, 2020 11 commits
-
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
adapter.json.json_deserialization: change use of Enum-Dicts from adapter.json.json_serialization to adapter._generic
-
Sebastian Heppner authored
-
Sebastian Heppner authored
The functions still have the parameter "namespace", that changes the namespace of the element they return, but if the function serializes everything inside the element after an xsd-schema, it only makes sense that every child has the namespace fixed to the one defined in the schema and not to the one, that the outer most element might have.
-
Sebastian Heppner authored
Since the Dicts to serialize Enum classes are the same for both XML and JSON, move them into a _generic module to avoid duplicate definition
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
- 28 Feb, 2020 9 commits
-
-
Sebastian Heppner authored
-
Sebastian Heppner authored
# Conflicts: # requirements.txt
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
XSD-Schema demands element "<value>", even if it is empty
-
Sebastian Heppner authored
somehow, the option of the submodelElement to be a ReferenceElement was missing
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
the element "<annotations>" is mandatory according to the xsd-schema, even, if there are no references inside
-
- 25 Feb, 2020 19 commits
-
-
Sebastian Heppner authored
-
Sebastian Heppner authored
since annotatedRelationshipElement inherits from RelationshipElement, an object of class annotatedRelationshipElement is obviously also instance of RelationshipElement, therefore, it would be wrong to serialize it twice, once as annotatedRelationshipElement and once as RelationshipElement, Fix by checking first for relationshipElement and then inside that check for annotatedRelationshipElement.
-
Sebastian Heppner authored
as they do not exist in the schema
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
- add "<allowDuplicates>" child with text="false" (default value), since this attribute does not exist in the pyass implementation - change order of the <ordered> and <value> children, to fit the order in the schema
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
According to the schema, child has to exist even if it is empty
-
Sebastian Heppner authored
According to the schema, the child has to exist, even if it is empty
-
Sebastian Heppner authored
According to the xsd-schema, the child <containedElements> has to exist even if it is empty
-
Sebastian Heppner authored
-
Sebastian Heppner authored
-
Sebastian Heppner authored
change location of "kind" in the serialization to the end of the asset element
-
Sebastian Heppner authored
the order/sequence of the serialization of attributes was wrong. switched the place of "derivedFrom" and "assetRef" serialization
-
- 22 Feb, 2020 1 commit
-
-
Sebastian Heppner authored
-