<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by The Travel Tech on Medium]]></title>
        <description><![CDATA[Stories by The Travel Tech on Medium]]></description>
        <link>https://medium.com/@thetraveltech?source=rss-1dabba54f3a9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*04PuZq40sKsOcTO-9oueug.png</url>
            <title>Stories by The Travel Tech on Medium</title>
            <link>https://medium.com/@thetraveltech?source=rss-1dabba54f3a9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:11:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thetraveltech/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Wrap-up: Winding Tree Hackathon @Lisbon 2019 #HackTravel]]></title>
            <link>https://medium.com/@thetraveltech/wrap-up-winding-tree-hackathon-lisbon-2019-hacktravel-eb7830791104?source=rss-1dabba54f3a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb7830791104</guid>
            <category><![CDATA[airlines]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[hotel]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[The Travel Tech]]></dc:creator>
            <pubDate>Sat, 20 Jul 2019 13:38:05 GMT</pubDate>
            <atom:updated>2019-07-20T13:38:05.784Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is a wrap-up of the Winding Tree <a href="https://windingtree.com/hacktravel-lisbon-2019">Hackathon</a> that took place in Lisbon in July 2019. <a href="https://windingtree.com/">Winding Tree</a> is a solution for travel distribution leveraging the Ethereum blockchain.</p><p>I take the opportunity to share my thoughts and review the main issues that were raised <a href="https://medium.com/@thetraveltech/a-winding-tree-tutorial-3273504aec4c">in my previous article</a> in January 2018. My aim is to provide constructive feedback on potential weaknesses in order to have a more robust solution for the industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iwavUTZmdgQcgRXITKlXFQ.jpeg" /><figcaption>The Winding Tree hackathon venue at Lx Factory</figcaption></figure><h3>Scalability and Privacy</h3><h4>No transactions limits</h4><p>One issue raised when Winding Tree started was the scalability. In its initial implementation, it was using Ethereum Smart Contracts to store the bookings themselves. It was relatively slow and constrained by the Ethereum limit of about <a href="https://ethereum.stackexchange.com/questions/49484/how-many-transactions-per-second-can-ethereum-currently-handle-what-changes-wil">25 transactions per second</a>.</p><p>Since then, the Winding Tree solution has evolved and is now completely scalable:</p><ul><li>The discovery and registration of participants is enabled by a set of Smart Contracts forming a directory structure.</li><li>Meta-Data on each participant is stored off-chain.</li><li>The actual inventory access and booking is made peer-to-peer between a distributor and a supplier. This has been demonstrated in the previous Hackathon in October 2018 by Siesta Cloud for Hotels and by Air France for airlines. Messages can be signed to prove their authenticity.</li></ul><p>With such structure, there is no limitation on the number of transactions that the platform can handle, it will be up to the participant’s systems to support the load.</p><h4>Protocol Standardization</h4><p>There is an inherent scalability issue with the standardization protocols. In a peer-to-peer environment, how do all participants speak the same language?</p><p>The Winding Tree foundation proposes (it does not seem to be enforced) its <a href="https://github.com/windingtree/wt-booking-api/blob/master/docs/source.yaml">own internal booking API</a>. While at first sight it feels like re-inventing the wheel, I believe it is a good architectural decision for the following reasons:</p><ul><li>No licensing issues with other standards: anyone can freely use this protocol since it is open source.</li><li>No governance issue with external bodies: the protocol can evolve at its own pace, without having to synchronize with external standardization bodies such as IATA or Open Travel Alliance.</li><li>Gateways for IATA NDC, OTA-XML or other private APIs can still be implemented by the suppliers themselves or by third party technology providers.</li><li>Easier implementation for Travel Agencies.</li></ul><p>The downside of such a choice is of course that the protocol in its current state is not mature enough to cover every features of industry standards. Just an example: the Loyalty Program number is not yet present in the schema.</p><p>A standardization work is therefore required to bring the Winding Tree standard to the level expected by the industry.</p><h4>GDPR and Privacy</h4><p>The privacy issue is solved with this new architecture since bookings are not present on the blockchain anymore.</p><p>GDPR compliance is possible if the two parties agree on a Data Processing Agreement (DPA) upfront and through an offline channel. To apply GDPR at the letter while respecting the spirit of a true decentralized ecosystem, there would be a need to establish standard DPA contracts in Smart Contract too.</p><h4>Business Scalability</h4><p>With the current architecture, there is still no defined mechanism for <em>billing</em> and <em>payment of commissions</em> from suppliers to distributors.</p><p>Without such mechanism, participants will need to make one-to-one arrangements prior to making bookings, which is against the philosophy of open marketplace claimed by Winding Tree.</p><p>It will also slow down the adoption of the platform, preventing its usage at scale if it not addressed.</p><h3>Scam Protection</h3><p>Another concern that was initially raised is the risk of scam. In a decentralized architecture with no central gatekeeper, a mechanism shall be present to prevent scammers from impersonating a legit company. These scams could upload fake hotels and run away with the money.</p><p>This is definitively a complex problem, and even in a centralized environment like Booking.com or Expedia, it is not an easy task: dedicated teams are required to verify the legitimacy of the properties listed. With a central party, there is always a risk that some scam properties are not being removed, or that legit properties are removed when they should not.</p><p>In the last months, Winding Tree came up with a number of proposals to address this issue and it was in my eyes the main focus of Winding Tree’s Hackathon in July 2019.</p><p>The proposal of Winding Tree is in two steps:</p><ul><li>Identity: A participant’s identity is created on the blockchain as a smart contract. This smart contract contains a URL to an off-chain JSON file containing meta-data on the property such as website, Geo-Location and physical address. The authenticity of the JSON file could also be verified with the Smart Contracts, it is not implemented yet but would be trivial with the current architecture.</li><li>Trust: To provide trust to other participants, each participant is requested to provide a number of <em>trust clues </em>to demonstrate it is a legit business.</li></ul><p>The possible <em>trust clues</em> that have been foreseen so far are:</p><ul><li>The participant’s DNS record can be updated with the address of the smart contract. If it matches it means the owner also owns the DNS record. If it matches and the SSL Certificate has undergone an Extended Validation, it means a third party has reviewed the legal information of the DNS owner.</li><li>LIF deposit: The participant can deposit in a smart contract an amount of LIF, Winding Tree’s ERC20 token. The withdrawal is delayed, the current implementation is one month. If the LIF deposit value is high enough, it is a proof that the participant is not creating many fake properties.</li><li>A trusted Third Party can verify participants.</li><li>The team which I joined in the Hackathon also proposed a concept of Peer-to-peer trust links between two parties. With a chain of trust links, a relative trust between two parties can be established (see <a href="https://github.com/windingtree/wt-hackathon/blob/master/submissions/2019-lisbon/trust-clue-validator-api.md">submission</a>).</li></ul><p>The fraud problem in the travel industry in general is not easy, participants rely currently on centralized parties (IATA, GDS, OTAs). With a decentralized solution, each participant will have to implement its own policies to ensure it is transacting with trusted participants.</p><h3>Conclusion</h3><p>The Winding Tree solution has made many improvements over the last 18 months. Significant effort has been made to bring identity, trust and unified APIs to the platform. I believe it is in a state where, after having made the necessary offline agreements, a reduced number of trusted participants can start piloting the platform in a live environment.</p><p>There are still some milestones to complete before delivering the full vision of this decentralized travel marketplace, but I believe the team is getting there, kudos!</p><p><em>Reports from other participants of the Hackathon:</em></p><ul><li><a href="https://blog.windingtree.com/2019-lisbon-hacktravel-technical-recap-509bcc9adcd7"><em>Technical recap</em></a><em> from Jiri, Winding Tree lead developer</em></li><li><em>Siesta Cloud&#39;s </em><a href="https://medium.com/siesta-cloud/winding-tree-hackathon-report-5773211b4310"><em>hackathon report</em></a></li><li><em>Peakwork&#39;s </em><a href="https://www.peakwork.com/en-EN/news/insights-and-press/insights-and-news-details/peakwork-addresses-latest-travel-industry-tech-at-hacktravel-2019"><em>communication</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb7830791104" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EU SCA: Challenges for airline distribution]]></title>
            <link>https://medium.com/@thetraveltech/eu-sca-challenges-for-airline-distribution-c1ccf8eb63ea?source=rss-1dabba54f3a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1ccf8eb63ea</guid>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[travel-agency]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[gds]]></category>
            <category><![CDATA[airlines]]></category>
            <dc:creator><![CDATA[The Travel Tech]]></dc:creator>
            <pubDate>Sun, 14 Jul 2019 15:00:44 GMT</pubDate>
            <atom:updated>2019-07-14T15:01:48.284Z</atom:updated>
            <content:encoded><![CDATA[<p>On September 14th 2019, the European directive on Strong Customer Authentication (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2018.069.01.0023.01.ENG&amp;toc=OJ:L:2018:069:TOC">SCA</a>) is entering into force, generating unique challenges for the airline indirect distribution model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MMyd4oEUki_1Q3mr_s9wqA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@randycolasbe?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Randy Colas</a> on <a href="https://unsplash.com/search/photos/europe-flag?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>What is SCA and what does it mean for my business?</h3><h4>An overview of SCA</h4><p>The Strong Customer Authentication (SCA) is one of the requirement of the European Directive EU 2015/2366 on Payment Services (<a href="https://ec.europa.eu/info/law/payment-services-psd-2-directive-eu-2015-2366_en">PSD2</a>), aiming at increasing the security of electronic payments.</p><p>Do you remember when additional fees where popping up on airline website when using some payment cards? Well this has been banned by PSD2, at least for European airlines accepting European-issued cards. It was already difficult for many airlines to be compliant, now wait for SCA.</p><p>SCA mandates the use of two-factor authentication in payments. It means that merchants need to authenticate cardholders with at least two of the below factors:</p><ul><li>Something they know: typically a password</li><li>Something they have: a physical card, a device</li><li>Something they are: fingerprint, iris, heartbeats</li></ul><p>The interesting point about SCA is that it is technology agnostic: there is no specific protocol mandated and all type of payments are in scope, not only payment cards.</p><p>For payment cards in particular, the answer of the payment industry to the SCA requirement is:</p><ul><li>For the E-Commerce channel: the <a href="https://en.wikipedia.org/wiki/3-D_Secure">3D-Secure</a> (3DS) authentication protocol</li><li>For the Face-to-face channel: the <a href="https://www.emvco.com/emv-technologies/contact/">EMV Chip&amp;PIN</a> authentication protocol</li></ul><h4>When is SCA applicable?</h4><p>SCA is applicable for electronic payments (not cash) when the two below conditions are satisfied:</p><ul><li>The merchant&#39;s bank is established in the European Union</li><li>The payment instrument is issued in the European Union</li></ul><p>There are a few exceptions, for example when the amounts are low or when the fraud risk is low.</p><p>For merchants this definition it pretty clear, but in the airline distribution — using Global Distribution Systems (GDS) or New Distribution Capability (NDC) — there is a possibility that a travel agency is passing payment to the airline, in which case SCA would apply as well for European Airlines and European cards.</p><p>We can already see that this can be challenging.</p><p>As a travel agency, how do I know that the airline&#39;s bank is in Europe and how do I know that the card is issued in Europe? How do I authenticate the customer?</p><p>As an airline, how do I enforce that SCA is applied by the travel agency?</p><h3>How to comply with SCA?</h3><h4>SCA compliance for Airlines</h4><p>As an airline with European acquirers, you will have to perform a complete analysis of all places where you accept payments:</p><ul><li>Implement 3D-Secure for all E-Commerce direct channels: Booking Engine, Mobile application, Redemption, Servicing, etc.. If you have the capability to identify the card country, you might decide to activate 3DS only for European cards. The version 1 of 3DS is in end-of-life and has been criticized to introduce too much friction at checkout, so you should rather support 3DS version 2.</li><li>Install Chip&amp;PIN devices in all places where you accept face-to-face card payments: City and Airport offices, Check-In, Gate, Kiosks, on board sales, etc..</li><li>For indirect distribution channels through IATA BSP such as GDS and NDC: ensure that all channels support 3DS and EMV and upgrade to <a href="https://www.iata.org/publications/Pages/bspdish.aspx">DISH 23</a>, which contains these records. You might want to closely monitor non-compliant transactions, eventually issuing Agency Debit Memos (ADMs) if a Travel Agency does not apply SCA.</li></ul><p>Also in general the airline revenue accounting software might need to be updated to support 3DS and EMV records, and to transmit the authentication data to your acquiring bank for clearing and settlement. This is the proof that they payment was authenticated.</p><h4>SCA compliance for Travel Agencies</h4><p>As a Travel Agency processing cards payments through BSP on behalf of European airlines:</p><ul><li>For the E-Commerce channel: Implement 3DS. If you have the capability to identify the card country, you might decide to activate 3DS only for European cards and airlines with European acquirers. For NDC, <a href="https://airtechzone.iata.org/docs/ImpForum/YMQ19/ADS%20Airline%20Brief%203DS.pdf">IATA recommends</a> to implement the release version 19.2 which is compatible with 3DS version 2.</li><li>For the face-to-face channel: to our knowledge there is no commercially available solution for travel agency bookings through GDS using a multi-merchant EMV Chip&amp;PIN device but some actors are working on it. In the meanwhile you might want to stop accepting European cards in the GDSs, and rather accept them on a Chip&amp;PIN device from your bank.</li></ul><h3>Conclusion</h3><p>The European SCA requirement is helping payments to be more secure, ultimately reducing the cost of accepting payment for the industry. However, SCA brings unique challenges to the Airline Distribution landscape. Due to the IATA BSP structure, many Travel Agencies worldwide are also impacted without knowing it.</p><p>Both airlines and travel agencies need significant investments in the payment area to be compliant with this directive. Will they be ready on September 14th, 2019? The clock is ticking.</p><p><em>Disclaimer: This article has been written with the best of our knowledge, but each situation and jurisdiction being unique we strongly advise if you are impacted to consult your lawyers. If you have any concern or question, feel free to reach out at consulting@noath.net.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1ccf8eb63ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The forgotten digital piece for travel companies: augmented communication]]></title>
            <link>https://medium.com/@thetraveltech/the-forgotten-digital-piece-for-travel-companies-augmented-communication-4ee7b4ee1791?source=rss-1dabba54f3a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ee7b4ee1791</guid>
            <category><![CDATA[airlines]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[customer-service-success]]></category>
            <category><![CDATA[travel-technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[The Travel Tech]]></dc:creator>
            <pubDate>Thu, 12 Jul 2018 12:04:37 GMT</pubDate>
            <atom:updated>2018-07-13T17:40:25.419Z</atom:updated>
            <content:encoded><![CDATA[<p>When it comes to digital, most travel companies think they have done a great job when they have a <em>website</em> and a <em>mobile app</em>. This is not enough.</p><p>In this article I will explain how travel companies can take advantage of the recent developments in technologies such as Chatbots, Machine Learning and Voice Recognition to improve their digital communication towards their customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aAXkqX-3cNpp0EGaXCplFg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/71CjSSB83Wo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Pavan Trikutam</a> on <a href="https://unsplash.com/search/photos/communication?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Websites and mobile applications are doing a great job when it comes to sale and servicing, but there is one piece missing and it is when things start to go wrong:</p><ul><li>Who can answer my specific doubt before completing the purchase?</li><li>How can I get information when there is a disruption like <a href="https://en.wikipedia.org/wiki/2010_eruptions_of_Eyjafjallaj%C3%B6kull">a volcano eruption</a> or, maybe more common, a strike?</li><li>When I have an error during my purchase, how can I know if my booking is confirmed or not? Am I going to be charged?</li></ul><p>During my career in the travel technology industry, I have also witnessed several high-impacts unexpected events, ranging from a website being down to <a href="https://www.independent.co.uk/news/business/news/british-airways-system-outage-it-worker-power-supply-switch-off-accident-flights-delayed-cancelled-a7768581.html">flights unable to take off</a>. And in such situations it always comes down to one thing: all the workload is shifted to the help desk and support agents.</p><p>For the traveler, it is also a painful experience to wait for an handling agent, pay the phone cost which could be international; or if the contact is through email to wait often a full day for an answer. I experienced first hand to wait 5 hours standing in a queue in the airport to get a new seat and an hotel voucher, and it was absolutely no fun.</p><p>When they are desperate for an answer, passengers are also turning to social media, threatening the company public image if the case is not properly handled.</p><p>I believe there is a big missed opportunity here to provide a proper <strong>augmented digital communication</strong>, in a proactive way.</p><p>The benefits of a good communication are:</p><ul><li><strong>Higher conversion rates</strong>: passengers are more likely to complete the purchase if they have the full details of the service that is going to be provided to them.</li><li><strong>Customer Retention</strong>: by caring about their customers, travel companies are building trust, and therefore loyalty.</li><li><strong>Brand Image</strong>: An issue that is well handled will turn the traveler in a promoter.</li></ul><p>Travelers are also expecting a fast answer in case of issues, <a href="http://info.boxever.com/travel-consumer-survey-infographic">a study by Boxever</a> shows that 60% of travelers expect an answer within 30 minutes in case of issues. People are also more patient when they know when the situation is going to be fixed compared to when no timeline indication is given.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AtkN2_Kcob5Gw_IAUA0kGA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/Ae5jmF2PJXg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jens Johnsson</a> on <a href="https://unsplash.com/search/photos/airport-phones?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>One could think that in practice, building a proper communication toward customers is hard and it can skyrocket your call center and support agent costs. How can you propose a solution in less than 30 minutes to the 500+ passengers of a canceled A380–800 flight?</p><p>This is not a dream anymore and while a proper investment is still needed, new technologies like Machine Learning, Artificial Intelligence, Natural Language Understanding &amp; Processing, Chatbots and Voice technologies can answer this challenge.</p><p>OK, these are a lot of buzz words together, but behind the hype there are concrete solutions usable today for travel companies to build an augmented, digitally powered, communication approach towards their customers.</p><h3>Chatbots solutions tailored to the Travel Industry</h3><p>A few companies understood the challenge of the travel industry, and built some chatbots aiming at answering the most common use cases.</p><p><a href="https://www.caravelo.com/">Caravelo </a>has a chatbot solution tailored to the airline industry, with the ability to answer completely some use cases. See for example this applied use case for Finnair requesting a flight status over Facebook Messenger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*o8q-90h2IByn98K3Zb2hgg.gif" /><figcaption>Finnair Flight Status query handled by a Facebook Messenger chatbot (by Caravelo)</figcaption></figure><p>Another company, <a href="https://www.travelaer.com/">Travelaer</a>, also provides a similar tool with even a deeper integration into the travel industry, using various APIs from Air, Car and Hotels. The below example shows an example of a check-in being completed over a Facebook Messenger chatbot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*-_akLItytwTtZMwTc9dgWw.png" /><figcaption>Icelandair boarding pass generated by a Facebook messenger chatbot (by Travelaer)</figcaption></figure><p>You will notice when trying these Chatbots that they do not try to blur the lines between a real human and a robot: they set the expectations presenting themselves as Virtual Assistant and inform upfront of what they can do or not.</p><h3>Empowering and not replacing support agents</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3vlxneAo50hBQYOZbT_ug.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/2EJCSULRwC8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alex Knight</a> on <a href="https://unsplash.com/search/photos/machine-learning?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The first thing to clarify is that the technology and its acceptance by humans<a href="https://www.theguardian.com/technology/2018/jul/06/artificial-intelligence-ai-humans-bots-tech-companies"> is not in a state</a> where it can replace the <em>human touch. </em>In my opinion<em>, </em>answers to emotions and frustrations during a travel disruption can not be taken care of by robots at the moment.</p><p>What the technology can already do is to extract intents from a conversation, understand the contextual information, automatically gather traveler related information from APIs and formulate the result of the action.</p><p>What I believe is the good solution is an hybrid product, with robotic helping human agents to be more efficient.</p><p>There are three possible levels of virtual assistant handling:</p><ol><li><strong>End-to-End Handling</strong>: The virtual assistant is able to answer to the customer inquiries autonomously. At the beginning, it can be only simple queries like product information, and more and more cases can then be handled. Of course the objective would be to handle as much cases as possible. In the airline industry some providers are claiming they can reach a rate of 60-80% of queries being handled end-to-end by a virtual assistant.</li><li><strong>Semi-Automatic handling</strong>: In this configuration, the virtual assistant can already <em>extract information </em>and <em>prepare possible answers.</em> This saves time for the agent that does not need to type the answers in most cases, does not have to search for the information in different places but still allow corrections and amendments to be made. This configuration can be used to train the virtual assistant using machine learning.</li><li><strong>Human Hand-Over</strong>: In this configuration, the virtual assistant has understood that the it can not handle the conversation and hands-it over to a human agent.</li></ol><p>The virtual assistant should start new conversations trying to handle it end-to-end. it should also measure it’s confidence and be able to switch to a semi-automatic or hand-over mode when its limits are reached: when the conversation takes too long or when the customer shows signs of emotions like special words, punctuation, sarcasms.</p><p>One such solution is <a href="https://mezi.com/">Mezi</a>, the AI-powered chat-based travel assistant. Mezi claims that 60% of all their flights requests are answered by Chatbots. They also <a href="https://web.archive.org/web/20180130175255/https://mezi.com/travel-dashboard">mentioned </a>the agent productivity increased 5x while the training costs were down from a matter of months to days. Unfortunately with their recent acquisition by American Express, it is not clear if such technology would be available for other travel providers such as Car Rental companies, Hotels and Airlines.</p><h3>Smart up-selling</h3><p>With such tool, it is also possible to propose additional services to the customers at the right moment. Is the passenger concerned about the time to go the airport? Likely after providing the right information it is the good time to propose a priority pass. Have you just said that the layover is several hours? The passenger will see the value for a lounge access.</p><p>With frequent interactions with the customers, virtual assistants can also learn about their preferences and automatically propose the right options. Is the passenger always flying with his pet? Maybe after booking you could inquire if he is traveling with his pet again and would like to buy this service.</p><p>In the recent past, such scenarios were almost impossible to implement but with a proper Customer Relationship Management (CRM) solution and automated conversations, you can now proactively propose relevant ancillary services to your customers at the right time. Ultimately this could convert your service center in a selling machine too!</p><h3><em>Voice</em> is the next step</h3><p>If you haven&#39;t yet seen the Google Duplex demo during the Google IO conference check-it out now: robots can already make phone calls and interact with humans to execute simple tasks without humans noticing it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dbd1mEm2Fy08&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fbd1mEm2Fy08&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b135a07c2e9d691397872e99737375a7/href">https://medium.com/media/b135a07c2e9d691397872e99737375a7/href</a></iframe><p>We can already feel that in a few years for now, voice assistants are going to be on the front-line of Service Desks, with the ability to hand-over the conversation to a human for more complex cases just like chatbots are already doing today.</p><p>In conclusion, it is the right time for travel companies to invest in an augmented communication with their customers. This communication should place virtual assistants in the front line of customer interactions, with the ability to shift to a human agent when needed.</p><p><em>Did you liked this article? Please clap or comment! If you are a travel company and would like to exchange deeper on this subject or other travel technologies, feel free to get in touch at consulting (at) noath.net</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ee7b4ee1791" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Could blockchain technology replace GDSs and BSPs for Airline ticket distribution?]]></title>
            <link>https://medium.com/@thetraveltech/could-blockchain-technology-replace-gdss-and-bsps-for-airline-ticket-distribution-d806c7ac668d?source=rss-1dabba54f3a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d806c7ac668d</guid>
            <category><![CDATA[airlines]]></category>
            <category><![CDATA[travel-agency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[gds]]></category>
            <dc:creator><![CDATA[The Travel Tech]]></dc:creator>
            <pubDate>Sat, 27 Jan 2018 16:27:48 GMT</pubDate>
            <atom:updated>2019-07-14T18:48:12.774Z</atom:updated>
            <content:encoded><![CDATA[<p>The Airline industry is fascinating for the collaboration that can happen between Airlines. Even when they are in fierce competition, many airlines are willing to work together if this can help to cut down the costs.</p><p>In the early 80’s many travel agencies were still relying on flights listing and had to call each airline to book flights. Airlines found out that this was not cost effective and started to build, mainly within the International Airline Transport Association (IATA), the infrastructure to automatize the reservation processes for Travel Agencies.</p><p>In today’s world, Travel Agency sales are organized around a few actors:</p><ul><li><em>Global Distribution Systems (GDS)</em> as the tool to book in real time the seats;</li><li><a href="http://www.iata.org/services/finance/clearinghouse/Pages/index.aspx"><em>IATA Clearing House (ICH)</em></a> as the tool to handle netting between all participants: between Airlines for interlining, between Airlines and Travel Agencies for ticket sales; and also between Airlines and Airports Handling Agents for all airports operations;</li><li><a href="http://www.iata.org/services/finance/bsp/Pages/index.aspx"><em>Billing and Settlement Plan (BSP)</em></a> (or ARC in the US) for settlement of sales from Travel Agents to Airlines.</li></ul><p>With the fast evolution of technologies, are these actors —established in the 70’s or 80’s — still relevant?</p><h3>Current Airline distribution landscape</h3><p>In the travel industry, a significant portion of the airline tickets sales are handled through Travel Agencies. You have of course the long tail of brick-and-mortar Travel Agencies, but also the Online Travel Agencies (OLTA), or Travel Management Companies (TMC) for businesses.</p><p>For the large majority, Travel Agencies are issuing airlines tickets through Global Distribution Systems (GDS), namely Sabre, Amadeus and Travelport. The Billing and Settlement Plan (BSP), or Airlines Reporting Corporation (ARC) in the US, is an essential piece to allow accounting and financial processes between the involved parties. This is a huge and truly global mechanism, <a href="https://www.iata.org/services/finance/bsp/Pages/index.aspx">according to IATA</a>:</p><blockquote>There are BSP operations in some 180 countries and territories. The system currently serves approximately 400 participating airlines with an on-time settlement rate of 100%. In 2016, IATA’s BSP processed $219.0 billion.</blockquote><p>The BSP allows two type of payments at the time of the sale:</p><ul><li>The Travel Agency can decide to be <em>Merchant of Record</em> for the transaction, which means that they will collect the money and pay the airline later</li><li>The Travel Agency can decide to let the airline be <em>Merchant of Record</em>, passing the traveller&#39;s payment information (in general a Credit Card), to the airline. The airline gets the money directly and pays later a commission to the agent.</li></ul><p>The BSP system is tight to the IATA Clearing House (ICH) that automatically does the accounting between the participants: at the end of a billing period, each participant receives a single Credit or a Debit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/0*PpKLYbXMytOu3KKC." /><figcaption>Overview of the BSP model for sales reporting</figcaption></figure><p>While the BSP system is great as an enabler, it comes with a number of limitations:</p><ul><li><strong>Accreditation</strong>: In order to participate in the BSP system, Travel Agents must undergo a <em>strong financial review</em> and <em>lock-in funds</em> in order to avoid a situation where a Travel Agent would sell a lot of tickets and go bankrupt. This basically means that it’s very difficult for some companies or start-up to get an IATA accreditation.</li><li><strong>Delayed payments</strong>: Payments through the BSP are done at the end of a billing period, which can cause some <em>cash-flow issues</em> for the Travel Agencies or Airlines. For example a Travel Agency doing 100% of airline-merchant sales will get paid its commission only after the billing period (eg: one month). This can be mitigated by balancing the number of transactions done in either of the <em>Merchant of Record</em> modes; at the cost of an additional complexity.</li><li><strong>Limited Methods of Payments</strong>: To guarantee compatibility between the large number of participants, the number of payment options in the airline-merchant mode is limited: the large majority is Credit or Debit Card, and only a few airlines accept something else than Visa, MasterCard or American Express. <a href="https://www.ideal.nl/en/">Ideal</a>? <a href="https://intl.alipay.com/">Alipay</a>? Naah, use the travel agency merchant model.</li></ul><p>Bottom Line: the barrier to entry for small companies and startups willing to create a Travel Agency is really high, innovation is limited in this space.</p><h3>With NDC BSPs are still alive but GDSs become Aggregators</h3><p>Travel Agencies and Airlines have always been searching for mechanisms to get out of the GDS &amp; BSP system as much as possible. In a given country, a local Travel Agency can partner directly with the leading airline in this country and sell directly tickets through a dedicated portal provided by the Airline. Of course this does not scale for Travel Agencies operating globally or selling international tickets.</p><p>Recently, Airlines have been pushing through IATA the <a href="http://www.iata.org/whatwedo/airline-distribution/ndc/Pages/default.aspx">New Distribution Capabilities (NDC)</a> XML standard in an effort to allow more direct connections between Travel Agencies and Airlines, in particular for ancillary services.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FRru0RgWxtqQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DRru0RgWxtqQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FRru0RgWxtqQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7318e8ee3b647c413a6658a7cba09987/href">https://medium.com/media/7318e8ee3b647c413a6658a7cba09987/href</a></iframe><p>Ironically, GDSs have been quick in embracing the <em>Aggregator</em> role and pass the IATA NDC Certifications. Strange? If you think about it, NDC is a technical enabler but it does not scale-up on the business side: Travel Agencies, in particular in the long tail, can not establish a direct connection and business relationship with any airline in the world!</p><p>Did NDC killed the BSP model? Well no, because it is still required to manage the accounting between Travel Agencies and Airlines, the only difference is that Airlines (the Offer Responsible Airline, ORA in NDC world) can now submit sales to the BSP. Also as a side note the IATA Clearing House is still a key element in NDC for interlining, see <a href="https://www.iata.org/whatwedo/airline-distribution/ndc/Documents/ndc-revenue-accounting-guide.pdf">this report</a>.</p><h3>Blockchain for airline ticket distribution</h3><p>For any blockchain enthusiast, all these accounting and settlement processes between Airlines and Travel Agencies could be a perfect fit for the blockchain:</p><ul><li>Decentralized trust between many parties, no more accreditation needed</li><li>Inventory search-able and book-able with smartcontracts</li><li>Instant Payments and currency conversions with cryptocurrency</li><li>Travel Agent in control of the payment methods</li><li>Easier to access for small companies and innovative startups</li></ul><p>In my opinion it is no more a matter of <strong><em>if</em></strong>, but a matter of <strong><em>when </em></strong>and <strong><em>how.</em></strong><em> </em>Multiple players could be well positioned to tackle this challenge:</p><ul><li><a href="http://www.travacoin.com/">Travacoin</a> obtained an Passenger Innovation Awards at IATA’s World Passenger Symposium in Dubai in October 2016 for compensation vouchers. Could it be an hidden IATA Proof of Concept ?</li><li><a href="http://uatp.com/">UATP</a>, a major player in airline payments, has integrated <a href="https://www.coindesk.com/bitcoin-bitnet-260-airlines-uatp/">bitcoin payments since 2015</a>.</li><li><a href="https://windingtree.com/">Winding Tree</a> is creating an open-source decentralized distribution platform for Travel <em>(see my </em><a href="https://medium.com/@thetraveltech/a-winding-tree-tutorial-3273504aec4c"><em>tutorial</em></a><em> to see how it works for Hotels)</em>, and partnered with major airlines <a href="https://newsroom.lufthansagroup.com/English/Press-Releases/lufthansa-group-partners-up-with-winding-tree-to-bring-blockchain-technology-to-the-travel-industry/s/16fc8ce5-4656-41ee-a6b2-026441ba19b6">such as Lufthansa</a>.</li><li>Any other?</li></ul><p>It will take some time before we observe a complete shift to the blockchain for airlines ticket distribution and there are some major technical challenges to solve first. However knowing the history of collaborations between airlines, we might have some surprises!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d806c7ac668d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Winding Tree tutorial]]></title>
            <link>https://medium.com/@thetraveltech/a-winding-tree-tutorial-3273504aec4c?source=rss-1dabba54f3a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3273504aec4c</guid>
            <category><![CDATA[winding-tree]]></category>
            <category><![CDATA[hotel]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[The Travel Tech]]></dc:creator>
            <pubDate>Sat, 20 Jan 2018 17:36:54 GMT</pubDate>
            <atom:updated>2019-07-14T16:55:56.838Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Editor Note:</em></strong><em> This story was originally published on January 20th, 2018. Since then, the Winding Tree project has progressed significantly and published official tutorials on </em><a href="https://developers.windingtree.com/"><em>https://developers.windingtree.com/</em></a><em>. This tutorial and its conclusions are mostly outdated, the story is kept only for reference.</em></p><p>There is one project that really caught my eye in the travel industry recently which is <a href="https://windingtree.com/">Winding Tree</a>. This open-source project aims at nothing less than replacing the backbone of the travel industry by a blockchain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MHNag4hkCcY-E7z2.jpg" /></figure><p>According to their <a href="https://windingtree.com/files/White%20Paper_EN_nov21.pdf">white paper</a>:</p><blockquote>Five companies in the travel industry control the most of the travel market. The two largest OTAs (Online Travel Agencies), Priceline Group and Expedia Inc., control 95% of OTA market in the U.S. Amadeus, Sabre, and Travelport, the top three GDSs (Global Distribution Systems), have 99% combined market share in non-direct inventory in the air market.</blockquote><p>Boom, problem stated. And they partnered with some big names like Lufthansa Group. As someone working in the travel technology area I had a lot of questions: how the project team plans to disrupt a trillion dollar industry? How the economics work? How do they solve the technology challenges? In order to get answers to my questions, I decided to get a first hand experience, experiment with the open source code they have released and share my feedback in a tutorial.</p><p>For this tutorial we are going to use the Minimum Viable Product (MVP) for hotels that is available on Winding Tree’s <a href="https://github.com/windingtree">Github</a>. It is expected to change a lot but that’s already good to get an understanding of the potential of the technology.</p><p>Our goal will be to:</p><ul><li>Create an Hotel on the blockchain with one room</li><li>Book this room for 5 days.</li></ul><p>We will need some tools to interact with the smart contracts: <a href="https://git-scm.com/">git</a>, <a href="https://nodejs.org/">node</a> (≥7.6), <a href="https://www.npmjs.com/">npm</a> and <a href="http://truffleframework.com/">truffle</a>. If you don’t have them already just follow the instructions from their respective pages.</p><p>We clone the contracts and install the dependencies:</p><pre>$ cd /tmp<br>$ git clone https://github.com/windingtree/wt-contracts --recursive<br>$ cd wt-contracts<br>$ npm install</pre><p>We just want to test the contracts without actually interacting with the live blockchain, so we will use a specific <em>testrpc</em> server that simulates the blockchain and brings some benefits:</p><ul><li>We don’t have to pay real money to interact with the blockchain,</li><li>We do not have to synchronize all the blockchain on our computer,</li><li>We do not need to wait for the mining processes</li></ul><p>In a live environment we would need first to to import our Ethereum account address on the Ethereum node and unlock it using the private key, but here <em>testrpc</em> has already unlocked the first account for us.</p><p>Also Truffle has a Javascript interpreter with a web3 provider injected, so for the purpose of this tutorial we will simplify the setup and just execute Javascript code in the command line. The same code could be run by a Node.js server or in a Web Browser.</p><p>We enter the truffle development console:</p><pre>$ truffle develop<br>Truffle Develop started at <a href="http://localhost:9545/">http://localhost:9545/</a></pre><pre>Accounts:<br>(0) 0x627306090abab3a6e1400e9345bc60c78a8bef57<br>(1) 0xf17f52151ebef6c7334fad080c5704d77216b732<br>(2) 0xc5fdf4076b8f3a5357c5e395ab970b5b54098fef<br>(3) 0x821aea9a577a9b44299b9c15c88cf3087f3b5544<br>(4) 0x0d1d4e623d10f9fba5db95830f7d3839406c6af2<br>(5) 0x2932b7a2355d6fecc4b5c0b6bd44cc31df247a2e<br>(6) 0x2191ef87e392377ec08e7c08eb105ef5448eced5<br>(7) 0x0f4f2ac550a1b4e2280d04c21cea7ebd822934b5<br>(8) 0x6330a553fc93768f612722bb8c2ec78ac90b3bbc<br>(9) 0x5aeda56215b167893e80b4fe645ba6d5bab767de</pre><pre>Mnemonic: candy maple cake sugar pudding cream honey rich smooth crumble sweet treat</pre><pre>truffle(develop)&gt;</pre><p>Truffle automatically starts an Ethereum node and creates some test accounts for us with free ETH (unfortunately only valid within our <em>testrpc </em>instance) and we have the mnemonic associated. During the tutorial we will not bother to change accounts for the different roles: WT Foundation, Hotel Manager, Travel Agency.</p><p>Let’s compile the contracts:</p><pre>&gt; compile<br>&gt; deploy</pre><p>We are now ready to start using the Winding Tree contracts!</p><p>Here is a very simplified diagram showing the contract hierarchy:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/172/0*2_9vraNeOsXH7GiS." /><figcaption>WT Hotel MVP Contract Hierarchy (simplified)</figcaption></figure><p>The <em>WTIndex</em> contract is at the root of the hierarchy and created by the Winding Tree Foundation. For this tutorial, our <em>testrpc</em> instance completely simulates the Ethereum blockchain so the contract does not exist and we need to create it:</p><pre>&gt; WTIndex.new().then(instance =&gt; wt = instance)</pre><p>In a real Ethereum network, we should now wait for the transaction to be picked up by an Ethereum miner, have it included in a block and confirmed several times. However here thanks to our magic <em>testrpc</em> node we do not have to wait and we can get the contract address immediately:</p><pre>&gt; wt.address<br>&#39;0xf25186b5081ff5ce73482ad761db0eb0d25abfbf&#39;</pre><p>Great, our <em>WTIndex</em> contract is now deployed!</p><p>Now that we have our <em>WTIndex</em> contract, let’s create an <em>Hotel</em>.</p><p><em>Hotels</em> contracts are created automatically by the <em>WTIndex</em> contract when calling the <em>registerHotel()</em> function. They are not supposed to be deployed directly by the Hotel manager, and they are owned by the <em>WTIndex</em>.</p><pre>&gt; wt.registerHotel(&#39;My Hotel&#39;,&#39;A very nice Hotel&#39;)</pre><p>We can check that we have our hotel created by calling some other functions, for example to filter only the hotels we manage from the current ethereum account:</p><pre><br>&gt; wt.getHotelsByManager(web3.eth.coinbase)<br>[ &#39;0xf2beae25b23f0ccdd234410354cb42d08ed54981&#39;]</pre><p>The Hotel Contract is created and we have its address. Let’s create a variable <em>h</em> with the instance for convenience:</p><pre>&gt; wt.getHotelsByManager(web3.eth.coinbase).then(addr =&gt; h = Hotel.at(addr[0]))</pre><p>Let’s check that we are able to access the name and description:</p><pre>&gt; h.name()<br>&#39;My Hotel&#39;<br>&gt; h.description()<br>&#39;A very nice Hotel&#39;</pre><p>Cool we have an hotel, but our hotel is completely empty. This is like just having the land without having started the construction. We now need to create rooms and describe how the rooms are like.</p><p>For this, we will create a <em>UnitType</em> and a <em>Unit</em> for our room. Contrary to what we did for the Hotel which was created by the <em>WTIndex</em> contract, we need to deploy these contracts ourselves, and we need to give the ownership to the Hotel address.</p><p>Let’s create a Basic Room:</p><pre>&gt; UnitType.new(h.address, &#39;BASIC_ROOM&#39;).then(i =&gt; ut = i)<br>&gt; Unit.new(h.address, &#39;BASIC_ROOM&#39;).then(i =&gt; u = i)</pre><p>Now to add the <em>Unit</em> and <em>UnitType</em> in your <em>Hotel</em>, the trick is the <em>Hotel</em> contract is not owned by our address but by the <em>WTIndex</em> contract. If we attempt to modify it, we will be rejected:</p><pre>&gt; h.addUnitType(ut.address)<br>Error: VM Exception while processing transaction: invalid opcode</pre><p>To add the <em>UnitType</em> and <em>Unit</em>, and in general for all modifications to the Hotel contract, we will need to use the <em>callHotel()</em> function. Fortunately this is protected so that only us as manager can call this function:</p><pre>&gt; wt.callHotel(0, h.contract.addUnitType.getData(ut.address))<br>&gt; wt.callHotel(0, h.contract.addUnit.getData(u.address))</pre><p>To accept bookings, hoteliers have two options:</p><ul><li><strong>Instantly</strong> with Winding Tree native token LIF</li><li>With a <strong>confirmation</strong> mechanism with other payment options.</li></ul><p>For this tutorial we will use the confirmation mechanism, so let’s configure it:</p><pre>&gt; wt.callHotel(0, h.contract.changeConfirmation.getData(true))</pre><p>All set! Our Hotel is created and we are ready to receive bookings from customers! Please note that here we have over simplified the process as naturally we would need to customize the room with description, amenities, price, availability, images, and so on.</p><p>Now switching perspective, we will assume we are a Travel Agency (or a very tech-savvy traveller!) and we are going to book the hotel room we created.</p><p>Searching for Hotels requires a great deal of indexing in order to avoid duplicated entries, and be able to find the hotel prices, availabilities and amenities in line with the traveller expectations. The current design is quite simple with one index containing all hotels addresses but we can safely assume better indexing mechanisms will be available in the future (for example a tree with countries and cities). <strong>The search itself is completely free and fast</strong> as all the inventory data is decentralized in each Ethereum node and is only a read access. If you think about it, that’s a great deal for both Travel Agencies and Hotels!</p><p>For this tutorial we will assume we already found the hotel and unit we would like to book (that’s easy we have only one!).</p><p>In the Winding Tree ecosystem the reservation is made of two parts:</p><ul><li>A <strong>private </strong>one with the guest details</li><li>A <strong>public </strong>one with the details of the hotel being booked and the dates.</li></ul><p>The private one is not specified yet, but the idea is that it’s a JSON structure. An example of such structure freely inspired from the Winding Tree code repository could be:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/460410035cace24db1e222619f52a26b/href">https://medium.com/media/460410035cace24db1e222619f52a26b/href</a></iframe><p>There’s a technical detail here: potentially not all hotels will require the same data and accept the same payment methods so how can the Travel Agency know which fields are mandatory or not?</p><p>The decision by the Hotelier to accept or not the booking based on the private data is not relevant for this tutorial, so let’s simply consider an arbitrary string for now.</p><p>The mechanism to book is based on <a href="https://media.consensys.net/technical-introduction-to-events-and-logs-in-ethereum-a074d65dd61e">Ethereum Events</a> which allow asynchronous interactions over the blockchain. The Travel Agency can initiate the booking request and this creates an event:</p><pre>&gt; privateData = &quot;PRIVATE_GUEST_DATA&quot;<br>&gt; publicData = h.contract.book.getData(u.address, web3.eth.coinbase, 20150, 5)<br>&gt; h.beginCall(publicData, privateData).then(i =&gt; beginCalltx = i)</pre><p><em>Note: 20150 is the number of day after January 1st,1970: March 3rd, 2025</em></p><p>The Hotel can <em>watch</em> the blockchain for booking events. When an event is received, the Hotel can retrieve the public and private details:</p><pre>&gt; abiDecoder = require(&#39;abi-decoder&#39;)<br>&gt; abiDecoder.addABI(Hotel._json.abi)<br>&gt; beginCallEvent = abiDecoder.decodeLogs(beginCalltx.receipt.logs)[0]<br>&gt; beginCalltxCode = web3.eth.getTransaction(beginCalltx.tx).input<br>&gt; transferDecoded = abiDecoder.decodeMethod(beginCalltxCode)</pre><pre>&gt; abiDecoder.decodeMethod(transferDecoded.params[0].value)<br>{ name: &#39;book&#39;,<br>  params: <br>   [ { name: &#39;unitAddress&#39;,<br>       value: &#39;0xf25186b5081ff5ce73482ad761db0eb0d25abfbf&#39;,<br>       type: &#39;address&#39; },<br>     { name: &#39;from&#39;,<br>       value: &#39;0x627306090abab3a6e1400e9345bc60c78a8bef57&#39;,<br>       type: &#39;address&#39; },<br>     { name: &#39;fromDay&#39;, value: &#39;20150&#39;, type: &#39;uint256&#39; },<br>     { name: &#39;daysAmount&#39;, value: &#39;5&#39;, type: &#39;uint256&#39; } ] }</pre><pre>&gt; web3.toAscii(transferDecoded.params[1].value)<br>&#39;PRIVATE_GUEST_DATA&#39;</pre><p>And accept the booking:</p><pre>&gt; pendingCallHash = beginCallEvent.events[1].value<br>&gt; wt.callHotel(0, h.contract.continueCall.getData(pendingCallHash))</pre><p>Everyone can then see that this room is booked for that day and by which address, and it can not be booked again:</p><pre>&gt; u.getReservation(20150)<br>[ BigNumber { s: 1, e: 0, c: [ 0 ] },<br>  BigNumber { s: 1, e: 0, c: [ 0 ] },<br>  &#39;0x627306090abab3a6e1400e9345bc60c78a8bef57&#39; ]</pre><pre>&gt; h.beginCall(publicData, privateData)<br>Error: VM Exception while processing transaction: invalid opcode</pre><p>Success!</p><p>In this tutorial, we have seen how to use the Winding Tree MVP Contract for Hotel and we have been able to get a feeling of the potential of the platform.</p><p>Yet a number of points are still open and require further developments from the Winding Tree team and its community:</p><ul><li><strong>Scalability</strong>: The current cost to setup an hotel is quite high (in gas fees) as we need to send multiple transactions to create each unit type and units and configure them. Frequent updates to the inventory are also required when some works are being done in a given room. A descriptive file stored out of the contract for example in IPFS or SWARM would be much better. Also some general evolutions of Ethereum with the move to <a href="https://github.com/ethereum/wiki/wiki/Proof-of-Stake-FAQ">Proof-of-Stake</a> and <a href="https://blog.windingtree.com/lif-token-state-channels-1dc2629617f0">State Channels</a> should greatly improve the situation.</li><li><strong>Privacy</strong>: With the current mechanism, it’s relatively trivial with the Hotel Contract ABI to retrieve the guest private data. We have voluntary put in the example a credit card to raise the question of <a href="https://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard">PCI-DSS</a> Compliancy. There is also <a href="https://en.wikipedia.org/wiki/General_Data_Protection_Regulation">GDPR</a> in Europe. How is this data going to be secured? Also some Travel Agencies have private rates as a result of business negotiations, should this data be public?</li><li><strong>Duplicates and Fake listings: </strong>Nothing prevents a bad actor to create a fake Index, fake Hotels and so on. They can even generate a lot of dummy reservations to make it appear legit. How is the Travel Agency and ultimately the traveler protected from this situation? It’s not acceptable to have a traveler getting to an Hotel to find there is nothing here, or worst. Any serious implementation will need to put in place a great deal of measures to ensure they have the good contract address to an hotel that do exist in the physical world.</li></ul><p>My personal opinion is that the platform in itself does work even if there are many challenges ahead. The platform could completely disrupt the Travel Industry in the coming years, wait and see!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3273504aec4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello World!]]></title>
            <link>https://medium.com/@thetraveltech/hello-world-7264745f7f7a?source=rss-1dabba54f3a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/7264745f7f7a</guid>
            <category><![CDATA[myself]]></category>
            <category><![CDATA[introduction]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[The Travel Tech]]></dc:creator>
            <pubDate>Tue, 16 Jan 2018 23:12:04 GMT</pubDate>
            <atom:updated>2018-01-16T23:12:04.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/520/0*Dy7IBNSVIg0BlWZq." /><figcaption><em>Illustration Image credit of </em><a href="http://opensource.com/education/15/9/apis-not-apps"><em>opensource.com</em></a></figcaption></figure><p>When following the tutorial of a new programming language, programmers are familiar with this simple yet outstanding output:</p><pre>Hello World!</pre><p>This is in general the point of the beginning of your travel. You took the time to investigate a technology, and found it useful for you. You wrapped your head around, you had to install tools and write your code. You made an effort to learn, you tried and this display is already the result of your <em>own</em> work.</p><p>You know these two worlds are simple and pretty much useless, however they mean already so much to you. You are feeling so great to read them!</p><p>They mean you have understood the surface of this new technology. You made the program be nice to you, and the world. You have a grasp on how the things are working.</p><p>They mean you understood what someone was teaching you when writing the tutorial. They mean someone took time to explain you, to share with the world in an effort to collaborate and improve the life of others, to improve <em>your</em> life.</p><p>You can find an <em>Hello World</em> in any programming language. This is an universal concept like saying <em>Hi!</em> to humans exists in any language.</p><p>An example in python:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d7b1c2dae1e0381dc23da93140f27874/href">https://medium.com/media/d7b1c2dae1e0381dc23da93140f27874/href</a></iframe><p>Yet while reading what you wrote, you know this is just the beginning. You have to write specific symbols to make the program talk. You already understand there are some new concepts you will need to investigate deeper and assimilate.</p><p>With this post I am also starting a new journey! I am passionate about travel and technologies, and after having learnt and tried on this subject during a long time, it is my turn to start to give back. It’s my turn to share on these complex and exciting subjects, hopefully in a way that makes it easier to understand: Hello World!</p><p>As background, I am Engineer and have been working directly or indirectly with many kind of travel technology providers: from Brick-and-Mortar Travel Agencies, to Global Distribution Systems, Tier-1 Airlines, Airports and major Hotel Chains.</p><p>I would like to share in the following publications several activities on topics I am investigating in the travel technology space, stay tuned!</p><p>I am starting this in an really open way, please excuse in advance the errors I might do: I just completed the <em>Hello World</em> and I am still learning! And feel free to contact me to provide feedback and share your views as well!</p><p><em>Disclaimer: Any content I am writing in this article and the following on Medium is my own opinion and is not related in any ways to companies I am working for or with.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7264745f7f7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>