-
Got this request from today from one of the feature teams:
> hi, we are thinking about a simple CSV data export. do you think this would
> be appropriate to add to our data API endpoints as a differ…
-
Perhaps we should switch to the "Content negotiation API", it seems more stable:
* https://www.crossref.org/documentation/retrieve-metadata/content-negotiation/
_Originally posted by @ronaldtse …
-
```
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…
-
It would be great that AppSync services support content encoding negotiation as API Gateway does. In order to accomplish it, AppSync services should honor Accept-Encoding header a provide compressed r…
-
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…
-
Raised by @beaudet on the WG call of 2018-01-30:
If the resource is requested with language based content negotiation (e.g. the HTTP header `Accept-Language`), should there be any changes to the li…
-
Eg see how we did it for Getty LOD some 8 years ago: http://vocab.getty.edu/doc/#Semantic_Resolution.
Requirements:
- the same URL should serve HTML and various semantic formats
- Use content negot…
-
```
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…
-
Enable content negotiation on as many RDF formats as possible.
Since fully non-blocking streaming libs are not yet available, don't spend too much time on it.
-
## Expected Behavior
It would be great to have a configurable and client-driven fallback mechanism for template resolution; for example, if there's both `templates/feed.html` and `templates/feed.xm…