It looks like the current version of the Unicode license (v3, found at unicode.org/license.txt <https://www.unicode.org/license.txt>) has been around for at least ten years. The Unicode Intellectual Property, Licensing <https://www.unicode.org/policies/licensing_policy.html> page suggests that the primary difference between their license and the MIT license is that their license expressly covers data and data files.
On Tue, Apr 29, 2025 at 2:24 PM Sutou Kouhei <k...@clear-code.com> wrote: > Hi, > > https://www.apache.org/legal/resolved.html is the 3rd party > license policy of the ASF. Could you check this? > > ("UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE" > in category A case? But > https://www.unicode.org/copyright.html doesn't have the > "Exhibit1" anchor now...) > > Thanks, > -- > kou > > In <CAO-Cae78_v09L0hR0KG68=hEUKh6qCKkGSB6RU6KPLZ4=qa...@mail.gmail.com> > "Copyright and dependencies" on Tue, 29 Apr 2025 14:07:07 -0700, > 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 >
