ontology-summit
[Top] [All Lists]

Re: [ontology-summit] Process to build a domain ontology

To: mcoyne@xxxxxxxxxx, ontology-summit@xxxxxxxxxxxxxxxx, peter.benson@xxxxxxxxx
From: Michael Priddy <mpriddy@xxxxxxxxxxxxx>
Date: 6 Jun 2011 09:09:18 -0400
Message-id: <647654516.1307365758479.JavaMail.cfservice@sl1app1>
 
All, per your interest in building Ontologies. We worked with NIST and MITRE to develop a Ontology Methodology (SWIM). We give this away for free and it is available on our web page (Above Link). Scott is speaking at SemTech so you can ask him about it if you wish. Most of the ontologies that we build are 90% done from our search and we add or combine a lot. We typically complete our first run at an ontology in one to two weeks and adjust accordingly when we get our data aligned. Let me know if you need any additional help.
 
We have sent our Product "Feast" over to AFS last week and it has a number of really cool features including a SOLR store with no database provenience, context sensitive security, GIS and workflow. Look for this soon to be free to download.
 
Michael Priddy
CEO
Intervise Inc
(240) 599 9301
 
 

 
-----Original Message-----
From:Peter R. Benson peter.benson@xxxxxxxxx
To: "mcoyne@xxxxxxxxxx" , "Ontology Summit 2011 discussion" ;
Sent: Jun 6, 2011 06:46:00 AM
Subject: Re: [ontology-summit] Process to build a domain ontology

My, we build ontologies using a somewhat different approach. We focus first on creating a subset of a very large open technical dictionary that contains concept identifiers and associated terminology. We then create data requirement specifications, these contain the properties needed to identify and describe the physical and performance (capabilities) of a class. Finally we then create class hierarchies as needed for analysis. We use a tool that is linked to the eOTD (dictionary) and the eDRR (data requirement registry) to create what we call a "corporate preferred ontology".

These ontologies are used to create portable data warehouses and to improve the quality of master data and the descriptions in ERP systems.

Peter
Cell: +1 610 462 5923

On Jun 4, 2011, at 11:16 PM, My Coyne <mcoyne@xxxxxxxxxx> wrote:





All,

I am looking for a best or good practice  on a process to build a domain ontology and tools to use in each step if it is helpful.

 I have seen a process that comprises of the following process steps:
1.  Specification - in this step one would acquire knowledge about the domain, describe them, specify goals and scope, and most important is to describe motivating scenarios and competence questions to query of the ontology.    Tool: one may use use case specification, text base for this process and it would be suffice.
2. Conceptualization.  In this step the domain conceptual model is designed.   The desired end product of this step is a set of terms and concepts; and identification of classes, relations, and attributes.  A concept classification tree can be constructed for knowledge organization.  Tool: I don't know if there is tool for this.
3.  Implementation: in this step the conceptual model will be implemented using different ontology editing tools. 
4.  Publishing.  I am encouraged by the site such as NCBO BioPortal where ontologies are deposit, for public to query and comments on. 

The above process is the only one process that I know.  I'm soliciting for other good practice processes (and tools) that anyone might have used to build a domain ontology.   Any comments, directions to paper, or advice  are greatly appreciated. 



My Coyne
mcoyne@xxxxxxxxxx
(cel): 301-399-6351

_________________________________________________________________
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/OntologySummit2011/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2011  
Community Portal: http://ontolog.cim3.net/wiki/     (01)
<Prev in Thread] Current Thread [Next in Thread>