Notices

Contents

Code of Conduct

Contacts for Code of Conduct reports and questions:

  • Trent Scholl (@TrentScholl); private contact address to be added
  • Second contact: to be appointed

Two individuals are listed so that a report can go to someone who is not involved in it.

License Acceptance

Per Community Specification License 1.0 Section 2.1.3.3, Licensees may indicate their acceptance of the Community Specification License by issuing a pull request to this file, including the Licensee’s name, authorized individuals’ names, repository system identifier (for example, GitHub ID), and specification version.

A Licensee may consent to accepting the current Community Specification License version or any future version of the Community Specification License by indicating “or later” after their specification version.


Licensee’s name:

Authorized individual and system identifier:

Specification version:


Withdrawals

Name of party withdrawing:

Date of withdrawal:


Exclusions

This section includes any Exclusion Notices made against a Draft Deliverable or Approved Deliverable as set forth in the Community Specification License. Each Exclusion Notice must include the following information:

  • Name of party making the Exclusion Notice:
  • Name of patent owner:
  • Specification:
  • Version number:

For issued patents and published patent applications:

  1. patent number(s) or title and application number(s), as the case may be:
  2. identification of the specific part(s) of the Specification whose implementation makes the excluded claim a Necessary Claim.

For unpublished patent applications, provide either:

  1. the text of the filed application; or
  2. identification of the specific part(s) of the Specification whose implementation makes the excluded claim a Necessary Claim.

No Exclusion Notices have been made.

Everyone is welcome.

Read a draft and open an issue, try the Data Model with your own tank’s data, or build something that reads or writes it.