ontology-summit
[Top] [All Lists]

Re: [ontology-summit] [Bottlenecks] Identifying Bottlenecks in Ontology

To: ontology-summit@xxxxxxxxxxxxxxxx
From: John McClure <jmcclure@xxxxxxxxxxxxxx>
Date: Tue, 21 Jan 2014 07:29:11 -0800
Message-id: <52DE9247.8020800@xxxxxxxxxxxxxx>

On 1/18/2014 1:33 AM, Matthew West wrote:
> -          What is it that takes a lot of time and effort?
>
> -          What is it that is very expensive?
>
> -          What is it that is held up because of a lack of scarce resources?
>
> -          Why is it that ontological approaches are not taken when they
> could/should be?    (01)

1. Learning and inter-weaving open-source ontologies from W3, schema.org 
and elsewhere. Development (design, coding & testing) of software to 
store, validate or display queries of resources/properties for a given 
ontology.
2. Changes to my methodology for best practice ontologies. Changes to my 
ontology's hierarchies.
3. Development of statistical entity/attribute analysis software.
4. The ontology 'industry' got off on the wrong foot: ontologies are 
more complex than they need to be. The most glaring symptom is they are 
about TWICE the size necessary, as properties are defined which 
duplicate classes. A second symptom emanates from the simple fact that 
ontologists are needed at all, to interface between SMEs and ontologies 
composed of weird techno-jargon. The root issue in both cases is the 
W3's physical design for the RDF; unfortunately it's not semantic but 
rather might/should be considered a compromised relational database model.    (02)


_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/   
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/  
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2014/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2014  
Community Portal: http://ontolog.cim3.net/wiki/     (03)
<Prev in Thread] Current Thread [Next in Thread>