Re: LodgingReservation / LodgingSearch extension

Thanks for your quick reply, SearchAction look like a good starting point
but the docs contradict themselves, it lists the properties as:

PropertyExpected TypeDescription
Properties from SearchAction <https://schema.org/SearchAction>
query <https://schema.org/query> Text <https://schema.org/Text>  A sub
property of instrument. The query used on this action.

But then in the examples it has a search for a hotel:


   1. <script type="application/ld+json">
   2.   // John searched for hotels.
   3. {
   4.   "@context": "http://schema.org",
   5.   "@type": "SearchAction",
   6.   "agent": {
   7.     "@type": "Person",
   8.     "name": "John"
   9.   },
   10.   "query": {
   11.     "@type": "Class",
   12.     "name": "http://schema.org/Hotel"
   13.   }
   14. }
   15. </script>


As you can see the query property is now a class object, *surely this won't
validate as Text?*

Ideally I'd like to make the query an Intangible object so that I could
make it have structure rather than just free text.

Are people sub classing SearchAction or making query an object and the docs
are just wrong?


On Tue, Feb 5, 2019 at 3:39 PM Umutcan Simsek <umutcan.simsek@sti2.at>
wrote:

> Hi Dan,
> Why not use the SearchAction?
> I believe you can achieve the same goal by using a HotelRoom description
> as object and LodgingReservation as result.
> You can check the schema.org/Action type and it's documentation as a
> starting point.
>
> Greetings
> Umut
>
> On Feb 5, 2019 15:57, Dan Bodart <dan.bodart@triptease.com> wrote:
>
> I'm looking for some design advice: I work in the hotel industry and our
> platform currently uses a number of key elements from the Hotel ontology
> (Organisation, Brand, Hotel, HotelRoom, Offer, LodgingReservation
> <https://schema.org/LodgingReservation>).
>
> These preexisting elements have allowed our tools to automatically
> recognise our clients hotels sales funnels. We can identify what hotel we
> are on, what rooms the hotel has available for a given search and when the
> user makes a purchase. One area that we would like to support is
> identifying the search parameters a user entered for making a reservation.
>
> The data we would like to capture is virtually identical to a
> LodgingReservation <https://schema.org/LodgingReservation> and so the
> first question:
>
> *Should we extend ReservationStatusType
> <https://schema.org/ReservationStatusType> to have an extra enum value of
> ReservationSearch or should we create a new Intangible call LodgingSearch
> (or a better name)?*
>
>
> *Common properties:*
>
>    - checkinTime
>    - checkoutTime
>    - numAdults
>    - numChildren
>    - priceCurrency
>    - totalPrice
>
> *Additional properties*
>
>    - numRooms : Integer or QuantitativeValue
>    - childAge : Integer or QuantitativeValue
>
>
> Any advice would be much appreciated
>
> Thanks
>
> Dan
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
>
>