Enhance usability/accessibility of concepts

[oellers]

Situation

• Currently the docker image skohub/skohub-vocabs-docker:latest provides language-based html files, no general "index.html" (as found in skohub-docker-vocabs#7)

Drawbacks

• Dealing with concept ids looking like URIs might confuse users, if they are used to accessing them with the expectation of reaching meaningful content. Although the main purpose is unique identification, it might not be from a user's perspective

Non-working Example

• The concept id "https://w3id.org/comein/vocabs/DigCompEdu/3.2" leads to "You just hit a route that doesn't exist... the sadness."

Working Example

• Skohub.io seems to integrate a redirect pattern based on the working example concept id "http://w3id.org/kim/kmk-vocabs/digitalisierungsbezogene-kompetenzen/F427CBE5-3444-405B-B3ED-31392C5AD548" which leads to the concept item

How to deal with the drawback

• Maybe generation of index.html or htaccess rules redirecting to existing language files by default/existance?

[sroertgen]

The main purpose of the current behavior seems to come from the need to identify a language, so Skohub Vocabs knows which language to select and render.
We can maybe bypass this using the browsers navigator.language (https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language).
This would also allow us to be independent of a specific web server (Apache), which I would really like.

[awagner-mainz]

I have manually modified the .htaccess file resulting from the build to

• enable indexes and multiviews
• add another filename to the "DirectoryIndex" type, reflecting the name of my conceptScheme ("scheme")
• declare the languages used in my vocabulary

Options +FollowSymLinks +MultiViews +Indexes

DirectoryIndex index scheme

AddLanguage da .da
AddLanguage de .de
AddLanguage en .en
AddLanguage fr .fr
AddLanguage nl .nl
AddLanguage sv .sv

AddType text/index .index
AddType application/json .json
AddType application/ld+json .jsonld

(the AddType directives have been there before)

The second and third point are likely to vary from vocabulary to vocabulary, but during building we should have knowledge of these things. Maybe create an .htaccess file automatically. If the user runs nginx, caddy or something else, they at least have an indication of what they'd need to implement in their webserver's configuration.