For example a manufacturer wants to add additional Information to the Ticket (“BaseTicketType”).
Additional information can be to structure the composite or additional licensing information.
This opens up new possibilities because tickets are a secured, trusted container for information from the issuer to the device.

My first thought was to inherit the BaseTicketType but this is not possible. We should find a more generic solution like a key-value pair array.

See also this mail thread:
One question to 21:
As a manufacturer I want to add additional Information to the Ticket (“BaseTicketType”).
Then I would inherit from DeviceIdentityTicketType and add my additional variables.
Is that correct or would you prefer another way?

For a future version: I would like to have a Key/Value Pair list on the BaseTicketType for such extensions.

...Answer...

There is no mechanism to do this.
Creating a subtype does not help when the containers only allow the existing types and AllowSubtypes = false.