Re: Finalizing Reservation schemas for schema.org

I sent another update to Dan. The changes are:

- Changed reservationNumber to reservationId

- Removed Reservation > modifyReservationUrl

- Removed Reservation > cancelReservationUrl

- Removed Reservation > confirmReservationUrl

- Removed Reservation > checkinUrl

- Removed Ticket > downloadUrl

- Removed Ticket > printUrl

- Removed FoodEstablishment > reservationUrl

- Added Reservation > priceSpecification

- Changed Reservation > price and Ticket > price to pricePaid.

- Changed pricePaid to accept PriceSpecification in addition to number.

- Changed Flight > aircraft to accept a Vehicle.

- Added Taxi.

- Added TaxiReservation.


The various URL properties were removed in favor of the forthcoming
addition of ActionHandler.


- Vicki







Vicki Tardif Holland | Ontologist | vtardif@google.com



On Wed, Jan 29, 2014 at 12:36 PM, Vicki Tardif Holland
<vtardif@google.com>wrote:

>
> On Wed, Jan 29, 2014 at 5:48 AM, Charles McCathie Nevile <
> chaals@yandex-team.ru> wrote:
>
>> The changes indeed make sense. But why aren't BusTrip, etc subclasses of
>> Event?
>>
>
> The properties on Event did not seem to fit for BusTrip, etc., but I am
> open to a discussion on this topic.
>
>
>
>>
>> (And can you make reservations for something recurrent? Like a meeting
>> room, or a time-share property at beautiful Lake Mulwala, safe for the
>> kids, fun for the family, …*)
>>
>
>
> Recurring reservations were discussed, but there were a lot of
> complexities, so we left them out of this round.
>
> - Vicki
>
>
> Vicki Tardif Holland | Ontologist | vtardif@google.com
>
>