schemata

But too many people drank the semantic kool-aid and tried to autogenerate classes from schemata or other such silliness.

Here [1] is a list of some Winograd schemata devised for testing artificial intelligence chatterbots.

Your general musing is right, but the problem of source-data quality is generally considered to be distinct from the design of schemata.

Our job is turning business models into schemata and then coding the fuck out of them into something original, beautiful, and useful.

I think it's a fundamentally bad idea to think of class hierarchies as ontological schemata of real world things.

Oh, I'm handwaving, not talking about the underlying details of star schemata, clever column representations and whatnot.

Your first step is to check that your logical design was sound, because poorly designed schemata are hard for query planners to reason correctly about.

If I don't need complex schemata or a huge dataset, why would I choose something else that is less easy to manage?

If you're on the fence as to whether you want to read a blog post about database schemata do yourself a favour and give it a look.

You can serialize a message defined with one schema and deserialize the result to a message with a different schema if the two schemata are compatible enough.

Schematize everything, but nothing's actually using the schemata.

I wonder if you could do machine learning on schemata.

The bigger question is about the implications of "authorized user access" schemata, more generally.

I don't think it requires a whole lot more thought that you ought to be putting into your Mongo "schemata" anyway.

What is meant by "[the] client is free to have full coherence of server's public domain including all its public API, domain objects and schemata"?

I didn't see any way of defining schemata for "one-off" top-level resources.

Schemata likely must be triggered by a validation function being called on live code.