Bruce D'Arcus

> The idea is 1. to make macros usable with different relations (e.g. a macro "title" with reviewed and original relations), and 2. to make macro definitions easier (no need...

> My thinking was that there would be no nested relationships. We should probably explicitly disallow them in the data schema. I agree, but it's not possible or convenient to...

This is why I think we probably shouldn't allow that. The style author should write two macros, or a single macro with whatever conditional logic.

One way to split the difference: keep the content in the schema, and pull it out (by simple script) for human-readable purposes? On Mon, Aug 25, 2014 at 3:05 PM,...

FWIW, I included documentation early on in both the CSL schema and the first (XSLT) implementation. But that was mostly because tools and applications supported them. Not sure JSON Schema...

> ... **an object** might provide a good place for ... Perhaps, but surely not _this_ object? I don't really understand that use case, but it seems from your example...

> If they are referenced subsequently, they are generally referred to again all at once (citing just the group number), but they might also be referenced individually, citing both the...

I suppose this is worthy of a larger conversation, somewhere, about compatibility. I've been assuming different schema versions for citation and data, and processors would thus be able to handle...

That works; I missed that.

Actually, no it doesn't. The first commit is that; there's no commit with a diff of the main schema file. Or if it's straightforward, I suppose you could just tell...