<div dir="ltr"><br><div><h2 style="color:rgb(0,0,0);font-variant-ligatures:normal;font-variant-east-asian:normal;border:0px;font-family:Georgia,'Times New Roman',serif;font-size:20px;margin:40px 0px 10px;outline:0px;padding:0px;vertical-align:baseline;clear:both;line-height:28px;text-align:center"><font color="#ff0000">RV-CuBES</font></h2><h3 style="font-variant-ligatures:normal;font-variant-east-asian:normal;color:rgb(96,96,96);border:0px;font-family:Georgia,'Times New Roman',serif;font-size:16px;font-weight:inherit;margin:40px 0px 10px;outline:0px;padding:0px;vertical-align:baseline;clear:both;line-height:18px;text-align:center">An International Workshop on Competitions, Usability, Benchmarks, Evaluation, and Standardisation for Runtime Verification Tools</h3><h4 style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;font-weight:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline;clear:both;text-align:center">Held in conjunction with the 17th International Conference on Runtime Verification (RV 2017)</h4><div style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;font-size:12.800000190734863px"><br></div><div style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;font-size:12.800000190734863px;text-align:center"><font size="2" face="HelveticaNeue"><a href="http://rv2017.cs.manchester.ac.uk/rv-cubes/" target="_blank">http://rv2017.cs.manchester.<wbr>ac.uk/rv-cubes/</a></font></div><div style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"> <br class="gmail-m_7236614978038733762webkit-block-placeholder"></div><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">The goal of this workshop is to provide a venue to discuss ongoing efforts to improve how we evaluate and compare tools for runtime verification. This workshop invites submissions that contribute to this discussion (see below). The workshop replaces the Runtime Verification Competition this year, giving an opportunity for reflection and planning for the future.</span></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><strong style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">HIGHLIGHTS</strong></p><ul style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 20px 3em;outline:0px;padding:0px;vertical-align:baseline;list-style-position:initial"><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">We invite two kinds of submissions: tool overview papers of <strong style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">existing</strong> tools and position papers</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Attendance at the workshop <strong style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">is not compulsory</strong> for submission, but encouraged</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">The workshop will be integrated into RV 2017 to engage with the wider RV community</span></li></ul><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><strong style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">BACKGROUND</strong></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Over the last three years, beginning in 2014, the Competition on Runtime Verification (CRV) has compared 14 different runtime verification tools using over 100 different benchmarks. It has motivated the development of new tools and extensions of existing ones. Thanks to the time and effort of the various organisers and participants it has successfully provided a platform to discuss how we evaluate and compare our tools. However, we are aware that the competition has not served all members of the community and required significant effort from its participants and therefore we have decided not to run the competition in the same form in 2017.</span></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">This workshop has two aims.</span></p><ul style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 20px 3em;outline:0px;padding:0px;vertical-align:baseline;list-style-position:initial"><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Firstly, to kickstart an online repository of tool descriptions that focus on usability, rather than implementation. Much effort within Runtime Verification is spent developing tools. The planned repository will help advertise these tools within and beyond the community and to document their existence. To this end, this workshop invites tool overview papers (details below) that present an opportunity to demonstrate the diverse range of available RV tools and to advertise their advanced features and capabilities. </span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Secondly, to provide a forum in which the future of the competition, and wider efforts to improve how we evaluate RV tools, can be discussed in a structured and informed way. There have been various informal discussions at the previous three RV conferences and in other settings. By inviting position papers (details below) this workshop aims to establish the issues and possible directions before holding a structured panel session during RV 2017.</span></li></ul><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><strong style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">RELATION TO RV 2017</strong></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">There is no overlap in scope between this workshop and RV 2017. Any papers containing original technical developments should be submitted to RV 2017 rather than this workshop as the workshop focuses on tool reviews (containing existing work) and position statements. If there is any uncertainty please contact the workshop chairs.</span></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">The workshop will be integrated into RV 2017. The workshop activities will include a poster presentation session and a panel decision, both of which will be scheduled within the main conference program. A consequence of this is that there will be no separate registration for the workshop. To attend the workshop activities it will be necessary to attend RV 2017. Although, attendance is not a requirement for submission.</span></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><strong style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">SUBMISSIONS</strong></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">We invite two forms of submission: Tool Overview papers and Position papers. All submissions will be subject to a lightweight review by the PC to ensure a reasonable standard and to provide constructive feedback to improve the quality of the submission.</span></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><em style="border:0px;font-family:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Tool Overview Papers</em></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">These should describe an existing tool using a minimum of 5 pages. The paper should at least describe how to obtain the tool, the RV problem the tool is aiming to solve, the key defining features of the tool and relevant references. Additionally, we might expect it to include some of the following:</span></p><ul style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 20px 3em;outline:0px;padding:0px;vertical-align:baseline;list-style-position:initial"><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">The history of the tool</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">High-level overviews of key aspect such as the input language or architecture from a user’s perspective</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Usability details undocumented elsewhere</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Examples demonstrating key features</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Details of case studies or applications to real world problems</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Discussion of features particular to the tool</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Summaries (rather than detailed tables) of experimental results</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Analysis of the kinds of problem the tool is suited for and those it is less-well suited for</span></li></ul><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Ideally, the tool and related material (e.g. benchmarks) will be available online and linked to in the submission. The paper should not cover any significant new contributions (these can be submitted as tool papers to RV 2017) and should rely on previous research and tool papers to provide further details. Note that there is no upper page limit however the number of pages used should reflect the level of detail given. Submissions of 2 pages giving minimal details would be suitable in a situation where the tool is well documented elsewhere but an entry in the repository is still desired. All accepted submissions will be invited for presentation at a special Poster session during RV 2017.</span></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><em style="border:0px;font-family:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Position papers</em></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Initial submissions should use a minimum of 2 pages to explore a particular position related to the evaluation, comparison or standardisation of Runtime Verification tools (and benchmarks). Topics may include, but are not limited to:</span></p><ul style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 20px 3em;outline:0px;padding:0px;vertical-align:baseline;list-style-position:initial"><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">What should a RV benchmark look like?</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Can we have a common specification language for RV? If so, what should it look like?</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Is execution time the most important performance criteria? What might be more important?</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">How can we evaluate hardware monitoring tools?</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">What are we doing wrong in evaluation? Can we fix this?</span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">What can be borrowed form other communities?</span></li></ul><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">A selection of position papers will be used to structure a discussion panel to be held at RV 2017. Again, there is no upper page limit however the number of pages used should reflect the level of detail given. There will be an opportunity to update the paper based on discussions before inclusion in post-proceedings (see below).</span></p><p style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><em style="border:0px;font-family:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Publishing and Submission</em></p><p style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline">Contributions will be published as a post-proceedings volume in the Open-Access Scopus-Indexed EasyChair <a href="http://www.easychair.org/publications/Kalpa" target="_blank" style="color:rgb(17,123,184);border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Kalpa </a>Series. To be eligible for inclusion in the post-proceedings, papers should be at least 5 pages. Please see the relevant <a href="http://www.easychair.org/publications/for_authors" target="_blank" style="color:rgb(17,123,184);border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">information for authors</a> when preparing your paper.</p><p style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline">Please submit contributions to the following EasyChair page.</p><p style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline;text-align:center"><a href="https://easychair.org/conferences/?conf=rvcubes2017" target="_blank">https://easychair.org/<wbr>conferences/?conf=rvcubes2017</a></p><p id="gmail-m_7236614978038733762dates" class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><strong style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">DATES</strong></p><ul style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 20px 3em;outline:0px;padding:0px;vertical-align:baseline;list-style-position:initial"><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline;color:rgb(255,0,0)"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline"> Submission Deadline <span style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline;text-decoration:line-through"><span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">1 July 2017</span></span></span></span></span><ul style="border:0px;font-family:inherit;font-style:inherit;margin:0px 0px 20px 1.5em;outline:0px;padding:0px;vertical-align:baseline;list-style:disc"><li style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline;color:rgb(255,0,0)">Abstracts: <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">8 July 2017</span></span></span></li><li style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline;color:rgb(255,0,0)">Final Submission: <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">15 July 2017</span></span></span></li></ul></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Notification <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">1 August 2017</span></span></span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Workshop at RV 2017 <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">13-16 September 2017</span></span><br></span></li><li class="gmail-m_7236614978038733762p1" style="margin:0px;border:0px;font-family:inherit;font-style:inherit;outline:0px;padding:0px;vertical-align:baseline">Post-proceedings deadline <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">14 October 2017</span></span></li></ul><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><strong style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">ORGANISATION</strong></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">For local and general organisation please see RV 2017.</span></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><em style="border:0px;font-family:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Program Committee Chairs</em></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Giles Reger, University of Manchester, UK<br></span><span class="gmail-m_7236614978038733762s1" style="border:0px;font-family:inherit;font-style:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Klaus Havelund, NASA Jet Propulsion Laboratory, USA</span></p><p class="gmail-m_7236614978038733762p1" style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline"><em style="border:0px;font-family:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline">Program Committee</em></p><p style="font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;color:rgb(64,64,64);border:0px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;margin:0px 0px 1.5em;outline:0px;padding:0px;vertical-align:baseline">Ezio Bartocci, TU Wien, Austria<br>Domenico Bianculli, SnT Centre – University of Luxembourg, Luxembourg<br>Borzoo Bonakdarpour, McMaster University, Cananda<br>Christian Colombo, University of Malta, Malta<br>Ylies Falcone, Univ. Grenoble Alpes, Inria, Laboratoire d’Informatique de Grenoble, France<br>Adrian Francalanza, University of Malta, Malta<br>Sylvain Hallé, Université du Québec à Chicoutimi, Canada<br>Felix Klaedtke, NEC Europe Ltd.<br>Daniel Thoma, University of Lübeck, Germany<br>Dmitriy Traytel, ETH Zürich, Switzerland<br>Gordon Pace, University of Malta, Malta<br>Cesar Sanchez, IMDEA Software Institute, Spain<br>Leonardo Mariani, University of Milano Bicocca, Italy<br>Julien Signoles, CEA LIST, France<br>Tarmo Uustalu, Tallin University of Technology, Estonia</p></div></div>