Re: data schema / vocabulary / ontology / repositories

On 3/13/11 6:44 PM, Dieter Fensel wrote:
> Dear Kingsley,
> the context of my question is the following. The are of Ontologies had 
> encountered
> a severe paradigm shift though LOD. In the old days you had plenty of 
> design
> methodologies to develop Ontologies based on first principles from 
> scratch
> (despite the fact that there was some verbal hand waving on reuse). Then
> Ontologies became populated by data. In the end it was always not really
> easy to explain what their difference was compared to a traditional data
> schema approach. Often it felt like in the tale of the The Emperor's 
> New Clothes


The problem (as I've experienced it) is that people weren't able to read 
ontologies due to a dearth of tools.

Imagine this sequence:

1. Someone announces a new ontology for a discourse realm
2. Postulates about its virtues.

Problem (back in the day) is that you had raw RDF/XML (or some other 
format) and no instance data on the ABox side.

> With LOD the data are suddenly the driving force. When published they are
> used to collect some ontological pieces here and there. It is 
> obviously not
> a trivial task to select this pieces properly and it calls for new 
> design guidelines
> to form these combined ontology snippets.
> What you propose is indeed somehow what I am looking for. However, your
> proposal is a bit procedural and not very much declarative and explicit.


I listed some steps instead of saying:

1. Go to the query UI and use it to perform faceted navigation over the 
URIBurner or LOD data spaces
2. Go to the SPARQL endpoint and perform a SPARQL query.

You don't get more declarative than #2 :-)

> Probably
> I missed the fact that Yahoo failed but I still wonder, whether 
> specific data repositories
> can be extracted, maintained, and made explicit. In this case, they 
> would be data
> schema repositories. It would require some manual effort but it may 
> not even
> be hard to figure out a business model for it around education and 
> consultancy?

Once folks are able to stumble across an ontology, read it, and even 
explore across the TBox and ABox dimensions, life gets much easier. 
Training gets much easier, uptake gets much easier, and most of all: 
value proposition articulation becomes easier on the part of the pitcher 
and fun on the part of the pitch recipient (current and future customers).


1. -- 
saved Ontology search with a list of Ontology URIs

2. -- 
ditto with results filtered by Attributes

-- GoodRelations with effect of TBox and ABox navigation re. 
follow-your-nose pattern


- SPARQL Query behind the PivotViewer page .


> Many greetings,
> Dieter
> At 18:47 13.03.2011, Kingsley Idehen wrote:
>> On 3/13/11 12:15 PM, Dieter Fensel wrote:
>>> Dear all,
>>> for a number of projects I was searching for vocabularies/Ontologies
>>> to describe linked data. Could you please recommend me places
>>> where to look for them? I failed to find a convenient entrance point 
>>> for such
>>> kind of information. I only found some scattered information here and
>>> there?
>>> Thanks,
>>> Dieter 
>> Dieter,
>> Do you mean: I would a place where I can search for vocabularies and 
>> assess their usage across LOD datasets? Goal being reuse of existing 
>> terms re. new datasets coming into the burgeoning LOD cloud?
>> If the above is true, the you can do the following:
>> 1. Goto  -- the live 15 Billion+ triples 
>> LOD Cloud Cache we maintain
>> 2. Enter a text pattern (with Class, Property, or Vocabulary 
>> discovery in mind)
>> 3. On receipt of the initial results page, use the Links in the 
>> Navigation section to filter by Type or other Attributes (so you are 
>> looking for Entities of type: Ontology or Class or Property
>> 4. Once you find one of the Entity Types above, click on the 
>> "describe" link
>> 5. At this point navigation should be obvious i.e. you can use 
>> isDefinedby to find the Ontology associated with Classes and 
>> Properties or use the inverse relations to find the Class and 
>> Properties defined by an Ontology.
>> Hope this helps.
>> -- 
>> Regards,
>> Kingsley Idehen        
>> President&  CEO
>> OpenLink Software    
>> Web:
>> Weblog:
>>  <>
>> Twitter/ kidehen
> -- 
> Dieter Fensel
> Director STI Innsbruck, University of Innsbruck, Austria
> phone: +43-512-507-6488/5, fax: +43-512-507-9872



Kingsley Idehen	
President&  CEO
OpenLink Software
Twitter/ kidehen

Received on Monday, 14 March 2011 00:37:59 UTC