fergcb

@bagelbits that's not what I meant by that comment. I don't mean that subclasses should be merged into classes like levels, starting equipment, etc. I mean that subclass levels could...

I like this, but I think it would be nice if the choice property was nested under some kind of `feature_specific` attribute. This would just keep the Feature model organised...

I dislike that, personally. The SRD doesn't read as allowing the character to choose between multiple features; it grants one feature that allows a choice of subclass. If you allow...

Yeah, this is exactly what I meant when I was talking about how the `feature_specific` property would help keep things organised as we expand on *all* the features in this...

I'm also not a fan of `formula`. @Redmega is right that it implies that the data is supplying the instructions to calculate the AC, rather than the calculated AC or...

@bagelbits More than acceptable! I'd forgotten about the Conditions collection, if I'm quite honest, but you know me and my fondness for my APIReferences :)

Perhaps other field(s) could be useful for information about the conditions necessary for the resistance/vulnerabilities?

It's defined in the [API documentation](https://www.dnd5eapi.co/docs/) (which does actually need updating), but the definition there is this: | Name | Description | Data Type | | --- | --- |...

I really like this proposed structure, and I think breaking the rules sections down into smaller, bitesize pieces makes a lot of sense. I think bidirectional relationships would be a...

I think we can assume that sections with no parent are top-level. Though I see no issue with creating a single root "SRD" section containing all the true "top-level" sections,...