[Hotel Info] Proposal for new future feature

Matteo Dalle Feste

unread,

Mar 27, 2017, 11:35:14 AM3/27/17

to AlpineBits

Hi.

Could be interesting for a propriety to share its general informations like:

- Hotel general text descriptions (Facilities, proximity, reception Hours..)

- Hotel Images (Internals, Externals, Logo...)

- Hotel Amenities (Bar, Pets allowed, Wifi...)

- General Rooms Amenities (Tv Sat, Air conditioning, Jacuzzi..)

- Propriety Policies (Check-in, Check-out, cancellation, guarantee..)

- Review value

- Contact Infos (Address, Phone, Mail, Fax, Website..)

The function that could be used is OTA_HotelDescriptiveInfoRS

Here an example:

<OTA_HotelDescriptiveInfoRS Version="1.01" TimeStamp="2007-07-31T15:35:51+12:00">

<HotelName>Hotel AlpineB Spa Resort</HotelName>

<!—- Type of Propriety. Ex. Hotel, B&B, Chalet... -->

</CategoryCodes>

<!—- Descriptive elements of the Propriety - See OTA Code Table for INF Information codes -->

<Text> AlpineB Hotel is situated in the most beautiful.. </Text>

</Description>

<Text>This property has gained another star.. </Text>

</Description>

<Text>All rooms have a mountain view...</Text>

</Description>

<Text>A great restaurant is closer the lodging</Text>

</Description>

</Description>

<Text>We provide a lot of tour in mountain..</Text>

</Description>

<Text>Take the A22 Highway and follow the main road ...</Text>

</Description>

<Text>We have a big parking covered by trees ...</Text>

</Description>

<Text>See our special offers about Winter and Spring with your Family…</Text>

</Description>

<Text>All internet bookings are discounted by 20% from our normal rates.</Text>

</Description>

<Text>meta tag title</Text>

<Text>meta tag keywords</Text>

<Text>meta tag description</Text>

</Description>

<!—Logo Of property -->

<Image>http://.../images/AlpineBitsHotel.jpg</Image>

</Description>

<Image>http://.../images/External_proprietyImageWinter_SMALL.jpg</Image>

</Description>

<Image>http://.../images/External_proprietyImageSummer_SMALL.jpg</Image>

</Description>

<Image>http://.../images/External_proprietyImageWinter_BIG.jpg</Image>

</Description>

<Image>http://.../images/ External_proprietyImageSummer_BIG.jpg</Image>

</Description>

</Descriptions>

<!—- Hotel Amenities -->

</Services>

</OwnershipManagementInfo>

</OwnershipManagementInfos>

</HotelInfo>

</Amenities>

<!— Useful? See Inventory Rooms -->

<Text>This superbly appointed room is designed for the wine connoisseur ...</Text>

</Description>

<Text>This room includes a 12-bottle wine chiller to keep those Martinborough sauvies at perfect ...</Text>

</Description>

<Text>We offer a luxurious king-sized bed or, by prior arrangement, you may choose a twin bed ...</Text>

</Description>

<Description Name="Room Image" PictureCategoryCode="006.PIC" MultiMediaObjectHeight="300" MultiMediaObjectWidth="400"

ContentCode="004.CTT">

<Image>http://.../images/room_photo/DZ-Room.jpg</Image>

</Description>

</GuestRoom>

</GuestRoom>

</GuestRooms>

</FacilityInfo>

<!—- Check-in and Check_out period, penalities, deposit, Child Policy -->

</Policy>

<Text>Full refund of deposit if cancelled within 2 days of arrival ...</Text>

</PenaltyDescription>

</CancelPenalty>

</CancelPolicy>

<Text>One-third deposit is required to secure your booking...</Text>

</Description>

</GuaranteePayment>

</GuaranteePaymentPolicy>

<Text>This Propriety is designed for Kids..</Text>

</Description>

</PolicyInfo>

</Policy>

</Policies>

<!—- Useful? See later ContactInfos tag -->

</RefPoints>

</AreaInfo>

<!—- Could be useful, if it’s a trusted value.. -->

</Awards>

</AffiliationInfo>

<!—- Useful info for geolocalization, website, email, contact info -->

<Names>

<Name>

<Surname> Sparrow </Surname>

<JobTitle>Reservations Contact</JobTitle>

</Name>

</Names>

<AddressLine>Bolzano</AddressLine>

</Address>

<AddressLine>Via Macello, 65</AddressLine>

<AddressLine>Bolzano</AddressLine>

</Address>

</Addresses>

</Phones>

<Value>in...@alpineb.com</Value>

</Email>

</Emails>

<URLs>

<Value>alpineb.com</Value>

</URL>

</URLs>

</ContactInfo>

</ContactInfos>

</HotelDescriptiveContent>

</HotelDescriptiveContents>

</OTA_HotelDescriptiveInfoRS>

Some informations could be removed (like MaxOccupancy shown on <Guest Room> tag because is used into others Alpinebits functionalities.)

Possible Capabilities division:

OTA_HotelDescriptiveContents_HotelInfo

OTA_HotelDescriptiveContents_FacilityInfo

OTA_HotelDescriptiveContents_Policies

OTA_HotelDescriptiveContents_review

OTA_HotelDescriptiveContents_ContactInfo

Matteo Dalle Feste

unread,

Jun 13, 2018, 9:45:37 AM6/13/18

to AlpineBits

ContactInfo

