Paper Submission Electronic submission is done through EDAS: here. Submissions should be unpublished, written in English, be no longer than 16 pages (including the illustrations and bibliography) and using the LNCS style. Acceptable file formats for initial electronic submission are PostScript and PDF. Authors should ensure that their paper is printable in other systems around the world, since printing problems may jeopardize the review process. The proceedings are to be published as a book in the LNCS series. Authors should prepare their papers according to the Springer LNCS Guideline. Accepted papers must be presented at the conference by one of the authors. Deadlines May 15, 2007 Deadline for submission of full papers. While preference will be given to full papers, short papers (particularly experience reports) will be considered. June 15, 2007 Notification of acceptance. June 30, 2007 Final papers for the proceedings.

Extended Call For Papers It has come to the attention of the Programme Committee for this event that the previous short title (SDL2007) gave the wrong impression that the event is concerned only with the ITU Specification and Description Language. In fact the invite was to submit papers on topics related to System Design Languages in general that are or could be used for real time systems, such as Telecommunications. This is a broader scope. Fortunately since issuing the original call for papers, the timescale for producing the proceedings for the event have become much clearer, and it is now possible to extend the call for papers. You are encouraged to read the revised call for papers with the scope 'System Design Languages' in mind and consider submitting any suitable papers by 15th May 2007. Authors need to be available between 16th June and 30th June for revision of their papers and submission of final versions. As the deadline has been extended, the many authors who have already submitted papers are allowed to revise their submissions up to 15th May 2007. While preference will be given to full papers, short papers (particularly experience reports) will be considered. Experience reports are inherently different from research papers, with respect the criteria of scientific merit, novelty, and research contribution. The main criteria is to share experience for the benefit of others. For example to provide citable evidence of the effectiveness (positive of negative) of particular approaches, or particular effective techniques or obstacles in practice when applying a language or set of languages. Anecdotal evidence is acceptable provided if well argued and the author explains efforts made to gather evidence. Material should contain comparisons and measurements of effectiveness wherever possible. A report that simply states that System Z was successfully developed using technique Y is a little use to others. A useful report would be something like: the technique Y was used (in this case on the real example System Z) and to be able to meet the requirements it was necessary to "..." otherwise "...", or "..." was particularly effective/ineffective because "...". Other do not want to know all the details of your project and its implementation, but what helped or hindered the engineering that might be relevant to their own projects, in particular unusual aspects of the project. It is suggested the title starts with the words `Experience Report'. The extended call for papers can be found here or downloaded as pdf file here.