I can think of a use-case in support of Mark's position. If you are building a hosted ETL web service (like Mulesoft) and you want users to be able to use spec to validate records flowing through it.
One customer wants :org/postcode to be integer (i.e. US) and another wants it to be string (i.e. UK) With a global registry this is not possible. It's possible to spec this but then you need to predict all the data shapes supported i.e. not an open validation system You can prefix the key with an org id e.g. :<id>.org/postcode but if you are hosting a lot of orgs the registry will become large. Removal could help manage space but it would require some kind of registry garbage collection i.e. incidental complexity. Any thoughts on how best to do this with spec? Could a multi-spec help here? -- 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.
