<commit_before>---
title: "program"
bg: '#abd1bb'
color: black
fa-icon: list-alt

---

## Session 1: Opening &amp; Keynote

Session Chairs
: <NAME> and <NAME>

---

9:00 - 9:15
: Workshop Opening &amp; Introductions

9:15 - 10:30
: *"The Changing Landscape of Refactoring Research in the Last Decade"*
<!-- : *"[Human-centered Methods for Improving API Usability](http://www.cs.cmu.edu/~NatProg/papers/Myers-WAPI-keynote%20submitted.pdf)"* -->
: Workshop Keynote by [<NAME> (Oregon State University)](http://eecs.oregonstate.edu/people/dig-danny)
: **Abstract:** In the last decade refactoring research has seen exponential growth. I will attempt to map this vast landscape and the advances that the community has made by answering questions such as who does what, when, where, why, and how. I will muse on some of the factors contributing to the growth of the field, the adoption of research into industry, and the lessons that we learned along this journey. This will inspire and equip you so that you can make a difference, with people who make a difference, at a time when it makes a difference.
<!-- : See [the slides](http://www.cs.cmu.edu/~NatProg/papers/Myers%20WAPI%202017%20talk.pdf) -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-keynote/). -->

{:.gap} 10:30 - 11
: Coffee Break

## Session 2: API Evolution

Session Chair
: TBA

---

11:00 - 11:20
: [*"Non-Atomic Refactoring and Software Sustainability"*](http://abseil.io/resources/wapi18-winters.pdf)
: by _<NAME>_ (Google)
<!-- : See [the slides](resources/wapi17_hammouda_api_fittness.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-api-fittness/). -->

11:20 - 11:40
: *"On Software Modernisation due to Library Obsolescence"*
:  by <NAME>, <NAME>, <NAME>, <NAME>, and <NAME> (University of York, Delft University of Technology)
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-api-in-descriptions/). -->

11:40 - 12:00
: [*"Exploring API/Client Co-Evolution"*](http://www.ii.uib.no/~anya/papers/eilertsen-bagge-api-coevo-wapi18.pdf)
: by _<NAME>_, <NAME> (University of Bergen)
<!-- : See [the slides](resources/wapi17_wittern_web_api_consumption.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-web-api-consumption/). -->

12:00 - 12:20
: *"Discovering API Usability Problems at Scale"*
: by <NAME>, _<NAME>_, <NAME>, <NAME>, <NAME>, <NAME>, and <NAME> (North Carolina State University, Google, University of California Berkeley)
<!-- : See [the slides](resources/wapi17_wittern_web_api_consumption.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-web-api-consumption/). -->
<!-- : Discussion of presented topics &amp; listing of open questions/topics for Session 4 -->

12:20 - 12:30
: Discussion of presented topics

{:.gap} 12:30 - 2:00
: Lunch Break

## Session 3: API Learning &amp; Analysis

Session Chair
: TBA

---

2:00 - 2:45
: *"Web APIs - Challenges, Design Points, and Research Opportunities"*
: Invited talk by [<NAME> (IBM T.J Watson Research Center)](https://researcher.watson.ibm.com/researcher/view.php?person=us-witternj)
: **Abstract:** Web APIs provide programmatic, network-based access to remote data or functionalities. Applications, for example, use the Google Places API to learn about nearby establishments, use the Twitter, Instagram, or Facebook API to connect users with friends and family, or use the Stripe API to accept end-user payments. Increasingly, applications themselves consist of micro-services that expose their capabilities to one another using web APIs.
: In comparison to library APIs, which are a common subject of software engineering research, web APIs present unique challenges - both for providers and consumers - that are arguably much less explored yet. In this talk, we outline the characteristics of web APIs causing these challenges. We discuss relevant design points, both for providers and consumers, and how these design points have been implemented by different web API paradigms in recent years. Throughout the talk, we give examples of our research to address web API-related challenges. Our goal is to inspire WAPI attendees to take on some of the many research opportunities surrounding web APIs.
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi-api-evolution-and-migration-at-google/). -->

2:45 - 3:05
: [*"Where Does Google Find API Documentation?"*](https://cs.adelaide.edu.au/~christoph/wapi18.pdf)
: by <NAME>, _Maur&iacute;<NAME>_ (The University of Adelaide, Delft University of Technology)
<!-- : See [the slides](resources/wapi17_sawant_usage_trends.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-motivated-trends/). -->

3:05 - 3:25
: *"Extending Existing Inference Tools to Mine Dynamic APIs"*
: by <NAME>, <NAME> (University of Oregon)
<!-- : See [the slides](resources/wapi17_kechagia_type_checking.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-type-checking/). -->

3:25 - 03:30
: Discussion of presented topics

{:.gap} 3:30 - 4:00
: Coffee Break

## Session 4: Open Discussion
---

4:00 - 5:30 Structure of open discussion TBA. Our goal is to ensure concrete outcomes from this workshop.
<commit_msg>Add session chairs.<commit_after>---
title: "program"
bg: '#abd1bb'
color: black
fa-icon: list-alt

---

## Session 1: Opening &amp; Keynote

Session Chairs
: <NAME> and <NAME>

---

9:00 - 9:15
: Workshop Opening &amp; Introductions

9:15 - 10:30
: *"The Changing Landscape of Refactoring Research in the Last Decade"*
<!-- : *"[Human-centered Methods for Improving API Usability](http://www.cs.cmu.edu/~NatProg/papers/Myers-WAPI-keynote%20submitted.pdf)"* -->
: Workshop Keynote by [<NAME> (Oregon State University)](http://eecs.oregonstate.edu/people/dig-danny)
: **Abstract:** In the last decade refactoring research has seen exponential growth. I will attempt to map this vast landscape and the advances that the community has made by answering questions such as who does what, when, where, why, and how. I will muse on some of the factors contributing to the growth of the field, the adoption of research into industry, and the lessons that we learned along this journey. This will inspire and equip you so that you can make a difference, with people who make a difference, at a time when it makes a difference.
<!-- : See [the slides](http://www.cs.cmu.edu/~NatProg/papers/Myers%20WAPI%202017%20talk.pdf) -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-keynote/). -->

{:.gap} 10:30 - 11
: Coffee Break

## Session 2: API Evolution

Session Chair
: [<NAME>]

---

11:00 - 11:20
: [*"Non-Atomic Refactoring and Software Sustainability"*](http://abseil.io/resources/wapi18-winters.pdf)
: by _<NAME>_ (Google)
<!-- : See [the slides](resources/wapi17_hammouda_api_fittness.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-api-fittness/). -->

11:20 - 11:40
: *"On Software Modernisation due to Library Obsolescence"*
:  by <NAME>, <NAME>, <NAME>, <NAME>, and <NAME> (University of York, Delft University of Technology)
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-api-in-descriptions/). -->

11:40 - 12:00
: [*"Exploring API/Client Co-Evolution"*](http://www.ii.uib.no/~anya/papers/eilertsen-bagge-api-coevo-wapi18.pdf)
: by _<NAME>_, <NAME> (University of Bergen)
<!-- : See [the slides](resources/wapi17_wittern_web_api_consumption.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-web-api-consumption/). -->

12:00 - 12:20
: *"Discovering API Usability Problems at Scale"*
: by <NAME>, _<NAME>_, <NAME>, <NAME>, <NAME>, <NAME>, and <NAME> (North Carolina State University, Google, University of California Berkeley)
<!-- : See [the slides](resources/wapi17_wittern_web_api_consumption.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-web-api-consumption/). -->
<!-- : Discussion of presented topics &amp; listing of open questions/topics for Session 4 -->

12:20 - 12:30
: Discussion of presented topics

{:.gap} 12:30 - 2:00
: Lunch Break

## Session 3: API Learning &amp; Analysis

Session Chair
: [Jürgen Cito]

---

2:00 - 2:45
: *"Web APIs - Challenges, Design Points, and Research Opportunities"*
: Invited talk by [<NAME> (IBM T.J Watson Research Center)](https://researcher.watson.ibm.com/researcher/view.php?person=us-witternj)
: **Abstract:** Web APIs provide programmatic, network-based access to remote data or functionalities. Applications, for example, use the Google Places API to learn about nearby establishments, use the Twitter, Instagram, or Facebook API to connect users with friends and family, or use the Stripe API to accept end-user payments. Increasingly, applications themselves consist of micro-services that expose their capabilities to one another using web APIs.
: In comparison to library APIs, which are a common subject of software engineering research, web APIs present unique challenges - both for providers and consumers - that are arguably much less explored yet. In this talk, we outline the characteristics of web APIs causing these challenges. We discuss relevant design points, both for providers and consumers, and how these design points have been implemented by different web API paradigms in recent years. Throughout the talk, we give examples of our research to address web API-related challenges. Our goal is to inspire WAPI attendees to take on some of the many research opportunities surrounding web APIs.
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi-api-evolution-and-migration-at-google/). -->

2:45 - 3:05
: [*"Where Does Google Find API Documentation?"*](https://cs.adelaide.edu.au/~christoph/wapi18.pdf)
: by <NAME>, _Maur&iacute;<NAME>_ (The University of Adelaide, Delft University of Technology)
<!-- : See [the slides](resources/wapi17_sawant_usage_trends.pdf). -->
<!-- : Read [Sven Amann's summary of the talk](http://academicscode.com/posts/2017/05/wapi17-motivated-trends/). -->

3:05 - 3:25
: *"Extending Existing Inference Tools to Mine Dynamic APIs"*
: by <NAME>, <NAME> (University of Oregon)
<!-- : See [the slides](resources/wapi17_kechagia_type_checking.pdf). -->
<!-- : Read [<NAME>'s summary of the talk](http://academicscode.com/posts/2017/05/wapi17-type-checking/). -->

3:25 - 03:30
: Discussion of presented topics

{:.gap} 3:30 - 4:00
: Coffee Break

## Session 4: Open Discussion
---

4:00 - 5:30 Structure of open discussion TBA. Our goal is to ensure concrete outcomes from this workshop.

[<NAME>]: https://www.ifi.uzh.ch/en/seal/people/proksch.html
[<NAME>]: http://people.csail.mit.edu/jcito

{'fraction_non_alphanumeric': 0.13530636256674813, 'fraction_numerical': 0.03602135939904064, 'mean_word_length': 4.351089588377724, 'pattern_counts': {'":': 0, '<': 85, '<?xml version=': 0, '>': 85, 'https://': 5, 'lorem ipsum': 0, 'www.': 7, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '214454', 'n_tokens_mistral': 3825, 'n_tokens_neox': 3377, 'n_words': 1182}