- From: Vicki Tardif Holland <vtardif@google.com>
- Date: Thu, 23 Jan 2014 17:33:25 -0500
- To: Karen Coyle <kcoyle@kcoyle.net>
- Cc: PublicVocabs <public-vocabs@w3.org>
- Message-ID: <CAOr1obFKhrq8eSHaJHRH17xwR4F9C7GRg7JWaoN13VShtN0+AA@mail.gmail.com>
Instead of having the information within a reservation, the reservation could refer to a TrainTrip (or some other, better term. Forgive me. It's getting late here). The TrainTrip would specify the arrival/departure information. A train schedule is a list of TrainTrips. The Flight type (in the same proposal) uses such a pattern. A FlightReservation refers to a Flight. - Vicki Vicki Tardif Holland | Ontologist | vtardif@google.com On Thu, Jan 23, 2014 at 4:07 PM, Karen Coyle <kcoyle@kcoyle.net> wrote: > It looks to me like the /trainReservation properties could also be useful > in a non-reservation situation, such as a general train schedule: > > arrivalPlatform Text The platform where the train arrives. > arrivalStation TrainStation The station where the train trip ends. > arrivalTime DateTime The expected arrival time. > departurePlatform Text The platform from which the train departs. > departureStation TrainStation The station from which the train > departs. > departureTime DateTime The expected departure time. > trainCompany Organization The organization that operates the train > (e.g. Deutsche Bahn (DB)). > trainName Text The name of the train (e.g. The Orient Express). > trainNumber Text The unique identifier for the train. > > None of these are specific to reservations, AFAIK. Could this be > generalized to be something on the order of "train schedule information"? > If so, how would trainReservation then be structured? > > kc > > > On 1/23/14, 12:38 PM, Dan Brickley wrote: > >> Many thanks to Vicki for working through all the fine-grained detail >> for finalizing the Reservation vocabulary, which was circulated here a >> while back. This version reflects all feedback, and in particular >> pulls several pieces of ticketing-related information into a dedicated >> Ticket type. >> >> Here's the RDFS: >> https://dvcs.w3.org/hg/webschema/file/6910d4e4591a/ >> schema.org/ext/Reservation.html >> >> Wiki: https://www.w3.org/wiki/WebSchemas/ReservationsSchema (not up to >> date, like much of wiki currently) >> >> A test build is here: >> >> http://sdo-wip2.appspot.com/Reservation >> http://sdo-wip2.appspot.com/Ticket etc. >> >> We consider this a candidate for including a version 1.0g of >> schema.org within the next few weeks, potentially alongside the QA >> schema (http://lists.w3.org/Archives/Public/public-vocabs/2014Jan/ >> 0107.html). >> Feedback on either very much welcomed. The 1.0f draft is ready to go, >> so expect http://lists.w3.org/Archives/Public/public-vocabs/2014Jan/ >> 0118.html >> in the near future. >> >> cheers, >> >> Dan >> >> >> > -- > Karen Coyle > kcoyle@kcoyle.net http://kcoyle.net > m: 1-510-435-8234 > skype: kcoylenet > >
Received on Thursday, 23 January 2014 22:33:52 UTC