[alicebot-archcomm] Blank condition values

[Anne Kootstra]

This would work if the people working on the idea have programming
experience. Sadly I don't really fall into that category, so if anyone would
ask me to have a look into the <set> <get> algorithms than I would be
completely useless in that discussion.

Nevertheless, I would like to know how a proposal would be made. Over the
last few months I've been diving into the ArchComm archives and I've found a
few proposals. Most of them where only a couple of paragraphs and some only
a few lines. So, I'm curious what a *good* proposal would look like. Maybe
someone has a few examples from their own business?

--Anne

-----Oorspronkelijk bericht-----
Van: alicebot-archcomm-admin@list.alicebot.org
[mailto:alicebot-archcomm-admin@list.alicebot.org]Namens Jon Baer
Verzonden: maandag 20 mei 2002 17:23
Aan: alicebot-archcomm@list.alicebot.org
Onderwerp: Re: [alicebot-archcomm] Blank condition values


Why not assign a development "owner" to some of the AIML tags?  So that one
person is working on ideas for one set of a framework, something like a
subcommittee without the contraints ... if we could as a group come up with
a
decent proposal template this could help streamline the process of getting
things approved rather than say having to discuss a <tag> for 2-3 weeks and
nothing happening with it.  Something that could go out once a week not
everyday, for example Id like to tackle the storage stuff
(<add>,<set>,<get>,<remove>) and that's it (quite honestly some areas are
COMPLETE programming projects all by themselves) ...

At least this way if the "owner" proposes it and someone has a problem with
some
issues they can work directly on it with that person ... I just dont want to
see
it go nowhere.

- Jon

Anne Kootstra wrote:

> I have to agree with Conan that I would like to see the <condition> tag
> expanded with a few features but I do think that the emphasis for the near
> future would have to lie on the <random>/<shuffle> tag and the extension
> mechanism.
>
> However, we could have a brainstorm sessions on the mailinglist, lets say
> two days, where everyone could input their wildest ideas regarding one
topic
> or <tag>. And then a week later have the same type of session for another
> topic or tag.
>
> Just a passing thought.
>
> --Anne
>
> -----Oorspronkelijk bericht-----
> Van: alicebot-archcomm-admin@list.alicebot.org
> [mailto:alicebot-archcomm-admin@list.alicebot.org]Namens Conan Callen
> Verzonden: maandag 20 mei 2002 16:27
> Aan: alicebot-archcomm@list.alicebot.org
> Onderwerp: Re: [alicebot-archcomm] Blank condition values
>
> Given the existing rules, this addtion would add to the complexity of the
> interpreter possibly leading to error ambiguity, and confusing the aiml
> programmer. Unless botmasters are filling your mail box asking for this
> feature, extensions are probably a higher priority
>
> Conan
>
> ----- Original Message -----
> From: "Noel Bush" <noel@alicebot.org>
> To: "Alicebot and AIML Architecture Committee"
> <alicebot-archcomm@list.alicebot.org>
> Sent: Monday, May 20, 2002 2:54 AM
> Subject: Re: [alicebot-archcomm] Blank condition values
>
> > By the way, I think it's entirely possible that the doc should be
> > changed to support what you want more directly.  ;-)
> >
> > On Mon, 2002-05-20 at 12:06, Conan Callen wrote:
> > > Right after I sent my question I read the docs (opps), and saw just
what
> you
> > > are talking about.
> > >
> > > Thanks, Conan
> > >
> > > ----- Original Message -----
> > > From: "Noel Bush" <noel@alicebot.org>
> > > To: "Alicebot and AIML Architecture Committee"
> > > <alicebot-archcomm@list.alicebot.org>
> > > Sent: Sunday, May 19, 2002 11:54 PM
> > > Subject: Re: [alicebot-archcomm] Blank condition values
> > >
> > >
> > > > We have said that the value of the value attribute must be a valid
> AIML
> > > > pattern.  An empty string is not a valid AIML pattern.  So according
> to
> > > > the current specification it is not possible to test for a blank
value
> > > > in the ways you illustrated.  A valid way could be:
> > > >
> > > > <condition name="color">
> > > >   <li value="*">Color is associated with a non-blank value.</li>
> > > >   <li>Color is associated with a blank value.</li>
> > > > </condition>
> > > >
> > > > On Mon, 2002-05-20 at 00:14, Conan Callen wrote:
> > > > > On a condition statement if the value is "" (blank), is it
> nessessary to
> > > include the value="" or can it be left off?
> > > > >
> > > > > <condition name="color" value=""> == <condition name="color">
> > > > >
> > > > > or
> > > > >
> > > > > <li name="color" value=""> == <li name="color">
> > > >
> > > >
> > > > _______________________________________________
> > > > alicebot-archcomm mailing list
> > > > alicebot-archcomm@list.alicebot.org
> > > > http://list.alicebot.org/mailman/listinfo/alicebot-archcomm
> > > >
> > >
> > > _______________________________________________
> > > alicebot-archcomm mailing list
> > > alicebot-archcomm@list.alicebot.org
> > > http://list.alicebot.org/mailman/listinfo/alicebot-archcomm
> > >
> >
> >
> > _______________________________________________
> > alicebot-archcomm mailing list
> > alicebot-archcomm@list.alicebot.org
> > http://list.alicebot.org/mailman/listinfo/alicebot-archcomm
> >
>
> _______________________________________________
> alicebot-archcomm mailing list
> alicebot-archcomm@list.alicebot.org
> http://list.alicebot.org/mailman/listinfo/alicebot-archcomm
>
> _______________________________________________
> alicebot-archcomm mailing list
> alicebot-archcomm@list.alicebot.org
> http://list.alicebot.org/mailman/listinfo/alicebot-archcomm

_______________________________________________
alicebot-archcomm mailing list
alicebot-archcomm@list.alicebot.org
http://list.alicebot.org/mailman/listinfo/alicebot-archcomm