OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

humanmarkup-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


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


----- Original Message -----
From: Bullard, Claude L (Len)

> Good:  a static description.  That is representable in
> an XML Schema given you take out the illegal whitespaces
> in the generic identifiers (unqualified names).
>

Hi Len,

With PNLP <some tag with some white space in it/> could
be transformed to <some_tag_with_some_white_space_in_it/> in
an extremely fast manner. It could transform tags back to human
readable for presentation purposes in an application/user form.
Then all that would be necessary is nesting the information as
well formed.

> The nut of the problem in the original paper described
> reasoning by analogy.
>
> That is, all the system knows is how to turn the heater
> on or off.  It has to reason its way to facts or
> really tests to figure out the air conditioner.  That
> is why it has to identify an analog, then do the
> substitution.   It actually doesn't know the air conditioner
> is there.  It knows there is a red button to activate
> the heater and there is a blue button.
>

So this description includes a set of if/then capabilities:

<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>
                    <if-then> windows are down, put windows up</if-then>
                    <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/off switch>
              <heater on/off switch>
                 <automobile characteristics>
                    <if-then> windows are down, put windows up, do machineTask1, do
reportTask7</if-then>
                    <machineTask1>autoControl spec#00023-76</machineTask1> -- closes windows
                    <reportTask7>reportControl message#7</reportTask7> -- reports auto system status
                    <turns AC off when activated/>
                    <is visible on dashboard with a Red indicator/>
                    <is illuminated with a Red indicator light at night/>
                    <turns off Heater if selected while Heater is on/>
                 </automobile characteristics>
              </heater on/off 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>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC