Horus Technical Overview DAML PI Meeting 18 July 2001

Horus Technical OverviewDAML PI Meeting

18 July 2001

Brian KettlerHorus Technical Lead

ISX [email protected]

For Official Use Only

mailto:[email protected]

Topics Horus Toolkit

Key Requirements 5 Component Toolkits Ontologies Future Plans

Horus-DAML Interchange

Horus is a joint project of the Intelink Management Office and DARPA.

Contractors are BBN Technologies (prime), ISX Corporation, and Logicon (Sterling Federal Systems)

Key Requirements for Horus Store assertions from marked up Intelink documents and

other data sources (e.g., databases) assertions defined with respect to ontologies assertions aggregated into knowledge objects metadata stored for assertions

e.g., data source, drilldown (URLs, etc.), collection dates, validity dates, etc. Retrieve knowledge objects (and constituent assertions) in

response to queries Allow users to link knowledge objects Support development of web-based portals to browse,

query, and link knowledge objects support drilldown to original web pages, databases

Horus Version 1.0 (FY00)

Demonstration prototype Intelink Conference demo in 9/00 Demo version running now on Intelink-S

Military Units and Terrorist Events domain Portals built by Horus Team EJB/Java servlets infrastructure Support for SHOE ontologies/markup KB implemented with Parka and Oracle

Horus Toolkit Version 2 (FY01) Support DAML+OIL/RDF(S) languages for ontology

definition and markup not necessarily all of DAML’s ontology constructs support future language changes

More automation for document markup Toolkit architecture allows modular configuration and

upgrade versus Horus V1 “System” approach increased flexibility/extensibility leverage emerging DAML tools more easily

Tools for portal developers to add new data sources more easily

Horus Toolkit Technical Architecture

Knowledge BaseData Access Toolkit

Ontology Toolkit

Portal Toolkit

User(Consumer)

User(Producer)

User(Ontology Author)

User(Site DBA)

User(KB Admin)

Markup ToolkitAutomatic

Markup Tool(Aerotext+)

ManualMarkup

Tool

DocumentSubmitter

Tool

MarkupSubmitter

Tool

ReferenceResolution

Tool

OntologyAuthoring

Tools (DAML Pgm)

Ontology Validation

Tools(DAML Pgm)

Ontology Import

Tool

OntologyExportTools

HKOManager &Repository

Ontology Manager &Repository

AssertionManagement

Tools

KB Maint/Admin Toos

Markup Processor

(RDF-API+)

DS to OntologyMap Tool

DS to KBUpdateTool

ProductGeneration

(PGT)

DB

Class ViewerTool

(CVT)

HKO QueryTool

(HQT)

Data SourceQuery Tool

(DSQT)

XMLTransform

Tool (XTT)

Portal

Ontology Submission

Tool

Data Sources

Oracle

Parka

Ontology Tools (ISX, DAML)


Ontology Toolkit

Portal Toolkit

User(Consumer)

User(Producer)


User(Site DBA)

User(KB Admin)



ManualMarkup

Tool

DocumentSubmitter

Tool

MarkupSubmitter

Tool

ReferenceResolution

Tool

OntologyAuthoring

Tools (DAML Pgm)

Ontology Validation

Tools(DAML Pgm)

Ontology Import

Tool

OntologyExportTools



AssertionManagement

Tools

KB Maint/Admin Toos

Markup Processor

(RDF-API+)


DS to KBUpdateTool

ProductGeneration

(PGT)

DB

Class ViewerTool

(CVT)

HKO QueryTool

(HQT)


(DSQT)

XMLTransform

Tool (XTT)

Portal

Ontology Submission

Tool

Data Sources

Oracle

Parka

Ontology Tools Ontology Authoring Tools

GUI for authoring/editing an ontology in DAML support extension of ontologies through importing

Currently using COTS XML authoring tools (e.g, XML Spy) Future: Investigate DAML tools for ontology authoring (e.g., Protégé, OilEd, etc.)

Ontology Validation Tool Future: Check syntax/semantics of DAML ontologies (e.g., investigate DAML tools

such as Chimera) Ontology Submission Tool

GUI to submit an ontology (URL) to the KB (also done automatically) Ontology Import Tool

Reads in a DAML ontology to organize the Horus Knowledge Base Future: import ontologies from XML DTDs/Schemas, etc.

Ontology Export Tool Future: Export an ontology in other languages

Markup Tools (Logicon)


Ontology Toolkit

Portal Toolkit

User(Consumer)

User(Producer)


User(Site DBA)

User(KB Admin)



ManualMarkup

Tool

DocumentSubmitter

Tool

MarkupSubmitter

Tool

ReferenceResolution

