[Prev][Next][Index][Thread]

IEEE/ACM MEMOCODE conference



Hi,

This preliminary announcement may be of interest to type theory people
as well, because some of the recent works in System Level Design brings
out a lot of type theory issues. 

Regards

Sandeep


FIRST ANNOUNCEMENT AND PRELIMINARY CALL FOR PAPERS

			   MEMOCODE 2003
                                 
First ACM-IEEE International Conference on Methods and Models for
Codesign
         
	 Programming models, formal analysis methods and
	 verification  techniques  for high-level system
	 design:  towards  convergence of formal methods
	 and industrial trends.

	 June 24th-26th, 2003 - Mont Saint-Michel, France

		      ______________________
         
CO-SPONSORS      ACM Special Interest Group on Digital Automation
		 IEEE Circuits and System Society
		 IEEE Computer Society, Digital Automation TC

		 in cooperation with INRIA and IRISA

OPENING SPEAKER  Jose Meseguer (SRI)

INVITED SPEAKERS Ahmed Jerraya (IMAG)
		 Nancy Lynch (MIT)
		 Ken McMillan (Cadence)

GENERAL CHAIR	 Rajesh Gupta (University of California at San Diego)
		      ______________________

CALL FOR PAPERS. Prospective authors are invited to submit original and
unpublished papers describing innovative techniques and results
addressing one or several of the following topics:

    1. From general-purpose languages to formal semantic models
    2. Analysis and verification of system-level models
    3. System-level design methodologies
    4. Formal methods for various aspects of system -evel design
    5. Distribution, fault-tolerance, scheduling, non-functional
       requirements (portability, availability, maintainability, etc).

SPECIAL ATTRACTION - PROBLEM SOLVING SESSIONS. Following extensive
discussions, the technical program committee has identified the
following specific problem areas where the need for innovation and
community contribution is important:
 
    1. Levels of abstraction, notion of conformance and equivalence
    2. Hierarchical verification
    3. Should the space of implementation possibilities be determined
       by the abilities of high-level synthesis and validation ?
    4. Functional coverage, test generation, and incremental
verification
    5. Post-fabrication verification, update and patch

More details on the problem background and discussions can be found on
the conference website at http://www.irisa.fr/MEMOCODE.  We especially
seek contributions addressing these problem areas while contributions
within the larger scope of the conference charter are welcome. Papers
submitted to problem solving sessions and general sessions will be
reviewed in the same manner, and papers submitted to one session may be
moved to another session if deemed appropriate by the committee.

Conference proceedings will be published by ACM or IEEE Press. Selected
papers from the conference will be published as a special volume by
Kluwer Academic Publishers on a later date.



______________________________________________
Dr. Sandeep K. Shukla
Assistant Professor
Electrical and Computer Engineering
Virginia Tech
Blacksburg, VA 24061
email:shukla@vt.edu
URL:http://filebox.vt.edu/users/shukla
______________________________________________

-----Original Message-----
From: Benjamin C. Pierce [mailto:bcpierce@saul.cis.upenn.edu] 
Sent: Saturday, May 25, 2002 9:36 AM
To: types@cis.upenn.edu
Subject: TYPES submission guidelines (FYI)

[----- The Types Forum, http://www.cis.upenn.edu/~bcpierce/types -----]

Dear TYPES readers,

Over the past few years, the Types list has grown substantially: there
are now over 1200 subscribers.  At the same time, the world seems to
have
gotten very much busier, and everyone seems to want to announce their
event on all the mailing lists as they can find the names of.

In order to keep the signal-to-noise ratio as high as possible -- and
the
absolute volume of messages tolerable -- in the face of this deluge,
I've
gradually increased the strictness of the submission guidelines for
Types, to the point where I now reject or query over 80% of the
submissions I receive.  For example, I don't distribute second (or
third!) announcements of events unless there are changes in important
particulars such as deadlines.  I do distribute some announcements of
events in 'adjacent' areas, but only if their authors are willing to
take
the trouble to write a short prolog explaining why a significant numbers
of Types readers might be interested.  Etc.

Since these new guidelines represent a significant change from what some
people may expect (especially old-timers, who started reading Types in
its early glory days under the leadership of Albert Meyer or Philip
Wadler), it seems worth circulating them.  If you're interested, read
on...

Regards,

        Benjamin Pierce
        (TYPES moderator)

                         ----------------------

   TYPES is a moderated e-mail forum focusing on Type Theory in Computer
   Science, with a broad view of the subject encompassing semantical,
   categorical, operational, and proof theoretical topics, as well as
   algorithmic issues and applications. Typical topics include:
   
     Typed, untyped, or polymorphic lambda calculus; type checking,
     inference, and reconstruction; subtyping, dependent types, calculus
     of constructions, the lambda cube; linear logic, the Curry-Howard
     correspondence; recursive types; adequate and fully abstract
     models; domain theory; category theory; term reduction,
     normalization, confluence; abstract data types; type systems for
     object-oriented, concurrent, distributed, and mobile programming.
     
   Comments and criticisms of results in the literature, open problems,
   and research queries are encouraged. Announcements of relevant
   meetings, publications, and abstracts of papers are also welcome.
   
   Announcements of a general nature should not be sent to the Types
   Forum. The usual criterion for deciding relevance is that the
   announcement should mention one or more subjects in the list above.
If
   an announcement does not obviously meet this criterion but would
still
   be of interest to many Types readers, it may be prefaced with a brief
   note explaining its relevance.
   
   Normally, only one announcement of a given event will be accepted for
   distribution. Exceptions will be made for second announcements where
   there have been important changes in information such as submission
   dates, provided these changes are mentioned prominently at the top of
   the message.
   
   Submission instructions:
     * Send submissions to types@cis.upenn.edu. Submissions must
       literally include the address types@cis.upenn.edu in their To: or
       Cc: headers. Mailing to a blind To: or Cc: list that happens to
       include types@cis.upenn.edu may result in your message being
       silently ignored.
     * Submissions should be in plain ASCII format -- please, no
embedded
       HTML, document attachments, or MIME-encodings.
     * Please include an informative subject line with your message. To
       announce a paper, the subject line should state the subject of
the
       paper rather than just `New paper.' To announce a conference,
       please put the conference's name in the subject line, rather than
       just 'Call for papers.'
     * Please don't begin your message with an apology for sending it to
       multiple lists -- this is just a further waste of readers'
       attention. (Many announcements these days are cross-posted, for
       reasons that people generally accept as valid. But if you truly
       feel bad about it, a better solution might be not to post to so
       many lists!)