2014 IEEE International Conference on Services Computing 2014
DOI: 10.1109/scc.2014.58
|View full text |Cite
|
Sign up to set email alerts
|

API Terms and Conditions as a Service

Abstract: Service Oriented Architecture (SOA) has evolved from business-to-business interactions, into the new API model that enables open partnerships and interoperability with just about anyone. In SOA, terms of service (ToS) and service level agreements (SLAs) were agreed upon on one-to-one basis, as the Web service interfaces were defined. In contrast, API ecosystems appeal for self-serve and instant gratification, being able to access, try and buy an API with a single click. As business teams and citizen developers… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2014
2014
2024
2024

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 11 publications
(4 citation statements)
references
References 7 publications
0
4
0
Order By: Relevance
“…For one such domain, the presented work can be very useful in business negotiation scenarios like contracts management or using software where multiple parties are involved and can have different vantage points (mental models) for discussion. There has been some work on analyzing contracts for identifying gaps (Desai et al, 2008) and terms of conditions for software services (Vukovic et al, 2014) but they do not consider parties' mental models. Finally, we aim to further enhance and refine the CPF such that it can be used to capture and reason about more complex domains than the presented blocks world, such as described in Barker-Plummer et al (2017); Johnson et al (2016) and how agents may interact with them.…”
Section: Discussionmentioning
confidence: 99%
“…For one such domain, the presented work can be very useful in business negotiation scenarios like contracts management or using software where multiple parties are involved and can have different vantage points (mental models) for discussion. There has been some work on analyzing contracts for identifying gaps (Desai et al, 2008) and terms of conditions for software services (Vukovic et al, 2014) but they do not consider parties' mental models. Finally, we aim to further enhance and refine the CPF such that it can be used to capture and reason about more complex domains than the presented blocks world, such as described in Barker-Plummer et al (2017); Johnson et al (2016) and how agents may interact with them.…”
Section: Discussionmentioning
confidence: 99%
“…It stores temporal information about when entities and relationships were created and possibly deleted, allowing insights into the evolution of API ecosystems. On the other hand, in [22] they present a data model for API terms of service that captures a set of non-functional properties of APIs and allows for terms and conditions to be automatically assessed and composed. Later, in [23] they define a formal representation of service license description that facilitates automated license generation and composition.…”
Section: Related Workmentioning
confidence: 99%
“…We identify that there is a gap of the refinement from the strategic business planning to ubiquitous services 18 implementation especially in the API (Application Program Interface) 31 economy trend.…”
Section: Introductionmentioning
confidence: 99%