Coverage decreased (-0.8%) to 63.379% when pulling cb566db on cweitkamp:feature-110-country-description-provider into fcc9b8f on svendiedrichsen:master.

@cweitkamp Thank you for your effort but this API is in my view only about handling holiday calendars. Those calendars are structuring holidays hierarchically without interpreting those hierarchies. They can be (and are mainly, looking at the provided ones) countries. But even the provided calendars contain examples like Holidays_nsye_euronext.xml which contain holidays of the NYSE. Generally should it be possible to have any kind of hierarchical structure of holidays like i.e.

• one for an international company and its national sub-companies
• or a company and some form of company holidays by company branches
• a calendar of all stock exchanges worldwide
• some kind of personal calendar of all family members

I admit that I have also started thinking only about countries first but since I have seen several different kind of holiday calendar structures.

@svendiedrichsen Thank you for your opinion. You are absolutely right. To take care of the country structure is not the purpose of this API.

For the requirements specified in #110 it would be sufficient to expose the resource bundles of country descriptions. Would it be okay for you to change the visibility of the methods ResourceUtil::getCountryDescriptions() and ResourceUtil::getHolidayDescriptions() to public? The rest can be implemented on our side.