Version 8 of BCBP standard support

[groubis]

Hey @georgesmith46,

I also didn't found any other way to contact you...
Are there any plans for version 8 of BCBP Standard?

Thanks,

[georgesmith46]

Hey,

If you can provide the documentation on version 8, I'll be happy to implement it.

Thanks

[TimmPearl]

V8 is very simple. Just another gender option:

The BCBP group of experts updated Resolulation 792 version 8, which has become effective on June 1, 2020. The list of changes to Resolution 792 - Version 8 is as follows:
• Gender Code - Field 15: Gender Code the gender code “X” which is defined as “Unspecified” and gender code “U” defined as “Undisclosed”.

[TimmPearl]

Here is V7 too:

The BCBP group of experts updated the BCBP Implementation Guide 7th Edition reflecting the latest changes to Resolution 792 - Version 7 that has become effective on June 1, 2018. Section 2.2.4 provides additional information and examples related to certain data elements contained in the standard for implementation purposes. The list of changes to Resolution 792 - Version 7 is summarized below:
• Bar Code on Printed Boarding Pass: the default Bar Code presented on printed boarding pass is a 2-dimensional Bar Code in PDF417 standard containing a structure data message (SDM). On the request from the Airlines version 7 extend the standards to allow Aztec, Datamatrix or QR code formats on printed boarding pass those formats are currently used on Electronic (Mobile) Boarding Pass only.
• Field 23 (Baggage Tag License Plate Number (s)): last 3 digits have been changed to follow RESO 740/RP1745 where 001= 1 bag, 002= 2 bags, 007= 7 on version 6th of RESO 792, 000=1 bag.
• Field 6 (Field Size of variable size field): there was a change in the Implementation Guide where the previous version stated: Items 8 to 118, Plus Item 4, and now Size of data used within the subsequent conditional and airline individual fields (items 8 to 254, plus item 4) in ASCII-printed hexadecimal. If not used, enter "00."
• Field 10 (Field Size of following structured message - unique): there was a change in the Implementation Guide where the previous version stated: Items 15 to 23 the updated version: Size of data used within the subsequent fields (items 15 to 32), in ASCII-printed hexadecimal. If not used, enter "00." Should only count for the length of the conditional data identified as unique. In other words, it is the sum of the length of items 15, 12, 14, 22, 16, 21, 23, 31 and 32.

[kcd71461]

@TimmPearl
Off topic, but may you know how to check the latest BCBP spec (resolution 792)?
The IATA BCBP implement guide lacks information (for example, the maximum length of certain fields), so I tried to find resolution 792, but when I googled it, no data came out.
Is it information that I can know if I need to buy PSCRM?