Posted:September 24, 2008

Fitting the Pieces

Coherence is Needed for Continued Sustainability

Since early in 2008 my colleague, Fred Giasson, has been authoring a series of important blog posts on ‘exploding the domain.’ Exploding the domain means to make class-to-class mappings between a reference ontology and external ontologies, which allows properties, domains and ranges of applicability to be inherited under appropriate circumstances. Exploding the domain expands inferencing power to this newly mapped information.

Fred first used the phrase in an April post that introduced the concept:

“. . . once the linkages between UMBEL subject concepts and external ontologies classes are made, the following becomes possible: 1) the UMBEL subject concept structure can be used to describe (instantiate) things using the UMBEL data structure; 2) external ontology properties can be re-used to describe these new instances since external ontologies classes are linked to UMBEL subject concept classes; and 3) in some cases, the properties defined in these ontologies can be used in relation with UMBEL subject concept classes.”

Since that time, Fred has continued to explore these implications. In an August posting looking at UMBEL as a possible reference framework for mapping and exploding domains, Fred stated,

“. . . once we have the context in place, we are on our way to achieve coherence. UMBEL is 100% based on OpenCyc and Cyc, which are internally consistent and coherent within themselves. We thus use these coherent frameworks to make the mappings to external ontologies coherent, too.

The equation is simple:

a coherent framework + ontologies contextualized by this framework = more coherent ontologies.”

The thrust of this analysis was to show how UMBEL subject concepts can act to create context (his emphasis) for linked classes defined in external ontologies. Where the individuals in a dataset are instances of classes, and some of these classes are linked to UMBEL (or a similar contextual structure), these subject concept classes also give context to those individuals.

Finally, and most recently, Fred demonstrated how the use of UMBEL could explode DBpedia’s domain by linking classes using only three properties: rdfs:subClassOf, owl:equivalentClass and umbel:isAligned. (And, as I noted in an earlier posting this week, those mappings have now been made bi-directional from DBpedia to UMBEL as well.)

As we discuss and apply these concepts we are starting to see some further guidelines emerge. Presenting these is the purpose of this post in this ongoing exploding the domain series.

The Mere Existence of Classes is Not Enough

Since its inception, DBpedia has had a class structure of sorts, first from the native Wikipedia categories from which it was derived and then with the incorporation of the YAGO structure (based on WordNet concept relationships). Yet we have claimed that class structure has truly only recently been brought to DBpedia with the mappings to UMBEL. Why? Does not DBpedia’s initial class structure meet the test?

(BTW, these same questions may be applied to some of the other large data structures beginning to emerge on the semantic Web such as Freebase. But, those are stories for another day.)

There are really two answers to these questions. First, the mere existence of classes is not enough; they must actually be used. And, second, the nature of those classes and their structure and coherence are absolutely fundamental. This subsection addresses the first point; the following the second; with both aided by the table below.

There has been a class structure within DBpedia from inception, which was then supplemented a few months after release with the YAGO structure. The starting Wikipedia structure showed early issues which began to be addressed through a cleaned Wikipedia category class (CWCC) hierarchy. These relationships were established with the rdf:type predicate that relates an instance to a class. The classes themselves were related to one another through the rdfs:subClassOf predicate. These class relationships allowed the linked classes to be shown in a hierarchical (taxonomy-like) structure.

Initially, in the case of the beginning Wikipedia categories, the internal class relationships were weak. This was somewhat improved with the addition of YAGO and its WordNet-based concept relationships (with better semantics).

However, these class relationships were (to my knowledge) never mapped to any external structures or ontologies. If used at all, they were only implied for ad hoc navigation within the internal instance data.

Really, anyone could have approached DBpedia at this point and began an effort of mapping its existing class structures to external data. Indeed, we (as editors of UMBEL) considered doing so, but chose a different structure (see next section) for reasons of context and coherence.

The net result is that DBpedia and the other instances of the linking open data (LOD) cloud have remained focused and useful at the instance level, and not yet at the class level.

