You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4.2.2 requires complex types that are serializable to JSON format. Also, it requires importing OPC UA nodeset files (XML) format. Does there already exist a full translation from Part 5 Nodeset XML to JSON?
If a Nodeset->JSON conversion already exists, then modifying the import requirement to only the JSON flavor would simplify application design.
If a Nodeset -> JSON conversion does not already exist, then the number of incompatibilities between Part 5 structures and JSON is undetermined and a considerable risk.
At a minimum, I suggest copying the items from Part 5 to filter for those that MUST be supported by this standard so any updates to Part 5 can be reviewed for applicability before support is required by this API.
4.2.2 requires complex types that are serializable to JSON format. Also, it requires importing OPC UA nodeset files (XML) format. Does there already exist a full translation from Part 5 Nodeset XML to JSON?
If a Nodeset->JSON conversion already exists, then modifying the import requirement to only the JSON flavor would simplify application design.
If a Nodeset -> JSON conversion does not already exist, then the number of incompatibilities between Part 5 structures and JSON is undetermined and a considerable risk.
At a minimum, I suggest copying the items from Part 5 to filter for those that MUST be supported by this standard so any updates to Part 5 can be reviewed for applicability before support is required by this API.
https://reference.opcfoundation.org/Core/Part5/v105/docs/
The text was updated successfully, but these errors were encountered: