Issue 8799: type of all attributes of Geographic_location (snp-ftf) Source: Japan Biological Informatics Consortium (Mr. Martin Senger, martin.senger@gmail.com) Nature: Uncategorized Issue Severity: Summary: The type of all attributes of Geographic_location are now 'double' to allow fractional degrees Definition: Location of an individual or population in a geographic map. Locations are expressed in decimal degrees. Northern latitides and eastern longitudes have positive values by convention. Resolution: Revised Text: Resolution: Proposed solution: · Apply the change into the UML diagram of the PIM model (make a new figure) · Apply the change into the XMI file created from the UML diagram (update the accompanying file by a new omgsnp-xmi12.xml file) · Apply the change in the section "3.2 Model classes, attributes and associations (details)" (re-generate the whole section from the XMI) Disposition: Resolved Actions taken: May 20, 2005: received issue November 1, 2005: closed issue Discussion: The "Proposed resolution" for all of them is the following: ----------------------------------------------------------- * apply the change into the UML diagram of the PIM model (make a new figure) * apply the change into the XMI file created from the UML diagram (update the accompanied file) * apply the change in the section "3.2 Model classes, attributes and associations (details)" (re-generate the whole section from the XMI) End of Annotations:===== $FORM{$name} f all attributes of Geographic_location are now 'double' to allow fractional degrees Definition: Location of an individual or population in a geographic map. Locations are expressed in decimal degrees. Northern latitides and eastern longitudes have positive values by convention. The "Proposed resolution" for all of them is the following: ----------------------------------------------------------- * apply the change into the UML diagram of the PIM model (make a new figure) * apply the change into the XMI file created from the UML diagram (update the accompanied file) * apply the change in the section "3.2 Model classes, attributes and associations (details)" (re-generate the whole section from the XMI)