ContactInfo is used to define the contacts for consumers and technical people at the hotel facility. It include telephone numbers,e-mail addresses,urls or any respective attribute or affiliation for the hotel.

I started from this thread and relative codes: https://groups.google.com/forum/#!topic/alpinebits/IipS2P35IDc

I added up to 300 urls and the validator did't give me errors.

Code in Attach has been validated with a local validator and using the official AlpineBits validator https://development.alpinebits.org/#/validator
Only PULL_OTA_HotelDescriptiveInfoRQ.xml fail the validation against Alpinebits 2017-10 xsd file.

PS: I found another big player that use the call OTA_HotelDescriptiveContentNotif
https://connect.booking.com/user_guide/site/en-US/ota-hoteldescriptivecontentnotif/

Matteo

PULL_OTA_HotelDescriptiveInfoRQ.xml

PULL_OTA_HotelDescriptiveInfoRS.xml

PUSH_OTA_HotelDescriptiveContentNotifRQ.xml

PUSH_OTA_HotelDescriptiveContentNotifRS.xml

Message has been deleted

Matteo Dalle Feste

unread,

Jun 27, 2018, 9:52:24 AM6/27/18

to AlpineBits

As requested in the last DevMeeting, i've investigated about other possible way to transmit codes without use the URL tag for a non URL field.

inside ContactInfo i found only space for strings of 32/64 chars length and i think could be useful have more flexibility.

So i prepared an alternative use case with AffiliationInfo->Descriptions. See. https://www.pilotfishtechnology.com/modelviewers/OTA/index.html?page=https%3A//www.pilotfishtechnology.com/modelviewers/OTA/model/Format.OTA_HotelDescriptiveInfoRS.html

Code in Attach has been validated with a local validator and using the official AlpineBits validator https://development.alpinebits.org/#/validator
Only PULL_OTA_HotelDescriptiveInfoRQ.xml fail the validation against Alpinebits 2017-10 xsd file.

In the same PULL case the OTA protocol doesn't allow an attribute SendDescriptions="true" inside of <AffiliationInfo> tag. See: https://www.pilotfishtechnology.com/modelviewers/OTA/index.html?page=https%3A//www.pilotfishtechnology.com/modelviewers/OTA/model/Format.OTA_HotelDescriptiveInfoRQ.html

So in the example PULL_OTA_HotelDescriptiveInfoRQ.xml i gived this string:

<AffiliationInfo SendAwards="false" SendBrands="false" SendDistribSystems="false" SendLoyalPrograms="false"/>

Could be a valid solution?

Regards.

Matteo Dalle Feste

PULL_OTA_HotelDescriptiveInfoRS.xml

PUSH_OTA_HotelDescriptiveContentNotifRQ.xml

PUSH_OTA_HotelDescriptiveContentNotifRS.xml

PULL_OTA_HotelDescriptiveInfoRQ.xml

Matteo Dalle Feste

unread,

Aug 3, 2018, 10:26:42 AM8/3/18

to AlpineBits

As discussed in the meeting of August 2, 2018, the first proposal was chosen with some changes:
- The "id" attribute identifies the site / service we want to share
- The "Type" attribute is not necessary at this time.

It might be useful to add a suggestion in the specifications that explains how to create new elements for the id attribute. Eg. "Service name written in capital letters"

as regards the URL element, OTA valid for xs: anyURI.
Therefore valid both elements of type: https://www.xyz.it and id:12345

Another suggestion could be to include lowercase characters in URIs

An example follows.

<?xml version="1.0" encoding="UTF-8"?>

<!-- PULL RESPONSE Example -->

<OTA_HotelDescriptiveInfoRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
                       xmlns="http://www.opentravel.org/OTA/2003/05"
                       xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_HotelDescriptiveInfoRS.xsd"
                       Version="1.002">
    <Success></Success>
    <HotelDescriptiveContents>
        <HotelDescriptiveContent HotelCode="12345" HotelName="Hotel AlpineBits Spa Resort" HotelCityCode="A007">
            <ContactInfos>
                <!-- 
                    - Location Attribute is used to specify the location of the contact Info. Location = 6 is the "Hotel direct contact" (See CON codelist)
                    - Removal Attribute, if true, is used to remove the previus transmitted data.
                -->
                <ContactInfo Location="6" Removal="false">

                    <URLs>
                        <!--
                            - Has been tested with 300+ Url and no validation problems has been detected.
                            - ID  attribute (String:1-32chars) is used for giving a reference key Ex. TRUST*OU, TRUST*ILOT, FACE*OOK, H*V, D*LOMITI, P*ER ..  
                            Could be useful to specify a common ID attribute table or a rule set Ex. Uppercase, without space..
                        -->
                        
                        <URL  ID="FACEBOOK" >http://www.fac...book.com/hotelalpineb</URL>
                        <URL  ID="WHATSAPP" >https://wa.me/34712345678?text=Hello%20World</URL>
                        <URL  ID="TWITTER" >https://www.twit....com/user/HotelAlpineB/</URL>            
                        <URL  ID="TRUSTYOU" >id:234567</URL>
                        <URL  ID="YOUTUBE" >https://www.youtube.com/channel/KDLLmtt85a27DPQ7f9sd</URL>
                    </URLs>
                </ContactInfo>
            </ContactInfos>
        </HotelDescriptiveContent>
    </HotelDescriptiveContents>
</OTA_HotelDescriptiveInfoRS>

Reply all

Reply to author

Forward