-
provide guidelines on content negotiation (accept / content-type).
-
```
curl -H "Accept: application/rdf+xml" http://wals.info/languoid/family/jabuti
redirects to
http://127.0.0.1:6084/languoid/family/jabuti.rdf
instead of
http://wals.info/languoid/family/jabuti…
-
Right now the generated Content-Type for the Content Negotiation in based entirely on the Accept header. Would be nice to support additional options like selecting the type from a GET parameter, the U…
-
The OM URIs appear to resolve nicely each to a HTML page, e.g.
http://www.ontology-of-units-of-measure.org/page/om-2/squareMetre
However, it would be better still if they were available direct…
-
I'm running a Quarkus application with a Prometheus endpoint which will shows the "old" Prometheus format without exemplars when accessing the metrics endpoint in the Chrome browser, and it will show …
ahus1 updated
3 weeks ago
-
The distribution spec currently does not describe active content negotiation, leaving it up to individual implementations whether (and _how_) content negotiation should be performed.
This proposal …
-
According to `https://github.com/mlcommons/croissant/blob/main/docs/croissant.ttl`, The croissant namespace is ``
However, `http://mlcommons.org/croissant/` redirects to `https://mlcommons.org/work…
-
### MDN URL
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
### What specific section or headline is this issue about?
How Subresource Integrity helps
### What informat…
-
### Ktorfit version
2.1.0
### What happened and how can we reproduce this issue?
So the docs states there is no need in additional configuration.
If I just use
```
implementation…
-
The meta resolver should provide content negotiation for DOI pids.