Re: Finalizing Reservation schemas for schema.org

On 29 January 2014 21:19, Sam Goto <goto@google.com> wrote:
> A few more notes:
>
> - Why is the reservation status called ReserveStatusType and the order
> status called OrderStatus? Should we make them consistent?

We are now avoiding having pairs of type + property that differ only
in their case.

schema.org/orderStatus + schema.org/OrderStatus violates that, but
slipped through. We should probably migrate it to OrderStatusType.

Dan

> - There is a lot of intersection between the various statuszes classes (with
> one more being added to the list ActionStatus). Should we look at that more
> holistically?
> - http://sdo-wip2.appspot.com/TaxiReservation can we add the dropoffLocation
> and dropoffTime too? Should TrainReservation have those properties too?
> - thanks for adding Taxi and TaxiReservation! Greatly appreciated!
>
>
>
>
> On Wed, Jan 29, 2014 at 12:35 PM, Dan Brickley <danbri@google.com> wrote:
>>
>> On 29 January 2014 20:26, Vicki Tardif Holland <vtardif@google.com> wrote:
>> > I sent another update to Dan.
>>
>> Which I've posted to W3C webschemas Mercurial repo:
>>
>> ~/w3c/webschema/schema.org/ext$ hg commit -m "update from vicki,
>> http://lists.w3.org/Archives/Public/public-vocabs/2014Jan/0206.html "
>> Reservation.html
>>
>> ->
>> https://dvcs.w3.org/hg/webschema/log/dddf24b53d65/schema.org/ext/Reservation.html
>>
>> I've also regenerated the test site, see
>> http://sdo-wip2.appspot.com/Reservation and nearby (some of the
>> subtypes now have examples too, thanks Vicki :)
>>
>> Dan
>>
>

Received on Wednesday, 29 January 2014 21:24:04 UTC