Re: HM.applications-Profiling-Level of Details/Abstraction

[Mark Brownell <gizmotron@earthlink.net>]

----- Original Message ----- 
From: Sean B. Palmer 
[...]
> :Button a :Mechanism .
> :Blue a :Class; rdfs:comment "the class of things which are blue";
>    rdfs:label "Blue Thing" .
> :Red a :Class; rdfs:comment "the class of things which are red";
>    rdfs:label "Red Thing" .
> x:BlueButton a [ daml:intersectionOf (:Button :Blue) ] .
> x:RedButton a [ daml:intersectionOf (:Button :Red) ] .
> x:Heater a :Heater .
> x:AirConditioner a :AirConditioner .
[...]
> let's feed all that junk into CWM and get it to think about it... aha, it
> concluded (correctly):-
> 
>     x:BlueButton     a  [
>              daml:intersectionOf  (
>             :Button
>             :Blue  ) ];
>          :activates x:AirConditioner .
> 
>     x:RedButton     a  [
>              daml:intersectionOf  (
>             :Button
>             :Red  ) ];
>          :activates x:Heater .
> 
> Neat.
---------------------

From: Rex Brooks 
> 
> I haven't gotten completely through Mark Brownell's Meaningful Text 
> Markup Language work, but I have gotten far enough to see that one of 
> our most important domains is a significant subset of that work, 
> namely the categorization of text into Human Meaningful areas.

Hi All,

So for the sake of information like this above, if I understand it correctly, here is
a MTML representation of the same information in a human readable form, that
could be used by an application using PNLP, Parallel Numerical Lineal Parser.

The MTML below is descriptive of a single object, that could be expressive of 
many objects, that are about things that happen while in a car.

<while in the car> -- relates to things that happen while in a car.
  <human comfort > -- relates to human comfort wherever it may happen.
    <senses change in comfort> -- relates to senses involving comfort.
      <reaction to change in comfort> -- implies a human action to change
         <possible choices in this situation> 
           <air condition controls on the dashboard>
              <air conditioner on/off switch>
                 <automobile characteristics>
                    <turns heater off when activated/>
                    <is visible on dashboard with a blue indicator/>
                    <is illuminated with a blue indicator light at night/>
                    <turns off air conditioner if selected while AC is on/>
                 </automobile characteristics>
              </air conditioner on switch>
              <heater on switch>
                 <automobile characteristics>
                    <turns heater off when activated/>
                    <is visible on dashboard with a blue indicator/>
                    <is illuminated with a blue indicator light at night/>
                    <turns off air conditioner if selected while AC is on/>
                 </automobile characteristics>
              </heater on switch>
           </air condition controls on the dashboard>
           <open windows>
             <automobile characteristics>
                 <roll down windows using the correct window switch/>
             </automobile characteristics>
           </open windows>
           <do nothing about it>
              <reference human traits/>
           <do nothing about it>
         </possible choices in this situation>
      </reaction to change in comfort> 
    </senses change in comfort>
  </human comfort >
</while in the car> 

<while in the car> 
   ... more stuff about cars
</while in the car> 

This set of nested tags could be used to reconstruct sentences that make sense to the 
inquiring application using this markup. At any level there are objects within other objects. 
So it is possible to gather together parts of one object that can be used to populate parts 
of another object. It just depends on how you want to build the application.  As you can see 
the information is in a human readable form.

Happy trails,

Mark