The XML schema and the resources/attributes exposed via the management API are not necessarily identical. When an extension that provides a subsystem is installed, it registers it's management API. That's distinct from the XML schema.
The two should be close, but sometimes they'll differ due to different presentation needs. For example, in xml an element that wraps a bunch of pool configuration attributes makes sense as an organizational structure. In the management API we could make a resource for the pool, but it's ugly to create an arbitrary resource address for the pool, since an address requires a type=value format and there's no logical value for pool=???. We could also make the pool a complex attribute (of dmr ModelType.OBJECT) with all the relevant attributes as fields of the attribute. But complex attributes are more painful to manipulate via the CLI, so we discourage their use.
The result of this is you get attribute names in the management API like "pool-use-strict-min".