@inproceedings {2018:wesoacs,
	title = {May Contain Nuts: The Case for API Labels},
	year = {2018},
	month = {September},
	address = {Como, Italy},
	abstract = {As APIs proliferate, managing the constantly growing and evolving API landscapes inside and across organizations becomes a challenge. Part of the management challenge is for APIs to be able to describe themselves, so that users and tooling can use descriptions for finding and filtering APIs. A standardized labeling scheme can help to cover some of the cases where API self-description allows API landscapes to become more usable and scalable. In this paper we present the vision for standardized API labels, which summarize and represent critical aspects of APIs. These aspect allow consumers to more easily become aware of the kind of dependency they are going to establish with the service provider when choosing to use them. API labels not only summarize critical coupling factors, but also can include claims that require to be validated by trusted third parties.},
	keywords = {API, API Labels},
	author = {Cesare Pautasso and Erik Wilde}
}
@book {rest:2014,
	title = {REST: Advanced Research Topics and Practical Applications},
	year = {2014},
	pages = {1-214},
	publisher = {Springer},
	organization = {Springer},
	keywords = {REST},
	isbn = {978-1-4614-9298-6},
	url = {http://ws-rest.org/book/2/},
	editor = {Cesare Pautasso and Erik Wilde and Rosa Alarc{\'o}n}
}
@proceedings {wsrest2012,
	title = {Third International Workshop on RESTful Design (WS-REST 2012)},
	year = {2012},
	month = {March},
	publisher = {ACM},
	address = {Lyon, France},
	keywords = {proceedings, REST},
	isbn = {978-1-4503-1190-8},
	doi = {10.1145/2307819.2307821},
	url = {http://dl.acm.org/citation.cfm?id=2307819},
	editor = {Rosa Alarc{\'o}n and Cesare Pautasso and Erik Wilde}
}
@inbook {DBLP:books/sp/wilde2011/PautassoW11,
	title = {Introduction to REST: From Research to Practice},
	booktitle = {REST: From Research to Practice},
	year = {2011},
	pages = {1-18},
	publisher = {Springer},
	organization = {Springer},
	chapter = {1},
	keywords = {REST},
	doi = {10.1007/978-1-4419-8303-9_0},
	url = {http://ws-rest.org/book/},
	author = {Cesare Pautasso and Erik Wilde}
}
@conference {rest:bpm:icsoc2011,
	title = {Push-Enabling RESTful Business Processes},
	booktitle = {9th International Conference on Service-Oriented Computing (ICSOC 2011)},
	volume = {7084},
	year = {2011},
	month = {December},
	pages = {32-46},
	publisher = {Springer},
	organization = {Springer},
	address = {Paphos, Cyprus},
	abstract = {Representational State Transfer (REST) as an architectural style for service design has seen substantial uptake in the past years. However, some areas such as Business Process Modeling (BPM) and push services so far have not been addressed in the context of REST principles. In this work, we look at how both BPM and push can be combined so that business processes can be modeled and observed in a RESTful way. Based on this approach, clients can subscribe to be notified when certain states in a business process are reached. Our goal is to design an architecture that brings REST{\textquoteright}s claims of loose coupling and good scalability to the area of BPM, and still allow process-driven composition and interaction between resources to be modeled.},
	keywords = {business process management, REST, RESTful business process management},
	doi = {10.1007/978-3-642-25535-9_3},
	author = {Cesare Pautasso and Erik Wilde}
}
@book {rest:2011,
	title = {REST: From Research to Practice},
	year = {2011},
	publisher = {Springer},
	organization = {Springer},
	address = {New York, NY},
	keywords = {REST},
	isbn = {978-1-4419-8302-2},
	doi = {10.1007/978-1-4419-8303-9},
	url = {http://ws-rest.org/book/},
	editor = {Erik Wilde and Cesare Pautasso}
}
@conference {www:wsrest2011,
	title = {Second international workshop on RESTful design (WS-REST 2011)},
	booktitle = {WWW (Companion Volume)},
	year = {2011},
	month = {March},
	pages = {311-312},
	publisher = {ACM},
	organization = {ACM},
	address = {Hyderabad, India},
	keywords = {proceedings, REST},
	isbn = {978-1-4503-0637-9},
	doi = {http://doi.acm.org/10.1145/1963192.1963327},
	author = {Cesare Pautasso and Erik Wilde and Rosa Alarc{\'o}n}
}
@proceedings {wsrest2010,
	title = {First International Workshop on RESTful Design (WS-REST 2010)},
	year = {2010},
	month = {April},
	publisher = {ACM},
	address = {Raleigh, NC, USA},
	doi = {http://doi.acm.org/10.1145/1798354.1798375},
	url = {http://portal.acm.org/beta/citation.cfm?id=1798354},
	editor = {Cesare Pautasso and Erik Wilde and Alexandros Marinos}
}
@conference {restws:2009:www,
	title = {Why is the Web Loosely Coupled?  A Multi-Faceted Metric for Service Design},
	booktitle = {18th World Wide Web Conference (WWW2009)},
	year = {2009},
	month = {April},
	pages = {911-920},
	publisher = {ACM},
	organization = {ACM},
	address = {Madrid, Spain},
	abstract = {Loose coupling is often quoted as a desirable property of systems architectures. One of the main goals of building systems using Web technologies is to achieve loose coupling. However, given the lack of a widely accepted definition of this term, it becomes hard to use coupling as a criterion to evaluate alternative Web technology choices, as all options may exhibit, and claim to provide, some kind of "loose" coupling effects. This paper presents a systematic study of the degree of coupling found in service-oriented systems based on a multi-faceted approach. Thanks to the metric introduced in this paper, coupling is no longer a one-dimensional concept with loose coupling found somewhere in between tight coupling and no coupling. The paper shows how the metric can be applied to real-world examples in order to support and improve the design process of service-oriented systems.},
	keywords = {coupling, REST, RESTful Web service interface},
	doi = {10.1145/1526709.1526832},
	author = {Cesare Pautasso and Erik Wilde}
}
