https://ontologforum.com/index.php?action=history&feed=atom&title=OntologySummit2010_Communique%2FDraft_FeedBackOntologySummit2010 Communique/Draft FeedBack - Revision history2026-05-24T23:54:29ZRevision history for this page on the wikiMediaWiki 1.39.0https://ontologforum.com/index.php?title=OntologySummit2010_Communique/Draft_FeedBack&diff=189&oldid=previmported>KennethBaclawski: Fix PurpleMediaWiki references2016-01-09T08:13:14Z<p>Fix PurpleMediaWiki references</p>
<p><b>New page</b></p><div>== [[OntologySummit2010|Ontology Summit 2010]] Communique Draft Feedback Page ==<br />
<br />
This is a scratch workspace used during the [[OntologySummit2010|Ontology Summit 2010]] [[OntologySummit2010_Symposium|Communique Draft "reactions"]] session <br />
<br />
Session Chair: Professor [[MichaelGruninger|Michael Gr&uuml;ninger]] <br />
<br />
Baseline Communique Draft (at start of this session): http://ontolog.cim3.net/cgi-bin/wiki.pl?action=browse&id=OntologySummit2010_Communique/Draft&revision=59 <br />
<br />
----<br />
<br />
Summary of Communique Feedback Discussion, March 15 <br />
<br />
Issues to be Added <br />
<br />
How do we evaluate ontologies (methods and metrics) <br />
<br />
Evaluate with respect to application and reuse <br />
<br />
Linguistic aspects of ontologies <br />
<br />
Cross linkages between languages <br />
<br />
Deduction, abduction, induction as core knowledge <br />
<br />
Automated reasoning as a core knowledge <br />
<br />
Ontology lifecycle management <br />
<br />
Engineering principles <br />
<br />
Adding object oriented methodologies, modularity, and info hiding <br />
<br />
Add engineering and manufacturing to Application Domains <br />
<br />
Simple summary of ontology benefits (before current state of training) <br />
<br />
Case studies? <br />
<br />
Link to prior communiques <br />
<br />
Resources for ontologies (further reading) <br />
<br />
Inclusion of uncertainty in knowledge <br />
<br />
Clarification of ontologists as profession vs discipline <br />
<br />
more justification for requirements <br />
<br />
Relationships between requirements and the goals of the Summit (ontology to support this) <br />
<br />
Development of ontolgoies as discipline<br />
Dept of Ontologies <br />
<br />
Disentangle knowledge and skills into different kinds of ontologists and tasks <br />
<br />
References to successful ontology projects <br />
<br />
Funding paths <br />
<br />
Issues Related to Modification <br />
<br />
2BSE "computer science" to "computing" <br />
<br />
2ATR "applying ontologies to the solution of real and complex problems" <br />
<br />
2BSE move to 2ATR <br />
<br />
skills are developed not taught <br />
<br />
'ontology" --> "applied ontology" and/or "ontological engineering" or "computational ontology" or "formal ontology" <br />
<br />
"technology" to "semantic technology" <br />
<br />
Clarify the definition of "semantic technology" <br />
<br />
references to commercial products and endeavors <br />
<br />
institution to organization <br />
<br />
Justify the comment "There is a high demand for ontologists" <br />
<br />
* examples from biomedical domains <br />
* 51 government projects containing the word "ontology" <br />
<br />
Programs at the graudate level are not enough -- we need undergraduate courses/ programs <br />
<br />
* intergrating ontologies into current undergrad courses <br />
<br />
We need to train more than ontologists -- also need management training <br />
<br />
Emphasis on soft skills in ontology design projects <br />
<br />
Need to be pragmatic in the communique <br />
<br />
Keep in mind the published version in Applied Ontology journal <br />
<br />
What does an ontologist bring to a project? <br />
<br />
[[Category:WorkSpace]] [[Category:OntologySummit]] [[Category:OntologySummit2010]]<br />
<br />
<br />
<br />
</div>imported>KennethBaclawski