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
I'm irritated about the example given section Canonical Representation
"codes":[
{
"name":"CMQ",
"description":"cubic centimetre,
"sector":"Space and time",
"quantity":"volume",
"symbol":"cm³",
"canonicalUnit":"MTQ",
"conversionFactor":10E-6
},
When referring to the columns in the Excel definition of Rec 20, the field "name" should be called "code" or "commonCode". This code's name is "Cubic centiemtere", the field "description" would be empty for CMQ, for MTQ it would contain "synonym: metre cubed".
An adjustment would require to modify the json original located at /rec20/codes.json and then adjust its reference in the docs.
The text was updated successfully, but these errors were encountered:
@onthebreeze and @cmsdroff , could you please provide your comments on this issue? If we are going for #21 , we would need to provide explicit explanation why do we use a name property instead of code, otherwise it would raise questions like @JostFK raised.
I'm irritated about the example given section Canonical Representation
"codes":[
{
"name":"CMQ",
"description":"cubic centimetre,
"sector":"Space and time",
"quantity":"volume",
"symbol":"cm³",
"canonicalUnit":"MTQ",
"conversionFactor":10E-6
},
When referring to the columns in the Excel definition of Rec 20, the field "name" should be called "code" or "commonCode". This code's name is "Cubic centiemtere", the field "description" would be empty for CMQ, for MTQ it would contain "synonym: metre cubed".
An adjustment would require to modify the json original located at /rec20/codes.json and then adjust its reference in the docs.
The text was updated successfully, but these errors were encountered: