search

oasis-open / tosca-community-contributions

OASIS TC Open Repository: Manages TOSCA profiles, tests, and templates that are maintained by the TOSCA community. They are intended to be used as examples to help developers get started with TOSCA and to test compliance of TOSCA implementations with the standard.
https://github.com/oasis-open/tosca-community-contributions
Apache License 2.0
39 stars 25 forks source link

The case sensitivity issue with scalar-unit.bitrate #81

Open aszs opened 2 years ago

lauwers commented 1 year ago

All scalar units are case insensitive. The note in https://docs.oasis-open.org/tosca/TOSCA/v2.0/csd05/TOSCA-v2.0-csd05.html#_Toc125468705 states this for scalar-unit.size. That note should be moved up to the general description about scalar units.

pmjordan commented 1 year ago

It may be acceptable to define scalar units of size as case insensitive but I think it would be a poor descision to state that all scalar units are case insensitive. Many scalars are derived from SI units and SI does define case as significant; s for seconds is not the same as S for Siemens and m for milli is not the same as M for Mega.

lauwers commented 1 year ago

I vote for consistency. Either all scalar units should be case insensitive, or they should all be case sensitive.

tliron commented 1 year ago

I vote for appropriateness. :) I don't see why case sensitivity can't be dependent on the type.

If we must have consistency, then let them all be case sensitive. If users get it wrong, it's an easy error to detect and correct.