Tool

OntologyAuthoring

Tools (DAML Pgm)

Ontology Validation

Tools(DAML Pgm)

Ontology Import

Tool

OntologyExportTools



AssertionManagement

Tools

KB Maint/Admin Toos

Markup Processor

(RDF-API+)


DS to KBUpdateTool

ProductGeneration

(PGT)

DB

Class ViewerTool

(CVT)

HKO QueryTool

(HQT)


(DSQT)

XMLTransform

Tool (XTT)

Portal

Ontology Submission

Tool

Data Sources

Oracle

Parka

Markup Tools Document Submitter

GUI to submit a new document (URL) to the markup process Automatic Markup Tool

Generates markup automatically from text in document (using Lockheed’s Aerotext product)

concepts matched in text converted to knowledge objects in DAML rules engineered to match concepts

Manual Markup Tool GUI to validate/modify knowledge objects

can take input from Automatic Markup Tool user provided form generated from ontologies

Markup Submitter Tool GUI to submit a document with DAML markup to the KB

Reference Resolution Tool Matches incoming markup assertions (from docs, DB) to existing knowledge objects

Knowledge Base Tools (ISX)


Ontology Toolkit

Portal Toolkit

User(Consumer)

User(Producer)


User(Site DBA)

User(KB Admin)



ManualMarkup

Tool

DocumentSubmitter

Tool

MarkupSubmitter

Tool

ReferenceResolution

Tool

OntologyAuthoring

Tools (DAML Pgm)

Ontology Validation

Tools(DAML Pgm)

Ontology Import

Tool

OntologyExportTools



AssertionManagement

Tools

KB Maint/Admin Toos

Markup Processor

(RDF-API+)


DS to KBUpdateTool

ProductGeneration

(PGT)

DB

Class ViewerTool

(CVT)

HKO QueryTool

(HQT)


(DSQT)

XMLTransform

Tool (XTT)

Portal

Ontology Submission

Tool

Data Sources

Oracle

Parka

Knowledge Base Tools Horus Ontology Manager and Repository

Persistently stores ontologies as Java Objects API to query ontologies (similar idea to DAML-API)

EJB interface (Oracle for Entity EJB persistence) Horus Knowledge Object Manager and Repository

Persistently stores assertions (takes DAML as input) assertions grouped into Knowledge Objects via HOIDs metadata stored on a per-assertion basis

Uses Parka KBMS and Oracle DBMS inheritance-based inference in Parka, Oracle for “bulk” retrieval

Avoids “closed world” assumptions re constraint enforcement (e.g., domain, range)

XML-based query interface (KBQL) with DAML output supports highly structured queries

EJB interface to update/query functions

Data Access Tools (Logicon)


Ontology Toolkit

Portal Toolkit

User(Consumer)

User(Producer)


User(Site DBA)

User(KB Admin)



ManualMarkup

Tool

DocumentSubmitter

Tool

MarkupSubmitter

Tool

ReferenceResolution

Tool

OntologyAuthoring

Tools (DAML Pgm)

Ontology Validation

Tools(DAML Pgm)

Ontology Import

Tool

OntologyExportTools



AssertionManagement

Tools

KB Maint/Admin Toos

Markup Processor

(RDF-API+)


DS to KBUpdateTool

ProductGeneration

(PGT)

DB

Class ViewerTool

(CVT)

HKO QueryTool

(HQT)


(DSQT)

XMLTransform

Tool (XTT)

Portal

Ontology Submission

Tool

Data Sources

Oracle

Parka

Data Access Tools Data Source to Ontology Mapping Tool

GUI for a user (DBA) to link elements of a DB schema to elements of DAML ontologies

user specifies JDBC connection information to DB user specifies DB tables/fields and mapping to ontology classes/properties stores mapping persistently – used by other Horus tools

Data Source to KB Update Tool Uses DB-to-Ontology mapping to update the KB

sends DAML to the KB for new data, after reference resolution (if required) using Reference Resolution Tool

can be run by user, triggered by cron job, etc. Product Generation Tool

Provides drilldown information from a data source generates a product as XML from DB XSL applied to XML to generate HTML

Portal Tools (Logicon)


Ontology Toolkit

Portal Toolkit

User(Consumer)

User(Producer)


User(Site DBA)

User(KB Admin)



ManualMarkup

Tool

DocumentSubmitter

Tool

MarkupSubmitter

Tool

ReferenceResolution

Tool

OntologyAuthoring

Tools (DAML Pgm)

Ontology Validation

Tools(DAML Pgm)

Ontology Import

Tool

OntologyExportTools



AssertionManagement

Tools

KB Maint/Admin Toos

Markup Processor

