In the future, it may make sense to further expand the configuration options of the rule set. For example, a typification of metadata values is conceivable. Currently, a metadata value is only considered a string. In the future, it may make sense for some use cases to follow a certain scheme - such as a certain time or date format - or to allow only integer values for certain metadata types. This would save a lot of additional business logic for the superordinate application, which currently has to check corresponding inputs before further processing. A descriptive XML schema that maps such things would be very desirable and helpful. Furthermore, a mechanism would be very useful that can also map things that cannot initially be covered by an XML schema, such as a check whether a metadata defined at the beginning of the ruleset reappears in all required areas in the ruleset. For example, in a particular <formats> section or in the structural data; extended in this way, a method of the UGH library could easily check the correctness of a rule set comprehensively and point out errors.