Closed myroslav closed 8 years ago
FYI, the "Data Formats Gudeline" of CWA 16558 BII sticks to UnitCode of "UN/CEFACT recommendation 20, revision 4" only without any additional description firelds or variations in unit schemes.
Linked to issue #145.
The more I look at this, the more I'm leaning towards QUDT as the mid-term solution, as it provides human and machine-readable identifiers, which seem to be possible to map to UCUM
However, I'm not sure I can see any way of mapping these to UNECE/CEFACT Common Codes (perhaps via symbol?).
Have we got clear uses cases where the UNECE/CEFACT Common Codes are in use that we need to cater for?
At the moment I see clear need of "informative units" that QUDT is lacking, but UN/CEFACT r20 r4 provides in Annex II/III. Additionally compatibility with the CWA 16558 BII would be great, and they are explicitly requesting use of "UN/CEFACT recommendation 20, revision 4" in UnitCode. Such compatibility would save us from maintaining unit code conversion tables.
I'm not a big fan of cryptic codes like "MTK" thus asked if we should include some extra field like unitDesctiption, to have "square metre" there.
From co-working session today:
I suppose it's not full one. The full one could be found there http://base.consultant.ru/cons/cgi/online.cgi?req=doc;base=LAW;n=167465;fld=134;dst=1000000001,0;rnd=0.38406801223754883 (National Classification units "(app. Resolution of the State Standard of Russia from 26.12.1994 N 366) (Ed. By 28.03.2014)
Another possible source of units from the XBRL registry of units: http://www.xbrl.org/utr/utr.xml
Unfortunately I do not see pieces, bottles, pallets, packs and boxes. Other more exotic but used in procurement units are manmonth, manweek, etc.
On Tuesday, 6 October 2015, timgdavies notifications@github.com wrote:
Another possible source of units from the XBRL registry of units: http://www.xbrl.org/utr/utr.xml
— Reply to this email directly or view it on GitHub https://github.com/open-contracting/standard/issues/177#issuecomment-145852945 .
.................................................................................................................................... Myroslav Opyr ▪ CTO ▪ Quintagroup ▪ +1.917.475.4725 ▪ http://quintagroup.com ˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙
This question on units re-surfaced recently in one of the missions with Marcela. Let me know if you need help researching this topics with colleagues and see if there best practices.
@dc-coder Support on looking into this would be great.
A full proposal has now been developed and is in issue #366
At the moment we have single
string
field forItem.unit
.Having reviewed CODES FOR UNITS OF MEASURE USED IN INTERNATIONAL TRADE Revision 9" (UNECE/CEFACT Trade Facilitation Recommendation No.20) there are following fields of interest:
Common Code
Name
Symbol
Which of the fields is expected to be used in
unit
ofItem
?Common Code
is looking like code that is unique, but sometimes too cryptic for average human to understand (for exampleMTK
stands for "square metre").Should we turn that field into something similar to
classification
? I.e. provide the unit scheme id (UNCE20), unit id (MTK), and unit description (square metre)?