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
The library parses encoding metadata (TextEncoding, JSONEncoding, BinaryEncoding, XMLEncoding) via parseEncoding(), but the demo never displays how observation/command data is encoded.
Current Behavior
Schema display shows fields, types, UoM, and definitions
No indication of how values are actually encoded (delimiters, block separators, byte order, etc.)
Proposed Change
After the schema field table, add an "Encoding" section showing:
Encoding type badge (Text / JSON / Binary / XML)
For TextEncoding: tokenSeparator, blockSeparator, decimalSeparator, collapseWhiteSpace
For BinaryEncoding: byteOrder, byteEncoding, member details
Summary
The library parses encoding metadata (
TextEncoding,JSONEncoding,BinaryEncoding,XMLEncoding) viaparseEncoding(), but the demo never displays how observation/command data is encoded.Current Behavior
Proposed Change
tokenSeparator,blockSeparator,decimalSeparator,collapseWhiteSpacebyteOrder,byteEncoding, member detailsparseDatastreamSchemaResponse())Library Support
parseEncoding()is fully implemented and exportedPriority
Medium — helpful for understanding data formats, especially for interoperability testing