ASA Proof of Concept DAMl by alicejenny

VIEWS: 3 PAGES: 13

									                                      HotDAML Driven Information Push

The objective of HotDDIP is to provide content based knowledge management
  and distribution for a stream of DAML annotated documents.

   • Value added annotations.                                            Web-based Access
   • Citation of other documents.
   • Document Search and
   Retrieval
                                                Source N                           Analysis,
                                       Source               Document
                                        Doc                                        Review,
                                                Source 1    Processing
                                                                                 Administration
              • URN assignment
              • Transformations                            Meta-
                                                                    Tagged
                                                                                      Notifi-   Anno-
              • Structural Tagging                                  Source
                                                           Data                       cation    tations
                                                                     Doc
              • Create Meta-data

• Document Management                                              Publish & Subscribe
• Topic and Sub-topic
• Basic Geo-spatial and Temporal

              • Structurally Tagged
              • Formatted                                                    Document
                                                                             Repository
     •Semantic based Publish
     and Subscribe
     • Notification Generation        •DAML Centric Document
     • Feed to Repository             Repository.
                                              HotDDIP Project
                                                   Document Model

         Working Documents
                                     •   Working Documents
                                          –   Fluid Working Environment
                                          –   Migrate to Repository
                                     •   Document Repository
                                          –   XML/RDF/DAML Centric
 Analysis, Meta-Data &                    –   Repository is “read-only”
 Other Annotations
                                     •   Documents Tagged with concepts from
                                         various DAML ontologies
                                          –   Citation Ontology - provides citation down
                                              to paragraph level.
                                          –    Document Structure Ontology - Structural
                                              concepts for various formats.
                                          –   Reference Ontology(s) - Specific reference
                                              domain concepts.
                                          –   Domain Ontology(s) - Specific analysis
Domain Specific          Reference            domain concepts.
                                          –   Analysis Ontology - Provides terms used
           Document Repository                for analysis rational and conclusions.
                                                                              HotDDIP Project
                                                                   Publish and Subscribe Demonstration

ASA Simulation
                                                                                             Talker
                                 Command
                              Logistic
            Alternative        and Control
     Platform                 Systems
      Sensor
    Assessment
              Action
             Analyzer
                           System Interface
                             Interfaces
                                                                                             Listener
                              TOC
                          Command and
                          Control
                                              HotDDIP Publish and Subscribe
                          System
                          Interface

                                               XSLT
                                               Engine          Ontology
                                   XML                                        Subscription
                                                                Service
Phase I                                                                         Service
                                                 Publication
                                                  Service           Query
Phase II                                                            Service          BCM
                                      DAML
                                              Various

                                                         Document Repository
                                                          •RetrivalWare
                                                          •Sybase EP
DAML Crawler                                              •Other


  Document Feeder
HotDART
Hot Data Analysis and
Reconciliation Tool

Lewis Hart
James Lu
                                                HotDART Components

                                       •DART - provides a foundation for mapping and
Leveraging IR&D funding, and            analytical functions.
existing GRCI developed GOTS
applications to build a distributed,       –Import Meta-Data from Oracle DBMS, MS Access,
web centric RDBMS meta-data                 ER/Win, Oracle designer 2000, SQL Scripts, XML,
analysis and management tool.               UML
                                           –Comparative Analysis supports Database Mapping,
                                            Data interoperability, Migration and Integration
                                       •DAML - provides an Articulation Service for
     DART                               further analysis of meta-data.
                                           – DAML Ontology for the description of relational
                                            databases and articulations between.
                     DMIR                  – Rule based identification of candidate mappings
                                            between subjects, tables, and elements in RDBMSs.
   DAML
                                       •DMIR - provides a web portal with tools for further
                                        analysis and a repository for past results.
                                           – Web based access to analysis and reporting tools.
                                           – Shared repository for RDBMS meta-data
                                            descriptions and comparisons between RDBMS
                                            systems.
                                                               HotDART Project
                                                                  Phase I Demonstration

 GTN
                  DART                                  GTN :
                                                        CMOS
                                                                         DMIR                 WWW
CMOS

  DART XML          Import         Export            DART XML
  Registration       XSLT           XSLT             Comparison

                   Articulation Service
                       DAML API                       Rules
                           Jess

