Please find github link in bellow https://github.com/Mamun/spec-model
Br, Mamun On Sunday, November 27, 2016 at 11:37:30 PM UTC+1, Mamun wrote: > > > > It is very common that application needs different format of data, > sometime only entity, sometimes with entity type or list of entity. As an > example > > Business entity > Dept {dept-name,id } has many employee {empl-name, id}. > > > As entity : {:dept-name "IT"} > List of entity [{:dept-name "IT"}] > Domain type {:dept {:dept-name "IT"}} > List of domain type [{:dept {:dept-name "IT"}}] > > > Additionally you need to think about namespace qualified key, unqualified > key and string conformation. In the end to define spec registry key will be > challenging that will be understandable to all team member within project. > > spec-model is solution for it. Like UML tools, define business model as > data. spec-model will generate spec for it. > > Br, > Mamun > > -- 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.