(RDF-API+)


DS to KBUpdateTool

ProductGeneration

(PGT)

DB

Class ViewerTool

(CVT)

HKO QueryTool

(HQT)


(DSQT)

XMLTransform

Tool (XTT)

Portal

Ontology Submission

Tool

Data Sources

Oracle

Parka

Portal Tools Class Viewer Tool

Java servlet that displays class hierarchies from ontologies ontology obtained from KB Ontology Manager

Used by other Horus tools (Manual Markup, DS to Ontology Mapping tool, etc.) Horus Query Tool

Java servlet that presents a query form, dynamically generated from class/properties in an ontology, and displays query results

ontology obtained from KB Ontology Manager query sent in XML (KBQL) to KB HKO Manager and DAML results displayed as HTML

(via XTT/XSL) Data Source Query Tool

Java servlet that displays product dynamically generated from DB for drilldown product generated by Product Generation Tool and converted to HTML (via XTT/XSL)

Horus Ontologies Developed in DAML Authored by Horus Team, with inputs from subject

matter experts at Joint Analysis Center (Molesworth, UK) Focus domain is Geopolitical (Balkans) Studied applicable ontologies

JAC E-Point Taxonomy, JIVA K-MAPS, IMO general/security metadata, DAML-ized CIA World Factbook

Studied domain exemplars – e.g., Eurasian Intelligence Digests

COTS Tools (e.g., XML Spy) used to encode ontologies in DAML

Developed 10 new DAML ontologies for Horus/JAC 278 Classes, 137 ObjectProperties, 117 DatatypeProperties unclassified, “For Official Use Only”

Details on access for DAML PIs forthcoming…

Horus Ontology Hierarchy

Horus generic ontologies Horus Base Horus Locus Horus Person-Organization Horus Common Horus Installation Military Unit

JAC specific ontologies JAC Upper-Level JAC Geopolitical Issue JAC Geopolitical Influence JAC Geopolitical

Horus-DAML Program Interchange DAML to Horus

DAML Program is source of language, tools, and ontologies

Horus to DAML Horus is source of requirements for real-world

systems (e.g., a DAML “use case”) Horus is a testbed for DAML technology

e.g., scalability, usability, etc. Horus is a source of DAML tools too

Horus Tools for DAML Markup

Manual Markup Tool Automatic Markup Tool (Aerotext)

Data Access Tools map schema to DB generate DAML from DB

KB (Parka/Oracle) store/retrieve assertions

Portal Tools servlets to access KB and DBs servlets to navigate ontologies

Potential DAML Tools for Horus(*=have used already) Parsers

have used RDF-API*, SIRPAC* some memory issues with RDF-API (large # of triples with metadata)

Ontology Authoring Tools Authoring - e.g., Protégé, OilEd

need ones to support “end user” (SME) authoring Visualization – e.g., Dumpont*, graphical Validation – e.g., Chimera Need APIs to launch these tools easily from Horus Tools

Markup Tools Authoring – e.g., Teknowledge Powerpoint/Word Visualization – e.g., HyperDAML* Validation – e.g., BBN DAML Validator*

need support for streaming Need APIs to launch these tools easily from Horus Tools

Other Horus Needs – KB Technologies KB Validation

find invalid assertions using ontologies and flag to KBA, etc. levels of validation: vs. ontology (e.g., domain/range) to organizational (e.g.,

authorization) consolidate HKOs/assertions

KB Processing tools that exploit assertions in KB

temporal/spatial reasoning, fusion, other kinds of analysis/processing other kinds of inference

e.g., support for inverse and transitive properties rules may investigate XSB, etc.

KB Distribution multiple, distributed KBs

Other Horus Needs – Language Issues Metadata/Tagging

e.g., using RDF reification (bags, aboutEach) URLs across networks (e.g., SIPRNET, JWICS)

both for fixed pages (e.g., w3c.org) and ontologies/markup Enumerated types (e.g., Country Codes)

several options DAML enumeration in ontology predefined/preloaded KB instances XSD datatype

Query languages we invented a simple XML one (KBQL)

geared towards Horus implementation somewhat Support for rules

Conclusions Horus completing second year of development

new “toolkit” approach for Horus-enabling user sites support for DAML language consumer/producer of DAML tools

Horus is a good use case for DAML e.g., centralized KB, toolkit approach real users to be evaluating Horus-enabled portals this Fall need to support much better than “demo quality” use

user-authored ontologies (with some training/support) versioning, etc.

document markup navigation, search, and linking through portals

Future Work new tools packaging/distribution of tools over Intelink new user sites

Continued interchange with DAML Program planned

Documents

Horus Technical Overview DAML PI Meeting 18 July 2001