So continuing on revisiting current schema, cs:info:

Originally the scheme made much more about the type/class of a style;
so much so that the class attribute had values like “author-date” and
"number" and validation was conditioned on those.

Simon and I agree to change that and to shift a lot of that to generic

I wonder if we should revisit this. One possibility is to have
cs:category only really cover fields, and encode the type somewhere



It probably depends a bit on how a CSL-style repository should
function. I could imagine a relatively sparse interface (see also, with a
focus on finding journal-specific styles, or one that also allows
users to find styles based on style format characteristics (like the
current Endnote style page,