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 documentation uses both "number/temperature/C" and "number/Temperature/C" as examples (differing just in the case of the initial letter of the measurement name element).
The regex for event type allows mixed case, but I haven't found any guidance in the specification as to whether event type names should be compared case-sensitive or not? Measurement units guidelines - Case sensitive behaviour only covers the units.
The text was updated successfully, but these errors were encountered:
garethsb
changed the title
Are event types case sensitive?
Are all parts of event types case sensitive?
May 2, 2019
I would normally support case-insensitivity, but given that the SI units which are recommended are case sensitive, I think we should stick to case sensitivity and fix the documentation. @cristian-recoseanu , what do you think?
I'd strongly recommend being case sensitive in these cases. It's very common for client applications to be written based upon an example implementation rather than by reading the spec, and as such making the assumption that you can simply test for string equality.
garethsb
added a commit
to garethsb/nmos-event-tally
that referenced
this issue
May 16, 2019
The documentation uses both
"number/temperature/C"
and"number/Temperature/C"
as examples (differing just in the case of the initial letter of the measurement name element).The regex for event type allows mixed case, but I haven't found any guidance in the specification as to whether event type names should be compared case-sensitive or not? Measurement units guidelines - Case sensitive behaviour only covers the units.
The text was updated successfully, but these errors were encountered: