# Presentation: 083311

## The Critical First Year:  Introducing Semantic Technologies into an Organization

*John M. Linebarger, PhD*
*Bettina K. Schimanski, PhD*
- Sandia National Laboratories
- 23 May 2007

## Outline

- Technology Diffusion is a Process of Organizational Change
- The Critical First Year
- Timeline
- Semantic Technology Project Descriptions
- Reflections and Recommendations
- Organizational
- Marketing
- Ontology Development
- Tools and Support
- Resources

## Diffusion of Innovations

- Everett M. Rogers (University of New Mexico)
- Technology diffusion is a process of organizational change
- The change process follows a predictable pattern
- Early adopters (opinion leaders) are vitally important in the process

- Image source:  http://www.mitsue.co.jp/english/case/concept/02.html

## Outline

- Technology Diffusion is a Process of Organizational Change
- The Critical First Year
- Timeline
- Semantic Technology Project Descriptions
- Reflections and Recommendations
- Organizational
- Marketing
- Ontology Development
- Tools and Support
- Resources

## Timeline of “The Critical First Year”

- Nov. 2005—Full-time on Semantic Technologies for the National Infrastructure Simulation and Analysis Center
- Dec. 2005—Semantic Working Group formed
- May 2006—Pædogogical Application created
- July 2006—Semantic Navigation prototype and user tests with the help of student interns
- Oct. 2006—Lockheed Martin Shared Vision project involvement; hired a second person for Semantics
- Nov. 2006—FEMA IPAWS project involvement
- Dec. 2006—First Semantic Web application placed into production (NISAC program)
- Jan. 2007—Virtual Manufacturing project involvement

## The NISAC Program

- The National Infrastructure Simulation and Analysis Center (NISAC) program is sponsored by the Department of Homeland Security (DHS)
- NISAC is often called upon to quickly analyze the impact on critical infrastructures of a potential future event
- Fast Analysis and Simulation Team (FAST) exercises
- Time-limited (from four hours to several days)

## NISAC CIP KM Portal

- Critical Infrastructure Protection (CIP) Knowledge Management (KM) Portal
- Supports rapid access of information during a FAST exercise
- Documents
- Presentations
- Media files
- Links to external Web pages
- Information is organized using multiple taxonomies, which has not proven to be sufficient
- Programs
- Projects
- Infrastructures
- Tools
- Models
- Keyword search has well-known limitations

## Semantics in the NISAC Program

- Ontology development
- Critical Infrastructure Protection (CIP)
- CIP Knowledge Management (KM)
- Semantic Navigation of the CIP KM Portal (prototype)
- Synonym expansion of keywords used to search the CIP KM Portal (production)

## Semantic Navigation of the CIP KM Portal

## Why Was the Prototype Never Productionized?

