1. First, I want to refine my notion of a context pipeline. It takes the
form
at view=v1 {propositionlist1}
| at view=v2 {propositionlist2}
| ...
| at view=vN {propositionlistN};
v2 thru vN are optional specifications of context names, which were
omitted in my previous discussions.
2. You might want to use a context pipeline because you want to make
a sequence of related changes to concept hierarchies and individual
hierarchies. For example, you might want to form new concepts by
differentiation or integration. You might want to delete concepts
and/or individuals. You might want to reclassify individuals to
different concepts.
3. What is the concept hierarchy?
It is the lattice of all concepts (classes), connected by all the
"iss" (subClassOf) relations. It can be simplified by removing
redundant "iss" links to higher-level concepts.
4. What is the individual hierarchy?
It is the concept lattice with all the individuals added, connected by all
the "isu" (type) relations. It can be simplified by removing redundant
"isu" links to higher-level concepts.
5. Revisiting my RealEstate example.
In my previous email
at view=RealEstate {do read from mls.rel.html done;} # mls iss relation;
| {mls3 := do select from mls with $8=3, $3=Sold done;}
| {average3 := do average price od mls3 done;};
I just kept adding propositions.
In the spirit of filtering out propositions which are of no interest,
I might have have included this in the second proposition list
do delete od mls done;
6. I offer all of the above as part of my continuing efforts to focus
on the epistemology and the real-world meanings of our knowledge
representations.
Dick McCullough
Ayn Rand do speak od mKR done;
mKE do enhance od Real Intelligence done;
knowledge := man do identify od existent done;
knowledge haspart proposition list;
http://mKRmKE.org/