Skip to content

Latest commit

 

History

History
61 lines (38 loc) · 2.89 KB

PRN-yaml.md

File metadata and controls

61 lines (38 loc) · 2.89 KB
Raw

YAML proposal contribution to the ICAO, WTO, IATA's advances on Alignment, Cooperation, Efficiency.

This proposed improvement relates to PASSENGER DATA. Electronic data concerning passengers’ identity (API) or travel reservations (PNR) which is used by public authorities for border control.

Add Modern Format/Tools compatible with traditional ones

Compared to traditional handling of PNR records (EDifact, XML.. or this Worldspan PNR net fare data:)

		<AccountingRemark TypeInGds="NetFare/VC/CAR" ProviderCode="1P">
		    <RemarkData>NetAmount123/CarCode12/ 1001002IATAnumber</RemarkData>
		 </AccountingRemark>

This use of YAML allows improved performance and fast processing by re-using modern yaml tools:

AccountingRemark:
  '@TypeInGds': NetFare/VC/CAR
  '@ProviderCode': 1P
  RemarkData: NetAmount123/CarCode12/ 1001002IATAnumber

Hence, locating data not only via JQuery but also enhanced searches using JmesPath and YQuery.

Enhanced processing of PNR Credit Card data

Another improvements on Credit card authorization inside PNR, from traditional (related to published complaints on uncensored card number found after a filled FOIA request).

Locating /UniversalRecord /AirReservation /CreditCardAuth @Amount @AuthCode ... in Yaml vs Xml:

    <CreditCardAuth Number="************1111" Amount="USD981.80" AuthCode="1234" AuthResultCode="approved"/>

The yaml bi-directional format processing shown here (C.J. ) achieves faster crawling of PNR records:

CreditCardAuth:
  '@Number': '************1111'
  '@Amount': USD981.80
  '@AuthCode': '1234'
  '@AuthResultCode': approved

Allowing processing by the latest yq tools used in modern Apps & Kubernetes, Aws, Gcp, Azure,...

xq . PNR.xml --yaml-output | yq -r '.CreditCardAuth."@Number"' #% extract number
	************1111

References

This document listed last ( InfChg/GeoInt for Safe & Security of Personnel & Users )