The commonly cited definition of ontology in information science comes from Thomas Gruber’s 1993 paper, which describes an ontology as “an explicit specification of a conceptualization” \u2014 a deliberate enumeration of the concepts in a domain and the constraints on how they relate, made explicit enough for software to process rather than left implicit in a person’s understanding. The definition was later refined by other researchers to emphasize that a genuine ontology is also formal (machine-processable) and shared (agreed upon across a community), not just one team’s private schema.<\/p>\n
Technically, ontologies in DAM and broader digital systems are usually implemented using W3C’s Web Ontology Language (OWL), a W3C Recommendation since February 2004, built on top of the Resource Description Framework (RDF) that also underlies XMP’s data model. OWL lets a system define classes, individual entities, and typed properties between them \u2014 and, critically, lets a reasoning engine derive new facts from those relationships rather than just retrieving what was explicitly stored.<\/p>\n
Full ontology-driven metadata is still uncommon in mainstream DAM deployments \u2014 it requires modeling work well beyond setting up a category tree, and most organizations get adequate search performance from a well-maintained taxonomy and controlled vocabulary alone. Where it does show up is in large media libraries and knowledge-graph-backed AI search features, where entity relationships (people, places, products, events) need to be queried, not just their labels.<\/p>","protected":false},"excerpt":{"rendered":"
A formal model of a domain’s concepts and the specific relationships between them (not just hierarchy, but ties like “depicts” or “part of”) that lets software infer connections a flat taxonomy can’t.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"How is an ontology different from a taxonomy?","answer":"A taxonomy is hierarchy only \u2014 broader and narrower categories. An ontology is a formal model of a domain's concepts plus specific typed relationships between them, like 'depicts' or 'part of,' letting software infer connections a flat taxonomy can't."},{"question":"What can an ontology let a DAM's search do that a taxonomy can't?","answer":"It lets search or recommendation reason across relationships \u2014 for example, encoding that a person is 'CEO of' a company, so a search for 'leadership team' can surface a headshot tagged only with an individual's name, without anyone manually re-tagging it 'leadership.'"},{"question":"Is every DAM feature marketed as ontology-powered actually an ontology?","answer":"Often not. Vendors and teams label any tag hierarchy an 'ontology,' but without genuine typed relationships between entities, not just broader\/narrower nesting, no system can actually perform the inference the term implies."},{"question":"What does an ontology add on top of a metadata schema?","answer":"A schema defines what fields exist; an ontology defines how the concepts those fields represent relate to each other, enabling inference rather than just structured storage and lookup."},{"question":"What's a practical example of ontology-driven inference in a DAM?","answer":"Surfacing a headshot tagged only with a person's name in a 'leadership team' search, because the ontology encodes that the person holds a 'CEO of' relationship to the company \u2014 a connection a flat taxonomy has no way to represent."},{"question":"How can a team tell if their DAM's ontology is genuine?","answer":"By checking whether it defines actual typed relationships between distinct entities, not just category nesting labeled with ontology language. If it only supports broader\/narrower browsing, it's a taxonomy regardless of what it's called."}],"checked_date":"2026-08-07","sources":[{"statement":"Gruber's widely cited 1993 definition describes an ontology as \"an explicit specification of a conceptualization\"","source_name":"T. Gruber, cited via academic literature review","url":"https:\/\/www.ncbi.nlm.nih.gov\/books\/NBK584339\/","checked":"2026-08-07"},{"statement":"The Web Ontology Language (OWL) became a W3C Recommendation on 10 February 2004","source_name":"W3C, OWL Web Ontology Language Reference","url":"https:\/\/www.w3.org\/TR\/owl-ref\/","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"related":[2422,2543,2503,2468,2528,2541],"definition":"A formal model of a domain's concepts and the specific relationships between them (not just hierarchy, but ties like \"depicts\" or \"part of\") that lets software infer connections a flat taxonomy can't.","why":"An ontology is what lets a DAM's search or recommendation engine reason across relationships instead of just matching a category path \u2014 for example, encoding that a person is \"CEO of\" a company, so a search for \"leadership team\" can surface a headshot tagged only with an individual's name, without a human ever manually re-tagging it \"leadership.\" This is the layer behind genuinely semantic or AI-assisted DAM search, as distinct from search that's just matching against a taxonomy or keyword list.","example_rows":[{"field":"Entity","values":"Jane Alvarez"},{"field":"Relationship: role_at","values":"Alvarez Photography"},{"field":"Relationship: depicted_in","values":"IMG_4471.CR2, IMG_4502.CR2"},{"field":"Inferred","values":"\"Alvarez Photography team\" query can surface IMG_4471 and IMG_4502"}],"mistake":"Vendors and teams label any tag hierarchy an \"ontology,\" but without genuine typed relationships between entities \u2014 not just broader\/narrower category nesting \u2014 no system can actually perform the inference the term implies; what's marketed as \"ontology-powered search\" is often just a taxonomy with better branding.","deep_link":""},"silo":[24],"class_list":["post-2447","glossary","type-glossary","status-publish","hentry","silo-glossary"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2447","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/glossary"}],"version-history":[{"count":3,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2447\/revisions"}],"predecessor-version":[{"id":3627,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2447\/revisions\/3627"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2447"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}