Confusing example

[wschella]

In the Linked Data Publishing Section, specifically following slides: 1 2 3 4 (Static blob).

The mapping from

{ "Performance" :
  { "Perf_ID": "567",
    "Venue": { "Name": "Vooruit", "Venue_ID": "78" },
    "Location": { "longitude": "3.725379", "latitude": "51.0477644" } },
}

to

<http://ex.com/venues/78>
    geo:long 3.725379;
    geo:lat 51.0477644.

<http://ex.com/venues/91>
    geo:long 3.728515;
    geo:lat 51.056008.

is made.

This is a decent example to demonstrate the flexibility and power of RML, but might be a bit confusing in demonstrating it's concepts and goals, since the original and new data model are different¹. If this is intentional, a footnote might be in it's place.

¹: The original data model seems 'wrong' as to not include the geolocation attributes as part of the venue; it includes them in the performance itself.

[RubenVerborgh]

Thanks! Definitely intentional, and cases like the above are actually quite common. Will think for a good footnote.