- Haskell - Haskell.org

Re: [Haskell] Re: Global Variables and IO initializers
by MR K P SCHUPKE 05 Nov '04

05 Nov '04

>The point is to avoid threading global state to IO actions manually. >Programming langages exist in order to conveniently write programs in, >not only to admire their beauty. So if you are not interested in beauty, why not use the IO monad! If something is IO then declare it. You should not lie to the type system, or try to cheat it. It is your friend, and will help prevent errors in code. The point is to write correct error free programs, If you find the requirements too constrictive you should use another language. We don't need yet another Visual Basic/Java/C whatever. I see no problem with threading global state to IO actions, that is after all making clear in the function type what is happening! If you hide this from the type system, it can only lead to problems in the long run. Keean.

2 1

Re: [Haskell] Re: Global Variables and IO initializers
by George Russell 04 Nov '04

04 Nov '04

John Peterson wrote (snipped): > The implementer of these functions has to guarantee that the > actions do not destroy the commutativity of the CIO monad. Sorry, but several of my variable initialisation actions involve things like starting up child processes or rapid exits from the program if unsuccessful, which certainly cannot be guaranteed to be commutative. I still think the proposal I made to this list in June http://www.haskell.org//pipermail/haskell/2004-June/014104.html is sound. It requires nothing other than a new library, which is trivial to implement using the existing unsafePerformIO. It is safe. I don't think it's especially clunky. Essentially the only serious limitation is that you can only access a bit of initialised state from an IO action, but in my experience at least this is not a serious issue. However virtually everyone seems to have their own patent solution, and we are no closer to agreement. Might it be an idea to have a Wiki or something like that devoted to discussion of this problem, and we can all try to agree on the advantages and disadvantages of the competing methods?

3 2

grammar for Haskell?
by Peter Schneider-Kamp 04 Nov '04

04 Nov '04

