© Copyright 2011 TopQuadrant Inc. Slide 1 Linked Models TopQuadrants Linked Models Ontologies: VAEM, VOAG, DTYPE, QUDT, oeGOV Irene Polikoff, Ralph Hodgson

© Copyright 2011 TopQuadrant Inc. Slide 1

Linked Models

TopQuadrant’s Linked Models Ontologies:

VAEM, VOAG, DTYPE, QUDT, oeGOV

Irene Polikoff, Ralph HodgsonTopQuadrant

June 29-30, 2011


As it grows, LOD needs models for interpreting and transforming data

2007 2011

ref1: http://www.readwriteweb.com/cloud/2011/01/the-concept-of-linked-data.phpref2: http://richard.cyganiak.de/2007/10/lod/

LinkedModels.org

2011


Brief history of TQ’s ontology building projects in government

2002 2004 2006 2008 2010

BEA

FEA-RMOOSERA

NASA NExIOM

DoDAF

CCTS

oeGOV

NATO

FAA

Business Reference Model (BRM)• Lines of Business• Agencies, Customers, Partners

Service Component Reference Model (SRM)• Service Layers, Service Types• Components, Access and Delivery Channels

Technical Reference Model (TRM)• Service Component Interfaces, Interoperability• Technologies, Recommendations

Data Reference Model (DRM)• Business-focused data standardization • Cross-Agency Information exchanges

Performance Reference Model (PRM)

• Government-wide Performance Measures & Outcomes• Line of Business-Specific Performance Measures & Outcomes

Bu

siness-D

riven

Ap

pro

ach

(Citize

n-C

ente

red Fo

cus)

Com

pon

en

t-Base

d A

rchite

cture

s

Capability Cases

Identifies WarfighterRelationships and Information Needs

OperationalView

Prescribes Standards and Conventions

TechnicalView

Relates Capabilities andCharacteristics to Operational Requirements

SystemsView

Technical Criteria GoverningInteroperable Implementation/Procurement of the SelectedSystem Capabilities

Specific Capabilities Identifiedto Satisfy Information-Exchange Levels and OtherOperational Requirements

class Class Model

Capabilities Serv ices

Projects

PerformersObject Exchanges

RulesMeasures

Foundation

according-to according-toto-meet

meet

satisfy follow

lead-to lead-to

meet comply-with

result-inresult-in

conduct

class Capability

Type

Capability

TemporalType

Effect

TemporalType

CapabilityConfiguration

Type

Measure

TemporalType

Condition

Performer

Organization

ExchangeObject

Materiel

TemporalType

Skill

ExchangeObjectPerformer

PersonnelType

InterfaceTypeTemporalType

Activ ity

TemporalType

RealProperty

Performer

System

realizes

1..*

is-part-of

0..*

is-a-part-of

0..*

is-a-part-of

is-a-part-of

0..*

is-a-part-of

0..*

is-a-part-of

0..*

results-in

0..*

0..*

is-a-part-of

0..*

applies-to

0..*

1..*

is-performed-under

class Serv ices

TemporalType

Effect

Type

M easure

TemporalType

Condition

Organization

ExchangeObject

M ateriel

TemporalType

Skill

ExchangeObject

PersonnelType

In terfaceType

TemporalType

Activ ity

TemporalType

RealProperty

System

Serv iceRequirement

Serv iceImplementation

Rule

Standard

PerformerState

Performer

Softw areServ ice

is-a-part-

o f

0..*

resul ts-in

0..*

0..*

appl ies-

to 0..*

0..*

perform s1..*is-perform ed-by

class ExhangeObjectFlow

PerformerState

Performer

TemporalType

ExchangeObject

Data

Materiel

Information


Activ ity

Rule

Standard

according-

to

PersonnelType

1..*

is-performed-by

0..*

performs

0..*

is-produced-by

0..*

0..*

is-consumed-by0..*

is-a-part-of

class Project

Event

Type

Vision

TemporalType

Project

TemporalType

Goal

Cost

Plan

Rule

Means


Activ ity

TemporalType

Condition

TemporalType

PerformerState

TemporalType

EffectType

Measure

1..*

initiates-stimulates

0..*

is-realized-by

0..*

directs

0..*

1..*

is-realized-by

initiatesis-necessary-for

0..*

seeksChangeTo

1..*

0..*

changes1..*

0..*

results-in

0..*

0..*

applies-to

0..*

class Rule

Type

Rule

Standard

Agreement

FunctionalStandard TechnicalStandard

Guidance

Constraint

TemporalType

Condition

Means

UCORE IC-ISM-v 2::SecurityAttributesGroup

0..*

is-valid-under

1..*

class Measure - WIP

Cost

Type

Baseline::Measure

Timeliness

RateThroughput

Capacity

AccuracyPrecision

Dependability

