Place URI scheme

[saumier]

Propose a Place URI scheme for all locations of events organized by NAC.

Suggestions:

• URIs that will also dereference for humans without any changes: https://nac-cna.ca/en/venue/southam-hall#Place https://nac-cna.ca/venue/southam-hall#Place. --> multi-lingual is better in my opinion

• URIs that could be dereferenced in the future using the path /resource https://nac-cna.ca/resource/southam-hall https://nac-cna.ca/resource/southam-hall#Place

• URIs that could be dereferenced in the future using subdomain https://data.nac-cna.ca/place/southam-hall

Dereferencing is when the URI redirects to a URL based on content negotiation (humans get a webpage, bots get an .ttl or .jsonld or .rdf)

[saumier]

Here is the issue raised by Frederic in the reference doc

# 1 – Remove location.@id or replace the current values with a unique URI for each venue
Issue: The value for @id is the same as the event page URL + a URI fragment. While this is an acceptable way of transforming a URL into a URI, the resulting URI is not unique within the NAC domain: each hall ends up with as many different identifiers as there are events on the website (x2 because of the mirror en/fr sites).
If the NAC can designate URI for each hall that is not dependent on language tags in the URL path (i.e. the exact same URI is used on both the en and fr site) that would be the best solution. This URI may or may not resolve to a webpage describing the hall.
If you can’t designate a single URI per hall, please remove location.@id from your schema altogether.

[nac-cna-dcopeland]

Location has been updated to include a language-agnostic URI and these redirect for users to the english side of our website. Future efforts can be made to handles these resource endpoints in a different fashion for bots but for now, it looks like so: https://nac-cna.ca/venue/southam-hall#Place