| An empirical exercise, based on the following example presented by Neil Christopher | at the NIST Semantic Distance Workshop, November 2003 | | Verson 1 20031113 | | In this version, we use a scalar Distance measure that Adrian proposed at the workshop. | ( A distance of 0 is unambiguous. A distance >0 is a warning that ambiguity must be reduced ) | However, it's important to note that what is in this file is simply a framework for exploring | different scalar and non-scalar measures, by running them to see what results we get. | | Given some information about the following two systems: | | ERP GTM | Enterprise Resource Planning Global Trade Management | ( Alternatively ( Alternatively | Sales Order Entry/Shipment Trade Management Operations | Enterprise Model View ) Enterprise Model View ) | | Try some experiments aimed at answering the following questions: | | Q1. Given two interface definitions, derived from their respective ontologies, | can the distance between the two be measured? | | Q2. Is this measure a single value? A set of like values with harmonized units ? | | Q3. What factors would contribute to uncertainty in this measure? | | Q4. Is time a factor in this measure? i.e. is it reasonable to expect distance measure to change over time? | | Q5. Could a Distance Measure be mapped empirically to a $ cost of integration? | | Q6. Could a Distance Measure be mapped empirically to a $ cost of maintenance? | You can run and change this exercise in a browser, using the Internet Business Logic system | at www.reengineeringllc.com this-concept is shared between the this-name1 system and the this-name2 system ontologies ========================================================================================= Heaviness ERP GTM Financial ERP GTM in the ERP system ontology this-name is an instance of this-concept ============================================================================= Customer GTM person Buyer GTM person Weight Heaviness Shipper Goods Transportation Organization Cost Financial in the GTM system ontology this-name is an instance of this-concept =================================================================================== Ship To Precise Physical Location Net Weight Heaviness Country of Origin Area Physical Location Fees Financial Price Financial Purchaser GTM person the canonical measure for this-concept is this-unit =================================================== Heaviness pounds Financial US dollars in the ERP system this-quantity is measured in these-units ========================================================== Weight pounds Cost US dollars in the GTM system this-quantity is measured in these-units ========================================================== Net Weight kilograms Fees Euros in the some-name1 system ontology some-item1 is an instance of some-concept in the some-name2 system ontology some-item2 is an instance of that-concept that-concept is shared between the that-name1 system and the that-name2 system ontologies count some-item1a : in the that-name1 system ontology that-item1a is an instance of that-concept = some-ambiguity1 count some-item2a : in the that-name2 system ontology that-item2a is an instance of that-concept = some-ambiguity2 that-ambiguity1 + that-ambiguity2 = some-ambiguity that-ambiguity - 2 = some-dist ------------------------------------------------------------------------------------------------------------------- that-item1 in the that-name1 system maps with distance that-dist to that-item2 in the that-name2 system some-item1 in the some-name1 system maps with distance some-dist to some-item2 in the some-name2 system in the that-name1 system that-item1 is measured in some-unit1 in the that-name2 system that-item2 is measured in some-unit2 in the that-name2 system ontology that-item2 is an instance of some-concept the canonical measure for that-concept is some-standard-unit that-unit2 is not equal that-standard-unit --------------------------------------------------------------------------------------------------------------------- that-item1 in the that-name1 system maps with distance that-dist and CONVERSION to that-item2 in the that-name2 system | the GTM system uses this-name of this-type with this-definition | =============================================================================== | Ship To struct Receiver Address | Net Weight number Weight per Item without Dunnage | Country of Origin Char2 Country of Manufacture | Fees number Port Fees and Insurance | Purchaser Char2 The contact in GTM | the ERP system uses this-name of this-type with this-definition | ======================================================================= | Customer Char 256 Buyer | Weight number Weight of Orderable Item | Shipper Char 256 Overland Carrier | Cost number Customer Cost