-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ValueOnly serialization in json #29
Comments
@matgnt the ValueOnly serialization has a broken design -- so we didn't include it in the library. For example, what happens if your Moreover, ValueOnly serialization can not be automatically generated. There are specific rules for each class, and these rules change between the versions of the meta-model. The logic is thus complicated and would require a substantial effort if we want to transpile it. I think the easiest is to implement the meta-only and value-only serializations by hand. I wouldn't bother patching the original code of this SDK, but instead have parallel de/serialization functions which use the SDK to structure the inputs and the outputs, respectively. |
Hi @mristin Is it possible to add this limitation to the Readme / Documentation? [1] https://catena-x.net/ |
@matgnt we could add it as a manually-written module to the SDK. Would you be interested to help me with the implementation? |
Hi,
I'm starting to use this library because I like to have those things generated from the specs! Good approach I think!
One question or feature request I had is about the serialization.
I'm following the example here:
https://aas-core30-python.readthedocs.io/en/latest/getting_started/jsonize.html
but what I would require in my project is a ValueOnly serialization as described here:
https://industrialdigitaltwin.org/wp-content/uploads/2023/04/IDTA-01002-3-0_SpecificationAssetAdministrationShell_Part2_API.pdf#%5B%7B%22num%22%3A254%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22XYZ%22%7D%2C54%2C788%2C0%5D
My expectation would be to just use the same function
but probably pass in an additional parameter to indicate the desired meta data for serialization, e.g.
Any thoughts on this?
Thanks,
--
Matthias Binzer
The text was updated successfully, but these errors were encountered: