Matthew, thank you, I am delighted. (... though not astonished!) (01)
Sincerely,
Christopher (02)
P.S. In a follow-up point I am busy addressing how TMA escapes the
problem of those long type names we tend to concoct for explanation
purposes. That apparently minor point then leads to some bigger ones... (03)
P.P.S. Meanwhile, I must correct a typo in my previous post:
Not "the result has a far more flexible form of the Separation of
Concerns that is implicit in the layering of the top two tiers of the
conventional 3-tier model, namely UI and application."
but "the result has a far more flexible form of the Separation of
Concerns than is implicit in the layering of the top two tiers of the
conventional 3-tier model, namely UI and application."
I should also have been more specific and emphatic: the result is not
only "more flexible" but more appropriate, more ontology-leveraging,
hence far higher quality too. (04)
----- Original Message -----
From: "Matthew West" <dr.matthew.west@xxxxxxxxx>
To: "'Ontology Summit 2012 discussion'"
<ontology-summit@xxxxxxxxxxxxxxxx>
Sent: Monday, February 06, 2012 11:28 AM
Subject: Re: [ontology-summit] System Components (05)
Dear Christopher, (06)
This is in fact almost exactly the approach I take in my book
"Developing High quality Data Models". (07)
> The entire doubly-inherited hamburger, the paired FU-TS or
> PumpRole-ActualPump, is an instance of a new type, subtype of both
> PumpRole and ActualPump. It might be spelled out as type
> "ActualPumpInAPumpRole", itself optionally defined as a subtype of,
> say, "UnitInARole". It would have the attributes of actual units,
> such as serial number and measured dimensions with their precisions,
> as well as the attributes of required units, such as required
> functionality and dimensions with their tolerances.
>
MW: The differences are that the result is called installed_object, and
it is a subtype of state_of_system_component, and
state_of_ordinary_physical_object, because the pump installed is not
installed for the whole of its life, or necessarily for all of the life
of the system_component, but only part of it. (08)
MW: That it is a subtype of these things is one reason why non-4D
ontologies struggle, since they do not recognise that states exist as
objects in their own right. (09)
MW: The whole data model is available to browse at:
http://www.matthew-west.org.uk/hqdm_framework/ (010)
Regards (011)
Matthew West
Information Junction
Tel: +44 1489 880185
Mobile: +44 750 3385279
Skype: dr.matthew.west
matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx
http://www.informationjunction.co.uk/
http://www.matthew-west.org.uk/ (012)
This email originates from Information Junction Ltd. Registered in
England and Wales No. 6632177.
Registered office: 2 Brookside, Meadow Way, Letchworth Garden City,
Hertfordshire, SG6 3JE. (013)
_________________________________________________________________
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/OntologySummit2012/
Community Wiki:
http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
Community Portal: http://ontolog.cim3.net/wiki/ (014)
_________________________________________________________________
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/OntologySummit2012/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
Community Portal: http://ontolog.cim3.net/wiki/ (015)
|