Alpha.3 release 31 March 2026
- add a meta property to payload (next to data). meta object carries a property "schema" which must be populated 
  with the $id of message schema that validates a json message
- resolve BDT constraints issue
- rebase to DEV TDM (JSON schema release follows XML schema upgrade cycle for official releases)
- switch from relative reference to library (relative to root of message schema) to absolute reference
- switch absolute reference root from (future) IATA Registry to virtual registry as this is an alpha schema
- update mapping of constraint (choice) to more closely mirror XML mapping
- add support for signature
- reference to release where this schema is published is defined but absent as these schemes are not yet part of a release ($comment tag)

The set of schema are now in compliance with
- current version of Baggage model (business data)
- current version of OpenAPIWG Best Practices for JSON Schema and IATA Open Air API Standards and Best Practices v1.3


Alpha.2 release 5 March 2026
- adjust name of object containing the business information from "payload" to "data"
- incorporate fix for issue with cardinality>1 BBIE
- increase version from 0.1.0.alpha.1 to 0.1.0.alpha.2 (pending implementor feedback)
- Alpha.2 is fully aligned on content in XML 26.1 release 
- deferred
  -fix for issue with constraints on BDT other than *_ Code
  -switch from relative reference to library (relative to root of message schema) to absolute reference


Alpha.1 release 7 January 2025
- adjust to emerging JSON Schema best practices guidance documentation, 
  new naming conventions for files and message root


Second release 19 November 2025
- fix naming conventions for root key and schema files
- release now indicated as alpha 1 based on 25.3 package (per XML best practices naming convention of alpha/beta releases)


Fix release: 4 November 2025
- add Role property (XOR) to owner(individual)
- apply set of minor fixes


Initial release: 9 October 2025