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 Recording & supporting material

Attendees

Main Goal of this Meeting

Discussion of using accessing a Travel Profile as a self-asserted verifiable document (signed by traveler) which is accessed via a presentation protocol interface which is an extension of the W3C Presenation Protocol (for Verifiable Credentials, which is no longer on the W3C Standards track and is currently stalled. Discussion also includes the use of JAVA for the Travel Profile Schema, for the presentation request and resulting response to the verifier.

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.
  • New Members:
55 minsDiscussionAll

Summary: The meeting discussed challenges related to the W3C specification portfolio, particularly around presentation requests from verifiable documents like credentials. Neil Thomson highlighted a specific use case related to the Diff Traveler Profile group, emphasizing the need for a structured approach to managing and presenting personal data and preferences, especially in the context of travel.

Key Points Discussed:

  • The importance of layered schema approaches and JSON specification for crafting requests.
  • Discuss selective disclosure, sensitive data, and the legal implications of sharing personal information.
  • Insights into the travel profile concept, detailing how travelers might manage their information across various service providers.
  • Challenges associated with guardianship and delegation in digital identities, particularly concerning minors and dependent adults.
  • There is potential for dynamic and customized travel profiles to adjust preferences based on specific trips or conditions.

Action Items:

  1. Explore the implementation of layered schema and JSON for efficient data request crafting.
  2. Further investigate selective disclosure practices and develop guidelines for handling sensitive information.
  3. Develop a prototype or framework for travel profiles that can accommodate various personalization and privacy needs.
  4. Address the guardianship issue by consulting with industry stakeholders and reviewing regulatory requirements.
  5. Consider the feedback from the discussion in developing a document to present to relevant industry bodies like IATA and ICAO.

General Observations:

  • The travel industry's current handling of data privacy and guardianship is minimal, primarily driven by regulation rather than proactive measures.
  • There's a recognized need for better management of personal data by allowing travelers to control their profiles and preferences actively.
  • Challenges remain in defining the balance between data sharing for convenience and maintaining privacy and security.
  • The discussion underscored the complexity of implementing digital identities in the travel context, highlighting both technological and regulatory challenges.

Alternate summary (slightly different parameters)

Sankarshan Mukhopadhyay

  • Emphasized the importance of addressing privacy and customization in travel profiles. Discussed the complexity of implementing guardianship and delegation in digital identities, especially for minors and dependent adults. Mentioned discussions with Singapore Airlines about handling guardianship and the minimal steps taken by the airline industry due to regulations. Currently, airlines lean towards accepting guardianship documents from adults accompanying someone else, particularly minors. Unless there is something obvious in the guardian/dependent (clear distress of the dependent), the airline will not question the papers - which is a problem related to the trafficking of minors.

Neil Thomson

  • Focused on the gaps in the W3C specification portfolio, particularly around presentation requests from verifiable documents. Highlighted the need for structured data handling, using JSON and layered schemas. Raised issues around selective disclosure, data sensitivity, and legal implications. Proposed the concept of dynamic, customizable travel profiles to manage personal data across various service providers. Discussed the challenges of guardianship and data privacy from an industry perspective.

Carly Huitema

  • Shared thoughts on the challenges of managing travel profiles for minors and dependents. Suggested that travel profiles could undergo a "growth" similar to how phone usage is managed for children, becoming less restrictive over time. Highlighted the potential for creating generic profiles that could be customized based on individual needs.

Burak Serdar

  • We discussed the technical aspects of using JSON to manage travel profiles and the potential for dynamic schema negotiation. We also emphasized the flexibility of the layered schema architecture for selective disclosure and data exchange.

Summary of Key Points:

  • The discussion highlighted the need for improved data management in travel, focusing on privacy, selective disclosure, and the handling of sensitive information.
  • The concept of travel profiles was discussed extensively, focusing on dynamic customization and managing personal preferences across different travel service providers.
  • The challenges of guardianship and data privacy were acknowledged, with a particular emphasis on the complexities involved in digital identities for minors and dependent adults.
  • Technical discussions revolved around using JSON, layered schemas, and the potential for dynamic schema negotiation to facilitate selective disclosure and data privacy.

Supporting Material:

Human Colossus Overlays Capture Architecture

What is OCA

Layered Schema Architecture (Burak Serdar)

IIW 32 session on Layered Schemas for semantic Interoperability (on linkedIn)

Cloud Privacy Labs - Layered Schemas (github)

 - 



  • No labels