Hi Curt, I see the Unicode license under Category A (all good!) on [1] so I think you can just vendor and attribute it. That page may also have other advice on how to handle it.
Maybe you can reply here with a link to the PR when you vendor it, and others here can review and make sure it follows the ASF guidelines? Neal [1]: https://apache.org/legal/resolved.html#category-a On Tue, Apr 29, 2025 at 5:07 PM Curt Hagenlocher <c...@hagenlocher.org> wrote: > I'm sure this is the wrong audience for legal-adjacent advice :P but I > thought I'd start here anyway. > > I'm interested in incorporating cldr/common/supplemental/windowsZones.xml > at main · unicode-org/cldr > < > https://github.com/unicode-org/cldr/blob/main/common/supplemental/windowsZones.xml > > > into > the .NET 4.7.2 build of the Arrow library. This is a data file that's > copyrighted by the Unicode consortium and can be used to translate IANA > time zones into Windows time zones. This data has been incorporated into > newer versions of .NET, so it's only required for builds targeting the > "desktop Framework" that still ships inside Windows. > > Is there a kosher way of doing this? And if so, could it be copied directly > into the source tree or would it need to be incorporated into the build > process in some fashion -- e.g. by downloading it from a canonical location > as part of the build. > > Thanks! > -Curt >
