PyI40AAS issueshttps://git.rwth-aachen.de/acplt/pyi40aas/-/issues2020-11-02T16:31:24+01:00https://git.rwth-aachen.de/acplt/pyi40aas/-/issues/63adapter: Change JSON and XML parser interface to add objects directly into a ...2020-11-02T16:31:24+01:00Michael Thiesadapter: Change JSON and XML parser interface to add objects directly into a given AbstractObjectStoreThis allows to use a CouchDBObjectStore or other database-backed ObjectStores without collecting the objects in memory first.
The parser functions should return a set of Identifiers of the parsed objects instead.
See `aas.adapter.aasx....This allows to use a CouchDBObjectStore or other database-backed ObjectStores without collecting the objects in memory first.
The parser functions should return a set of Identifiers of the parsed objects instead.
See `aas.adapter.aasx.AASXReader.read_into()` [LINK](https://git.rwth-aachen.de/acplt/pyi40aas/-/blob/6278d03f6bbb5b22e707dc054382844f05794a3e/aas/adapter/aasx.py#L107), which already has a similar interface.
Progress:
- [x] JSON Deserialization
- [x] XML DeserializationStable library APIhttps://git.rwth-aachen.de/acplt/pyi40aas/-/issues/75Change name of `timeout` parameter of update method2020-10-28T17:08:34+01:00Michael ThiesChange name of `timeout` parameter of update methodThe `timeout` is more like a "caching expiration timeout" of the object, not a timeout for the actual update.
Thus, we should rename it to avoid confusion.
Maybe we can introduce an additional (optional) timout parameter for the actual...The `timeout` is more like a "caching expiration timeout" of the object, not a timeout for the actual update.
Thus, we should rename it to avoid confusion.
Maybe we can introduce an additional (optional) timout parameter for the actual update (e.g. the HTTP timeout for the HTTP client and CouchDB client).Stable library APIhttps://git.rwth-aachen.de/acplt/pyi40aas/-/issues/85Improved update()/commit() functionality2020-11-02T09:16:47+01:00Michael ThiesImproved update()/commit() functionalityWe plan a full redesign of the `update()`/`commit()` functionality of AAS objects for synchronization with an external data source.
* Instead of overriding these functions for different data sources, all `Referable` objects will include...We plan a full redesign of the `update()`/`commit()` functionality of AAS objects for synchronization with an external data source.
* Instead of overriding these functions for different data sources, all `Referable` objects will include a `source` attribute with an URI representation of their data source. The URI's schema is used to determine the correct backend/client.
* `update()` and `commit()` should always effect the object itself and all (recursively) included objects
* If the object itself has no data source/backend itself, the next higher object with a data source is used to update the object's data.
* After the update, all included objects that are linked with an own data source are updated recursively in a top-down manner.
* An object is always committed to its own data source and the data sources of all its ancestors in the object hierarchy.
* The included objects are committed recursively. (TODO: Define order of committing.)Stable library APISebastian Heppners.heppner@iat.rwth-aachen.deSebastian Heppners.heppner@iat.rwth-aachen.dehttps://git.rwth-aachen.de/acplt/pyi40aas/-/issues/97model: Remove `_`-suffix from parameters of `__init__` functions2020-11-25T10:42:57+01:00Leon Mauritz Möllermodel: Remove `_`-suffix from parameters of `__init__` functionsRemove `_`-suffix from parameters like `submodel_` and `security_` in the `__init__` function of all classes of the `model`, as Igor suggested on Zulip.Remove `_`-suffix from parameters like `submodel_` and `security_` in the `__init__` function of all classes of the `model`, as Igor suggested on Zulip.Stable library API