AIM Licence

The licence of an AIM, in two states of one Data Type: the Implementer’s offer, in the AIM Metadata, which is the Implementer’s licence to the MPAI Store; and the AIM Licence that the MPAI Store issues, signed, to the Entity that runs Controllers (the holder of a Trust Anchor) that obtains the AIM, which is the MPAI Store’s sublicence and which its Controllers keep in their AIM repository.

2.1 General Requirements

The AIM Licence shall:

• include a Header matching the pattern AIF-LIC-V<major>.<minor>;
• include a Grant, whose Rights include Run;
• disallow any undefined field at the root level (additionalProperties: false).

2.2 The offer

• The offer is the AIMLicence field of the AIM Metadata. It states what may be done, the limits, for how long, whether newer versions are covered, the price, and where its terms are (TermsURI, required).
• The offer is the Implementer’s licence to the MPAI Store: it states what the MPAI Store may grant, and the sale price that the Implementer proposes (Payment). It shall have Sublicensing, which states whether the MPAI Store may sublicense the AIM; the MPAI Store issues no AIM Licence for an AIM whose offer does not allow it.
• The offer shall not have Licensee, Licensor, ParentLicence, Status or Signature: the AIM Metadata is published once, for everybody, and is never overwritten.

2.3 The issued AIM Licence

• It shall complete the offer for one licensee: it names the AIM and the files covered, each with the fingerprint the MPAI Store approved (AIM); the Licensor, the MPAI Store; the Licensee, the holder of a Trust Anchor; when the Term begins (NotBefore); where validity and revocation are asked, and how long a status may go unconfirmed (Status); and, where the AIM has a price, the proof of payment (Payment).
• It is a sublicence: it shall be within the offer (what it grants, its Term, its Updates), and shall name the offer it is under (ParentLicence): the Implementer and the hash of the offer. Its price is the sale price proposed in the offer with the mark-up of the MPAI Store applied. Its licensee is the Entity that runs Controllers; it does not license the users of that Entity.
• It shall be signed by the MPAI Store. What only an issued AIM Licence has comes with the Signature and nothing else does.
• A Controller shall check, before it builds the AIM, that the signature is the MPAI Store’s, that the Controller is under the Trust Anchor the AIM Licence names, that the AIM Licence is under the offer in the AIM Metadata it holds (ParentLicence), that the files it holds are those the AIM Licence covers, that the Term has not ended, that the Grant covers the use and, when the MPAI Store can be reached, that it is not revoked.
• The Grant says whose control: Run covers the control of the licensee, wherever the AIM executes; RunUnderOtherControl is needed for the control of a party that is not under the licensee’s Trust Anchor.