DCMO-DM2 Ontology Design/Approach Summary 19-March-2012 DCMO BEA/DM2 Ontology Working Group Department of Defense

Eliminated IDEAs foundation concepts DM2 Ontology Approach Eliminated IDEAs foundation concepts Specifically, leverage similar concepts from the OWL language for creating Classes, Properties, and Individuals Started with Classes from the DM2 Conceptual Data Model (CDM) to create the initial top-level taxonomy. Built out more detailed relationships and additional classes from the logical model documentation available on DoDAF website http://dodcio.defense.gov/sites/dodaf20/DM2_HTML/index.htm

IDEAS Foundation

DM2 Ontology Approaches OR DM2 IDEAS Foundation DM2 OWL/RDFS/RDF IDEAS Foundation Reified model IDEAS Foundation OWL/RDFS/RDF DM2 DoDAF 2.0 1st Attempt OR OWL/RDFS/RDF Pure OWL model?

IDEAs Foundation -> OWL RDF/RDFS/OWL ideas:Thing ideas:superSubType ideas:ypeInstance ideas:couple ideas:propertyOf ideas:measureOf* ideas:powerTypeInstance dm2:DM2Names owl:Thing owl:subClassOf rdf:type owl:ObjectProperty owl:DatatypeProperty owl:ObjectProperty* No Mapping rdfs:label** * Further discussion is required to determine the best approach to describing measures in OWL ** Will apply use of language tags on strings to allow for multiple languages

Object Property Hierarchy Approach Domain/Range assumptions***: part1Type = rdfs:range part2Type = rdfs:domain Object Property hierarchy was maintained based on the DM2 documentation as closely as possible, although the DM2 logical model lacks specificity in many cases (e.g. why create a sub-property if there is no additional specificity) No inverse properties defined at this time, but those could be fleshed out as the ontology matures. Specified rdfs:domain and rdfs:range (latest version) constraints on properties for now since relation names are very specific, but realize that this could change if we adopt more re-usable property names later on. *** Action item to evaluate domain/range assignments to see which ones make sense and which ones may/should be reversed.

Class Hierarchy Approach Was decided to make no distinction between ideas:Individual and ideas:Type. All sub-types are simply an owl:Class Started with high-level concepts from DM2 conceptual model to create top-level taxonomy. Extended taxonomy based on concepts defined in logical model Usage of “Type” suffix dropped. Again we were only focused on fleshing out lower taxonomy layers to extend the high-level concepts defined by the conceptual model

IDEAS/DM2 concepts The IDEAS based DM2 ontology includes IC-ISM and Location concepts in one OWL file These should be broken out into separate ontologies (which was done in the PES/XSD implementation) and referenced as imports to the DM2 ontology Currently, the DCMO version excludes the IC-ISM concepts, but retains the Location concepts pending further review/discussion with the BEA Ontology Working Group

http://dcmo.defense.gov Department of Defense