-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional FlightReservation -related properties #288
Comments
I have added some properties related to boarding passes at vholland@b8f85c9. Specifically, the proposed new properties on FlightReservation are: passengerSequenceNumber: The passenger's sequence number as assigned by the airline. passengerPriorityStatus: The priority status assigned to a passenger for security or boarding (e.g. FastTrack or Priority). securityScreening: The type of security screening the passenger is subject to. And on Airline: boardingPolicy: The type of boarding policy used by the airline (e.g. zone-based or group-based). |
See pull request https://github.com/schemaorg/schemaorg/pull/324/files |
@vholland, what is the difference between the existing http://schema.org/boardingGroup property and the proposed passengerSequenceNumber property? Also, can you update the examples to show the usage of the new properties? |
boardingGroup is something like "Group A" or "Zone 1" which determines the order people board the plane. The passengerSequenceNumber is a unique identifier the airline uses for the passenger. I'll update the examples as well. |
OK, thanks. I guess I don't travel enough. I hadn't seen (or noticed) the unique ID for a passenger before. |
The pull request has expanded examples. I also incorporated @chaals suggestion to not try to enumerate the security screening programs. The securityScreening property now expects Text. |
Looks good to me. |
Issue #288: Added properties to FlightReservation to handle more boarding pass information.
Merged into sdo-gozer. |
http://schema.org/FlightReservation
It has been suggested that additional properties around FlightReservation (or on Ticket, Airline etc.) would improve the usefulness of our flight reservations vocabulary. @vholland has been working on a specific proposal.
The text was updated successfully, but these errors were encountered: