Hi all, (I have googled for information on the below, but come up empty)
I am looking for *the most authoritative written sources*, usable as references in a bachelor thesis on an idea/principle/data type that Rich Hickeys talks about e.g. in the talk *Maybe Not*: https://github.com/matthiasn/talk-transcripts/blob/master/Hickey_Rich/MaybeNot.md The idea is to represent data by maps while observing the following two principles: 1. *Keywords have type declarations for their values, not maps*: The types of the values of the keys are defined *per keyword*, no per map type *Advantage*: *This turns keywords into reusable components in their own right* 2. *Non-existence expressed by omisson of keyword.* Non-existence of a value in a key/value-pair must be expressed by omission of the whole key/value pair, not by `null` as a value. *Advantage*: This makes it possible to observe the informational status of a map by observing it's *shape,* (what key/value pairs are present), thus exposing the shape as something that can be reasoned about, type-checked and expressed in function signatures. This makes it possible to keep the conceptual meaning of the map orthogonal from it's *shape* or *completeness of information*, thus uncomplecting the aspects. The above description is my interpretation of what Rich says in the talk. I am thankful for correction, if I have misunderstood something! I (my project group) will be using these two principles when we design a specific domain model in our bachelor thesis/programming project, and the opposition will probably give us a hard time if our only source is a talk on YouTube ;-) 1) Is this data type described in a research paper? Or Maybe Rich have written a more precise description than given in "Maybe Not"? 2) Does it have an established name, that can be search for on the web? The combination of the two principles above seems very appropriate for modelling certain domains, so it certainly deserves a name, don't you think? Hickey Types anyone? Or Component/Shape Map Types? 3) Is Rich the first one to combine these two principles or are there prior art? 4) Is the second principle covered somewhere in the clojure/spec documentation. Thanks for any info on this! Regards/Henning Sato von Rosen (I study CS at CSE Chalmers University of Technology/Gothenburg University) -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
