Cesare Pautasso
USI Lugano, Switzerland
http://www.pautasso.info
[email protected]
@pautasso
Erik Wilde
CA Technologies, Zurich, Switzerland
http://dret.net/netdret/
@dret
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.
Platform for Privacy Preferences Project
(W3C 2002)
API Labels should be self-describing
API Labels should be certified
API Labels are not meant to completely specify APIs and replace existing languages and service discovery tools
Instead, they include complementary information currently not found in API descriptions as written by service providers, because this information may include claims that need to be verified by trusted third parties.
(See the paper for details)
Made with
http://asq.inf.usi.chUse a spacebar or arrow keys to navigate