ontolog-forum
[Top] [All Lists]

Re: [ontolog-forum] Using controlled natural languages for ontology

To: ontolog-forum@xxxxxxxxxxxxxxxx
From: Ron Wheeler <rwheeler@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 14 Mar 2011 12:01:12 -0400
Message-id: <4D7E3BC8.1080500@xxxxxxxxxxxxxxxxxxxxx>
On 14/03/2011 8:20 AM, John F. Sowa wrote:
> Dear Matthew and Anders,
>
> MW
>> Yes, but the different departments need to talk to each other, and this
>> is most efficiently done with a "common language" which need not be "ideal"
>> for any of them, but which each is able to translate into and out of. What
>> we found in Shell was, that as you did this successively, there was
>> considerable advantage in giving up your own "language" and increasingly
>> sharing fewer more common ones.
> AT
>> An interesting dimension at play here; how much centralisation is
>> needed  in a corporation with extensive work specialisation.
> I agree with both of you.
>
> The engineers, for example, need to consider all the details about
> how components interact.  Manufacturing has to focus on those details
> relevant to assembling the parts.  Finance can treat each product as
> a "black box" with a focus on just the costs and revenues.  Sales
> focuses on the features the users see and how they compare with the
> competition.  Shipping treats the units as black boxes, whose relevant
> features are size, weight, fragility, and perishability.
>
> All the departments need to use the same terminology about the products,
> including part numbers for components.  But that is a requirement for
> a *terminology* with very few axioms that are shared among departments.
>
> AT
>> Typically commonality is deemed as beneficial, but sometimes an ad hoc
>> approach is of benefit depending on ones (investment) horizon.
>> 
>http://www.workem.com/rl/fesa/fragments/modeling/LargeScaleSystems/ls_centralisation/files/page42-mot_artifact_canonical.jpg
> I agree with the diagram, but I would change the label "ad hoc" to
> "specialized".  The engineers, for example, may have a very general
> ontology for their designs.  But that ontology may have much more in
> common with the ontologies used by competitors in the industry than
> with other departments in the same company.
>
> The same is true of all the other departments.  People in the finance
> department share more common background with financial people in other
> companies or even other industries than they do with the engineering,
> sales, or shipping departments in their own company.
>
> Summary:  Terminology is the foundation for sharing information among
> people (and computers) with different specialties.  Ontologies with
> detailed axioms suitable for complex reasoning are used only in a
> narrow specialty.  The specialized ontologies are more likely to be
> sharable across different companies than with different departments
> in the same company.    (01)

> (But competition may prevent such sharing.)
That is where standards bodies and industry associations fix these 
competitive barriers for the mutual benefit of competitors.
Governments frequently regulate the use of common reporting schemes.
> John
>
> _________________________________________________________________
> 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
> To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
>
>    (02)


_________________________________________________________________
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
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx    (03)

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