Hotel Activity Info

[Stefano Seppi]

Hi all,

as decided at the last developers meeting I've created a new thread for the "Hotel Activity Information".

Thi "Hotel Activity Information" will allow the transmission in a standard form the descriptions of Activities, organized tipically by the Hotel or his service providers, that the Guests could participate in. Those could be organized by a specific Hotel, or a Lodging Structure could simply "collect" Activities organized by other entities (e.g. TV) and make them available.

The goal of this thread is to collect activity types (e.g. massages, SPA, ski tours, etc.) that could be interesting to manage in AlpineBits.

BR

Stefano

[Daniele Gobbetti - Peer GmbH/Srl]

Hello all,

please find attached a first draft of a possible message that could transfer an activity organized by the hotel inside its structure/for its guests. The message is of course valid according to OTA.

It is meant to transfer descriptive information only! An integration with the PMSs (for reserving some specific hotel places like conference rooms, wellness area, etc.) would be possible within the “EventSite” node (see the online navigator of OTA nodes).

One drawback of this message is that it’s a bit verbose (Location and Reservation information are repeated for every date), but it’s only a starting point for the discussion.

Best regards,
Daniele

—

--
You received this message because you are subscribed to the Google Groups "AlpineBits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alpinebits+...@googlegroups.com.
To post to this group, send email to alpin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/alpinebits/ff0d74ba-c66e-42d2-bf2f-e1b14117145b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

​

--

	Daniele Gobbetti Head of Development & Operations
	Peer GmbH/Srl - www.peer.biz Tel. +39 0471 631080 - Fax +39 0471 631724

[Matthias Ebner]

Hi Daniele,

in my opinion your example XML looks good for a first implementation to transfer events in a descriptive manner.

One question about prices/costs of an event:

A hotel offers a trekking tour where participants need a ropeway ticket of 20 Euro per Person and for additional 30 Euro they can have lunch at the alpine hut. So in total every participant will be charged 50 Euro.

How would you implement a price information like this?

We could implement an additional Comment node within the Date->Comments-Node like this:

<Comment Name="Price info">

<Text Language="en">Price: 50 Euro (ropeway ticket 20 Euro, lunch 30 Euro)</Text>

<Text Language="de">...</Text>

<Text Language="it">...</Text>

</Comment>

In this way it is very hard to highlight the price information for the user because to clearly identify it as a price information i have to handle the name attribute as an ID.

Looking at OTA_HotelPostEventNotifRQ specification it seems that there is no good possibility to add price information.

Best regards,

Matthias

[Daniele Gobbetti - Peer GmbH/Srl]

Hi all,

I am following up to this thread to report about a meeting between three AlpineBits members (Peer, Giggle, Marketing Factory) that explored the topic further.

Please note that everything that follows must and will be explored further by each company in order to share concrete OTA-based XML-Messages, these parallel efforts will then be merged into a common proposal to the AlpineBits Developers!

1. Foreword: The scope of this data exchange shall be limited to Hotel internal activity (e.g. Weekly Program).
2. It should be possible to transfer information in multiple languages within a single message.
3. There is a fundamental agreement that each activity should be categorized, and these categories be sent among each activity. Possibly each system could use its own internal categories, but ideally these “local” categories should be mapped to an AlpineBits equivalent, for instance the RatePlan-Categories (PDF AlpineBits 2018-10, page 53).
4. There are several approaches to categorization (user defined lists (open ended), predefined lists, category trees) each with its peculiarities and issues wrt. data exchange. To this end there is no consensus yet on the best approach.
5. There is agreement upon an optional deadline for registration (signing up) to activities, with integration with online booking systems still being explored. Deadline should be in the form of a timestamp (i.e. not simply “one day before the activity takes place”).
6. The group shares the opinion that generally speaking activities should have a begin and an end time. It is however important to support activities with “open start” and “open end”.
7. It is desirable to have the option to mark some activities as “highlight of the day”.
8. An aspect where a common ground has to be found is “disappearing content” (e.g. activities happening in the past? activities whose deadline is in the past?). This point needs further discussion.

The working group will meet again fairly soon (09/01/2019) and the OTA-based proposal will be posted to this thread even earlier, hopefully this will yield to an extended round of feedbacks and sharing.

