PyI40AAS issueshttps://git.rwth-aachen.de/acplt/pyi40aas/-/issues2020-11-06T10:53:50+01:00https://git.rwth-aachen.de/acplt/pyi40aas/-/issues/81aasx: Fix handling of File objects which refer to external URLs2020-11-06T10:53:50+01:00Michael Thiesaasx: Fix handling of File objects which refer to external URLsIt's currently unclear, what kind of values a `File` object may contain and how they should be interpreted. Probably, they are allowed to hold a full URL which refers to some webserver etc. as an alternative to relative and absolute path...It's currently unclear, what kind of values a `File` object may contain and how they should be interpreted. Probably, they are allowed to hold a full URL which refers to some webserver etc. as an alternative to relative and absolute paths (`./some_file.pdf` resp. `/some/path/to/some_file.pdf`), which refer to a local file.
We currently assume that all `File` objects within an AASX package refer to a supplementary file within that package. Thus, reading an AASX package file fails when it contains a `File` object refering to an external file via URL.
To fix that, we should distinguish between local and external references. However, currently the semantics of the `File.value` attribute's values are not clear from the standard (DotAAS), so we can only guess that the existence of the URL schema is the correct criterion.https://git.rwth-aachen.de/acplt/pyi40aas/-/issues/83model: ReferenceElement.value should have type Reference instead of AASReference2020-10-28T16:59:11+01:00Michael Thiesmodel: ReferenceElement.value should have type Reference instead of AASReferenceDotAAS describes the `value` attribute as follows:
> Reference to any other referable element of the same of any other AAS or a reference to an external object or entity.
Thus, References to other objects/entities than AAS objects are ...DotAAS describes the `value` attribute as follows:
> Reference to any other referable element of the same of any other AAS or a reference to an external object or entity.
Thus, References to other objects/entities than AAS objects are also allowed.
This needs to be fixed in the deserialization adapters as well.ahttps://git.rwth-aachen.de/acplt/pyi40aas/-/issues/90model: dataType of IEC61360ConceptDescription should be optional2020-10-07T17:17:51+02:00Torben Minymodel: dataType of IEC61360ConceptDescription should be optional**EDIT (MT)**: This is an issue in our Metamodel implementation. It must also be fixed in the deserialization and serialization accordingly.**EDIT (MT)**: This is an issue in our Metamodel implementation. It must also be fixed in the deserialization and serialization accordingly.https://git.rwth-aachen.de/acplt/pyi40aas/-/issues/72adapter.xml: Check serialization of `annotation` in `AnnotatedRelationshipEle...2020-05-07T14:04:40+02:00Sebastian Heppners.heppner@iat.rwth-aachen.deadapter.xml: Check serialization of `annotation` in `AnnotatedRelationshipElement`According to the metamodel, it should be of type `DataElement`, while we (de)-serialize as `Reference`. This is correct to the current XSD-Schema, since there is currently no `dataElement_t`, but it will probably get added with the new v...According to the metamodel, it should be of type `DataElement`, while we (de)-serialize as `Reference`. This is correct to the current XSD-Schema, since there is currently no `dataElement_t`, but it will probably get added with the new version of the schema, we should check it then.https://git.rwth-aachen.de/acplt/pyi40aas/-/issues/25model: Implement DataSpecificationIEC613602020-01-21T12:26:05+01:00Michael Thiesmodel: Implement DataSpecificationIEC61360https://git.rwth-aachen.de/acplt/pyi40aas/-/issues/39base.Referable.parent is of type: Optional[Namespace]. XSD-schema expects par...2020-01-16T16:45:48+01:00Sebastian Heppners.heppner@iat.rwth-aachen.debase.Referable.parent is of type: Optional[Namespace]. XSD-schema expects parent to be of type="aas:reference_t"How to serialize this parameter in compliance with the schema?How to serialize this parameter in compliance with the schema?https://git.rwth-aachen.de/acplt/pyi40aas/-/issues/37model.base.HasDataSpecification has parameter data_specification of type Set[...2020-01-07T13:27:10+01:00Sebastian Heppners.heppner@iat.rwth-aachen.demodel.base.HasDataSpecification has parameter data_specification of type Set[Reference]. XML-Serialization expects this to be just a Reference.https://git.rwth-aachen.de/acplt/pyi40aas/-/issues/27model: View does not inherit from HasDataSpecification, HasSemantics, Referable2019-12-16T10:53:23+01:00Michael Thiesmodel: View does not inherit from HasDataSpecification, HasSemantics, Referable