1 / 13

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

19 July 2001 Lewis Hart GRC International, an AT&T Company. 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

taite
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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 What’s Hot ...

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

  4. Articulation Ontology <!-- **** Articulation **** --> <daml:Class rdf:ID = 'Articulation' > <daml:subClassOf> <daml:Restriction> <daml:onProperty rdf:resource='#matches'/> <daml:toClass rdf:resource='#Match'/> </daml:Restriction> </daml:subClassOf> <daml:subClassOf> <daml:Restriction> <daml:onProperty rdf:resource='#matchFactor'/> <daml:toClass rdf:resource='#MatchFactor'/> </daml:Restriction> </daml:subClassOf> <daml:label>Articulation</daml:label> </daml:Class>

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

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

  7. Example MatchStructural, Not Perfect WorkOrder file:Shipyard_3.daml#genid662 WorkOrder file:Shipyard_2.daml#genid735 http://www.daml.org/2001/03/daml+oil#equivalentTo <c:Match rdf:about="grci2999" d:strength=”9.84" > <c:Match rdf:about="grci3027" d:strength="8.60" > WorkOrderID file:Shipyard_3.daml#genid308 OrderID file:Shipyard_2.daml#genid342 http://www.daml.org/2001/03/daml+oil#equivalentTo Tables c:reasons <c:MatchFactor rdf:about="grci1730" d:kind="EX_NM_MTCH:tbl_nm” d:detail=“WorkOrder” d:strength="8"> • Structural Match • Matching elements • found in matching • tables. <c:MatchFactor rdf:about="grci1819" d:detail="Unique marina work order ID." d:kind="PHRASE_MTCH:ele_defn" d:strength="8"> <c:MatchFactor rdf:about="grci3029" d:detail="grci3027 grci2999" d:kind="TBL_ELE_MTCH" d:strength="3"> c:MatchFactor rdf:about="grci3030” d:detail="grci3027 grci2999" d:kind="ELE_TBL_MTCH" d:strength="9"> <c:MatchFactor rdf:about="grci1825" d:detail="INTEGER" d:kind="EX_DT_MTCH:ele_data_type” d:strength="2"> c:reasons Elements

  8. Example Rule and Matches 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 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…. )

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

  10. 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 What’s Challenging ...

  11. Backup Stuff

  12. Components for Ontology Driven Information Push Source Ontologies Expert Knowledge Java OAB DUET UMLTool Built-in Articulation Service Articulation Engine API A P I Tool Adapter Articulating Ontology Other Tools Created Ontologies Semantic Based Information Request OFP OAB Runtime Query Engine • DUET - DAML-UML Enhanced Tool • OAB - Ontology Articulation Builder • OFP - Ontology Fact Processor Broadcast Channel Manager Semantically Routed DAML Fact Translator Fact Translator Source DAML Ontology Manager OFP Web Service Deployed OAB Web Service DUET with Rational Rose RDBMS Integration Tool Semantics based Pub/Sub Source Descriptions • 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. Existing Ontologies • 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 • FY’02 • Deployment in • Research and Early • Adopter Programs FY’03 Transition to Operational Systems

  13. HotDART Ontologies DAML+ OIL Articulation Ontology DART Ontology A B An Articulation A-B Trans • 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. 0 1 2

More Related