As we brought in UMBEL to provide a class structure to DBpedia and linked data, this circumstance began to change, as this table indicates:

  Yago UMBEL
Predicate
Differences
– subClassOf subClassOf
equivalentClass
superClassOf
isAligned
– and, entity-to-class predicates
Mapping/Application
Differences
– No external mappings made – Aggressive use of external mappings (‘exploding the domain‘)
– Consistent internal structure
Structural
Differences
– Based on WordNet concept relationships – Based on Cyc common sense structural relationships
– Inferencing and reasoning Cyc tools for testing coherence
– Microtheories framework for domain differences
– Extendable structure
Unique Class Count ~ 55,000 ~ 20,000

Though shown for comparison reasons, the number of classes probably has no real importance.

The key argument in this subsection is that classes matter. Indeed, one of the current challenges before the linked data community is to understand and treat differently the issues of instances from classes. But, the question of whether one class structure is better than another is moot if class mappings are neglected altogether.

Sustainability Requires Coherence

UMBEL’s reasons for not taking up the Wikipedia structure or the WordNet structure — that is, the initial structures within DBpedia — for its lightweight subject ontology was based on lack of coherence. I have spoken earlier about When is Content Coherent? regarding these arguments. Other analysis supports the conclusions in various ways [1].

A central (or “upper”) reference framework should be one that is solid and venerable. Over time, many subsidiary ontologies and structures will relate to it. Like a steel superstructure to a skyscraper or a structural framework to a large ocean-going tanker, this beginning structure needs to withstand many stresses and maintain its integrity as various subsidiary structures hang from it.

So long as we are still in “toy” mode with relatively few external mappings and relative few ontologies, simple class-to-class mappings without respect to the coherence of the underlying ontologies may be OK. But, we will soon (if not already) see that structural flaws, like slight perturbations at the Big Bang, may propagate to create huge discontinuities.

At the pace of development we are now seeing, there will be tens to hundreds of thousands of ontologies within the foreseeable future. Granted, for any given circumstance, only a minor few of those may be applicable. But the potential combinations still can defy imagination in terms of complexity and potential scope at widely varying scales.

At the scale of the Web, of course, there will never be a central authority (nor should there be) for “official” vocabularies or structures. Yet, just as certainly, those ontologies and structures that do share some conceptual and structural coherence and are therefore more likely to easily integrate and interoperate will (I believe) win the Darwinian race. Without some degree of coherence, these disparate structures become like ill-fitting jigsaw pieces from different puzzles.

As we watch structures and relationships accrete like layers in a pearl, we should begin with a solid grain of common sense and coherence. That is why we chose the Cyc structure as the basis of UMBEL — it provides one such solid, coherent framework for moving forward.

I am not sanguine that ad hoc, free-form ontological structures, created in the same manner as topic-specific articles in Wikipedia or as informal tags in bookmarking systems, will bring such coherence. But who knows? Perhaps on the Web where novelty and the joy of creation and exploration can trump usefulness, such could transpire.

But, when we look to linked data and semantic Web constructs finally achieving its potential in the enterprise to overcome decades of data silos, I suspect purposeful coherence will win the day.

Sustainable ontologies, which themselves can host and interoperate with still further ontologies and structures, will require coherent underpinnings to not collapse from the weight of keeping consistency. Just as our current highways and interstates follow the earlier roads before them, as early trailblazers we have a responsibility to follow the natural contours of our applicable information spaces. And that requires coherence and consistency; in other words, logic and design.

Vocabularies are Not Free Form

In the past few months there has been a remarkable emergence of interest in vocabularies and semantics (as traditionally understood by linguists). Today, for example, marks the kick-off of the first VoCamp get-together in Oxford, England, with interest and discussion active about potentially many others to follow. Peter Mika, Matthias Samwald and Tom Heath have each outlined their desires for this meeting.

I hope the participants in this meeting and others to follow look seriously at the issues of coherence and interoperability and sustainability. My caution is as follows: like tagging and Wikipedia, we have seen amazing contributions from user-generated content that have totally re-shaped our information world. However, we have not yet seen such processes work for structure and coherent conceptual relationships.

