diff options
author | Google Open Source <noreply+opensource@google.com> | 2022-03-08 13:57:09 -0800 |
---|---|---|
committer | Bill Neubauer <wcn@google.com> | 2022-03-16 15:41:31 -0700 |
commit | 36d22d226bd4f51307b9671941004ca3a30ffdbb (patch) | |
tree | 37852863393da6ebfa70953c5ad02199d1d7fb77 | |
parent | 6d488bd608387324370d5e67a7b514deaa005197 (diff) | |
download | licenseclassifier-36d22d226bd4f51307b9671941004ca3a30ffdbb.tar.gz |
Add timezone database info that is often distributed with ICU
PiperOrigin-RevId: 433303289
-rw-r--r-- | v2/assets/Supplement/ICU/timezone.txt | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/v2/assets/Supplement/ICU/timezone.txt b/v2/assets/Supplement/ICU/timezone.txt new file mode 100644 index 0000000..494f2b4 --- /dev/null +++ b/v2/assets/Supplement/ICU/timezone.txt @@ -0,0 +1,20 @@ + ICU uses the public domain data and code derived from Time Zone +Database for its time zone support. The ownership of the TZ database +is explained in BCP 175: Procedure for Maintaining the Time Zone +Database section 7. + + # 7. Database Ownership + # + # The TZ database itself is not an IETF Contribution or an IETF + # document. Rather it is a pre-existing and regularly updated work + # that is in the public domain, and is intended to remain in the + # public domain. Therefore, BCPs 78 [RFC5378] and 79 [RFC3979] do + # not apply to the TZ Database or contributions that individuals make + # to it. Should any claims be made and substantiated against the TZ + # Database, the organization that is providing the IANA + # Considerations defined in this RFC, under the memorandum of + # understanding with the IETF, currently ICANN, may act in accordance + # with all competent court orders. No ownership claims will be made + # by ICANN or the IETF Trust on the database or the code. Any person + # making a contribution to the database or code waives all rights to + # future claims in that contribution or in the TZ Database. |