NeedsSatisfactionMeasure

PerformanceMeasure

MaintainabilityMeasure

AdaptabilityMeasure

OrganizationalMeasure

Interoperability

Trustworthiness

Reliability

Security

class Performer

Performer

ExchangeObject

PersonnelType

System

SoftwareServ ice

Organization

TemporalType

Skill

ExchangeObject

Materiel


Activ ity

Rule

StandardTemporalType

Network

TemporalType

PerformerState

according-

to

AbstractFeatureType

GeoFeature

Location

1..*

is-performed-by

is-a-part-of

0..*

performs

is at

2..*

is-part-of

References: (1) SKOS-based FEA-RMO Ontologies are at http://www.oegov.us/blog/?page_id=102 (2) oeGOV ontologies are at http://www.oegov.us


The Linked Open Data World

IntrinsicS

tro

ng

RD

F/O

WL

+ C

on

tro

lled

V

oca

bu

lari

es

Tool-BasedNoneW

eak

No

n R

DF

/OW

LM

ediu

mR

DF

QUDT

PDF

“Link-ability”

Info

rmat

ion

Arc

hit

ectu

re

oeGOV

CSV (955)

XLS(344)

UK data.gov

US data.gov

KML(21)

ESRI(166)

XML(263)

F(#) Based on

data.gov June 2009

RDF(*)

dbPedia

Life Sciences


NASA Constellation Program Information Architecture

Information architecture (IA) defines a model, processes and services for how information is represented, governed and used in systems, applications, databases, documents and activities in order to ensure compliance to naming and identifier rules, standard data and information types, controlled vocabularies and coding schemes.

NASA Information ArchitectureNASA Information Architecture

GovernanceGovernance

ProvenanceProvenance

Names and Identifiers

Data Types

Information Types

Algorithms & Equations

Enco

ding

Rul

es

Nam

ing

& D

esig

n Ru

les

Met

adat

a

XML

OWLModels


Key to Success is an Ontology Architecture – Five Dimensions turned out to be important

• Ontologies partitioned by domains, disciplines, organizations, specificity and time;

• Named graphs aggregated using configuration ontologies according to need;

• Two other dimensions also important: aspect and viewpoint.

Domain

Discipline

Organization

Specificity

Time


VAEM:Vocabulary for Attaching Essential Metadata

VAEM stands for "Vocabulary for Attaching Essential Metadata". VAEM attaches basic metadata properties and dimension

properties, such as domain, discipline, aspect and viewpoint, to the 'owl:Ontology' class to fully qualify the ontology.

What VAEM regards as 'essential metadata' is data about dates and times, confidentiality, and other characterisitic qualifiers of the ontology. Also references to where a ontology is documented (catalog) and where to

find ontology Governance, Attribution and Provenance. For the latter, some properties from the VOAG ontology are used, notably,

'voag:hasGovernance', 'voag:withAttributionTo', and 'voag:hasLicenceType'.

© Copyright 2011 TopQuadrant Inc. Slide ‹#›

VAEM QUAD Chart

Work Accomplished Established dimensions for domain,

discipline, aspect and viewpoint Published version 1.2 catalog entry

• www.linkedmodel.org/doc/vaem/1.2

Motivations characterize a graph’s role, scope,

and intent with respect to a framework of dimensions

Provide catalog linkage (using VOAG) for governance and provenance

Next Objectives Provide better descriptions of

dimensions and give examples Align with VANN Reuse more of Dublin Core

Issues Alignment with VANN More use of Dublin Core?

• Concerns that importing DC causes "ontology glut", through the import of many DC Terms.

© Copyright 2011TopQuadrant Inc. Slide 9

VAEM

http://www.linkedmodel.org/doc/vaem/1.2


VOAG:Vocabulary for Attribution and Governance

VOAG stands for "Vocabulary Of Attribution and Governance". The ontology is intended to specify licensing, attribution,

provenance and governance of an ontology. Unlike VAEM is intended to be used “outside” of an ontology that is being

described VOAG captures many common license types and their

restrictions. Where a license requires attribution, VOAG provides resources that allow

the attribution to be made. Provenance is defined in terms of source and pedigree. A minimal model of governance is provided based on how issues,

releases and changes are managed. VOAG makes uses of some concepts from VOID

(http://vocab.deri.ie/void), notably void:Dataset.


VOAG QUAD Chart

Work Accomplished Attribution class and properties Catalog entry support Basic model of governance and

provenance Over 100 license types Published version 1.0 catalog entry

• www.linkedmodel.org/doc/voag/1.0

Motivations The need to specify licensing,

attribution, governance, provenance and pedigree of a model or dataset

Next Objectives Factor out Provenance Model

Issues Alignment with W3C Provenance

Group (TopQuadrant is a member) Provenance Model should be

separate to VOAG for use in contexts where other aspects of VOAG are not needed


VOAG

http://www.linkedmodel.org/doc/voag/1.0


DTYPE:Data Type Ontology (Level 1)

The ontology 'dtype' provides a specification of simple data types such as enumerations and codelists.

Examples of use:Conversion of XML Schemas and UML Models to OWLModeling of NIEM code-lists


DTYPE QUAD Chart

Work Accomplished Basic treatment of codelists and

enumerations Published version 1.0 catalog entry

• www.linkedmodel.org/doc/dtype/1.0

Motivations Need to represent codelists and

enumerations, where members can have codes, order and literals

Also supports derived enumerations and codelists such as sublists of countries and currencies

Anticipated need for other data types such as arrays

Next Objectives Provide examples from NIEM

Issues None


DTYPE

http://www.linkedmodel.org/doc/dtype/1.0


QUDT:Quantities, Units, Dimensions and Types

http://qudt.org


QUDT QUAD Chart

Work Accomplished Dimensional Units for all SI and non-

SI units and quantites Published version 1.1 catalog

• www.linkedmodel.org/catalog/qudt/1.1

Motivations provide a unified model of, measurable

quantities, units for measuring different kinds of quantities, the numerical values of quantities in different units of measure and the data structures and data types used to store and manipulate these objects in software

Next Objectives More coverage of non-engineering

domains

Issues Unit codes


QUDT

http://www.linkedmodel.org/catalog/qudt/1.1


oeGOV:Ontologies of US Government

An Ontology of the US Government containing over 600 government bodies.


oeGOV:DHS Example

usgov:DHS

a gov:CivilAgency , gov:ExecutiveAgency ;

rdfs:label "Department of Homeland Security (DHS)"^^xsd:string ;

dc:description "Homeland Security leverages resources within federal, state, and local governments, coordinating the transition of multiple agencies and programs into a single, integrated agency focused on protecting the American people and their homeland. More than 87,000 different governmental jurisdictions at the federal, state, and local level have homeland security responsibilities. The comprehensive national strategy seeks to develop a complementary system connecting all levels of government without duplicating effort. Homeland Security is truly a 'national mission'."^^xsd:string ;

gc:url "http://www.dhs.gov"^^xsd:anyURI ;

gov:adminstration usgov:TSA ; gov:agency usgov:CG , usgov:SS , usgov:FEMA ;

gov:center usgov:FLETC ;

gov:committee usgov:HSSTAC , usgov:DHS-TFNA ;

gov:council usgov:DHS-HSAC , usgov:DHS-NIAC , usgov:CIPAC , usgov:DHS-ICCEPID ;

gov:department usgov:DHS-ICE , usgov:DHS-CBP ;

gov:directorate usgov:DHS-DNPP , usgov:DHS-DST , usgov:DHS-DM ;

gov:mission "The Department of Homeland Security’s overriding and urgent mission is to lead the unified national effort to secure the country and preserve our freedoms. While the Department was created to secure our country against those who seek to disrupt the American way of life, our charter also includes preparation for and response to all hazards and disasters. The citizens of the United States must have the utmost confidence that the Department can execute both of these missions."^^xsd:string ;

gov:office usgov:DHS-PO , usgov:DHS-ESEC , usgov:DHS-OGC , usgov:DHS-OP , usgov:DHS-OIG , usgov:DHS-OHA , usgov:DHS-OLA , usgov:DHS-OIA , usgov:DHS-OCRCL , usgov:DHS-CISO , usgov:DHS-OPA , usgov:DHS-OS , usgov:DHS-MAO , usgov:DHS-CNE , usgov:DHS-OOC ; gov:reportsTo usgov:EOP ;

gov:service usgov:CIS ; gov:suborganization usgov:DHS-CBP .


oeGOV:Ontologies of US Government

DHS

NARA

HUD

Government “Core”

Government Ontology

Dublin“Core”

Specialization and extension of the Government Ontology to represent the US GovernmentUSDA

An Aggregation Graph that composes each Agency Graph


oeGOV QUAD Chart

Work Accomplished US Government Ontology with over

600 Government bodies Partitioning by Agency Published at http://oegov.us

Motivations Provide controlled vocabularies for

referring to government bodies Build an ontology model of the US

Government for Linked Government Data Provenance

Next Objectives Build catalogs like the VAEM, VOAG

and QUDT catalogs Build a community – can’t do this on

our own

Issues Completeness and Correctness

Checks Provenance is needed


oeGOV

http://oegov.us


Thank You

Irene PolikoffE-mail: [email protected] Twitter: @topquadrant, @oegovnews

Documents

© Copyright 2011 TopQuadrant Inc. Slide 1 Linked Models TopQuadrants Linked Models Ontologies: VAEM, VOAG, DTYPE, QUDT, oeGOV Irene Polikoff, Ralph Hodgson