ACM SIGCHI General Interest Announcements (Mailing List)


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Li Ruidong <[log in to unmask]>
Reply To:
Li Ruidong <[log in to unmask]>
Wed, 23 Nov 2022 22:34:32 +0900
text/plain (295 lines)
*** Please accept our apologies if you receive multiple copies of this CFP
24th ACM/IFIP International Conference Middleware 2023
11th – 15th December 2023 DAMSLab, Department of Arts University of
Bologna, Italy
Round: Fall/Winter deadline:

●       Full paper submissions due: *December 2nd, 2022*


The annual ACM/IFIP Middleware conference is a major forum for discussing
innovations and recent scientific advances in middleware systems with a
focus on the design, implementation, deployment, and evaluation of
distributed systems, platforms, and architectures for computing, storage,
and communication. The conference will include a high-quality single-track
technical program, invited speakers, an industrial track, panel discussions
involving academic and industry leaders, poster and demonstration
presentations, a doctoral symposium, tutorials, and workshops.
Topics of Interest

The Middleware conference seeks original submissions of research papers on
a diverse range of topics, particularly those identifying new research
directions. The topics of interest for the conference include, but are not
limited to:

●       Cloud and data centers

●       Virtualization, auto-scaling, provisioning, and scheduling

●       Data-intensive computing (big data) and data analytics

●       Stream processing

●       Middleware systems for machine learning

●       Mobile and pervasive systems and services

●       Middleware techniques for Internet-of-Things, smart cities

●       Fog, edge computing

●       Middleware for cyber-physical and real-time systems

●       Energy and power-aware techniques

●       Event-based, publish/subscribe, and peer-to-peer solutions

●       Networking, network function virtualization, software-defined

●       Middleware for multimedia systems

●       Fault tolerance and consistency

●       Blockchains

●       Middleware support for security and privacy

●       Monitoring, resource management, and analysis

●       Programming abstractions and paradigms for middleware

●       Reconfigurable, adaptable, and reflective middleware

●       Critical reviews of middleware paradigms, e.g., object models,
aspect orientation, etc.

●       Methodologies and tools for middleware systems design,
implementation, verification, and evaluation

●       Serverless, Function-as-a-Service computing

The conference seeks original papers of three types:

*Research Papers: *These papers report original research on the above
topics and will be evaluated on the significance of the problem, the
novelty of the solution, advancement beyond prior work, sufficient
supporting evidence, and clarity of the presentation.

*Experimentation and Deployment Papers: *These papers describe complete
systems, platforms, and/or comprehensive experimental evaluations of
alternative designs and solutions to well-known problems. The emphasis
during the review of these papers will be more on the demonstrated
usefulness and potential impact of the contributions, the extensive
experimentation involved, and the quality and weight of the lessons learned.

*Big Ideas Papers: *These are papers that have the potential to open up new
research directions. For such papers, the potential to motivate new
research is more important than full experimental evaluation, though some
preliminary evidence of the effectiveness of the approach or idea is
Important Dates, Deadlines, Conditions

Middleware 2023 will have two submission deadlines, and we are providing
the possibility of revision decisions for some papers that are deemed
promising but somehow not yet complete. A more detailed explanation of the
submission model is provided below.

First Round: Fall/Winter deadline:

●       Full paper submissions due: *December 2nd, 2022*

●       Rebuttal: *February 6th-10th, 2023*

●       Notification to authors (Accept/Accept with shepherding/Revise for
Spring deadline/ Reject): *February 24th, 2023*

●       Shepherded submissions due: *March 17th, 2023*

●       Notifications of decisions of shepherded papers (Accept/Reject): *March
31st, 2023*

●       Final paper files (camera-ready copy) due: *April 14th, 2023*
Second round: Spring/Summer deadline:

●       Full paper submissions due: *May 26th, 2023*

●       Rebuttal: *August 21-25th, 2023*

●       Notification to authors (Accept/Accept with Shepherding/Revise for
next calendar year/Reject): *September 8th, 2023*

●       Shepherded submissions due: *September 29th, 2023*

●       Notifications of decisions of shepherded papers
(Accept/Reject): *October
13th, 2023*

●       Final paper files (camera-ready copy) due: *27th October, 2023*

Key Changes and Conditions

*Once-per-year submission:* A research article may be submitted to ACM
Middleware only once a year. Submissions rejected in the 1st Round (Fall
Submission) of the ACM Middleware 2023 research track are *NOT ELIGIBLE* for
submission to the 2nd Round (Spring Submission) of ACM Middleware 2023.
Submissions rejected in the 2nd Round (Spring Submission) of ACM Middleware
2023 are *NOT ELIGIBLE* for submission to the 1st Round (Fall Submission)
of ACM Middleware 2024. The only exception to this once-per-year submission
is if the paper receives a *revision* decision, as described below.

