|Pretty good. Suggest you consider that in the construct rule the relations may be among the relations as well as among the objects (Weinberg). In other words, relations may be objects, too (as in perspective shift). This is important to systems and may be a challenge to ontologists.|
Warfield also proposed the Discovery and Design notion but Discovery was about the problem system (context of the system of interest) whereas Design was about the system of interest. Restricting Discovery to natural systems leaves a gap in discovery of the "real problem" that stakeholders want the system of interest to mediate.
On Jan 29, 2012, at 11:59 AM, joseph simpson wrote:
For example three, now consider:
--- "system of (X)"
--- "part of (X)"
Where X can be , laws, games, airplanes, cars, plants.. and so on..
The "system concept" may be viewed as a real world relationship that is used to order or constrain the environment.
Using this basic view, two types of definitions for a system can be constructed as well as two main types of activity for system concepts.
The two definition types are, function (rule) and constructive (rule).
The two main activity types are discovery and design.
The functional rule definition for a system was given previously and is restated here, "A system is a constraint on variety, where the constraint identifies and defines the system of interest."
The construction rule definition for a system is, " A system is a non-empty set of objects and a non-empty set of relationships mapped over these objects and their attributes."
Humans tend to use the concept of a system for two main activities:
--- Discovering, documenting and discussing natural systems (systems not constructed by man).
--- Designing, documenting and discussing artificial systems (systems constructed by man).
Johannes Kepler's laws of planetary motion that describe the behavior of solar system under the defining constraints of natural physical forces is one example of using the system concept in the discovery mode.
The Wright brothers are an example of the application of the system concept used in the design mode.
These modes of application have different approaches, methods and techniques.
Mixing these modes may generate a high degree of semantic conflict.
On Sun, Jan 29, 2012 at 3:36 AM, Christopher Spottiswoode <cms@xxxxxxxxxxxxx>
You both make very useful points. Here I highlight just 2 of them:
> This ontologizing-in-the-large lead to your need to define not only
> ontology-as-algorithm but also communication protocol between ontology
> components that reside in different nodes. I doubt that mantra about
> "federation" is helpful here. If you have web programming (that is in
> essence programming-in-the-large) you speak not about "federating" of
> web-server, load balancer, database, web-page generation, ad banner
> importing, etc. but have another engineering approach (while all that
> software developed by different organizations and reside on different
As I shall be describing in some detail later, appropriate architecture
leads to good 'Separation of Concerns', hence reliable and flexible
application modularity while also enhancing the various other qualities
usually sought. That is what a properly ontology-based architecture
should of course produce, and "federation" is a good word to describe
the result at the in-the-large level.
In contrast to what I shall be describing, the conventional web
programming you highlight is complication-inducing rather than
> I suggest that the "binding force" or "binding concept" that forms aYes! That is indeed most strongly the case in the architecture I shall
> number of items in to one entity is a key feature.
be describing (or trying once again to describe, lessons hopefully
having been learnt...).
All of which recalls that now very mainstream IS programming precept:
Larry Constantine's "high module cohesion with loose module coupling".
We don't have to reinvent that wheel.
> Have fun,
Yes thanks, Joe, we sure will!
Sent From My DROID!!
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
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/