Using Rosetta with CoABS TIE 1:Ontology-Based Term Transformations
bridge agent rearranged route points in the order required by the helicopter agents. Types of route points were implicit in this order
point DefaultHBPoint -lat 0.000000 -lon 0.000000
point LP_A -lat 29.384322 -lon 48.039903
point WP_A -lat 29.354845 -lon 47.999734
point DP_A -lat 29.333773 -lon 47.997891
point LZ_A -lat 29.329179 -lon 47.995596
point RP_A -lat 29.321262 -lon 47.987511
point DASP_B -lat 29.358754 -lon 47.931455
point DASP_A -lat 29.237487 -lon 47.982873
Bridge agent does not need to order points. Types of route points explicit in message
linkup-point LP_A -lat 29.384322 -lon 48.039903
detach-point DP_A -lat 29.333773 -lon 47.997891
landing-zone LZ_A -lat 29.329179 -lon 47.995596
MAIN detach-at-sea-pt DASP_B -lat 29.358754 -lon 47.931455
ALTERNATIVE detach-at-sea-pt DASP_A -lat 29.237487 -lon 47.982873
way-point WP_A -lat 29.354845 -lon 47.999734
rally-point RP_A -lat 29.321262 -lon 47.987511
home-base-point DefaultHBPoint -lat 0.00 -lon 0.00
Problem: Input/output requirements need to be addressed (e.g., order and semantics of route points for helicopter agents)