W3C home > Mailing lists > Public > semantic-web@w3.org > October 2020

Deadline Extended: Special Issue on Transport Data on the Web - Semantic Web Journal

From: David Chaves <dchaves@fi.upm.es>
Date: Thu, 1 Oct 2020 12:19:23 +0200
Message-Id: <CDB8788F-4D16-45EB-80EF-1B7B0050D235@fi.upm.es>
To: semantic-web@w3.org
Dear all,
We would like to inform you that the submission deadline for the Special Issue on Transport Data on the Web in the Semantic Web Journal <http://www.semantic-web-journal.net/blog/call-papers-special-issue-transport-data-web> has been extended until 1st of November 2020. Find below the details of the call for papers.


Mobility-as-a-Service (MaaS) integrates different transport services into a single mobility service. The goal is to provide a traveler with all the services needed for a door-to-door travel under a single payment whilst integrating disparate modes of mobility (public transport, car- or bike-sharing, taxi/car rental, or a combination thereof) under one travel experience. After years of conceptualization and strategizing, MaaS is becoming a reality. Different initiatives are creating specifications for route planning and ticketing APIs. As multiple companies can offer a way to get from A to B and validate a ticket, a “smart mobility” ecosystem is by definition decentralized, and Semantic Web technologies can thus excel for this use case.

Topics relevant to this special issue include – but are not limited to – the following:
	• Decentralized data management
		• Query languages and methods for a Web of Transport Data
		• Creating automated alignments between datasets using the various specifications
		• Recommendations for mobility specification builders to raise interoperability between specifications
		• Alignments with existing or upcoming general purpose Web API specifications such as W3C Web payments or SOLID
		• Interfaces between enterprise data and the Semantic Web
	• Exploitation of Transport Data on the Web
		• Challenges and opportunities for route planning and ticketing
		• Personalized route planning taking into account data stored on your client or personal data space
		• Anonymization in the mobility space for data sharing
	• Benchmarking of Web Infrastructure
		• Comparing ticketing API architectures
		• Comparing route planning API architectures
		• Publishing and querying planned transport data and their live updates on the Web
	• Knowledge Graphs and Ontologies in the transportation domain
		• Aligning regional vocabularies such as the Flemish Mobility specification or the Finnish reference vocabularies with international reference domain models such as Transmodel or DATEXII
		• Reusing existing linked datasets, such as Geonames, OpenStreetMap or Wikidata, for MaaS use cases
		• Bridging the gap with non-RDF specifications such as Mobility Data Specification, General Transit Feed Specification, General Bike Feed Specification, TOMP API or MaaS API.


Best regards,
 
David Chaves-Fraga, Universidad Politécnica de Madrid
Pieter Colpaert, Ghent University – IDLab – imec
Joshua Shinavier, Uber
Marco Comerio, Cefriel
Mersedeh Sadeghi, Politecnico di Milano


- - - -
David Chaves
PhD Student
Ontology Engineering Group (OEG)
Universidad Politécnica de Madrid


Received on Thursday, 1 October 2020 10:19:39 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:42:12 UTC