19 July 2001 Lewis Hart GRC International an

19 July 2001 Lewis Hart GRC International, an AT&T Company

What’s Hot. . . ï DAML-UML Enhanced Tool ï Imports / Exports, Implements UMLDAML mapping ï Interface to Articulation Service ïBuilt from re-useable DAML components ïDAML API , Articulation Service, UMM API ï Addin for Rational Rose ï Argo UML coming. ï DAML API ï Java Interfaces with implementation and utilities. ï Working on ‘standard’ interface with multiple implementations ï Interface to Jess inference engine. ï Content Driven Information Distribution ï Content based Publish and Subscribe ïRDBMS Articulation ïRule-based ïJava Expert System Shell (Jess) ï Extensible with Java. ï Validated on real world systems GTN/CMOS RDBMS Ontologies ï Subscribers provide an XQL query as specification of their interest ïThey are subscribed to channels that provide DAML annotated content that is the result of the XQL specification. ïPublishers provide DAML annotated content. . ï Annotated Document Repository

DAML UML Enhanced Tool (DUET ) Source Descriptions Expert Knowledge ï Rational Rose 2000 ï Argo. UML coming ï Implements current DAML Profile for UML Rose Adapter Existing Ontologies Created Ontologies Ontology Articulation Service

Articulation Ontology <!-- **** Articulation **** --> <daml: Class rdf: ID = 'Articulation' > <daml: sub. Class. Of> <daml: Restriction> <daml: on. Property rdf: resource='#matches'/> <daml: to. Class rdf: resource='#Match'/> </daml: Restriction> </daml: sub. Class. Of> <daml: Restriction> <daml: on. Property rdf: resource='#match. Factor'/> <daml: to. Class rdf: resource='#Match. Factor'/> </daml: Restriction> </daml: sub. Class. Of> <daml: label>Articulation</daml: label> </daml: Class>

Ontology Articulation Service Hot. DART DUET Rational Rose DART Import Export XSLT Rose Adapter UMM API Articulation Service DAML API Jess ï Service provides automated analysis of potential mappings between ontologies and builds an articulation ontology that codifies the mappings in DAML. ï Interfaced to multiple applications using reusable components.

A DAML API ï Moving towards a standard API interface for DAML.

Example Match Structural, Not Perfect Tables Work. Order file: Shipyard_3. daml#genid 662 file: Shipyard_2. daml#genid 735 c: reasons <c: Match. Factor rdf: about="grci 1730" d: kind="EX_NM_MTCH: tbl_nm” d: detail=“Work. Order” d: strength="8"> <c: Match. Factor rdf: about="grci 3029" d: detail="grci 3027 grci 2999" d: kind="TBL_ELE_MTCH" d: strength="3"> <c: Match rdf: about="grci 3027" d: strength="8. 60" > file: Shipyard_3. daml#genid 308 <c: Match. Factor rdf: about="grci 1819" d: detail="Unique marina work order ID. " d: kind="PHRASE_MTCH: ele_defn" d: strength="8"> Structural Matching elements found in matching tables. <c: Match rdf: about="grci 2999" d: strength=” 9. 84" > Work. Order. ID Work. Order http: //www. daml. org/2001/03/daml+oil#equivalent. To c: Match. Factor rdf: about="grci 3030” d: detail="grci 3027 grci 2999" d: kind="ELE_TBL_MTCH" d: strength="9"> <c: Match. Factor rdf: about="grci 1825" d: detail="INTEGER" d: kind="EX_DT_MTCH: ele_data_type” d: strength="2"> c: reasons http: //www. daml. org/2001/03/daml+oil#equivalent. To Elements Order. ID file: Shipyard_2. daml#genid 342

