Re: Proposal: Additional properties related to flight boarding passes

Hi Vicky,

+1!

A few minor issues:

1. passengerPriorityStatus

I would add schema:QualitativeValue to the range so that airlines could define canonical URIs for their status types.

2. boardingPolicy

For boardingPolicy, I think we should include schema:Flight to the domain, because the boarding policy may also be determined at the level of individual flights.

3. epartureTerminal

I would use Text instead of schema:QuantitativeValue for the range, because you may have alphanumeric terminal identifiers, and you never need units of measurement and very rarely intervals for this value. This will also make markup simpler.

If you want to avoid breaking existing markup, use both schema:Text and schema:QuantitativeValue.



Best wishes / Mit freundlichen Grüßen

Martin Hepp

-------------------------------------------------------
martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen

e-mail:  martin.hepp@unibw.de
phone:   +49-(0)89-6004-4217
fax:     +49-(0)89-6004-4620
www:     http://www.unibw.de/ebusiness/ (group)
         http://www.heppnetz.de/ (personal)
skype:   mfhepp 
twitter: mfhepp

Check out GoodRelations for E-Commerce on the Web of Linked Data!
=================================================================
* Project Main Page: http://purl.org/goodrelations/




On 02 Feb 2015, at 17:12, Vicki Tardif Holland <vtardif@google.com> wrote:

> Boarding passes often have information which is not currently modeled in schema.org. To that end, I propose the following new properties on FlightReservation:
> 
> 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).
> 
> The RDFa can be found at https://github.com/vholland/schemaorg/commit/b8f85c9e0a3c4816b8b5625dd2516b69ab200980.
> 
> The GitHub tracking issue is https://github.com/schemaorg/schemaorg/issues/288
> 
> Thank you for your consideration,
> - Vicki
> 
> Vicki Tardif Holland | Ontologist | vtardif@google.com 
>

Received on Tuesday, 3 February 2015 11:45:27 UTC