I believe participation and UGC have real roles to play in the emergence of coherent structures and vocabularies to enable interoperability. But I also believe they have not done so to date, and useful approaches to those will not emerge in a free-form fashion and without consideration for sustainability and coherence testing.

Putting this Context into Context

In these observations there is absolutely no criticism intended or implied with DBpedia or prior linked data practice. A natural and understandable progression has been followed here: first make connections between things, then begin to surface knowledge through the exploration of relationships. We are just now beginning that exploration through the use of classes, vocabularies and ontologies to explicate relationships. The fact that linked data and DBpedia first emphasized linking things and publishing things is a major milestone. It is now time to move on to the new challenges of structure and relationships.

There is much to be learned from other pathbreaking efforts such as the Open Biomedical Ontologies efforts and their attempts at coordination and standardization. As the demands and interests in interoperability increase, interfaces, consistency and coordination will continue, I believe, to come to the fore.

In another 18 months we will likely look back at today’s issues and thoughts as also naïve in light of new understandings. The pace of discovery and learning is such that I believe best practices will remain fluid for quite some time.


[1] An exact analysis related to our arguments of coherence has not been made, but related studies point to these observations in part or in slightly different contexts.

Wordnets tend to be star-like in structure, with sparse relations, and dominated by a few hub clusters. c.f., Holger Wunsch, 2008. Exploiting Graph Structure for Accelerating the Calculation of Shortest Paths in Wordnets, in Proceedings of Coling 2008, Manchester, UK, August 2008. See http://www.sfs.uni-tuebingen.de/~wunsch/wn-shortest-paths.pdf.

The strict uncorrected structure of Wikipedia categories can also be inconsistent, inaccurate, populated with administrative categories, demonstrate cycles, and lack uniform coverage. c.f., Jonathan Yu, James A. Thom and Audrey Tam, 2007. Ontology Evaluation Using Wikipedia Categories for Browsing, in Proceedings of 16th Conference on Information and Knowledge Management (CIKM), 2007; see http://goanna.cs.rmit.edu.au/~jyu/publications/YuEtal07.pdf. This paper also presents a comprehensive framework for ontology evaluation.

This reference describes a new way to calculate semantic relatedness (not the same as coherence) in relation to Wikipedia, ConceptNet and WordNet: Sander Wubben, 2008. Using Free Link Structure to Calculate Semantic Relatedness. ILK Research Group Technical Report Series no. 08-01, July 2008, 61 pp. See http://ilk.uvt.nl/downloads/pub/papers/wubben2008-techrep.pdf.

Table 3 in this citation presents an interesting contrast between what the authors call collaborative knowledge bases (CKBs, like Wikipedia) and linguistic knowledge basis (LKBs, like WordNet), again however not really addressing the coherence issue: Torsten Zesch and Christof Müller and Iryna Gurevych, 2008. Extracting Lexical Semantic Knowledge from Wikipedia and Wiktionary, in Proceedings of the Sixth International Language Resources and Evaluation (LREC’08), May 28-30, Marrakech, Morocco. See http://elara.tk.informatik.tu-darmstadt.de/publications/2008/lrec08_camera_ready.pdf. Also see Torsten Zesch and Iryna Gurevych, 2007. Analysis of the Wikipedia Category Graph for NLP Applications, in Proceedings of the Workshop TextGraphs-2: Graph-Based Algorithms for Natural Language Processing at HLT-NAACL 2007, 26 April, 2007, Rochester, NY, pp. 1-8. See http://www.aclweb.org/anthology-new/W/W07/W07-02.pdf.

Posted by AI3's author, Mike Bergman Posted on September 24, 2008 at 6:03 pm in Ontologies, Semantic Web, Structured Web, UMBEL | Comments (2)
The URI link reference to this post is: http://www.mkbergman.com/454/exploding-the-domain-in-context/
The URI to trackback this post is: http://www.mkbergman.com/454/exploding-the-domain-in-context/trackback/