• Sub-set of Global Transportation Network (GTN) and       •      The Articulation Service identifies matching tables
  Cargo Movement Operations System (CMOS) meta-                   and elements in the two system, and creates an
  data has been imported into DART.                               Articulation ontology comparing the two systems.

• DART exports the data in an XML format, which is         •      The articulation ontology is transformed back into
  transformed into RDF/DAML matching a DART                       XML and imported by DART, which exports the
  RDBMS ontology.                                                 results to DMIR.

• CODIP Articulation Service reads the transformed         •      DMIR provides WWW access to review and
  XML and asserts the DAML into Jess using the                    modify the results.
  DAML API.
                                                                      Example Match
                                                                            Simple, ‘Perfect’

                                                Elements
      BoatWidth                     http://www.daml.org/2001/03/daml+oil#equivalentTo             BoatWidth
file:Shipyard_2.daml#genid308                                                              file:Shipyard_3.daml#genid311



                                              <c:Match
                                               rdf:about="grci2659"
                                               d:strength="10.00" >




      <c:MatchFactor rdf:about="grci1913"                                         c:MatchFactor rdf:about="grci2271”
                                                      c:reasons
       d:detail="BoatWidth"                                                        d:detail="Boat width in meters rounded up."
       d:kind="EX_NM_MTCH:ele_nm"                                                  d:kind="PHRASE_MTCH:ele_defn"
       d:strength="7">                                                             d:strength="10">




         <c:MatchFactor rdf:about="grci2394"                           <c:MatchFactor rdf:about="grci2341"
          d:detail="BoatWidth"                                          d:detail="FLOAT8"
          d:kind="EX_NM_MTCH:ele_access_nm"                             d:kind="EX_DT_MTCH:ele_data_type"
          d:strength="6">                                               d:strength="2">
                                                                                Example Match
                                                                                   Structural, Not Perfect

                                                              Tables
                WorkOrder                    http://www.daml.org/2001/03/daml+oil#equivalentTo         WorkOrder
          file:Shipyard_3.daml#genid662                                                          file:Shipyard_2.daml#genid735

                                          c:reasons     <c:Match
<c:MatchFactor rdf:about="grci1730"                         rdf:about="grci3027"
 d:kind="EX_NM_MTCH:tbl_nm”                                 d:strength="8.60" >
                                                                                                     <c:MatchFactor rdf:about="grci1819"
 d:detail=“WorkOrder”
                                                                                                      d:detail="Unique marina work order ID."
 d:strength="8">
                                                                                                      d:kind="PHRASE_MTCH:ele_defn"
                                                                                                      d:strength="8">
<c:MatchFactor rdf:about="grci3029"                Structural Match
 d:detail="grci3027 grci2999"
                                                                                                     c:MatchFactor rdf:about="grci3030”
 d:kind="TBL_ELE_MTCH"                              Matching elements                                 d:detail="grci3027 grci2999"
 d:strength="3">
                                                    found in matching                                 d:kind="ELE_TBL_MTCH"
                                                                                                      d:strength="9">
                                                    tables.
                                                                                                     <c:MatchFactor rdf:about="grci1825"
                                                                                                      d:detail="INTEGER"
                                                                                                      d:kind="EX_DT_MTCH:ele_data_type”
                                                        <c:Match                                      d:strength="2">
                                                            rdf:about="grci2999"        c:reasons
                                                            d:strength=”9.84" >


              WorkOrderID                                                                                OrderID
          file:Shipyard_3.daml#genid308      http://www.daml.org/2001/03/daml+oil#equivalentTo   file:Shipyard_2.daml#genid342


                                                           Elements
                                                  HotDART Project
                                                    Phase II and Beyond

                    Web Application
                                                                    •Upload
      DART                  Server                                  •Author
      Services                                                      •Analyze
     Articulation                           WWW
       Service          DMIR
     Translation             A-B
       Service



•   Integration into a Web Application Server to provide DMIR portal with complete
    RDBMS meta-data management capability.
•   Addition of Translation, Migration and other services to provide additional
    functionality. Use as a test-bed for enhanced articulation technology.
