-
Notifications
You must be signed in to change notification settings - Fork 43
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
Usage of StreamParameter #52
Comments
Hi, When a streamDescriptor is set, the type information has to be taken from there. The value is then reported in a different way. Streams are listed in a StreamCollection, with one StreamEntry per stream identifier. The value type is "Octets". Since there is no standard unit for streams, a formula or factor must be applied if provided. I hope this clarifies the streamDescriptor usage. |
I guess we have a misunderstanding. |
Second: I highly recommend to prohibit the usage of formula for streamparameters. |
I have updated the documentation. It now clarifies that the type must numeric and that the value type has to match the type of the streamdescriptor, if specified. |
Unclear usage of Streamparameters due to lack of information.
There is no word said about whether a value must have the same type as the streamDescriptor tells us for the value within the stream. Furthermore there is no rule defined that the factor, when given, has to be used for the streamvalue too. And if so this has to be true for the formula as well and in that case the client has to calculate each single streamvalue using the formula...
The documentation needs an update here...
What if the provider sets the value to be an utf8 string, but the streamDescriptor points to a 16 bit little endian?
As far as i understand this is allowed... weird, but allowed
The text was updated successfully, but these errors were encountered: