Changes between Initial Version and Version 1 of ExternalRelationships


Ignore:
Timestamp:
10/19/09 13:37:42 (15 years ago)
Author:
gschadow
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ExternalRelationships

    v1 v1  
     1= External Relations =
     2
     3Goal: to document and manage relationships with other organizations.
     4
     5== Open Geospatial Consortium (OCG) ==
     6
     7Contacts: Carl Reed, Aaron Braeckel
     8
     9Status: an MoU was desired by OCG and drafted earlier this year.
     10
     11 1. OGC staff will facilitate the cooperative submission of UCUM into the OGC consensus standards process. This would require the following activities and tasks
     12   a. Provide a presentation of the UCUM specification to the OGC membership.
     13   b. Transform the UCUM document into the OGC document template format.
     14   c. Submit the UCUM document to the OGC membership for consideration as an OGC Best Practice
     15   d. Develop a Request for Comment (RFC) submission team to move UCUM into the OGC standards track.
     16   e. Form an OGC Standards Working Group (SWG) and process the document for approval as an OGC standard
     17 2. Cooperatively develop and publish joint outreach materials designed to promote the mission and standards of both organizations, to include but not limited to a best practice paper, white papers, presentations at conferences, etc.
     18 3. Cooperative involvement of organizational staff in relevant OGC and RI initiatives, including OGC working groups, testbed activities, or committee processes related to units of measure.
     19 4. Determine if the OGC UCUM standard should be submitted to ISO under the terms of reference of the OGC-ISO Class A Liaison agreement.
     20
     21Follow-up from UCUM side has been delayed because of bandwidth issues. As organizations approach UCUM to engage in the development of a standard, it requires significant time committment by UCUM affiliate personnel to maintain that process in that other organization. The engagement in the process to create another standard from UCUM may take more effort than actually maintaining UCUM. And there are several of these organizations who have similar plans. E.g. ONTOLOG project is similar.
     22
     23The question is whether UCUM can reasonably pick any one organization to engage in such work or if it would not be better for an organization wishing to reference UCUM in a specific document to provide a draft of such document which references UCUM reproduces the minimum necessary material and describes in detail how the UCUM development and the new proposed status in that other organization would be synchronized and managed.
     24
     25== DICOM ==
     26
     27Contacts: David Clunie
     28
     29Status: UCUM units adopted for at least a subset of measurements communicated in DICOM-SR.
     30
     31== IEEE 1073 Medical Devices Standards ==
     32
     33Contacts: Todd Cooper, Paul Schluter, Melvin Reynolds.
     34
     35Status: a few requests from Paul Schluter have been addressed in 2009. IEEE 1073 has a "rosetta" mapping effort and UCUM is part of that. This project requires little direct interaction by UCUM resources and a fruitful content-focused cooperation between IEEE 1073 and UCUM appears to be fully functional.
     36
     37== US FDA ==
     38
     39Contacts: Bill Hess, Randy Levin
     40
     41Status: UCUM used in medication description data standards. Accommodated procedure-defined units for several allergen and other disease-causing agents in 2009.
     42
     43== [http://www.dimdi.de/static/de/ehealth/ucum/index.htm DIMDI] ==
     44
     45Contacts: Sylvia Thun
     46
     47Status: DIMDI references UCUM among it's eHealth standards. DIMDI sponsored people are actively involved in the discussion process to determine organizational and procedural strategies required to be useful in the further evolution of the eHealth standards field in Germany, Europe, and world-wide.
     48
     49== LOINC Standard ==
     50
     51Contacts: Clem McDonald, Dan Vreeman
     52
     53Status: LOINC to reference UCUM units for example or canonical units used with LOINC codes.
     54
     55== [http://ontolog.cim3.net/cgi-bin/wiki.pl?UoM_Ontology_Standard ONTOLOG Ontology Forum's UoM Project] ==
     56
     57Contacts: Peter Yim
     58
     59Status: UCUM making contributions to the ONTOLOG UoM standard. Current activity September/October 2009.
     60
     61As with all engagement with external organizations, there is a bandwidth problem. There is a lot more activity required for the harmonization with other organizations than actually maintaining UCUM. Since that ONTOLOG community is an open forum and made the threshold for involvement quite low, it was possible to engage in a bit more detail. However, the stance is still to wait and see into what the ONTOLOG specification will turn into. There is little expectation that it would be 100% consistent with UCUM, but as in the JSR-275 work (see below) if the two are not in violation of each others' principles and not interfering, it would be a positive outcome.
     62
     63
     64== [http://kenai.com/projects/jsr-275 Java Measures and Units Specification JSR-275] ==
     65
     66Contacts: Jean-Marie Dautelle
     67
     68Status: UCUM was added into the Java JSR units of measure specification and reference implementation. This project required very little interaction between UCUM and JSR-275 people.
     69
     70== SNOMED ==
     71
     72Status: SNOMED has mapped from its units to UCUM units concepts. Some descriptions of these mappings had been shared, reviewed and commented on by UCUM personnel.
     73
     74== IUPAC C-NPU ==
     75