• An abstract of five-hundred (500) or less words is due by December 19, 2008, before midnight before submitting the paper. The abstract must include:
  1. A tentative title
  2. Authors, and their affiliation
  3. Author for correspondence
  4. Keywords that best describe the contents of the paper, given the focus of the conference
  5. A description of the problem, the proposed approach, and the contributions and results.
     
• The full length paper, by January 9 January 19, 2009, before midnight (Apia time). The paper must contain six thousand words or less and be fiften pages long or less, including reasonably sized (i.e. legible) figures and pictures, according to the Springer LNBIP formatting rules and templates (PDF file created with LaTeX most preferably, or with Word otherwise).
  
• Each paper will be reviewed by at least three program committee members, and will be evaluated based on:
  1. appropriateness to the conference’s general theme
  2. originality
  3. technical soundness of the underlying methodology
  4. quality of results
  5. quality of the presentation
     

Prospective authors for the industrial track are requested to submit, on-line (see submission site at http://www.mcetech.org/myreview/):

• An abstract of five-hundred (500) or less words is due by by December 19, 2008, before midnight before submitting the paper. The abstract must include:
  1. A tentative title
  2. Authors, and their affiliation
  3. Author for correspondence
  4. Keywords that best describe the contents of the paper. Make sure to include the industry, and the problem area (e.g., "automative industry, e-procurement").
  5. A description of the problem, challenges you faced when applying existing approaches, or of the benefits you realized (or losses you incurred) when adopting such approaches
• The full length paper, by January 9 January 19, 2009 , before midnight (Apia time). The paper must contain five thousand words or less and be twelve pages long or less, including reasonably sized (i.e. legible) figures and pictures, according to the Springer LNBIP formatting rules and templates (PDF file created with LaTeX most preferably, or with Word otherwise).
• Papers in the industrial track will also be reviewed by at least three members of the program committee, one or more of whom will be from industry. Papers will be evaluated based on:
  1. appropriateness to the conference’s general theme
  2. relevance of the business or technical problem to the realities of the day
  3. technical soundness of the underlying methodology
  4. quality of the presentation

• A workshop proposal should contain:
  1. A title
  2. A list of organizers (names and affiliation), with a brief description of each organizer's background that would qualify them favorably to organize and moderate discussions on the chosen theme.Relevant past experiences with workshops are a plus
  3. A description of the theme of the workshop:
     1. The problem that you are trying to solve
     2. A description of the solution framework for the problem area (e.g. "model checking for BPEL specifications")
     3. A justification for the relevance or importance of the technical or business problem, or of the solution framework
     4. A description of the desired format of the workshop: number of participants, types of planned activities before and during the workshop, and the expected output
     5. A description of the participant solicitation and selection process. Workshop proposals will be evaluated by the workshops program committee.
• Acceptance will be based on an assessment of:
  1. the relevance and timeliness of either the problem or the solution framework,
  2. the likelihood of the workshop theme to generate enough interest while producing useful results,
  3. the perceived ability of the organizers to lead a successful workshop in the chosen theme
• The program committee may suggest to submitters of distinct proposals to merge their proposals.

• A tutorial proposal should contain:
  1. A title and duration (half a day or a full day)
  2. A description of the theme of the tutorial, and of the skills that attendees would acquire from it
  3. For each tutorial presenter, the name, affiliation, and a short biography that highlights the presenter’s qualifications (relevant publications or industrial experience) in the chosen topic of the tutorial
  4. A detailed description of the contents of the tutorials (a breakdown in segments, with a description of relevant publications, standards, tools, or experiences for each segment)
  5. A description of the required logistics
• Tutorial proposals will be evaluated by the tutorial program committee. Acceptance will be based on an assessment of:
  1. the relevance and timeliness of the topic,
  2. the likelihood of the tutorial theme to generate enough interest to fill-up a room
  3. the qualifications of the tutorial presenters in the proposed theme, and their perceived ability to render the subject matter clearly and synthetically.