*One-shot revision:* A paper submitted in a given round may receive a
revision decision. Such a paper may be revised, given the information in
the reviews, and resubmitted as part of the next review round. Such a
revision decision will include a summary of the paper’s merits and a list
of necessary changes required for the paper to be accepted at Middleware.
Authors may then submit a revised version of their work by addressing those
needs by the deadline for the next round. Upon resubmission, the paper will
be re-reviewed to judge whether it addresses the requirements requested;
this review will be conducted, to the extent possible, by the same
reviewers as the original review. Papers receiving a revision decision for
the 2nd Round of review (Spring Submission) will be invited to be
resubmitted to the 1st Round (Fall Submission) for the next edition of the

Only papers in the research and experimentation/deployment track will be
eligible for the one-shot revision decision. Big ideas papers are not
eligible for a revise/resubmit decision; they may be shepherded before

*Shepherding:* Any paper in any category may be accepted conditionally to
complete a shepherding process. These papers can be considered something of
a “minor revision”. Such a decision will also be accompanied by a list of
straightforward changes (expected to be reasonably addressed in a short
amount of time). At least one PC member will check these changes before
being accepted.

Submission Guidelines

Your submission must be made within the due date specified above for a
given round. Submitted papers must have at most 12 pages of technical
content, including text, figures, and appendices, but excluding any
additional pages for bibliographic references. Note that the review process
will be doubly anonymous – authors’ names must not appear on the
manuscript, and authors must make a good-faith attempt to anonymize their
submissions. Submitted papers must adhere to the formatting instructions of
the ACM SIGPLAN style, which can be found on the ACM template page
<>. The font size has
to be set to 10pt.

Please submit papers to
<> (Round 1) and
<> (Round

A paper submitted to ACM Middleware 2023 cannot be under review for any
other conference or journal during the entire time it is considered for
Middleware 2023, and it must be substantially different from any previously
published work. All accepted papers will appear in the proceedings. ACM
reserves the right to exclude a paper from distribution after the
conference (e.g., removal from ACM Digital Library) if none of the authors
attends the conference to present their paper.

The Middleware 2023 conference proceedings will be published in the ACM
Digital Library. The official publication date will be when the proceedings
are made available in the ACM Digital Library. Note that the official
publication date may affect the deadline for any patent filings related to
published work. A list of papers accepted from the 1st Round review process
(Fall submission) will be posted on the ACM Middleware 2023 website in May
2023. In October, when the full program is available, paper titles and
abstracts will be posted for all accepted papers from the spring and fall

*Note to Authors:* By submitting your article for distribution in this
Special Interest Group publication, you now grant to ACM the following
non-exclusive, perpetual, worldwide rights:

to publish in print on the condition of acceptance by the editor
to digitize and post your article in the electronic version of this
to include the article in the ACM Digital Library and any Digital
Library-related services
to allow users to make a personal copy of the article for non-commercial,
educational, or research purposes

However, as a contributing author, you retain the copyright to your article
and ACM will refer requests for republication directly to you.
Anonymity Requirements for Doubly-Anonymous Reviewing

Every research paper submitted to ACM Middleware 2023 will undergo a
''doubly-anonymous” reviewing process: in addition to maintaining the
anonymity of the reviewers of the papers, the PC members and reviewers will
not know the identity of the authors. To ensure the anonymity of
authorship, authors must at least do the following:

Authors' names and affiliations must not appear on the title page or
elsewhere in the paper.

Funding sources must not be acknowledged anywhere in the paper under
review; these can be added to accepted papers upon submission of the
camera-ready manuscript.

Non-anonymized links to the authors’ online content must be removed

Research group members, or other colleagues or collaborators, must not be
acknowledged anywhere in the paper.

The paper’s file name must not identify the authors of the paper.

Authors should also use care in referring to related past work. The
solution is to reference past work in the third person (in the same way
that one would reference work by anyone else). This allows you to set the
context for your submission while at the same time preserving anonymity.

Despite the anonymity requirements, authors should still include all
relevant work, including their own; omitting them could reveal the author’s
identity by negation. However, self-references should be limited to the
essential ones, and extended versions of the submitted paper (e.g.,
technical reports or URLs for downloadable versions) must not be
referenced. The goal is to preserve anonymity while allowing the reader to
grasp the context of the submitted paper fully. It is the responsibility of
authors to do their very best to preserve anonymity. Papers that do not
follow the guidelines or potentially reveal the author's identity are
subject to immediate rejection.
Software and Data Artifact Availability for Accepted Papers

The authors of accepted papers will be invited to submit supporting
materials made publicly available as “source materials” in the ACM Digital
Library. The materials will be vetted by the Artifact Availability
Evaluation process run by a separate committee. This submission is
voluntary but encouraged and will not influence the final decision
regarding the papers. Papers that go through the Artifact Availability
Evaluation process successfully and are made available in the ACM Digital
Library will receive a badge printed on the papers themselves.

The Middleware conference adheres strictly to the ACM policies against
discrimination and harassment

    To unsubscribe from CHI-ANNOUNCEMENTS send an email to:
     mailto:[log in to unmask]

    To manage your SIGCHI Mailing lists or read our polices see: