ontolog-forum
[Top] [All Lists]

Re: [ontolog-forum] Architectural considerations in Ontology Development

To: ontolog-forum@xxxxxxxxxxxxxxxx
From: John F Sowa <sowa@xxxxxxxxxxx>
Date: Sat, 16 Feb 2013 02:12:35 -0500
Message-id: <511F3163.20509@xxxxxxxxxxx>
On 2/15/2013 11:26 PM, David Eddy wrote:
> And since pretty much by definition there is NO ontology for the legacy
> systems.    (01)

No.  That's not true.    (02)

Every application program is based on an ontology of the entities
and processes in the application.  The primary difference is in
the way that ontology is represented and used:    (03)

  1. Implicit:  The only ontology about the subject is in the mind
     of the programmer, and not in any form that can be examined
     and used by any other agent -- human or computer.    (04)

  2. Stated in the requirements.  The ontology is represented,
     formally or informally, in some document that specifies the
     domain of the application and requirements for what it does.    (05)

  3. Object level.  The ontology is represented in a form that can be
     processed by programs that use it to reason about the subject.    (06)

  4. Object level + Metalevel.  The ontology is explicitly represented
     in a form that can be processed by tools that reason about the
     ontology, translate it to object-level operations on the data,
     and use it to reason about and process the data.    (07)

In our discussions in Ontolog Forum, we have focused on levels 3
and 4.  Levels 1 and 2 also use ontology, but not in form that is
formally represented and processed.    (08)

> Unless, of course, there's some magic that can extract usable
> ontologies from existing systems in a week or so.    (09)

There is.  In fact, the first major application of VivoMind software
did exactly that.  It analyzed software (COBOL programs and other
computational and database resources), developed a hierarchy of
the types and relations in the software and the names used to
refer to them, and translated the information to conceptual graphs.    (010)

Then it used that information to analyze English documents about
the software -- manuals, reports, emails, comments, etc.  It
generated cross-indexes of the documentation and the software
and checked for discrepancies.  For further discussion, see
Slides 138 to 146 of    (011)

    http://www.jfsowa.com/talks/goal.pdf    (012)

> But I'm pretty sure such practical reverse engineering is
> of minimal interest to the Ontology world.    (013)

That depends on which world you're talking about.  Certain people have
no interest in anything except proving theorems about decidability.
That application was very interesting to the people who paid for it.    (014)

> This week I've seen what appeared to be a promising corporate glossary.    (015)

Just look at those slides.  As a by-product of the analysis, the
program generated a data dictionary for computer use and a glossary
for human use with cross references to both the software and the
documentation about it.    (016)

John    (017)

_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J    (018)

<Prev in Thread] Current Thread [Next in Thread>