Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Your parking site's data, integrated everywhere

Your parking site's data, integrated everywhere

You parking site's data can be reused in various ways: within simple apps, as well as in more seamless integration or as a smart city sensor. However, still many interoperability are currently holding back the wide adoption of your dataset that you'd like everyone to use.

We propose 2 things:
1. We want your parking site to have a persistent identifier across all datasets worldwide.
2. We introduce http://vocab.datex.org/terms as a vocabulary to describe your parking lot in various systems

More can be found at http://vocab.datex.org

Slides presented at the ITS Belgium advisory group - http://its.be

Pieter Colpaert

December 06, 2016
Tweet

More Decks by Pieter Colpaert

Other Decks in Technology

Transcript

  1. 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
  2. A service between 2 systems? Your system Third party system

    You cannot have a meeting/contract with all these parties and/or answer all their users’ questions
  3. Sharing data on the Web Your data ? ? ?

    ? ? ? = preparing your data for maximum reuse
  4. The biggest effort for integrators is in cleaning data, and

    linking identifiers together Is Parking 1 the same thing as Parking Site P1 in another dataset?
  5. Let’s use Web Addresses as generic identifiers across all interfaces

    Coming soon in city of Ghent: this identifier will identify Parking Vrijdagmarkt everywhere https://stad.gent/id/parking/P1
  6. Web Addresses in use in an HTML page We also

    gave the terms in Datex2 a Web address So, if you now go to http://vocab.datex.org/terms#ParkingSite, you will see the definition of a Parking Site