[Modeling] R: [Methodology] Terms for first release of the glossary
Wed, 6 Aug 2003 13:45:42 +0200
these terms are on the glossary page in the TC website from a long time
and have been proposed by several different members. In this phase I
just selected some of them for the first release of the glossary.
I think we shoud include (at least some of) them because also the most
general one have a direct influence in the definition of structural
related terms (like automonous or adaptive agent). The MAS metamodel
have a direct link with these latter and this metamodel is a key part of
our TC work since it can be used as a guide (and a coherence check) to
compose different method fragments.
If you think that we should postpone the discussion of some of them for
the next releases of the glossary, in principle I can agree, also
because I too think that a specific glossary TC could be the right place
for a deep discussion.
What is your proposal? Which terms do you prefer to leave apart by now?
To other TC members: what is your opinion?
> -----Messaggio originale-----
> Da: email@example.com
> [mailto:firstname.lastname@example.org] Per conto di James Odell
> Inviato: luned́ 4 agosto 2003 4.16
> A: 'FIPA methodology ML'; ModelingTC
> Cc: email@example.com
> Oggetto: Re: [Methodology] Terms for first release of the glossary
> > here is a proposal of a list of terms for the first release of the
> > glossary. Let me know if you want to add/remove any term.
> > The definitions in the list have been composed by me trying to
> > conciliate the different proposals (if more than one were
> in the list).
> > Obviously they are just a starting point and their
> discussion will be
> > one of the objectives of the Banff meeting.
> Could you tell me what the purpose of this glossary is for
> the Methodology TC? There are terms in it that I would *not*
> associate with process engineering. Moreover, there seem to
> be terms that should be defined at a much more general level:
> e.g., autonomy, adaptivity, behavior, belief, desire,
> intention, cooperation, conversation, etc. I would argue
> that most of these terms are not in the purview of the
> Methodology TC. That is, they are not terms that process
> engineers should be in charge of. The current Methodology TC
> work plan deals with method-base architecture, method
> fragments, and descriptions of techniques for method
> integration-- not a glossary of key agent terms. Instead,
> they may be work that an Agent Glossary TC might work on.
> The approved workplan states " A glossary of agent
> development methodologies
> related concepts (due October 2003)." I'm sorry, but I
> do not see the
> terms mentioned above in the glossary are related to agent
> development methodologies.
> Jim Odell
> Methodology mailing list
> Methodology@fipa.org http://www.fipa.org/mailman/listinfo/methodology
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.470 / Virus Database: 268 - Release Date: 08/04/2003
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.470 / Virus Database: 268 - Release Date: 08/04/2003