Re: Comments on Reservations, Orders drafts (was Re: Schema.org update: new and updated proposals)

I have a couple concerns about the proposed Reservations schema:

   1. ProgramMembership and Reservation are listed as a subclasses of
   Thing. It seems like they should be under Intangible since they're not
   real-world entities in the same way that Person, Product and Place are.
   2. The expected value of the reservationFor property is either a
   BusTrip, Event, Flight, FoodEstablishment, LodgingBusiness, RentalCar,
   Thing or TrainTrip. This is confusing because it actually depends on the
   type of reservation that you're using. A FoodEstablishmentReservation
   shouldn't accept a BusTrip as the value of reservationFor but according to
   the current spec it does. Would it be possible to make the expected value
   of reservationFor be an Event and then make BusTrip, CarRental, Flight and
   TrainTrip subclasses of Event?
   3. Different types of Reservation have different properties for
   startTime, startDate and departureTime which are all essentially the same
   property. Because the value of reservationFor is sometimes an event-like
   type and sometime not these properties appear in different places.
   On FoodEstablishment they go in the Reservation item itself but for all the
   other types of reservations they get nested inside the item referred to
   by reservationFor. If reservationFor always expected an Event we could just
   used the startDate/endDate properties inherited from Event with much less
   confusion.



On Thu, May 30, 2013 at 6:57 AM, Dan Brickley <danbri@google.com> wrote:

> Most of the new vocab discussion here in the last 2 weeks has been
> about Actions. Therefore I just want to draw attention again to the
> "Orders", "Reservations" and (the tiny) "EmailMessage" proposals
> linked below.
>
> Any comments/concerns on those docs? I'd like to get them in the queue
> for addition if we have rough consensus that adding them would be a
> step forward for schema.org...
>
> Dan
>
> On 12 May 2013 01:41, Dan Brickley <danbri@google.com> wrote:
> > New additions to WebSchemas Wiki from schema.org team
> >
> > I've just been updating the WebSchemas Wiki to share some drafts that
> > the schema.org team are considering adding to schema.org, as well as
> > making a pass over the Wiki to bring it closer to being up-to-date
> > w.r.t. schema.org.
> >
> > As always http://www.w3.org/wiki/WebSchemas is the front page, with
> > proposals listed at
> > http://www.w3.org/wiki/WebSchemas/SchemaDotOrgProposals
> >
> > Please comment here or in the Wiki; if you reply in email, do change
> > the Subject: line to a more specific topic, to help people keep track
> > of the discussion.
> [...]
> > 2. "Orders in Schema.org"
> > http://www.w3.org/wiki/WebSchemas/OrdersSchema
> > "While schema.org already supports marking up offers to sell products
> > (pre-transaction), it does not currently provide schema for the common
> > kinds of confirmations and notifications around orders
> > (post-transaction)".
> > PDF:
> http://www.w3.org/wiki/images/d/d4/Schema.org_Orders_Proposal_2013-04-19.pdf
> >
> > 3. "Reservations in Schema.org"
> > This proposal includes new types for describing reservations and tickets
> > ""This proposal includes new types for describing reservations and
> > tickets. A generalized Reservation type described, as well as
> > sub­types for flight, train, bus, car, restaurant, event and hotel
> > reservations. An additional type ReservationPackage is also proposed,
> > which should be used to group complex reservations (e.g. flights with
> > multiple legs, itineraries with a flight and a hotel) under a single
> > item."
> > http://www.w3.org/wiki/WebSchemas/ReservationsSchema
> > PDF:
> http://www.w3.org/wiki/images/7/74/Schema.orgReservationsProposalMay2013.pdf
> >
> > 4. EmailMessage
> > A simple additional type, subtype of CreativeWork and corresponding to
> > the existing type WebPage.
> >
> > 5. Events (revised proposal for update)
> > This is an improved version of a proposal from last year. The previous
> > version's design for recurring events was flawed; see
> > http://www.w3.org/wiki/WebSchemas/EventSchemaUpdate for a new design.
> > PDF:
> http://www.w3.org/wiki/images/d/db/Events-proposalforupdatedschemav2.pdf
>
>


-- 
Shawn Simister

Knowledge Developer Relations
Google