Model your application domain, not your JSON structures

@inproceedings{Lanthaler2013ModelYA,
  title={Model your application domain, not your JSON structures},
  author={Markus Lanthaler and C. G{\"u}tl},
  booktitle={WWW '13 Companion},
  year={2013}
}
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… Expand
14 Citations
Third Generation Web APIs - Bridging the Gap between REST and Linked Data
  • 6
A Framework for Semantic Description of RESTful Web APIs
  • 6
A community-based, Graph API framework to integrate and orchestrate cloud-based services
  • 6
Experiments with automated evaluation of domain usability
The design of manual domain usability evaluation techniques
Experimental Design of Metrics for Domain Usability
  • 1
  • PDF
...
1
2
...

References

SHOWING 1-5 OF 5 REFERENCES
Hydra Core Vocabulary Specification
  • 2013 (work in progress). [Online]. Available: http://www.markuslanthaler.com/hydra/. [Accessed: 22-Feb-2013].
  • 2013
Representing vCard Objects in RDF
  • W3C Member Submission, 2010. [Online]. Available: http://www.w3.org/Submission/vcardrdf/. [Accessed: 24-Feb-2013].
  • 2010
Linked Data Platform 1.0
  • W3C Working Draft, 2012. [Online]. Available: http://www.w3.org/TR/2012/WD-ldp-20121025/.
  • 2012
Linked Data Platform 1.0 W3C Working Draft
  • Linked Data Platform 1.0 W3C Working Draft
  • 2012
Namespaces in XML 1.0 (Third Edition)
  • W3C Recommendation, 2009. [Online]. Available: http://www.w3.org/TR/xml-names/.
  • 2009