You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Meeting Date

The DMRWG meets bi-weekly on Tuesdays at 12:00-13:00 PT / 16:00-17:00 UTC. Check the ToIP Calendar for meeting dates.

Zoom Meeting Link / Recording

Attendees

Main Goal of this Meeting

Discussion on the DIF - Hospitality/Travel SIG → Travel Profile TF - Travel Profile proposal and impact on ToIP, SSI and Data Privacy

  • Travel planning is online first. In 2023, each travel service typically collects a traveller's profile (requirements and preferences) through a direct ask or via incremental collection via pages and questionnaires shaped by the travel, accommodation and "things to do" context. While nominally being asked (consent) to share personal information, in practice, services are over-gathering personal information, clarifying what information is necessary to provide the service vs. collecting information to benefit the service for targeted marketing and other purposes.
  • The current Travel Profile is quite a large model containing PII/Sensitive data far beyond most examples of PII, and is designed to capture requirements and preferences in many different contexts. It needs some work for formal modeling as objects and database schema, plus notes on how the model can safely be extended
  • How does this data model mesh with SSI, Verifiable Data, and Privacy, including across jurisdictions?
  • What are all the interaction models (workflows) and their impact on consent, selective disclosure, "intent" broadcasting?
  • What are the mechanisms for collection (direct ask and observed behavior) in different contexts, and who stores and controls that data?
    • Given that travel organizations are being faced with GDPR, for which holding onto personal data is becoming a liability, particularly for breaches, what does a future mechanism look like (traveler controlled, on-demand selective disclosure to services, very limited lifetime service data regetion) and what are the prospects for a smooth transition?

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
  • Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
50 minDiscussionAll

Background - The proposed Travel Profile TF is currently working on completing a first pass on a core information about a traveler plus looking at how requirements (must have) and preferences (desired options) apply against different travel, hospitality and attractions (things to do) contexts. Investigations have also explored how this model can be extended for more traveler information and additional contexts.

The next stages on the project is to look at this from two perspectives

  • How (raw data model) can be enhanced to support SSI and Data Privacy in general and DIF/ToIP in particular.
  • How interactions (and there are clearly several different depths of data sharing and interactions) work, including doing a first deep dive into what does a verifier (in this case a travel service) ask for required and optional personal information pertinent to a given travel event or travel service

It is proposed to look at three levels of purpose - Intent broadcasting, selective disclosure and consent (these last two are closely coupled). A partial definition of intent broadcasting would: put out a requirement for travel and accommodation, with sufficient information for a travel provider to be able to offer a "travel package", revealing as little PII as possible. More detailed inquiries and then finalization of travel plans likely requires increasing personal information, so consent that data, precisely how it can be used and it's lifetime storage needs to be determined to minimize the risks for both the traveler and the service provider.  

Key points from discussion:

To some extent looking at the travel profile is looking at concrete inter-actions of a traveler (Holder) on a non-trivial set of their personal data, interacting with a Verifier (travel service) , at different levels of depth, where an important consideration is ensuring that the Verifier/travel service is asking for a set of data, some of which is mandator for a service provider to provide and answer or a proposed service and other data is optional, which the traveller can chose not to provide. This may be tempered by the service offering additional benefits to the traveller if they disclose more information. However, that raises the issue of a traveller understanding the consequences of additional disclosure, including harms.  This is a good stress use case for real-life consent.


5 minPlans for 2024All




Screenshots/Diagrams (numbered for reference in notes above)

An older image of the traveler profile model


Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item


  • No labels