On Wed, May 2, 2012 at 12:27 PM, Stuart Sierra <the.stuart.sie...@gmail.com> wrote: > The data *is* the API. Design the data structures you're going to accept & > return at all the public entry-points of your library or application. That's > your API design. > > It's kind of like web APIs returning JSON or XML: the structure of the data > you get back is part of the contract.
hmm. entities can be represented in different ways, even with different views of them, e.g. in REST, no? and with HATEOAS exposing the actions in a context-sensitive way. and you need to define what the REST HTTP action verbs mean for them. otherwise you just have something more CRUDy than RESTy? (not that one can never desire CRUD.) so design it seems would have to take into consideration both data and behaviour, they are inter-twined, at least. of course one might wish to pick one or the other as the starting off point for thinking about the design. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