•   Apply to current Marine Corp Systems Command (MCSC) Shared Data Environment
    (SDE) integration efforts and to future potential efforts such as GTN2.
•   Provide community access to DMIR portals into facilitate integration, migration, and
    interoperability in an operational community's data environment.
                                    HotDART Ontologies

                                    0              DAML+
                                                    OIL


• DART Ontology describes:          1
    – RDBMS content meta-data       Articulation                    DART
                                      Ontology                     Ontology
    – RDBMS comparison meta-data
• Articulation Ontology describes
  matching meta-data entities.
                                    2
                                                                       A      B
• Instances in the DART ontology
  describe RDBMS systems.
• An Articulation between DART
                                         An
  instance is translated into the        Articulation      Trans       A-B
  DART Compare ontology.
                                                                     Example Rule and Matches
                                                                     GTN-CMOS Matches
Jess Rule
                                                                     Sim_Name_Property_Match COMPARE_IRD.daml#grci9920
(defrule Sim_Name_Property_Match                                      file:CMOS_IRD.daml#genid1627 and
  (declare (salience 10))                                             file:GTN_IRD.daml#genid3586 because
  ;; Get a name property's info                                       SM_NM_MTCH:ele_access_nm NAME desig_name
  (NameProperty
    (name ?pnam)                                                     Sim_Name_Property_Match COMPARE_IRD.daml#grci9923
    (strength ?pstr0)                                                 file:CMOS_IRD.daml#genid1627 and
    )                                                                 file:GTN_IRD.daml#genid2095 because
  (DAMLProperty                                                       SM_NM_MTCH:ele_access_nm NAME passenger_name
    (localName ?pnam)
    (OBJECT ?ptype))                                                 Sim_Name_Property_Match COMPARE_IRD.daml#grci9928
  ;; Find one property of this type.                                  file:CMOS_IRD.daml#genid1627 and
  (DAMLProperty                                                       file:GTN_IRD.daml#genid1561 because
    (type ?ptype)
                                                                      SM_NM_MTCH:ele_access_nm NAME last_name
    (ID ?id1)
    (namespace ?ns1)
                                                                     Sim_Name_Property_Match COMPARE_IRD.daml#grci9925
    (subject ?sub1)
                                                                      file:CMOS_IRD.daml#genid1627 and
    (object ?obj1)
                                                                      file:GTN_IRD.daml#genid1353 because
    )
  ;; Find another property of this type.                              SM_NM_MTCH:ele_access_nm NAME full_name
  (DAMLProperty
    (type ?ptype)                                                    Sim_Name_Property_Match COMPARE_IRD.daml#grci9924
    (ID ?id2&~?id1)                                                   file:CMOS_IRD.daml#genid971 and
    (namespace ?ns2&~ns1)                                             file:GTN_IRD.daml#genid3474 because
    (subject ?sub2)                                                   SM_NM_MTCH:ele_nm MANIFEST_TYPE
    (object ?obj2)                                                                  air_manifest_type_code
    )
  ;; Compare there names as phrases.                                 Sim_Name_Property_Match COMPARE_IRD.daml#grci9926
  (test (not (sameIC (?obj2 getValue) (?obj1 getValue))))             file:GTN_IRD.daml#genid1739 and
  (bind ?pstr (comparePhraseIC (?obj1 getValue) (?obj2 getValue)))    file:CMOS_IRD.daml#genid1019 because
  (test (>= ?pstr 8 ))
                                                                      SM_NM_MTCH:ele_nm manifest_reference
=>
  (bind ?mf (createMF ?sub1 ?sub2                                                    PAX_MANIFEST_REFERENCE_ID
    (str-cat "SM_NM_MTCH:" ?pnam)
    (str-cat (?obj1 getValue) "|" (?obj2 getValue))                  Sim_Name_Property_Match COMPARE_IRD.daml#grci9921
    ?pstr                                                             file:GTN_IRD.daml#genid3441 and
    ))                                                                file:CMOS_IRD.daml#genid363 because
  ;; Log it                                                           SM_NM_MTCH:ele_access_nm weight TOTAL_BAG_WEIGHT
  (printout t "Sim_Name_Property_Match " (?mf getID)
  ;; etc….                                                           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

								
To top