Example Rule and Matches Jess Rule (defrule Sim_Name_Property_Match (declare (salience 10)) ; ; Get a name property's info (Name. Property (name ? pnam) (strength ? pstr 0) ) (DAMLProperty (local. Name ? pnam) (OBJECT ? ptype)) ; ; Find one property of this type. (DAMLProperty (type ? ptype) (ID ? id 1) (namespace ? ns 1) (subject ? sub 1) (object ? obj 1) ) ; ; Find another property of this type. (DAMLProperty (type ? ptype) (ID ? id 2&~? id 1) (namespace ? ns 2&~ns 1) (subject ? sub 2) (object ? obj 2) ) ; ; Compare there names as phrases. (test (not (same. IC (? obj 2 get. Value) (? obj 1 get. Value)))) (bind ? pstr (compare. Phrase. IC (? obj 1 get. Value) (? obj 2 get. Value))) (test (>= ? pstr 8 )) => (bind ? mf (create. MF ? sub 1 ? sub 2 (str-cat "SM_NM_MTCH: " ? pnam) (str-cat (? obj 1 get. Value) "|" (? obj 2 get. Value)) ? pstr )) ; ; Log it (printout t "Sim_Name_Property_Match " (? mf get. ID) ; ; etc…. ) GTN-CMOS Matches Sim_Name_Property_Match COMPARE_IRD. daml#grci 9920 file: CMOS_IRD. daml#genid 1627 and file: GTN_IRD. daml#genid 3586 because SM_NM_MTCH: ele_access_nm NAME desig_name Sim_Name_Property_Match COMPARE_IRD. daml#grci 9923 file: CMOS_IRD. daml#genid 1627 and file: GTN_IRD. daml#genid 2095 because SM_NM_MTCH: ele_access_nm NAME passenger_name Sim_Name_Property_Match COMPARE_IRD. daml#grci 9928 file: CMOS_IRD. daml#genid 1627 and file: GTN_IRD. daml#genid 1561 because SM_NM_MTCH: ele_access_nm NAME last_name Sim_Name_Property_Match COMPARE_IRD. daml#grci 9925 file: CMOS_IRD. daml#genid 1627 and file: GTN_IRD. daml#genid 1353 because SM_NM_MTCH: ele_access_nm NAME full_name Sim_Name_Property_Match COMPARE_IRD. daml#grci 9924 file: CMOS_IRD. daml#genid 971 and file: GTN_IRD. daml#genid 3474 because SM_NM_MTCH: ele_nm MANIFEST_TYPE air_manifest_type_code Sim_Name_Property_Match COMPARE_IRD. daml#grci 9926 file: GTN_IRD. daml#genid 1739 and file: CMOS_IRD. daml#genid 1019 because SM_NM_MTCH: ele_nm manifest_reference PAX_MANIFEST_REFERENCE_ID Sim_Name_Property_Match COMPARE_IRD. daml#grci 9921 file: GTN_IRD. daml#genid 3441 and file: CMOS_IRD. daml#genid 363 because SM_NM_MTCH: ele_access_nm weight TOTAL_BAG_WEIGHT Sim_Name_Property_Match COMPARE_IRD. daml#grci 9922 file: GTN_IRD. daml#genid 3441 and file: CMOS_IRD. daml#genid 1291 because SM_NM_MTCH: ele_access_nm weight PAX_WEIGHT

Content Based Publish and Subscribe DAML Annotated Content Publisher Publication Service Subscription Service XQL Content Specification Subscriber Channel Subscription Matching Channels with Selected Content Ontology Service Content Channel(s) Selected Content Broadcast Channel Manager ï Subscribers provide an XQL query as specification of their interest ï They are subscribed to channels that provide DAML annotated content that is the result of the XQL specification. ï Publishers provide DAML annotated content.

What’s Challenging. . . ï Variation in’ DAML’ Ontologies and Instance data. ï XML vs RDF ï RDFS vs DAML ï Large Ontologies ï Memory Usage ï Processing times ï Local Ontology Management ï Rules/Query ï ï Using CLIPS syntax in JESS Looking at RML Using XQLish and rules. Need a DQL

Components for Ontology Driven Information Push Source Descriptions Expert Knowledge Source Ontologies New Ideas UML Tool Adapter API Built-in Java DUET Articulation Engine Service OAB Existing Ontologies Created Ontologies Articulating Ontology Other Tools ïDUET - DAML-UML Enhanced Tool ïOAB - Ontology Articulation Builder ïOFP - Ontology Fact Processor Source DAML Ontology Manager OAB Runtime Fact Translator Query Engine OFP Fact Translator Broadcast Channel Manager • Automatic generation of semantic mapping between ontologies to facilitate database integration and content translation. • Application of an UML technology to leverage existing resources to provide Semantic knowledge engineering capability. Based Information • DAML processing components and services Request that can bring knowledge processing Semantically capability to Do. D applications. Routed DAML Impact • Leverages industry standard UML modeling tools and trained staff for Knowledge Engineering. • Provides enhanced ability to integrate disparate data in databases, messages streams and other sources. • Provides the foundation for accurate content based routing in publish and subscribe systems. • Will immediately increase precision, and as a DAML content increases, improve recall as well in information retrieval systems. FY’ 01 Prototypes and Initial Development Versions DUET with Rational Rose RDBMS Integration Tool FY’ 02 Deployment in Research and Early Adopter Programs Semantics based Pub/Sub OAB Web Service OFP Web Service FY’ 03 Transition to Operational Systems Deployed

Hot. DART Ontologies 0 ï DART Ontology describes: ï RDBMS content meta-data ï RDBMS comparison meta-data ï Articulation Ontology describes matching meta-data entities. ï Instances in the DART ontology describe RDBMS systems. ï An Articulation between DART instance is translated into the DART Compare ontology. DAML+ OIL 1 DART Ontology Articulation Ontology 2 A An Articulation Trans A-B B