SMPTE   AG   30
Administrative Guideline

Software license

Approved - Approved: 2024-08-20

Copyright Β© 2024 , Society of Motion Picture and Television Engineers . All rights reserved. No part of this material may be reproduced, by any means whatsoever, without the prior written permission of the Society of Motion Picture and Television Engineers.


Warning: This document is an unpublished work under development and shall not be referred to as a SMPTE Standard, Recommended Practice, or Engineering Guideline. It is distributed for review and comment; distribution does not constitute publication. Recipients of this document are strongly encouraged to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

Table of contents πŸ”—

  1. Foreword
  2. Introduction
  3. 1 Scope
  4. 2 Conformance Normative references
  5. 3 Normative references Terms and definitions
  6. 4 Terms and definitions Conformance
  7. 5 License
  8. Annex A Additional elements (Informative)

Foreword πŸ”—

The Society of Motion Picture and Television Engineers (SMPTE) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States of America, SMPTE has members in over 80 countries on six continents. SMPTE’s SMPTE's Engineering Documents, including Standards, Recommended Practices, and Engineering Guidelines, are prepared by SMPTE’s SMPTE's Technology Committees. Participation in these Committees is open to all with a bona fide interest in their work. SMPTE cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in its Standards Operations Manual.

For more information, please visit www.smpte.org .

This Standards Administrative Guideline forms an adjunct to the use and interpretation of the SMPTE Standards Operations Manual. In the event of a conflict, the Operations Manual shall prevail.

Introduction πŸ”—

Software is commonly used in Engineering Documents and Registered Disclosure Documents. It can, for example, provide a sample implementation of an algorithm or carry large amounts of machine-readable data.

By making the software available under a permissive copyright license, its use in implementations, both commercial and open-source, is facilitated, and interoperability is therefore enhanced.

1 Scope πŸ”—

This document specifies the copyright license for software that is part of Engineering Documents and Registered Disclosure Documents.

2 Conformance πŸ”— Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords: "shall", "should", or "may". Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, changed, or added editorially without affecting interoperability. Informative text does not contain any conformance keywords. All text in this document is, by default, normative, except: the Introduction, any clause explicitly labeled as "Informative" or individual paragraphs that start with "Note:" The keywords "shall" and "shall not" indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted. The keywords, "should" and "should not" indicate that, among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. The keywords "may" and "need not" indicate courses of action permissible within the limits of the document. The keyword "reserved" indicates a provision that is not defined at this time, shall not be used, and may be defined in the future. The keyword "forbidden" indicates "reserved" and in addition indicates that the provision will never be defined in the future. Unless otherwise specified, the order of precedence of the types of normative information in this document shall be as follows: Normative prose shall be the authoritative definition; tables shall be next; then formal languages; then figures; and then any other language forms.

3 2 Normative references πŸ”—

There are no normative references in this document.

4 3 Terms and definitions πŸ”—

For the purposes of this document, the following terms and definitions apply:

3.1
software
programs, procedures, rules, data, tests and associated documentation pertaining to the operation of a computer system

4 Conformance πŸ”—

The following keywords have a specific meaning in the context of this document:

5 License πŸ”—

Wherever its location, all software that is part of an Engineering Document or Registered Document is licensed under the terms of 3-clause BSD license, specified in Element a . The Engineering Document or Registered Document may be in any stage of development or published.

Software may contain components that were developed outside the Standards Community if and only if such components are also licensed under the terms of the 3-clause BSD license.

The copyright notice of Element a shall be present in every file or document that contains the software.

The Society of Motion Picture and Television Engineers shall be the sole copyright holder listed in the notice unless the software contain components that were developed outside the Standards Community, in which case the copyright owners listed for those components shall also be included.

Annex A
Additional elements (Informative) πŸ”—

This annex lists The following are the non-prose elements of this document. document:

  1. a . BSD 3-Clause License (normative). file: < bsd-3-clause.txt >.