ITS-EU Large-scale information sharing for the ITS domain

ITS-EU Large-scale information sharing for the ITS domain

25b6db9c0680e598186d819051ad9e4b?s=128

Pieter Colpaert

June 21, 2017
Tweet

Transcript

  1. PUBLIC Constraints for a large-scale ITS data sharing system Pieter

    Colpaert Peter Van der Perre, Dieter De Paepe, Thimo Thoeye, Ruben Verborgh, Erik Mannens
  2. None
  3. A service between 2 systems? Your system Third party system

    Agree on a protocol Will determine which questions can be answered Can ask fixed set of questions to your system
  4. Sharing data on the Web Your data ? ? ?

    ? ? ? = preparing your data for maximum reuse
  5. When do we need to maximize reuse? All parking spaces

    occupied Parking space available
  6. Option 1: a service https://api.{myservice}/nearestParkingLots

  7. Option 1: a service https://api.{myservice}/nearestParkingLots ?long={long} &lat={lat}

  8. Option 1: a service https://api.{myservice}/nearestParkingLots ?long={long} &lat={lat} &closeToTramToCenter

  9. Option 1: a service https://api.{myservice}/nearestParkingLots ?long={long} &lat={lat} &closeToTramToCenter &freeSpaceOnArrivalTime=17:00

  10. Option 1: a service https://api.{myservice}/nearestParkingLots ?long={long} &lat={lat} &closeToTramToCenter &freeSpaceOnArrivalTime=17:00 You

    cannot answer all questions for everyone
  11. Option 2: Idea of the Web – power to the

    clients https://{mydataserver}/parkings Cacheable documents, linked together. Smart clients download set of documents, regardless of server borders. Constraints 1. Stateless interaction 2. Cacheable documents 3. A uniform interface over HTTP ⇒ Following links to discover more information
  12. Option 2: remains functional for real-time data time Now

  13. New problem: semantic interoperability 1. Regarding identifiers Is there a

    documented global identifier that we can use or reuse? 2. Regarding domain model How do we document a “Parking Site” for machines? How do we know when 2 documents mean the same?
  14. 1 ⇒ URIs for identifying parking sites Official identifiers for

    parking sites in Ghent Ghent Sint Pieters Square: https://stad.gent/id/parkings/P10 2 ⇒ Unofficial URIs for DATEX2 created http://vocab.datex2.org
  15. Example: real-time and historic parking status In the city of

    Ghent: https://linked.open.gent/parking/ Federated Web querying on the client: http://bit.ly/2jUNnES ⇒ You can program your client to solve any question
  16. A call for joining forces 1. How do we get

    DATEX2 to publish HTTP URIs for their terms? 2. Let’s start publishing data as documents instead of services to enable smart clients ⇒ only way in which we are really going to make intermodal route planning happen
  17. PUBLIC