@inproceedings{ lan13,
  crossref = {wsrest2013},
  author = {Markus Lanthaler and Christian Gütl},
  title = {Model Your Application Domain, Not Your JSON Structures},
  pages = {1415-1420},
  abstract = {Creating truly RESTful Web APIs is still more an art than a science. Developers have to struggle with a number of complex design decisions because concrete guidelines and processes are missing. Consequently, often it is decided to implement the simplest solution which is, most of the time, to rely on out-of-band contracts between the client and the server. Instead of properly modeling the application domain, all the effort is put in the design of proprietary JSON structures and URLs. This then forms the base for the contract which is communicated in natural-language (with all its ambiguity) to client developers. Since it is the server who owns the contract it may be changed at any point, which, more often than not, results in broken clients. In this position paper, we discuss some of the challenges and choices that need to be made when designing RESTful Web APIs. In particular, we compare how contracts are supposed to be established and how they are defined in practice. We illustrate the problems that are the cause of these divergences. As a first step to address these issues we describe and motivate an alternative, domain-driven approach to design Web APIs.}
}

{"_id":{"_str":"53ff72c27c90ec6e13001354"},"__v":0,"authorIDs":[],"author_short":["Lanthaler, M.","Gütl, C."],"bibbaseid":"lanthaler-gtl-modelyourapplicationdomainnotyourjsonstructures","bibdata":{"downloads":0,"role":"author","bibbaseid":"lanthaler-gtl-modelyourapplicationdomainnotyourjsonstructures","type":"inproceedings","title":"Model Your Application Domain, Not Your JSON Structures","pages":"1415-1420","key":"lan13","id":"lan13","crossref":"wsrest2013","bibtype":"inproceedings","bibtex":"@inproceedings{ lan13,\n crossref = {wsrest2013},\n author = {Markus Lanthaler and Christian Gütl},\n title = {Model Your Application Domain, Not Your JSON Structures},\n pages = {1415-1420},\n abstract = {Creating truly RESTful Web APIs is still more an art than a science. Developers have to struggle with a number of complex design decisions because concrete guidelines and processes are missing. Consequently, often it is decided to implement the simplest solution which is, most of the time, to rely on out-of-band contracts between the client and the server. Instead of properly modeling the application domain, all the effort is put in the design of proprietary JSON structures and URLs. This then forms the base for the contract which is communicated in natural-language (with all its ambiguity) to client developers. Since it is the server who owns the contract it may be changed at any point, which, more often than not, results in broken clients. In this position paper, we discuss some of the challenges and choices that need to be made when designing RESTful Web APIs. In particular, we compare how contracts are supposed to be established and how they are defined in practice. We illustrate the problems that are the cause of these divergences. As a first step to address these issues we describe and motivate an alternative, domain-driven approach to design Web APIs.}\n}","author_short":["Lanthaler, M.","Gütl, C."],"author":["Lanthaler, Markus","Gütl, Christian"],"abstract":"Creating truly RESTful Web APIs is still more an art than a science. Developers have to struggle with a number of complex design decisions because concrete guidelines and processes are missing. Consequently, often it is decided to implement the simplest solution which is, most of the time, to rely on out-of-band contracts between the client and the server. Instead of properly modeling the application domain, all the effort is put in the design of proprietary JSON structures and URLs. This then forms the base for the contract which is communicated in natural-language (with all its ambiguity) to client developers. Since it is the server who owns the contract it may be changed at any point, which, more often than not, results in broken clients. In this position paper, we discuss some of the challenges and choices that need to be made when designing RESTful Web APIs. In particular, we compare how contracts are supposed to be established and how they are defined in practice. We illustrate the problems that are the cause of these divergences. As a first step to address these issues we describe and motivate an alternative, domain-driven approach to design Web APIs."},"bibtype":"inproceedings","biburl":"http://dret.net/biblio/dret.bib","creationDate":"2014-08-28T18:19:46.574Z","downloads":0,"keywords":[],"search_terms":["model","application","domain","json","structures","lanthaler","gütl"],"title":"Model Your Application Domain, Not Your JSON Structures","year":null,"dataSources":["mL7NKvaepNEWFcMvG"]}