From: Frank B. <fbe...@ca...> - 2015-05-06 17:47:30
|
> > In this case, we should change the UML diagram to make the 'sampledValue' also optional, and clarify in the spec that you should either use the single 'sampledValue' attribute, *or* you use the min/max values, but never all three at the same time. > > Why is this an either or? I feel like there is no harm in specifying all 3, is there? > Basically because it is ambigous: option 1: - define sampledValue and stick to it option 2: - define absolute min/max range and use that option 3: - define sampledValue -min to sampledValue + max I see a value in option 1 and 2. When reading / writing the SBML i don’t see an advantage in option 3. Frank |