Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "19 July 2001 Lewis Hart GRC International, an AT&T Company."— Presentation transcript:

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

2 Whats Hot... DAML-UML Enhanced Tool Imports / Exports, Implements UML- DAML mapping Interface to Articulation Service Built from re-useable DAML components DAML API, Articulation Service, UMM API Addin for Rational Rose Argo UML coming. RDBMS Articulation Rule-based Java Expert System Shell (Jess) Extensible with Java. Validated on real world systems - GTN/CMOS RDBMS Ontologies 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 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

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

4 Articulation Ontology Articulation Articulation

5 HotDART Articulation Service DAML API Jess DART Import XSLT Export XSLT DUET Rational Rose Rational Rose Rose Adapter UMM API Ontology Articulation Service 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.

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

7 Structural Match Matching elements found in matching tables. Example Match Structural, Not Perfect WorkOrder file:Shipyard_3.daml#genid662 WorkOrder file:Shipyard_2.daml#genid735 WorkOrderID file:Shipyard_3.daml#genid308 OrderID file:Shipyard_2.daml#genid342 c:MatchFactor rdf:about="grci3030 d:detail="grci3027 grci2999" d:kind="ELE_TBL_MTCH" d:strength="9"> c:reasons Tables Elements

8 Example Rule and Matches Jess Rule (defrule Sim_Name_Property_Match (declare (salience 10)) ;; Get a name property's info (NameProperty (name ?pnam) (strength ?pstr0) ) (DAMLProperty (localName ?pnam) (OBJECT ?ptype)) ;; Find one property of this type. (DAMLProperty (type ?ptype) (ID ?id1) (namespace ?ns1) (subject ?sub1) (object ?obj1) ) ;; Find another property of this type. (DAMLProperty (type ?ptype) (ID ?id2&~?id1) (namespace ?ns2&~ns1) (subject ?sub2) (object ?obj2) ) ;; Compare there names as phrases. (test (not (sameIC (?obj2 getValue) (?obj1 getValue)))) (bind ?pstr (comparePhraseIC (?obj1 getValue) (?obj2 getValue))) (test (>= ?pstr 8 )) => (bind ?mf (createMF ?sub1 ?sub2 (str-cat "SM_NM_MTCH:" ?pnam) (str-cat (?obj1 getValue) "|" (?obj2 getValue)) ?pstr )) ;; Log it (printout t "Sim_Name_Property_Match " (?mf getID) ;; etc…. ) GTN-CMOS Matches Sim_Name_Property_Match COMPARE_IRD.daml#grci9920 file:CMOS_IRD.daml#genid1627 and file:GTN_IRD.daml#genid3586 because SM_NM_MTCH:ele_access_nm NAME desig_name Sim_Name_Property_Match COMPARE_IRD.daml#grci9923 file:CMOS_IRD.daml#genid1627 and file:GTN_IRD.daml#genid2095 because SM_NM_MTCH:ele_access_nm NAME passenger_name Sim_Name_Property_Match COMPARE_IRD.daml#grci9928 file:CMOS_IRD.daml#genid1627 and file:GTN_IRD.daml#genid1561 because SM_NM_MTCH:ele_access_nm NAME last_name Sim_Name_Property_Match COMPARE_IRD.daml#grci9925 file:CMOS_IRD.daml#genid1627 and file:GTN_IRD.daml#genid1353 because SM_NM_MTCH:ele_access_nm NAME full_name Sim_Name_Property_Match COMPARE_IRD.daml#grci9924 file:CMOS_IRD.daml#genid971 and file:GTN_IRD.daml#genid3474 because SM_NM_MTCH:ele_nm MANIFEST_TYPE air_manifest_type_code Sim_Name_Property_Match COMPARE_IRD.daml#grci9926 file:GTN_IRD.daml#genid1739 and file:CMOS_IRD.daml#genid1019 because SM_NM_MTCH:ele_nm manifest_reference PAX_MANIFEST_REFERENCE_ID Sim_Name_Property_Match COMPARE_IRD.daml#grci9921 file:GTN_IRD.daml#genid3441 and file:CMOS_IRD.daml#genid363 because SM_NM_MTCH:ele_access_nm weight TOTAL_BAG_WEIGHT Sim_Name_Property_Match COMPARE_IRD.daml#grci9922 file:GTN_IRD.daml#genid3441 and file:CMOS_IRD.daml#genid1291 because SM_NM_MTCH:ele_access_nm weight PAX_WEIGHT

9 Content Based Publish and Subscribe 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. Publication Service Ontology Service Subscription Service Subscriber Publisher Broadcast Channel Manager DAML Annotated Content Matching Channels with Selected Content XQL Content Specification Content Channel(s) Channel Subscription

10 Whats 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

11

12 Components for Ontology Driven Information Push 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. New Ideas 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 knowledge engineering capability. DAML processing components and services that can bring knowledge processing capability to DoD applications. FY01 Prototypes and Initial Development Versions FY01 Prototypes and Initial Development Versions FY02 Deployment in Research and Early Adopter Programs FY02 Deployment in Research and Early Adopter Programs FY03 Transition to Operational Systems FY03 Transition to Operational Systems Existing Ontologies OFP Broadcast Channel Manager OAB Runtime Fact Translator Query Engine Fact Translator OAB Articulation Engine Ontology Manager Articulation Service A P I DUET UML Tool Built-in Tool Adapter Articulating Ontology Source Ontologies Java Source Descriptions Source Descriptions Expert Knowledge API Created Ontologies Other Tools Other Tools Semantic Based Information Request Semantically Routed DAML Source DAML DUET - DAML-UML Enhanced Tool OAB - Ontology Articulation Builder OFP - Ontology Fact Processor DUET with Rational Rose RDBMS Integration Tool OAB Web Service Semantics based Pub/Sub OFP Web Service Deployed

13 Trans DAML+ OIL Articulation Ontology AB A-B DART Ontology An Articulation HotDART Ontologies 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


Download ppt "19 July 2001 Lewis Hart GRC International, an AT&T Company."

Similar presentations


Ads by Google