-
-
Save pietercolpaert/6470b51ebc9ebe66f91615cc8d6964f2 to your computer and use it in GitHub Desktop.
Datex2 Rdfa Parking
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<!--Maps data to both schema and datex. I extended datex with URIs from dublin core terms (dct) and geo. Where possible, I added boht schema and datex approach--> | |
<html prefix="dtx: http://vocab.datex.org/terms# | |
dct: http://purl.org/dc/terms/ | |
schema: http://schema.org/ | |
geo: http://www.w3.org/2003/01/geo/wgs84_pos#"> | |
<article typeof="dtx:ParkingSite schema:ParkingFacility" resource="{{urlFromPage}}"> | |
<h2 property="dct:title schema:name">{{data.name}}</h2> | |
<p property="dct:spatial schema:address">{{data.address}}</p><!--We should have a more readable address here. Schema.org has a better example: http://schema.org/address (see RDFa and JSONLD examples)--> | |
<p property="">{{data.city}}</p><!--We can map a city to a URI... Should we? Furthermore: shouldn't this be part of the address property?--> | |
<p property="dtx:contactDetailsTelephoneNumber schema:telephone">{{data.telephone}}</p> | |
<p property="dct:description">{{data.description}}</p> | |
<p property="geo:long">{{data.longitude}}</p><!--Just a choice I made: I don't think we should create new URIs for long and lat if they already exist. going to remove long and lat from dtx!--> | |
<p property="geo:lat">{{data.latitude}}</p> | |
<p>spaces: <span property="dtx:parkingSpaceOccupied">{{data.occupied}}</span>/<span property="dtx:parkingSpace">{{data.maxSpace}}</span></p> | |
</article> | |
</html> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment