Tourism Data Spaces — From Exploration to Practice
This page documents my journey from attending FITUR 2026 in exploratory mode to becoming an active participant in the SEGITTUR LinX Tourism Data Space.
FITUR 2026 — What I Went Looking For
I attended FITUR in January 2026 with a specific focus on the SEGITTUR workshop on the National Tourism Data Space, confirmed as part of the official FITUR 2026 programme.
My objective was to understand how data spaces, interoperability frameworks, and data governance models were being implemented in the tourism ecosystem — particularly in the context of Smart Destinations and public–private collaboration.
I do not sell software or platforms. My background is in infrastructure modernisation, data workflows, and interoperability in complex industrial and regulated environments. FITUR was about observing whether those same principles were finding their way into tourism through a concrete initiative.
They were.
What Happened Next — LinX in Practice
Following FITUR, I participated directly in the SEGITTUR LinX Tourism Data Space, taking on two roles simultaneously:
- As a data provider: Defining and publishing tourism data endpoints following the LinX interoperability requirements.
- As a participant/consumer: Connecting to the space and querying data from other nodes.
Technical Implementation
The connector was built on a Cloudflare architecture using:
- Cloudflare Workers — serverless functions handling REST API request logic and authentication flows
- Cloudflare D1 — edge-native SQLite database providing low-latency data persistence aligned with the UNE 178503 taxonomy
This involved designing REST API endpoints that satisfied the LinX protocol requirements while remaining maintainable and deployable without traditional server infrastructure.
The Key Insight — Where Value Lives in Governed Data Spaces
The project surfaced an important structural observation:
When a government body absorbs the connector complexity, the value for participants shifts entirely to the data itself.
SEGITTUR's decision to offer the connector as a managed service (Connector-as-a-Service) significantly reduced the integration burden for participants. This is architecturally sensible for a national data space — but it also means that technical differentiation at the connector layer becomes largely irrelevant.
What matters instead:
- Quality and completeness of the data you bring to the space
- Semantic alignment with the shared taxonomy (UNE 178503 / SEGITTUR models)
- Operational reliability of your endpoints
- Understanding of what queries other participants will actually make
For independent consultants and small providers, this is a clarifying shift: the entry barrier drops, but the competitive advantage moves to domain knowledge and data governance, not infrastructure capability.
Areas of Continued Interest
- Data Space Governance Models: How public-sector anchor institutions shape participation dynamics
- Cross-sector Data Spaces: Applying lessons from tourism to energy, utilities, and industrial contexts
- Edge Architecture for Interoperability: Cloudflare Workers / D1 as a lightweight, deployable pattern for data space connectors
- Independent Technical Advisory: Supporting organisations evaluating participation in emerging data spaces
Professional Profile
Mario Pagés Independent Consultant — Energy Technology, Digital Infrastructure & Data Spaces
I bring a cross-sector technical perspective, combining direct implementation experience with advisory work across energy, tourism, and industrial digitalization.
"In governed data spaces, the real leverage is not in the plumbing — it is in what you know and what data you can offer."
Contact
- Email: [email protected]
- LinkedIn: linkedin.com/in/mario-pages
- Technical reference: digital.piy.es