should the uncertainty element be a string, a float or a complexType?

MSLNZ / equipment-register-schema

XML Schema Definition (XSD) for an Equipment Register

https://mslnz.github.io/equipment-register-schema/

0 stars 0 forks source link

should the uncertainty element be a string, a float or a complexType? #9

Closed jborbely closed 4 months ago

jborbely commented 5 months ago

Currently, when using an equation to store the calibration information, the uncertainty element is of type xsd:float. Should uncertainty be of type xsd:string that represents another equation to parse or a xsd:complexType that could potentially represent another situation?

rebeccahawke commented 4 months ago

As discussed, the value and the uncertainty could both be expressed as either a float or an equation depending on the situation. One solution is to allow these elements to each be an equation (xsd:string), with a 'variables' attribute that stores the equation variable(s) if applicable.