Open JohannesLipp opened 3 years ago
Same issue for https://international-data-spaces-association.github.io/InformationModel/docs/serializations/ontology.ttl (text/n3
vs text/turtle
)
and https://international-data-spaces-association.github.io/InformationModel/docs/serializations/ontology.xml
(application/rdf+xml
vs application/xml
)
Investigation by @clange : Github.io creates content-types based on file extension. We therefore need the file extensions *.rdf
, *.n3
, and *.jsonld
- and redirects to these.
In other words, we need to copy:
A waste of space, but the easiest way to achieve what we need.
See https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#mime-types-on-github-pages: "While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on GitHub Pages. For more information, see the mime-db contributing guidelines." For example, https://github.com/jshttp/mime-db/blob/master/db.json lists MIME type ld+json strictly as .jsonld. Maybe add .json?
As described in #302 , the response content-type for https://international-data-spaces-association.github.io/InformationModel/docs/serializations/ontology.json is
application/json
, althoughapplication/ld+json
is requested. Please verify how that content-type is generated, and if it is possible to alternate that. For example, via a mini experiment with custom file extensions likefoo.json
,foo.jsonld
,foo.bar
.