New license request: HDF5

[ycollet]

How license meets inclusion principles

This is a license used for the open source project HDF5 (Hierarcchical Data Format).
HDF5 is used in many other open source projects related to 3D.
Looks like a BSD-3-Clauses.

License Name

HDF5

Suggested short identifier

HDF5

License or Exception?

license

URL to license text

https://github.com/HDFGroup/hdf5/?tab=License-1-ov-file#readme

OSI Status

I don't know

License author or steward

The HDF Group

URL to project(s) that use license

https://github.com/HDFGroup/hdf5

paste text of license here

Copyright Notice and License Terms for
HDF5 (Hierarchical Data Format 5) Software Library and Utilities

HDF5 (Hierarchical Data Format 5) Software Library and Utilities
Copyright 2006 by The HDF Group.

NCSA HDF5 (Hierarchical Data Format 5) Software Library and Utilities
Copyright 1998-2006 by The Board of Trustees of the University of Illinois.

All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted for any purpose (including commercial purposes)
provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,
   this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions, and the following disclaimer in the documentation
   and/or materials provided with the distribution.

3. Neither the name of The HDF Group, the name of the University, nor the
   name of any Contributor may be used to endorse or promote products derived
   from this software without specific prior written permission from
   The HDF Group, the University, or the Contributor, respectively.

DISCLAIMER:
THIS SOFTWARE IS PROVIDED BY THE HDF GROUP AND THE CONTRIBUTORS
"AS IS" WITH NO WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED. IN NO
EVENT SHALL THE HDF GROUP OR THE CONTRIBUTORS BE LIABLE FOR ANY DAMAGES
SUFFERED BY THE USERS ARISING OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

You are under no obligation whatsoever to provide any bug fixes, patches, or
upgrades to the features, functionality or performance of the source code
("Enhancements") to anyone; however, if you choose to make your Enhancements
available either publicly, or directly to The HDF Group, without imposing a
separate written license agreement for such Enhancements, then you hereby
grant the following license: a non-exclusive, royalty-free perpetual license
to install, use, modify, prepare derivative works, incorporate into other
computer software, distribute, and sublicense such enhancements or derivative
works thereof, in binary and source code form.

---

---

Limited portions of HDF5 1.12.0 were developed by Lawrence Berkeley National
Laboratory (LBNL). LBNL's Copyright Notice and Licensing Terms can be
found in the LICENSE_LBNL_HDF5 file in this directory.

---

---

Contributors: National Center for Supercomputing Applications (NCSA) at
the University of Illinois, Fortner Software, Unidata Program Center
(netCDF), The Independent JPEG Group (JPEG), Jean-loup Gailly and Mark Adler
(gzip), and Digital Equipment Corporation (DEC).

---

Portions of HDF5 were developed with support from the Lawrence Berkeley
National Laboratory (LBNL) and the United States Department of Energy
under Prime Contract No. DE-AC02-05CH11231.

---

Portions of HDF5 were developed with support from Lawrence Livermore
National Laboratory and the United States Department of Energy under
Prime Contract No. DE-AC52-07NA27344.

---

Portions of HDF5 were developed with support from the University of
California, Lawrence Livermore National Laboratory (UC LLNL).
The following statement applies to those portions of the product and must
be retained in any redistribution of source code, binaries, documentation,
and/or accompanying materials:

This work was partially produced at the University of California,
Lawrence Livermore National Laboratory (UC LLNL) under contract
no. W-7405-ENG-48 (Contract 48) between the U.S. Department of Energy
(DOE) and The Regents of the University of California (University)
for the operation of UC LLNL.

DISCLAIMER:
THIS WORK WAS PREPARED AS AN ACCOUNT OF WORK SPONSORED BY AN AGENCY OF
THE UNITED STATES GOVERNMENT. NEITHER THE UNITED STATES GOVERNMENT NOR
THE UNIVERSITY OF CALIFORNIA NOR ANY OF THEIR EMPLOYEES, MAKES ANY
WARRANTY, EXPRESS OR IMPLIED, OR ASSUMES ANY LIABILITY OR RESPONSIBILITY
FOR THE ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION,
APPARATUS, PRODUCT, OR PROCESS DISCLOSED, OR REPRESENTS THAT ITS USE
WOULD NOT INFRINGE PRIVATELY- OWNED RIGHTS. REFERENCE HEREIN TO ANY
SPECIFIC COMMERCIAL PRODUCTS, PROCESS, OR SERVICE BY TRADE NAME,
TRADEMARK, MANUFACTURER, OR OTHERWISE, DOES NOT NECESSARILY CONSTITUTE
OR IMPLY ITS ENDORSEMENT, RECOMMENDATION, OR FAVORING BY THE UNITED
STATES GOVERNMENT OR THE UNIVERSITY OF CALIFORNIA. THE VIEWS AND
OPINIONS OF AUTHORS EXPRESSED HEREIN DO NOT NECESSARILY STATE OR REFLECT
THOSE OF THE UNITED STATES GOVERNMENT OR THE UNIVERSITY OF CALIFORNIA,
AND SHALL NOT BE USED FOR ADVERTISING OR PRODUCT ENDORSEMENT PURPOSES.

---

[karsten-klein]

{metæffekt} Universe
canonical name: BSD 3-Clause License (variant 049)
short name: BSD-3-Clause-049
markers: Do Not Promote Marker, General Terms Matches Marker, No Warranty Marker
category: BSD
ScanCode reference id: hdf5
OSI status: none

ScanCode
matched id: hdf5
matched id: llnl

Comment no particular conclusion yet. We are not detecting the capitalized disclaimer as a specific license. Yet the llnl match on ScanCode level is somewhat imprecise. We should discuss the expected outcome first. Single license or license with additional modifiers?

[ycollet]

Thanks for the analysis.
I opened this ticket because I thought this was a specific license.
If your conclusion is this license is just a variant spdx compatible with bsd-3-clause, then that's OK for me.

[Pizza-Ria]

We already have the concept of exceptions in SPDX - maybe we need a category of additional disclaimers and then we could a 1st ID for the base license and a 2nd ID for the disclaimer???

[jlovejoy]

discussed on 4/24 call (but ran out of time): the license file https://github.com/HDFGroup/hdf5/blob/develop/LICENSE does include the various contributors/portions of... sections as well as the extra disclaimer for some portions. We started to discuss whether this is really two licenses (which is kind of is) but also it is published in one file and not clear what portions only use the discolaimer at the bottom so might be better to treat all as one license, since it's also not likely to be used by others.

If any of the names/contributors changed, we could accommodate that with markup later down the road.

Also note that an example of how the license is referred to in source code, is as to the entire license file, see: https://github.com/HDFGroup/hdf5/blob/develop/src/H5AC.c

leaning to adding as one file/license as presented.

@swinslow @Pizza-Ria - can you add your comments since we ran out of time to come to a definitive conclusion??

[jlovejoy]

License Inclusion Decision

Decision:

• approved
• not approved

Name

HDF5 License

License ID

HDF5

XML markup

none at this time

Notes:

This license really contains two license texts, but they are presented together as per the project.

Next steps

If the license has been accepted, please follow the accepted-license process to create the PR.

[Pizza-Ria]

+1 to add.

[ycollet]

Thanks a lot, I will check the procedure to create the PR

[github-actions]

This new license/exception request has been accepted and the information for the license/exception has been merged to the repository. Thank you to everyone who has participated!
The license/exception will be published at https://spdx.org/licenses/ as part of the next SPDX License List release, which is expected to be in three months' time or sooner. In the interim, the new license will appear on the license list preview site at https://spdx.github.io/license-list-data/.
This is an automated message.