GitHub user chrisdutz added a comment to the discussion: Should we extend PLCValues with a map of Meta-Information?
So ... as I only got questions and no suggestions, I'll merge my version ... we can always change it later on ... Right now I know of multiple protocols, that generally have such concepts of meta-data ... IEC 60870-5-104, KNX, Profinet, DeltaV (even if we don't have a working driver for that). I was always annoyed that when using PlcStruct you needed to know which are the values and which is meta-data and needed to explicitly reference them. With my changed proposal, the driver developer decides what is data and what it meta-data and modells the driver accordingly. This way the user can use the values in their natural type directly and still access the other information. I'm not quite sure how to do this for KNX, as I generate the DataIO mspec via XSLT, but for the others, this is clearly a way better option. I'm also thinking of adding a new "metadata" field type for Data-IO types. So if you have a simple files with the name "value", that becomes the dominant field in that case, all "metadata" fields get added as metadata ... if you have multiple simple fields and none named "value", a struct is created. GitHub link: https://github.com/apache/plc4x/discussions/1086#discussioncomment-6902642 ---- This is an automatically sent email for dev@plc4x.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@plc4x.apache.org