Hopefully I did not forget anything important and made no mistake in my summary above, but I invite the other participants of the meeting to chime in in case that happened.

Best regards,
Daniele Gobbetti

—

ADDITIVE
Digital Marketing & Sales Automation
Industriezone 1/5 - Eurocenter
I-39011 Lana (BZ)

www.additive.eu

--
You received this message because you are subscribed to the Google Groups "AlpineBits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alpinebits+...@googlegroups.com.
To post to this group, send email to alpin...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/alpinebits/f4832c65-1247-4b48-95c2-793861e22811%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

​

--

Daniele Gobbetti Head of Development & Operations

d.gob...@peer.biz

[tob...@giggle.tips]

Dear AlpineBits members,

We have just had an additional meeting regarding the ambition to create AlpineBits API standards for the transfer of activity data.

In short:
We are now going to extend an already very reasonable proposal from Peer from the Giggle side to finally come up with a discussable XML format.
Paralelly we are coming up with a proposal for generalized activity/experience categories which should help us to better categorize our exchanged data.
Our aim would be to present our proposal at the next developer meeting in Bolzano on the upcoming Thursday.

The very best,
Tobias

[Daniele Gobbetti - Peer GmbH/Srl]

The topic has been accepted for the next AlpineBits release, and an issue for it has been created on gitlab, hence from now on the discussion should happen there.

The issue is https://gitlab.com/alpinebits/developers-kit/issues/14 

Best regards,

Daniele

--

Il giorno mer 9 gen 2019 alle 10:48, tob...@giggle.tips ha scritto:

Dear AlpineBits members, We have just had an additional meeting regarding the ambition to create AlpineBits API standards for the transfer of activity data. In short: We are now going to extend an already very reasonable proposal from Peer from the Giggle side to finally come up with a discussable XML format. Paralelly we are coming up with a proposal for generalized activity/experience categories which should help us to better categorize our exchanged data. Our aim would be to present our proposal at the next developer meeting in Bolzano on the upcoming Thursday. The very best, Tobias

--

You received this message because you are subscribed to the Google Groups "AlpineBits" group. To unsubscribe from this group and stop receiving emails from it, send an email to alpinebits+...@googlegroups.com. To post to this group, send email to alpin...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/alpinebits/60ffb568-5ab3-4710-8d06-a0fc43841ac6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.

[Tobias Schrott]

Great news! 😃

You received this message because you are subscribed to a topic in the Google Groups "AlpineBits" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/alpinebits/xpWosPwjyjE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to alpinebits+...@googlegroups.com.

To post to this group, send email to alpin...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/alpinebits/1547720249.30791.3%40mailserver.peer.biz.

For more options, visit https://groups.google.com/d/optout.

Tobias Schrott, M.A. (MCI)
Founder | Head of Product

M: +43 664 254 1696
E: t.sc...@giggle.tips

W: www.giggle.tips

Giggle GmbH; Firmensitz: Cranachstraße 5, D-12157 Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 170464 B; Geschäftsführer: Tobias Schrott. Internet: www.giggle.tips

Datenschutzhinweis: Der Schutz Ihrer persönlichen Daten ist uns ein besonderes Anliegen. Wir verarbeiten Ihre Daten daher ausschließlich auf Grundlage der gesetzlichen Bestimmungen (DSGVO, TKG 2003). In unserer DSGVO-Datenschutzrichtlinie, die Sie unter www.giggle.tips finden, informieren wir Sie über die wichtigsten Aspekte der Datenverarbeitung im Rahmen unserer Geschäftskorrespondenz. Vertraulichkeitshinweis: Diese E-Mail und etwaige Anlagen können vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, benachrichtigen Sie uns bitte durch eine Antwort-Mail und löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank!

Privacy statement: The protection of your personal data is very important to us. Therefore we process your data exclusively on the basis of legal regulations (DSGVO, TKG 2003). In our privacy policy according to DSGVO, which can be found at www.giggle.tips, we inform you about the most important aspects of data processing in the context of our business correspondence. Confidentiality Note: This e-mail, including any attachment, may contain confidential and privileged information. If you have received it by mistake, please notify us by reply e-mail and then delete this e-mail and any attachment from your system. Thank you!

________________________________________