Adrian,
My problem space is aerospace and
defence, where getting things wrong costs lives. One way of restating the
problem is that I am looking for systematic ways of evaluating the risk
that a term will be misapplied, or applied inaccurately, and also of
minimising that risk, where risk is the product of the probability of an
occurrence and the impact of that occurrence.
From your slides, Executable English is not
concerned with that problem. In fact, rhetorically, calling something
"executable English" is a claim that people already understand what terms mean.
I would contrast your statement on slide 19 "A term is
defined by the set of its superclasses in the taxonomy, and by its
properties" with my final comment "ontology classes used by a business process are exactly those
classes which label the alternative routes onward from a decision process, and
therefore define the grounding of terms." The way many people would read your
definition is that terms are acontextual, whereas I would insist that terms are
context sensitive, particularly where conventional terms are used with a
particular technical sense by a business process. For example, in one business,
a "drawing" was a concept reified as a database entry, whereas a thing with
lines on showing the shape of a part was called a "drawing
sheet".
The problem of accurate
communication is therefore one of alerting people to the actual meaning of a
term in the context in which it is being used, rather than allowing them to
assume they already know what the term means. In terms of Executable English, I
can see that it might have applications where the impact of misinterpretation of
terms is limited, but I see it as part of the problem exactly because it draws
attention away from the need to manage such risks. This is more a statement of
requirements than a criticism of Eexecutable English
Sean Barker, Bristol UK.
*** WARNING *** This message has originated outside your
organisation, either from an external partner or the Global Internet. Keep this
in mind if you answer this message. Sean --
You wrote:
I am looking for a razor that can cut between the
"ontologies as a formal system" and "ontology term grounding" parts of the
discussion, and so ensure that both parts are
solved.
A candidate for your desired
semantic razor is Executable English.
The diagrams on slides 14-17 and
slides 51-52 of [1] illustrate this.
There's a runnable example on slides
35-43.
Cheers, -- Adrian [1] www.reengineeringllc.com/Internet_Business_Logic_e-Government_Presentation.pdf
Internet Business
Logic A Wiki and SOA Endpoint for Executable Open Vocabulary English Q/A over
SQL and RDF Online at www.reengineeringllc.com
Shared use is free, and there are no advertisements
Adrian
Walker Reengineering
|