Re: Proposal: Additional properties related to flight boarding passes

Hi Vicki:

Thanks! Sorry for the confusion; departureTerminal is fine as it stands. My fault - I had assumed from the code snippets from your commit that the range was schema:QuantitativeValue (from line 9939), but that was from another element.

Best wishes 

Martin

On 03 Feb 2015, at 16:19, Vicki Tardif Holland <vtardif@google.com> wrote:

> I implemented the first two suggestions in commit 2af53d5
> 
> I don't understand the suggestion for departureTerminal. The property currently uses Text as the range.
> 
> Thanks for the suggestions,
> Vicki
> 
> Vicki Tardif Holland | Ontologist | vtardif@google.com 
>  
> 
> On Tue, Feb 3, 2015 at 6:51 AM, Phil Barker <phil.barker@hw.ac.uk> wrote:
> 
> On 03/02/2015 11:45, martin.hepp@ebusiness-unibw.org wrote:
> 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.
> 
> Case in point, London Gatwick has two terminals "North" and "South"
> Phil
> 
> 
> ----- We invite research leaders and ambitious early career researchers to join us in leading and driving research in key inter-disciplinary themes. Please see www.hw.ac.uk/researchleaders for further information and how
> to apply.
> 
> Heriot-Watt University is a Scottish charity
> registered under charity number SC000278.
> 
> 
>

Received on Tuesday, 3 February 2015 15:54:51 UTC