-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
289 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,163 @@ | ||
--- | ||
title: "1st CfP: SLE 2025 - 18th ACM SIGPLAN International Conference on Software Language Engineering" | ||
timestamp: "10/10/2024 5:15:44" | ||
deadline: "2/7/2025" | ||
--- | ||
18th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2025) | ||
12-13 June 2025 | ||
Koblenz, Germany | ||
|
||
https://www.sleconf.org/2025/ | ||
https://x.com/sleconf | ||
------------------------------------------------------------------------ | ||
|
||
We are pleased to invite you to submit papers to the 18th ACM SIGPLAN International Conference on Software Language Engineering (SLE) which is devoted to the principles of software languages: their design, their implementation, and their evolution. The SLE 2025 conference will be co-located with STAF 2025 and hosted in Koblenz, Germany, on 12-13 June 2025. | ||
|
||
--------------------------- | ||
Important Dates | ||
--------------------------- | ||
|
||
* Abstract submission: Fri 7 Feb 2025 | ||
* Paper submission: Fri 14 Feb 2025 | ||
* Authors response period: Tue 1 Apr - Sat 5 Apr 2025 | ||
* Notification: Tue 15 Apr 2025 | ||
* Conference: Thu 12 June - Fri 13 June 2025 (co-located with STAF) | ||
|
||
All dates are Anywhere on Earth. | ||
|
||
--------------------------- | ||
Topics of Interest | ||
--------------------------- | ||
|
||
SLE covers software language engineering in general, rather than engineering a specific software language. Topics of interest include, but are not limited to: | ||
|
||
* Software Language Design and Implementation | ||
- Approaches to and methods for language design | ||
- Static semantics (e.g., design rules, well-formedness constraints) | ||
- Techniques for specifying behavioral/executable semantics | ||
- Generative approaches (incl. code synthesis, compilation) | ||
- Meta-languages, meta-tools, language workbenches | ||
- AI-assisted language design and optimisation | ||
* Software Language Validation | ||
- Verification and formal methods for languages | ||
- Testing techniques for languages | ||
- Simulation techniques for languages | ||
- Model-based testing | ||
- AI-assisted validation | ||
* Software Language Integration and Composition | ||
- Coordination of heterogeneous languages and tools | ||
- Mappings between languages (incl. transformation languages) | ||
- Traceability between languages | ||
- Deployment of languages to different platforms | ||
- AI-assisted refactoring | ||
* Software Language Maintenance | ||
- Software language reuse | ||
- Language evolution | ||
- Language families and variability, language and software product lines | ||
* Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) | ||
* Empirical evaluation and experience reports of language engineering tools | ||
- User studies evaluating usability | ||
- Performance benchmarks | ||
- Industrial applications | ||
* Synergies between Language Engineering and emerging/promising research areas | ||
- Generative AI in language engineering (e.g., AI-based language modelling, AI-driven code generation tools) | ||
- AI and ML language engineering (e.g., ML compiler testing, code classification) | ||
- Quantum language engineering (e.g., language design for quantum machines) | ||
- Language engineering for physical systems (e.g., CPS, IoT, digital twins) | ||
- Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) | ||
|
||
--------------------------- | ||
Types of Submissions | ||
--------------------------- | ||
|
||
SLE accepts the following types of papers: | ||
|
||
* Research papers: These are “traditional” papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. | ||
* New ideas/vision papers: These papers may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas/vision papers must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. | ||
* SLE Body of Knowledge: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools, and methods developed by the SLE community. In this respect, the SLE conference will accept surveys, essays, open challenges, empirical observations, and case study papers on the SLE topics. These can focus on, but are not limited to, methods, techniques, best practices, and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. | ||
* Tool papers: These papers focus on the tooling aspects often forgotten or neglected in research papers. A good tool paper focuses on practical insights that will likely be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. They may optionally include an appendix with a demo outline/screenshots and/or a short video/screencast illustrating the tool. | ||
|
||
Workshops: Workshops will be organised by STAF. Please inform us and contact STAF 2025 organisers if you would like to organise a workshop of interest to the SLE audience. Information on how to submit workshops can be found on the STAF 2025 Website. | ||
|
||
--------------------------- | ||
Submission | ||
--------------------------- | ||
|
||
SLE 2025 has a single submission round for papers, including a mandatory abstract registration and a rebuttal phase, where all authors of research papers will have the possibility of responding to the reviews on their submissions. | ||
|
||
Authors of accepted research papers will be invited to submit artefacts. | ||
|
||
--------------------------- | ||
Format | ||
--------------------------- | ||
|
||
Submissions have to use the ACM SIGPLAN Conference Format “acmart” (https://sigplan.org/Resources/Author/#acmart-format); please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template, and that the document class definition is `\documentclass[sigplan,anonymous,review]{acmart}`. Do not make any changes to this format! | ||
|
||
Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colours remain distinct and font sizes in figures and tables are legible. | ||
|
||
To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. Accordingly, SLE will follow the double-blind process. Author names and institutions must be omitted from submitted papers, and references to the authors’ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. | ||
|
||
All submissions must be in PDF format. The submission website is: https://sle25.hotcrp.com | ||
|
||
--------------------------- | ||
Concurrent Submissions | ||
--------------------------- | ||
|
||
Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLAN’s Republication Policy (https://www.sigplan.org/Resources/Policies/Republication/). Submitters should also be aware of ACM’s Policy and Procedures on Plagiarism (https://www.acm.org/publications/policies/plagiarism-overview). Submissions that violate these policies will be desk-rejected. | ||
|
||
--------------------------- | ||
Policy on Human Participant and Subject Research | ||
--------------------------- | ||
|
||
Authors conducting research involving human participants and subjects must ensure that their research complies with their local governing laws and regulations and the ACM’s general principles, as stated in the ACM’s Publications Policy on Research Involving Human Participants and Subjects (https://www.acm.org/publications/policies/research-involving-human-participants-and-subjects). If submissions are found to be violating this policy, they will be rejected. | ||
|
||
--------------------------- | ||
Reviewing Process | ||
--------------------------- | ||
|
||
All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning soundness, relevance, novelty, presentation, and replicability. New ideas/vision papers will be evaluated primarily concerning soundness, relevance, novelty, and presentation. SLEBoK papers will be reviewed on their soundness, relevance, originality, and presentation. Tool papers will be evaluated concerning relevance, presentation, and replicability. | ||
|
||
For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review at the discretion of the PC chairs. | ||
|
||
For research papers, authors will get a chance to respond to the reviews before a final decision is made. | ||
|
||
--------------------------- | ||
Artefact Evaluation | ||
--------------------------- | ||
|
||
SLE will use an evaluation process to assess the quality of artefacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artefacts. | ||
|
||
--------------------------- | ||
Awards | ||
--------------------------- | ||
|
||
* Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. | ||
* Distinguished artefact: Award for the artefact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artefact evaluation committee. | ||
* Distinguished reviewer: Award for the programme committee member that produced the most useful reviews as assessed by paper authors. | ||
* Most Influential Paper: Award for the SLE 2015 paper with the greatest impact, as judged by the SLE Steering Committee. | ||
|
||
--------------------------- | ||
Publication | ||
--------------------------- | ||
|
||
All accepted papers will be published in the ACM Digital Library. | ||
|
||
**AUTHORS TAKE NOTE**: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. | ||
|
||
--------------------------- | ||
Organisation | ||
--------------------------- | ||
|
||
* General chair: Görel Hedin, Lunds Universitet, Sweden | ||
* PC co-chair: Regina Hebig, Universität Rostock, Germany | ||
* PC co-chair: Vadim Zaytsev, Universiteit Twente, The Netherlands | ||
* Publicity chair: Andrei Chiş, feenk gmbh, Switzerland | ||
* Local chair: Ralf Lämmel, Universität Koblenz, Germany | ||
|
||
--------------------------- | ||
Contact | ||
--------------------------- | ||
|
||
For additional information, clarification, or answers to any questions, please get in touch with the program co-chairs ([email protected] and [email protected]). | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,109 @@ | ||
--- | ||
title: "Principles of Secure Compilation: 2nd Call for Papers" | ||
timestamp: "10/21/2024 9:36:43" | ||
deadline: "11/7/2024" | ||
--- | ||
PriSC is a fun, welcoming and exciting venue. Join our friendly gathering, | ||
share your ideas, and start new collaborations: submit now! | ||
|
||
Important Dates | ||
=============== | ||
|
||
* Thu 7 Nov 2024: Submission Deadline | ||
* Thu 5 Dec 2024: Acceptance Notification | ||
* Mon 20 Jan 2025: Workshop | ||
|
||
Submission website: https://prisc25.hotcrp.com | ||
Workshop website: https://popl25.sigplan.org/home/prisc-2025 | ||
|
||
================================================ | ||
Call for Presentations: PriSC @ POPL 2025 | ||
================================================ | ||
|
||
Secure compilation is an emerging field that puts together advances in security, | ||
programming languages, compilers, verification, systems, and hardware | ||
architectures in order to devise more secure compilation chains that eliminate | ||
many of today's security vulnerabilities and that allow sound reasoning about | ||
security properties in the source language. For a concrete example, all modern | ||
languages provide a notion of structured control flow and an invoked procedure | ||
is expected to return to the right place. However, today's compilation chains | ||
(compilers, linkers, loaders, runtime systems, hardware) cannot efficiently | ||
enforce this abstraction against linked low-level code, which can call and | ||
return to arbitrary instructions or smash the stack, blatantly violating the | ||
high-level abstraction. Other problems arise because today's languages fail to | ||
specify security policies, such as data confidentiality, and the compilation | ||
chains thus fail to enforce them, especially against powerful side-channel | ||
attacks. The emerging secure compilation community aims to address such problems | ||
by identifying precise security goals and attacker models, designing more secure | ||
languages, devising efficient enforcement and mitigation mechanisms, and | ||
developing effective verification techniques for secure compilation chains. | ||
|
||
9th Workshop on Principles of Secure Compilation (PriSC 2025) | ||
============================================================= | ||
|
||
The Workshop on Principles of Secure Compilation (PriSC) is an informal 1-day | ||
workshop without any proceedings. The goal of this workshop is to identify | ||
interesting research directions and open challenges and to bring together | ||
researchers interested in working on building secure compilation chains, on | ||
developing proof techniques and verification tools, and on designing software or | ||
hardware enforcement mechanisms for secure compilation. The 9th edition of PriSC | ||
will be held on January 20 in Denver, Colorado, United States together with | ||
the ACM SIGPLAN Symposium on Principles of Programming Languages (POPL), 2025. | ||
|
||
|
||
Presentation Proposals and Attending the Workshop | ||
================================================= | ||
|
||
Anyone interested in presenting at the workshop should submit an extended | ||
abstract (up to 2 pages, details below) covering past, ongoing, or future work. | ||
Any topic that could be of interest to secure compilation is in scope. Secure | ||
compilation should be interpreted very broadly to include any work in security, | ||
programming languages, architecture, systems or their combination that can be | ||
leveraged to preserve security properties of programs when they are compiled or | ||
to eliminate low-level vulnerabilities. Presentations that provide a useful | ||
outside view or challenge the community are also welcome. This includes | ||
presentations on new attack vectors such as microarchitectural side-channels, | ||
whose defenses could benefit from compiler techniques. | ||
|
||
Specific topics of interest include but are not limited to: | ||
* Attacker models for secure compiler chains. | ||
* Secure compiler properties: fully abstract compilation and similar properties, | ||
memory safety, control-flow integrity, preservation of safety, information | ||
flow and other (hyper-)properties against adversarial contexts, secure | ||
multi-language interoperability. | ||
* Secure interaction between different programming languages: foreign function | ||
interfaces, gradual types, securely combining different memory management | ||
strategies. | ||
* Enforcement mechanisms and low-level security primitives: static checking, | ||
program verification, typed assembly languages, reference monitoring, program | ||
rewriting, software-based isolation/hiding techniques (SFI, crypto-based, | ||
randomization-based, OS/hypervisor-based), security-oriented architectural | ||
features such as Intel's SGX, MPX and MPK, capability machines, side-channel | ||
defenses, object capabilities. | ||
* Experimental evaluation and applications of secure compilers. | ||
* Proof methods relevant to compilation: (bi)simulation, logical relations, game | ||
semantics, trace semantics, multi-language semantics, embedded interpreters. | ||
* Formal verification of secure compilation chains (protection mechanisms, | ||
compilers, linkers, loaders), machine-checked proofs, translation validation, | ||
property-based testing. | ||
|
||
Guidelines for Submitting Extended Abstracts | ||
============================================ | ||
|
||
Extended abstracts should be submitted in PDF format and not exceed 2 pages | ||
(references not included). They should be formatted in two-column layout, 10pt | ||
font, and be printable on A4 and US Letter sized paper. We recommend using the | ||
new acmart LaTeX style in sigplan mode. Submissions are not anonymous and should | ||
provide sufficient detail to be assessed by the program committee. Presentation | ||
at the workshop does not preclude publication elsewhere. | ||
|
||
Contact and More Information | ||
============================ | ||
|
||
You can find more information on the workshop website: | ||
https://popl25.sigplan.org/home/prisc-2025 | ||
|
||
Submission website: https://prisc25.hotcrp.com | ||
|
||
For questions please contact the workshop chairs, Marco Patrignani | ||
([email protected]) and Marco Vassena ([email protected]). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
--- | ||
title: "2025 ACM SIGMETRICS: Call for Tutorial Proposals" | ||
timestamp: "10/30/2024 1:58:51" | ||
--- | ||
Dear colleagues, | ||
|
||
We would like to remind you about the early Nov 15 deadline for submitting proposals for 2025 ACM SIGMETRICS tutorials in Long Island New York next June 9-13. Introductory tutorials (on key analytical tools, measurement methodologies, problem areas, etc.) as well as tutorials covering new and emerging topics that are of broad interest to students, academics, and practitioners are particularly encouraged. We are also open to receiving proposals on the topics that are adjacent to the traditional focus of the conference. | ||
|
||
See the formal call for proposals here: https://www.sigmetrics.org/sigmetrics2025/tutorials.html | ||
|
||
Sincerely, | ||
|
||
Céline Comte | ||
2025 SIGMETRICS Publicity co-chair | ||
|
||
On behalf of Ting He and Christina Lee Yu | ||
2025 SIGMETRICS Tutorial co-chairs |