Hi! We are looking into parsing full Haskell98 (probably using SableCC) as an input language to our program verification environment (http://www-i2.informatik.rwth-aachen.de/AProVE) Does anyone know about and can point me to either a) a SableCC style Haskell98 grammar description, b) any LALR(1) gramamr for Haskell98, c) a Haskell98 grammar for either JavaCC, ANTLR or another Java-based compiler compiler, d) a Haskell98 grammar for a compiler compiler whose output can be compiled to Java classes/bytecode, or e) any other concise Haskell98 grammar which is less fragmented than the Haskell98 report. Any help in this matter is appreciated. The lower the letter, the better :-) Kind regards, Peter -- Peter Schneider-Kamp mailto:psk@informatik.rwth-aachen.de LuFG Informatik II http://www-i2.informatik.rwth-aachen.de/~nowonder RWTH Aachen phone: ++49 241 80-21211

2 1

Litle problem with a haskell Function...
by Manuel Costa 03 Nov '04

03 Nov '04

Hello, I' a Haskell Newbie and i need some help about a function.. My problem is to update a list of values in Runtime. For example i have a initial list: list1=3D"a"=20 and a function: add::add::String->[String] add x =3D [list1] ++ [x]=20 I need to do=20 add "c"=20 and the "c" most be append to list1 to make list1=3D["a","c"] Then if i input list1 the output must be ["a","c"] But i can't do it... Could you help me ?!

2 1

ICTCS'05 Call for affiliated workshops
by g. michele pinna 02 Nov '04

02 Nov '04

Please accept our apologies if you receive multiple copies of this call. _____________________________________________________________________ ICTCS 2005 http://ictcs05.dsmi.unisi.it/ Certosa di Pontignano, Siena, 12 - 14 October 2005 Call for Affiliated Workshops _____________________________________________________________________ This is an invitation to submit proposals for workshops affiliated with ICTCS 2005, to be held in Siena, at the Certosa di Pontignano, from October 12 (Wednesday) to October 14 (Friday). The workshops can be located either at the Certosa di Pontignano (http://www.unisi.it/servizi/certosa/) or at the Dipartimento di Scienze Matematiche ed Informatiche "R. Magari" (http://www.dsmi.unisi.it) in the days immediately preceding or following the Conference. Friday 14th afternoon is also available. Researchers and practitioners are invited to submit proposals for workshops on topics related to any field of theoretical computer science. Proposals should be submitted to the ICTCS organizing chair G. Michele Pinna (pinna(a)unisi.it) Proposals will be evaluated by the ICTCS Chairs Mario Coppo, Elena Lodi and G. Michele Pinna. Deadlines: In order to help ensure that space for the workshop will be available, please let us know as soon as possible if you are considering organizing a ICTCS-affiliated workshop, but in any case before December 31st. Workshop Proposals: Workshop proposals should consist of two parts: * A short scientific justification of the proposed topic, its scope and significance, and the particular benefits of the proposed workshop. One or two paragraphs are enough. * The following organizational details: - List of the organizers. - Address, email, phone, and fax of a single contact person. - Proposed format of the workshop. - Duration (number of days) of the workshop. - Expected number of participants and, for workshops that have been held in previous years, number of participants in the previous year(s). The ICTCS organization offers: - Link between ICTCS and Workshop web sites. - Support in the management of registration and hotel reservation. - Setup of meeting space, and related equipment. The workshop organization must take care of: - Workshop publicity and call for papers. - Providing a brief description of the workshop for inclusion on the ICTCS web page. - Scheduling workshop activities in collaboration with the ICTCS local organizer. - Printing (paper/CD) and distribution of the proceedings, if so desired. - Finding funding arrangements for their invited speakers.

1 0

ANN: Flippi v0.03
by Philippa Cowderoy 01 Nov '04

01 Nov '04

I'm writing to announce the latest version of Flippi, a simple and lightweight Wiki clone written in plain Haskell 98 using the hierarchical libraries. The main new feature in this version is support for scripts built in to the binary (yes, you can build one to shell out to another lang if you want), and the all-important RecentChanges page implemented via the scripting interface. Aside from this, various bugs have been corrected and there's a little less room for users to do silly things such as creating pages they can't link to. Flippi can be found at http://www.flippac.org/projects/flippi/ , with a running copy at http://www.scannedinavian.org/cgi-bin/flippi/flippi where I hope things such as user modifications will be linked to once they're available (I'm hearing about some as I type this). The code's all available under the BSD license, and is known to compile under GHC6 (but not GHC 5). -- flippa(a)flippac.org

1 0

Announcing: Postmaster ESMTP Server
by Peter Simons 01 Nov '04

01 Nov '04

Fellow Haskellers, at <http://postmaster.cryp.to/> you will find the first beta release of Postmaster, a mail transport agent written in Haskell. It can act as a full ESMTP server for leaf sites already, and if you have another MTA installed, then you can use it as a front-end for that to do mail relaying, too. I have been running the software in a pretty complex setup for a few days now and it works reliably. Mostly. :-) Have fun! Peter

3 4

Announce: Cabal 0.1 (Library Infrastructure Project)
by Isaac Jones 01 Nov '04

01 Nov '04

Much thanks to all who've made this possible :) The Haskell Cabal The Common Architecture for Building Applications and Libraries. DOWNLOAD: The Haskell Cabal has reached pre-release stage, with a 0.1 version The community should use this release to evaluate the interfaces and explore the concepts of these tools. Download the Cabal here: http://www.haskell.org/cabal/download.html BUGS: Please report bugs and wish-list items here: http://sourceforge.net/tracker/?func=add&group_id=44807&atid=440922 Or email Isaac Jones: ijones(a)syntaxpolice.org ABOUT: The Haskell Cabal is meant to be a part of a larger infrastructure for distributing, organizing, and cataloging Haskell Libraries and Tools. It is an effort to provide a framework for developers to more effectively contribute their software to the Haskell community. Specifically, the Cabal describes what a Haskell package is, how these packages interact with the language, and what Haskell implementations must to do to support packages. The Cabal also specifies some infrastructure (code) that makes it easy for tool authors to build and distribute conforming packages. The Cabal is only one contribution to the larger goal. In particular, the Cabal says nothing about more global issues such as how authors decide where in the module name space their library should live; how users can find a package they want; how orphan packages find new owners; and so on. NOTES: This release is meant to provide the community with concrete information about how the interfaces are shaping up. This release does NOT fix the interfaces, we can't promise not to break anything that relies on these interfaces. We hope that Haskell authors will try to package their software using these tools, and let us know where they fall short. MORE INFORMATION: Please see the web site for the source code, interfaces, and especially the proposal, which will serve as documentation for this release: http://www.haskell.org/cabal/

2 2

Dtd2Haskell question
by Peter Simons 31 Oct '04

31 Oct '04

I'd like to add one more question / feature request into the mix. I have a DTD which defines two elements with (almost) identical attributes: <!ENTITY % priorities "( veryhigh | high | medium | low | verylow )" > <!ELEMENT link EMPTY> <!ATTLIST link priority %priorities; #REQUIRED ... > <!ELEMENT note (#PCDATA | comment)* > <!ATTLIST note priority %priorities; #REQUIRED ... > Dtd2Haskell generates these data types: data Link = Link { linkPriority :: Link_priority , .... } data Link_priority = Link_priority_veryhigh | Link_priority_high | ... data Note_Attrs = Note_Attrs { notePriority :: Note_priority , ... } data Note_priority = Note_priority_veryhigh | Note_priority_high | ... It's no big deal, but IMHO it should be possible that Dtd2Haskell recognizes that the entity refers to the _same_ attribute type. Peter

1 0

AAMAS 2005 Conference: Final Call for Papers, Tutorial and Workshop Proposals
by Matthias Klusch 29 Oct '04

29 Oct '04

+++ Apologies for multiple copies due to cross posting to multiple relevant mailing lists +++ FINAL CALL for Papers, Workshop and Tutorial Proposals, and Special Industry Track Papers ****************************************************** 4th International Joint Conference AAMAS on Autonomous Agents and Multiagent Systems July 25 - 29, 2005 Utrecht University, The Netherlands ****************************************************** http://www.aamas2005.nl Important dates =============== Conference papers Electronic abstracts due: DECEMBER 6, 2004 Full electronic paper due: DECEMBER 10, 2004 Workshop and Tutorial proposals due: DECEMBER 20, 2004 Industry track contributions due: FEBRUARY 28, 2005 Please note that the conference will be BLIND reviewed! Authors should carefully read the respective online instructions before submitting. Online submission of papers possible at http://www.aamas2005.nl/paper_submissions'.php from NOVEMBER 8, 2004. More details are provided in the following. ----------------------------------------------------- CALL FOR CONFERENCE PAPERS ----------------------------------------------------- About the conference ==================== Agents are one of the most prominent and attractive technologies in computer science at the beginning of the new milennium. The technologies, methods, and theories of agents and multiagent systems are currently contributing to many diverse domains such as information retrieval, user interfaces, electronic commerce, robotics, computer mediated collaboration, computer games, education and training, ubiquitous computing, and social simulation. They not only are a very promising technology, but are also emerging as a new way of thinking, a conceptual paradigm for analyzing problems and for designing systems, for dealing with complexity, distribution, and interactivity, while providing a new perspective on computing and intelligence. The AAMAS conference series was initiated in 2002 as a merger of three highly successful related events: AGENTS (International Conference on Autonomous Agents), ICMAS (International Conference on Multi-Agent Systems), and ATAL (International Workshop on Agent Theories, Architectures, and Languages). The aim of the joint conference is to provide a single, high-profile, internationally renowned forum for research in the theory and practice of autonomous agents and multiagent systems. In particular, it brings together the world's researchers active in this important, vibrant, and rapidly growing field. AAMAS 2005 events include workshops and tutorials given by distinguished experts in the field, as well as an agent school, and doctoral mentoring program. Please check http://www.aamas2005.nl for latest information on the conference. Topics of interest ================== Topics of interest to AAMAS-05 include, but are not restricted to: * agents & complex systems; computational ecosystems * agent architectures; perception, action & planning in agents * agents & cognitive models * agents & networks: web agents, semantic web, grid, web services, P2P * agent communication: languages, semantics, pragmatics & protocols * agent-mediated electronic commerce & trading agents * agent-oriented software engineering & agent-oriented methodologies * agent programming languages, development environments & testbeds * applications of autonomous agents & multi-agent systems * artificial social systems; conventions, norms, social laws & institutions * autonomous robots & robot teams * coalition formation & teamwork; cooperative distributed problem solving * computational complexity in autonomous agents & multi-agent systems * cooperation & coordination; multi-agent planning * cooperative information systems, middle agents & brokers * distributed & multi-agent constraint satisfaction * game theoretic/economic foundations; algorithmic mechanism design * logics & formal models of agency; verification * multi-agent evolution, adaptation & learning * mobile agents * multi-agent simulation & modeling * negotiation, auctions, social choice mechanisms & argumentation * ontologies for agent systems * privacy & security issues in multi-agent systems * scalability & performance issues, robustness & dependability * synthetic agents; human-like, lifelike & believable qualities * theories of agency & autonomy * trust in agent systems; adjustable autonomy Submission of Conference Papers =============================== AAMAS-05 encourages the submission of theoretical, experimental, methodological, and applications papers. Theory papers should make clear the significance and relevance of their results to the AAMAS community. Similarly, applied papers should make clear both their scientific and technical contributions, and are expected to demonstrate a thorough evaluation of their strengths and weaknesses in practice. Papers that address isolated agent capabilities (for example, planning or learning) are discouraged unless they are placed in the overall context of autonomous agent architectures or multi-agent system organization and performance. A thorough evaluation is considered an essential component of any submission. Authors are also requested to make clear the implications of any theoretical and empirical results, as well as how their work relates to the state of the art in autonomous agents and multi-agent systems research as evidenced in, for example, previous AAMAS conferences. All submissions will be rigorously peer reviewed and evaluated on the basis of the quality of their technical contribution, originality, soundness, significance, presentation, understanding of the state of the art, and overall quality. In addition to conventional conference papers, AAMAS-05 also welcomes the submission of papers that focus on implemented systems, software, or robot prototypes. These papers require a demonstration of the prototype at the conference and should include a detailed project or system description specifying the hardware and software features and requirements. Please note that the conference will be BLIND reviewed! Please carefully check http://www.aamas2005.nl/paper_submissions.htm for submission details. The online submission web site http://www.aamas2005.nl/paper_submissions'.php can be used from November 8, 2004. ----------------------------------------------------- CALL FOR TUTORIAL PROPOSALS ----------------------------------------------------- INTRODUCTION ************ The AAMAS-2005 Organising Committee invites proposals for the Tutorial Program, to be held immediately before to the technical conference (July, 25-26). Tutorials should serve one or more of the following objectives: * Introduce novices to major topics of AAMAS research. * Provide instruction in established practices and methodologies. * Survey a mature area of AAMAS research and/or practice. * Motivate and explain an AAMAS topic of emerging importance. * Introduce expert non-specialists to an AAMAS subarea. * Survey an area of agent research especially relevant for people from industry REQUIREMENTS FOR SUBMISSIONS **************************** Proposals should be from two to four pages in length, and should contain the following information: * A brief description of the tutorial, suitable for inclusion in the conference registration brochure. * A detailed outline of the tutorial, including preferred length (1/2 or 1 day). * Characterization of the potential target audience for the tutorial, including prerequisite knowledge. * A description of why the tutorial topic would be of interest to a substantial part of the AAMAS audience. * A brief resume of the presenter(s), which should include name, postal address, phone and fax numbers, e-mail address, background in the tutorial area, any available example of work in the area (ideally, a published tutorial-level article on the subject), evidence of teaching experience (including references that address the proposer's presentation ability), and evidence of scholarship in the area. * The name and E-mail address of the corresponding presenter. The corresponding presenter should be available for E-mail correspondence during the evaluation process, in the case clarifications and discussions on the scope and content of the proposal are needed. The evaluation of the proposal will take into account its general interest for AAMAS attendees (e.g., a tutorial on object-oriented inheritance will be hardly accepted), the quality of the proposal (e.g., a tutorial that simply lists a set of concepts without any apparent rationale behind them will be judged badly) as well as the expertise and efficacy of the presenters. We emphasize that the primary criteria for evaluation will be whether a proposal is interesting, well-structured, and motivated, rather than the perceived experience/standing of the proposer. Those submitting a proposal should keep in mind that tutorials are intended to provide an overview of the field; they should present reasonably well established information in a balanced way. Tutorials should not be used to advocate a single avenue of research, nor should they promote a product. All proposals should be submitted by electronic mail to the Tutorial Chair, Onn Shehory (onn(a)il.ibm.com) in plain ASCII text, no later than ** December 20, 2004 **. The committee's decision will be notified no later than ** January 10, 2005**. The selection of the tutorials to be included in the final AAMAS program will be based upon a number of factors, including: the scientific/technical interest of the topics, the quality of the proposal, the need to avoid strictly overlapping tutorials, and the unavoidable need to limit the overall number of selected tutorials. RESPONSIBILITIES OF AAMAS AND OF TUTORIAL ORGANIZERS **************************************************** For all accepted proposals, AAMAS will be responsible for: * Providing logistic support and a meeting place for the tutorial. * Together with the organizers, determining the tutorial date and time. * Duplicating tutorial material and distributing them to the participants. Tutorial organizers will be responsible for the following: * Providing AAMAS with a legible PDF copy of their tutorial notes in due time. * Presenting the tutorial at AAMAS-05 AAMAS reserves the right to cancel any tutorial if the above responsibilities are not fulfilled, if deadlines are missed or if too few attendees register for the tutorial to support the costs of running the tutorial. IMPORTANT DATES *************** December 20, 2004 Proposal Submission Deadline January 10, 2005 Acceptance Notification April 10, 2005 Deadline for submitting tutorial materials July 25 - 26, 2005 AAMAS-05 Tutorials Proposals and inquiries should be sent by email (in ASCII) to the tutorials chair: Onn Shehory onn(a)il.ibm.com ----------------------------------------------------- CALL FOR WORKSHOP PROPOSALS ----------------------------------------------------- INTRODUCTION ************ The AAMAS-2005 Organising Committee invites proposals for the Workshop Program, to be held immediately before the technical conference (July, 25-26). The main goal of the AAMAS-2005 workshops is to stimulate and facilitate an active exchange, interaction and comparison of approaches, methods, and ideas about specific (both theoretical and applicative) topics on the Agents and Multi-Agent Systems domain. Workshops should be organized so that an informal and participated discussion among attendees is guaranteed. Members from all areas of the AAMAS community are invited to submit workshop proposals for review. Workshops on new emerging topics or specific relevant aspects of consolidated ones are particularly encouraged. Workshops can vary in length, but most will last a full day. Workshop organizers and attendees must register for their workshop and possibly for the main AAMAS conference. REQUIREMENTS FOR SUBMISSIONS **************************** Proposals for workshops should be from two to four pages in length, and should contain the following information: * A brief technical description of the workshop, specifying the workshop goals and the technical issues that will be its focus. * A brief discussion of why and to whom the workshop is of interest. * A list of related workshops held within the last two years, if any, and their relation to the proposed workshop. * If applicable, detailed information about previous editions of the same workshop (e.g., number of submissions, number of attendees). * A preliminary call for participation/papers. * The names, postal addresses, phone numbers, and email addresses of the proposed workshop organizing committee. This committee should consist of three or four people knowledgeable about the technical issues to be addressed. These people cannot all work at the same institution. * The name of the primary contact for the organizing committee; an email address of this person should be given. * A description of the qualifications of the individual committee members with respect to organizing scientific events, including a list of workshops previously arranged by any members of the proposed organizing committee, if any. All proposals should be submitted by electronic mail to the Workshop Chair, Rino Falcone (r.falcone(a)istc.cnr.it) in plain ASCII text, no later than ** December 20, 2004 **. The committee's decision will be notified no later than ** January 10, 2005**. The selection of the workshops to be included in the final AAMAS program will be based upon a number of factors, including: the scientific/technical interest of the topics, the quality of the proposal, the need to avoid strictly overlapping workshops, and the unavoidable need to limit the overall number of selected workshops. RESPONSIBILITIES OF AAMAS AND OF WORKSHOP ORGANIZERS **************************************************** For all accepted proposals, AAMAS will be responsible for: * Providing logistic support and a meeting place for the workshop. * Together with the organizers, determining the workshop date and time. * Duplicating working notes and distributing them to the participants. Workshop organizers will be responsible for the following: * Setting up a Web site for the workshop according to the template that will be distributed upon acceptance. * Advertising the workshop and issuing a call for participation/papers. * Collecting submissions, notifying acceptances in due time, and ensuring a transparent and fair selection process. All workshop organizers commit themselves to adopt the same deadlines for submissions and notifications of acceptance, i.e., - March 14, 2005 submission of contributions to workshops - April 18 2005, notifications * Making the PDF of the whole workshop notes available to the workshop chair in due time (approx. 7 weeks before the conference). * Ensuring that the workshop organizers and the participants get registered to the workshop and are invited to register to the main conference. AAMAS reserves the right to cancel any workshop if the above responsibilities are not fulfilled or if too few attendees register for the workshop. AAMAS encourages the production of publications based on the workshop, and leave this upon the workshop organizers. IMPORTANT DATES for Workshops ***************************** December 20, 2004 Proposal Submission Deadline January 10, 2005 Acceptance Notification March 14, 2005 Deadline for submitting of contributions to workshops April 18, 2005 Acceptance Notifications of contributions to workshops July 25 - 26, 2005 AAMAS-05 Workshops Please send proposals (in ASCII) and inquiries via email to: Rino Falcone r.falcone(a)istc.cnr.it ----------------------------------------------------- Call for INDUSTRY TRACK PAPERS ----------------------------------------------------- INTRODUCTION ************ The AAMAS-05 conference will, for the first time, feature a track specifically intended for industrial participants: the AAMAS Industry Track. The industry track is being organised in cooperation with AgentLink, Europe's IST-funded coordination activity for autonomous agents and multi-agent systems (see http://www.agentlink.org/) WHAT IS THE INDUSTRY TRACK? *************************** The AAMAS industry track is a special track at the AAMAS conference that will run in parallel to the regular AAMAS scientific track. It will feature presentations and demonstrations from industrial participants, giving them an opportunity to showcase the state of the art in technology and industrial application of autonomous agents and multi-agent systems to AAMAS delegates and to publish associated papers in a high quality, formal proceedings. The industry track aims to foster mutually beneficial links between those engaged in foundational scientific research and those working to make autonomous agents and multi-agent systems a commercial reality. This enables industrially-based software agent developers and practitioners to participate in AAMAS in a meaningful way and to present their technology and applications to both their peers and the associated scientific community. HOW WILL THE TRACK BE REFEREED? ******************************* Whereas in the regular conference track the overriding refereeing criterion is clearly scientific excellence, the industry track focuses primarily on the industrial relevance and technological significance of the contribution. Preference will be given to mature work demonstrating concrete industrial/commercial results and business value. Examples of an "ideal" paper might include: (i) a presentation of a particular kind of commercially available software agent technology, together with experience of how this was applied in a field-tested system; or (ii) a report on a field-tested agent-based system. We explicitly discourage the submission of purely speculative papers, proposals, and plans for future work/potential applications. Academic participation in the industry track is acceptable, but please note that we strongly discourage the submission of: (i) papers that merely appeal to potential applications, without demonstrating that they have been meaningfully applied; (ii) academic papers that work with highly abstracted versions of potential applications; or (iii) academic papers that describe software agent systems/platforms without either a real industrial link or genuine application. In general, if you believe that your paper makes a scientific contribution, you should think about submitting to the regular scientific track; whereas, if your paper is an overview of an agent technology, a "practical experience" paper, or similar, then you should probably submit to the industry track. HOW CAN I PARTICIPATE? ********************** The industry track invites developers, practitioners, and industrial researchers to submit high quality papers on agent technology and its applications. See the conference web site for paper formatting and submission instructions. Accepted contributions will be formally published in the "Proceedings of the Industry Track of AAMAS-05" and will be distributed at the conference along with the AAMAS-05 main conference proceedings. Selected publications will be encouraged to present their applications in the AgentLink newsletter. The contributions will influence the AgentLink Roadmap to be published in 2005. Note that the Industry Track is part of the AAMAS conference - there is no separate registration for the Industry Track. IMPORTANT DATES *************** Deadline for Submission of Contributions - 28 February 2005 Notification of acceptance - 28 March 2005 CO-CHAIRS Michal Pechoucek -- Czech Technical University, AgentLink Donald Steiner -- Quantum Leap Innovations Simon Thompson -- British Telecom Programme Committee: David Allsopp -- Qinetic Fabio Bellifemine -- Telecom Italia Laboratories Jeff Bradshaw -- IHMC Sven Brueckner -- Altarum Monique Calisti -- Whitestein Technologies Jonathan Dale -- Futjitsu Ian Dickenson -- HP Mark Greaves -- DARPA Jon Himoff -- CEO Magenta Martin Hofmann -- Lockheed Martin David Kinny -- Agentis James Lawton -- AFRL Vladimir Marik -- Rockwell Research Center David Martin -- SRI Peter McBurney -- AgentLink Jim Odell -- Agentis Christ Priest -- HP Chris Reed -- Calico Jack, Dundee University Ralph Ronnquist -- AOS Australia Jeff Rosenschein -- Hebrew Uni David Sadek -- France Telecom Onn Shehory -- IBM Israel John Shepherdson -- BT Petr Skobelev -- CTO Magenta Niranjan Suri -- IHMC Simon Thompson -- British Telecom CONTACT for the industry track: Michal Pechoucek pechouc(a)labe.felk.cvut.cz ----------------------------------------------------- =========================================================== AAMAS 2005 Joint Conference Organizing Committee =========================================================== General co-chairs Sarit Kraus, Bar-Ilan University / University of Maryland Munindar Singh, North Carolina State University Program co-chairs Sven Koenig, University of Southern California Michael Wooldridge, University of Liverpool Local organization chair Frank Dignum, Utrecht University Local treasurer Virginia Dignum, Utrecht University Finance chair Sandip Sen, University of Tulsa Workshops chair Rino Falcone, ISTC - CNR Tutorials chair Onn Shehory, IBM Israel Demos co-chairs Omer Rana, Cardiff University Thomas Rist, FH Augsburg Doctoral mentoring chair Jürgen Dix, TU Clausthal Publicity chair Matthias Klusch, DFKI Sponsorship co-chairs Monique Calisti (Europe) Zakaria Maamar (Middle East) Kamal Karlapalem (South Asia) Jiming Liu (East Asia) Ana Lúcia Bazzan (Latin America) William Walsh (US & Canada) Publications chair Bin Yu, Carnegie Mellon University Student scholarship chair Barbara Keplicz, Warsaw University Exhibits chair Marie-Pierre Gleizes, IRIT, University Paul Sabatier =========================================================== AAMAS 2005 GENERAL CONTACT Sarit Kraus sarit(a)macs.biu.ac.il Munindar Singh singh(a)ncsu.edu =========================================================== __________________________________________________ Dr. Matthias Klusch German Research Center for Artificial Intelligence Stuhlsatzenhausweg 3 66123 Saarbruecken, Germany Phone: +49-681-302-5297, Fax: +49-681-302-2235 http://www.dfki.de/~klusch/, klusch(a)dfki.de __________________________________________________

1 0