- Funding downturn in the NISAC program
- Expense of semantically tagging almost 9,000 documents
- With student help, over 10% were tagged in a few weeks
- Semi-automatic approaches are being investigated
- Expense of re-implementing the _[portalCore](http://www.swed.org.uk/swed/swed_technical_resources.htm)_ interface using the Tapestry Web application framework
- Performance issues in determining document counts
- Semantic Navigation examples on the Web generally assume that all information is available to everyone
- Access group-based security schemes mean that document counts can potentially be different for every person, which is time-consuming to calculate on the fly

## What Did We Do Instead?

- “Low-hanging fruit”
- Automatic expansion of search keywords into synonyms
- Allows more documents to be retrieved
- Simple Knowledge Organization System (SKOS) used as the representation mechanism
- RDF-based, so synonyms can link directly to the concepts in our OWL ontology
- Lighter-weight and more specifically tailored to our purposes than OWL
- Two kinds of synonyms
- Domain-independent synonyms, taken from the WordNet project and transformed into SKOS via XSLT
- Domain-dependent synonyms, culled from documents, Web pages, and our end users, and entered via a text editor

## Synonym Expansion Process Overview

- Enter keyword in search box

- Use SPARQL to expand keyword into all synonyms

- Create SQL statement with highest priority synonyms

- Pass SQL statement to Oracle
- to retrieve documents

- Synonyms in SKOS

- Documents in Oracle

- Source of synonyms

- one time conversion

## Synonym Expansion for Keyword Search

## NISAC Program Lessons Learned

- An incubator project is generally needed in order to introduce semantic technology into an organization
- Semantic technology is ready for production use, at least in low-to-medium volume environments
- Performance issues remain in high-volume environments
- Considerable work is required to integrate semantic technology into an existing production environment
- Semantic navigation is becoming a “standard” application of semantic technologies
- It is vitally important to pick a problem that your users really care about or are interested in
- Because it is so new, support for semantic technologies may be jeopardized by a funding downturn

## Semantic Web Advanced Toolkit (SWAT)

- 	Lockheed Martin-sponsored project to apply a statistical text analysis tool (STANLEY, for Sandia Text ANaLysis Extensible librarY) to the ontology development life-cycle
- Ontology learning from unstructured text corpora
- Classes (entities)
- Properties (*e.g.,* verbal relationships between entities, part-whole relations)
- Upper-level ontology taken from WordNet
- Semi-automated semantic annotation
- Ontology evolution and maintenance

## SWAT Lessons Learned

- Both ontology learning and semiautomated semantic annotation benefited from the use of a statistical text analysis tool
- More work is needed to determine the appropriate analysis parameters in order for ontology evolution and maintenance to benefit from statistical text analysis
- Automating the creation of ontologies and semantic metadata can facilitate the adoption of semantic technologies
- Successful implementation of a semantic technology project generally requires the integration of multiple technologies

## FEMA IPAWS

- Integrated Public Alert and Warning System (IPAWS) for Federal Emergency Management Agency (FEMA)
- Ontology-based publish and subscribe mediation system for alert and warning messages
- Messages published and subscribed to in terms of the ontology of each Community of Interest
- Message routing done by mapping COI ontologies to a normative ontology

## FEMA IPAWS Lessons Learned

- “Ontology” is a very plastic word
- For some, “ontology” means synonym resolution or vocabulary mapping
- For others, “ontology” is really a glorified taxonomy
- An ontology for “Ontology” is needed
- As a result, the technologies required in an “ontology” project can vary widely
- Semantic Web technology is not the only choice
- Other options
- Frame-based or Logic-based knowledge representations
- XML Topic Maps
- National Information Exchange Model (NIEM), which is XML Schema-based

## Virtual Manufacturing Supply Chain

- Information integration of the virtual manufacturing supply chain in the nuclear weapons complex
- Small-scale virtual manufacturing enterprise (VME)
- Ontology mapping
- “Plug and play” semantic navigation

## Virtual Manufacturing Lessons Learned

- Information integration is a “standard” application of semantic technology
- Electronic Data Interchange (EDI) for the 21st century
- Semantic technology is so new that you may need to find creative ways to fund it
- Write academic papers to demonstrate credibility
- Internal research project funding
- Technology infusion program funding

## Outline

- Technology Diffusion is a Process of Organizational Change
- The Critical First Year
- Timeline
- Semantic Technology Project Descriptions
- Reflections and Recommendations
- Organizational
- Marketing
- Ontology Development
- Tools and Support
- Resources

## Organizational Recommendations

- Attach yourself initially to an innovator or early adopter
- Begin with a “skunk works” team of 1-2 people working full-time
- Organize a semantics working group for knowledge sharing and set up a Wiki for it
- Don’t underestimate the learning curve, or the difficulty of integrating into existing systems
- Train internally if possible, but may need to hire externally
- Prototype and productionize early and often
- Semantic metadata is expensive!  Automate or support its creation.
- Pick problems people care about
- Must move beyond early adopters by demonstrating value to the wider organization to survive

## Early Adopters

- They can find you
- Working group Web site
- Marketing materials
- You can find them
- Project meetings
- Political connections
- You can create them
- Technology evangelism
- On-line demonstrations of semantic technology from the annual _[Semantic Web Challenge](http://challenge.semanticweb.org/)_
- But don’t get too dependent upon them ...

- Image source:  http://stylinonline.stores.yahoo.net

## Semantic Working Group (SWG)

## Learning Curve for Required Skill Sets

| Semantic Navigation Prototype |
| --- |
| OWL/RDFS/RDF |
| Protégé/Eclipse |
| Java Servlets |
| Jena API |
| Jena Rules |
| XSLT/XPath |
| Velocity Template Engine/HTML |
| Ant |
| Oracle |

| Synonym Expansion of Keywords |
| --- |
| OWL/SKOS/
RDFS/RDF |
| Protégé/Eclipse |
| Java Servlets |
| Tapestry/HTML |
| Jena API |
| SPARQL |
| XSLT/XPath |
| WordNet API |
| Ant/Watir/log4j |
| Oracle |

| Semantic Web Advanced Toolkit |
| --- |
| OWL/RDFS/RDF |
| Protégé/Visual Studio/Eclipse |
| C#/Java |
| Jena API |
| SPARQL |
| STANLEY API |
| WordNet API |
| NUnit |
| Pellet |

## Outline

- Technology Diffusion is a Process of Organizational Change
- The Critical First Year
- Timeline
- Semantic Technology Project Descriptions
- Reflections and Recommendations
- Organizational
- Marketing
- Ontology Development
- Tools and Support
- Resources

## Marketing Recommendations

- Practice (safe) promiscuous technology evangelism
- Define, Explain, Differentiate, Demonstrate
- Such evangelism must be scalable
- One-slide elevator speech
- 15-minute management-level presentation
- 2 hour technical presentation
- Articulate a vision for the rollout of semantic technologies in your company or organization
- The Web site for your Working Group can also serve as a marketing tool
- Demonstrations and Tools
- Presentations and Publications
- Other important items
- Glossy marketing materials
- Motivating scenario
- Pædogogical ontology and applications

## NISAC Semantics Fact Sheet

## Motivating Scenario

- Imagine a team of employees collaborating on-line on a time-critical analysis of avian flu.  One employee posts a document under ‘Avian Influenza,’ while another marks theirs as ‘Bird Flu.’  A third, pressed for time, abbreviates the topic as ‘AI.’  Each person uses his or her own filing system and organizational taxonomy, and when a keyword search is performed, the computer has no idea that ‘Avian Influenza’ is ‘Bird Flu’ is ‘AI.’
- With deadlines looming, no one can find the others’ documents, at least by keyword, leading to stress, delays, and unnecessary headaches.  This is an example of the Semantic Problem.

##  ?

-      AI

- Avian
- Influenza

-  ?

-      Bird
-       Flu

## Synonym Resolution

- “Avian Flu”
- “AI”
- “Bird Flu”

## Polysemy (Ambiguity) Resolution

- “Avian Flu”
- “AI”
- “AI”
- “AI”
- “Bird Flu”

## The Semantic Problem 

- 'When **I** use a word,' Humpty Dumpty said, in a rather scornful tone,' it means just what I choose it to mean, neither more nor less.'

- 'The question is,' said Alice, 'whether you *can* make words mean so many different things.'
- 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'

- From _[Through the Looking Glass](http://birrell.org/andrew/alice/lGlass.pdf)__[ ](http://birrell.org/andrew/alice/lGlass.pdf)__by __[Lewis Carroll](http://www.mattababy.org/~belmonte/Publications/Books/CSaW/2_language.html#Dodgson)_

## Jabberwocky

- 'Twas brillig, and the slithy tovesDid gyre and gimble in the wabe:All mimsy were the borogoves,And the mome raths outgrabe.
- “Beware the Jabberwock, my son!The jaws that bite, the claws that catch!Beware the Jubjub bird, and shunThe frumious Bandersnatch!”
- He took his vorpal blade in hand;Long time the manxome foe he sought --So rested he by the Tumtum tree,And stood a while in thought.
- And, as in uffish thought he stood,The Jabberwock, with eyes of flame,Came whiffling through the tulgey wood,And burbled as it came!

- One, two! One, two! And through and throughThe vorpal blade went snicker-snack!He left it dead, and with its headHe went galumphing back.
- “And hast thou slain the Jabberwock?Come to my arms, my beamish boy!O frabjous day! Callooh, Callay!”He chortled in his joy.
- 'Twas brillig, and the slithy tovesDid gyre and gimble in the wabe:All mimsy were the borogoves,And the mome raths outgrabe.

## Pædogogical Jabberwocky Ontology

- Ontology of parts of speech
- Nouns, Verbs, Adverbs, Adjectives, Interjections
- Instances were assigned to classes
- Properties were used to indicate connotations
- Positive
- Negative
- Semantic navigation capability was demonstrated using the portalCore framework from the SWAD-E project
- Observe that Jabberwocky is actually a dialect of English; another dialect of English is Scots
- A SPARQL query was developed to randomly combine Jabberwocky and Scots words into sentences with positive connotations and sentences with negative connotations

## Jabberwocky Ontology (cont’d)

## SPARQL Query

- Defined queries
- ---------------
-   0:  SELECT DISTINCT ?x ?y ?z WHERE { ?x ?y ?z } ORDER BY ?x
-   1:  SELECT ?x WHERE { ?x rdf:type word:Noun . ?x word:hasPositiveConnotation ?z }
-   ...
-   8:  SELECT ?x WHERE { ?x rdf:type word:PoliteWord } ORDER BY ?x
-   9:  SELECT ?x WHERE { ?x rdf:type word:ImpoliteWord } ORDER BY ?x
-   10:  <Positive MadLibs sentence appropriate for your boss>
-   11:  <Negative MadLibs sentence appropriate for an annoying co-worker>
- Enter query number (between 0 and 11), l (list) or q (quit)
- Choice: > 10
- I like working with you, boss, you're a pretty beamish guy!
- Choice: > 10
- I like working with you, boss, you're a pretty bonnie guy!
- Choice: > 11
- I can't believe I put up with a mimsy bampot like you!

## Marketing “Gotchas”

- Competitor technologies exist, so anticipate and address objections
- Data warehouses
- Database-driven taxonomies
- The Semantic Web is not the only way to implement an ontology
- Frame-based representation:  KL-ONE
- Logic-based representation
- Knowledge Representation System Specification (KRSS)
- CLASSIC/NEOCLASSIC and Loom/PowerLoom
- SUO-KIF (used in the Suggested Upper Merged Ontology)
- XML Schema:  National Information Exchange Model (NIEM)
- “Ontology” is in the eye of the beholder
- Synonym or vocabulary resolution
- Content conversion
- Taxonomy mapping

## Outline

- Technology Diffusion is a Process of Organizational Change
- The Critical First Year
- Timeline
- Semantic Technology Project Descriptions
- Reflections and Recommendations
- Organizational
- Marketing
- Ontology Development
- Tools and Support
- Resources

## Ontology Development Recommendations

- Ontology development is not the same as software development
- Knowledge engineering is not software engineering
- Special skills and training are needed
- Take the time to learn the formal Description Logic underpinnings of OWL; there are good _[courses and tutorials ](http://dl.kr.org/courses.html)_on the Web.
- Reuse instead of reinventing
*e.g.,* _[FOAF](http://www.foaf-project.org/)_, _[BibTeX](http://en.wikipedia.org/wiki/BibTeX)_, _[Dublin Core](http://dublincore.org/)_, PRISM
- Consider using appropriate upper ontologies
*e.g.,* _[Cyc](http://en.wikipedia.org/wiki/Cyc)_, _[SUMO](http://ontology.teknowledge.com/)_, _[WordNet](http://wordnet.princeton.edu/)_
- Be prepared to code or modify some ontologies by hand, particularly when you generate them with XSLT
- Beware the open world and unique name assumptions!
- Quantified restrictions are tricky
- For example, hasNegativeConnotation has “yes” and hasPositiveConnotation exactly 0 did not classify Impolite Words in the Jabberwocky ontology

## How to Learn Ontology Development

- Formal degree in Knowledge Representation or Knowledge Engineering
- Short courses, tutorials, and seminars on ontology development (which may be vendor- or tool-specific)
- Self-teaching resources
- “How to Build an Ontology” video from University of Buffalo
- Tutorials and papers from Manchester and Maryland
- “Practical Guide” and “Common Errors and Patterns”
- “Debugging Owl Ontologies” Web page and paper(s)
- “Learn from the Masters” by studying existing ontologies
- Presentation materials from ISWC 2006 tutorial
- Videos of the ISWC 2006 tutorial
*Ontological Engineering* book by Gómez-Pérez *et al.*
- Tip:  Develop your ontology with (and for) a reasoner, such that the structure of your ontology is not statically determined but instead is inferred by the reasoner

## Outline

- Technology Diffusion is a Process of Organizational Change
- The Critical First Year
- Timeline
- Semantic Technology Project Descriptions
- Reflections and Recommendations
- Organizational
- Marketing
- Ontology Development
- Tools and Support
- Resources

## Tools and Support Recommendations

- Start with free or open source tools
- _[Protégé](http://protege.stanford.edu/)__ has newsgroups with RSS feeds_
- SWOOP has some nice features but is no longer supported
- _[Jena](http://jena.sourceforge.net/)__ has an extremely responsive Yahoo support group with an RSS feed_
- _[Sesame](http://www.openrdf.org/)__ has support forums and mailing lists_
- _[Pellet](http://pellet.owldl.com/)__ has a mailing list_
- _[Saxon](http://saxon.sourceforge.net/)__ parser for XSLT 2.0 has a mailing list and forum_
- It’s still a small world after all
- Seek out contacts with movers and shakers
- “Strip-mine” conferences and workshops
- _[International Semantic Web Conference (ISWC)](http://iswc2007.semanticweb.org/)_
- _[Semantic Technologies Conference](http://www.semantic-conference.com/)_
- “Cold call” email requests for information are generally received favorably, especially if you have information to offer in return

## Outline

- Technology Diffusion is a Process of Organizational Change
- The Critical First Year
- Timeline
- Semantic Technology Project Descriptions
- Reflections and Recommendations
- Organizational
- Marketing
- Ontology Development
- Tools and Support
- Resources

## Resources

- The May 2001 Scientific American article that started it all:  “_[The Semantic Web](http://www.sciam.com/print_version.cfm?articleID=00048144-10D2-1C70-84A9809EC588EF21)_,” by Tim Berners-Lee, James Hendler, and Ora Lassila
- The 2006 update to the above article, in IEEE Intelligent Systems:  “_[The Semantic Web Revisited](http://eprints.ecs.soton.ac.uk/12614/01/Semantic_Web_Revisted.pdf)_,” by Nigel Shadbolt, Wendy Hall, and Tim Berners-Lee
- _[A Semantic Web Primer](http://www.ics.forth.gr/isl/swprimer/)__[ ](http://www.ics.forth.gr/isl/swprimer/)_by Grigoris Antoniou and Frank van Harmelen
- “_[A Practical Guide to Building OWL ](http://www.co-ode.org/resources/tutorials/ProtegeOWLTutorial.pdf)__[Ontologies](http://www.co-ode.org/resources/tutorials/ProtegeOWLTutorial.pdf)_” (a.k.a. “Manchester Pizza Tutorial”) for OWL and ontology development using (an older version of) Protégé
- _[Swoogle](http://swoogle.umbc.edu/)_ to search for existing ontologies
- Eventually, you need to study the W3C OWL Specifications in some detail (also RDFS and RDF)

## Acknowledgements

- The National Infrastructure Simulation and Analysis Center (NISAC) is a program under the Department of Homeland Security’s (DHS) Preparedness Directorate.  Sandia National Laboratories (SNL) and Los Alamos National Laboratory (LANL) are the prime contractors for NISAC under the programmatic direction of DHS’s Infrastructure Protection/Risk Management Division.
- Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin Company for the United States Department of Energy’s National Nuclear Security Administration under contract DE-AC04-94AL85000.

## Question and Answer