This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-15
Channels
- # aleph (9)
- # announcements (6)
- # beginners (42)
- # calva (4)
- # cider (9)
- # clara (2)
- # clj-kondo (1)
- # cljdoc (108)
- # cljs-dev (10)
- # clojure (25)
- # clojure-brasil (1)
- # clojure-chicago (1)
- # clojure-europe (4)
- # clojure-italy (42)
- # clojure-nl (14)
- # clojure-uk (66)
- # clojurebridge (3)
- # clojurescript (23)
- # clojutre (2)
- # community-development (1)
- # cursive (2)
- # datomic (4)
- # figwheel-main (21)
- # fulcro (23)
- # jobs-discuss (1)
- # kaocha (1)
- # off-topic (10)
- # pedestal (4)
- # reitit (2)
- # shadow-cljs (41)
- # spacemacs (7)
- # sql (20)
- # xtdb (3)
I have a terminology question, maybe someone here can help? We are developing a learning system in clojure and use EDN Documents to describe several components (Exercises, Content, Quizzes, Learning Units). So for every component we a have rules, that the base structure is a map {}, it should have an attribute :id, and so on.. (it gets complex, these are simple rules) I am not a native speaker so my question is, what is the correct English term for the entirety of these rules? Notation, Specification, Schema, File Format?
Are you using clojure.spec to specify these rules/constraints?
I think that, as you said, "schema" might be the right term. Many applications define json/xml schemas and there are validators for json/xml schemas.
@U1Q12R4F2 Not sure if this is what you mean, but perhaps domain model? https://en.wikipedia.org/wiki/Domain_model
I think that domain model is one abstraction level above. At the moment it's focused on the data structure, so schema seems to be the right word. Domain Model, might be interesting, when I'm describing how, why and with whom the data and the whole system is used/shared.