content-negotiation

I was wondering why Wikidata content negotiation results with more than one entities in the file. For instance P2044 in the browser http://www.wikidata.org/entity/P2044.nt gives me triples also about Q6452016 entity: http://www.wikidata.org/entity/Q6452016 I would expect either triples about P2044 or document metadata. Thanks in advance. There are many options of what to produce in an RDF output (as well as there is no standard on what to return in a DESCRIBE query result). In Wikidata, you can use one of these options documented here . See also RDF Dump Format about the Wikidata data model.

If a clients sends data in an unsupported media type to a HTTP server, the server answers with status " 415 unsupported media type ". But how to tell the client what media types are supported? Is there a standard or at least a recommended way to do so? Or would it just be written to the response body as text? There is no specification at all for what to do in this case, so expect implementations to be all over the place. (What would be sensible would be if the server's response included something like an Accept: header since that has pretty much the right semantics, if currently in the wrong

Using Spring MVC, I have controllers already working for both JSON and XML media formats. In the content negotiation configuration, I would like to rely on Accept header only, and introduce a custom name media type, for example: "myXml" My configuration: @Configuration @EnableWebMvc public class WebConfig extends WebMvcConfigurerAdapter { @Override public void configureContentNegotiation(ContentNegotiationConfigurer configurer) { configurer .favorPathExtension(false) .favorParameter(false) .ignoreAcceptHeader(false) .useJaf(false) .mediaType(MediaType.APPLICATION_JSON_VALUE, MediaType

I am enjoying the auto HTTP content negotiation of JAX-RS (specifically Jersey), i.e. its ability to route my resources by "Accept" and/or "Content-Type" headers. But I'm finding that sometimes it doesn't give me enough control when there is a conflict. For example, consider the following endpoints: @Path("/order") public class OrderController { @GET @Path("{orderID: \\d+}") @Produces("text/html") public View getOrderView(@PathParam("orderID") long id) { Order order = this.getOrderData(id); return new OrderView(order); } @GET @Path("{orderID: \\d+}") @Produces({"application/json", "application

When a browser's Accept request header says something like the following: Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Does that mean that application/xml , application/xhtml+xml , and text/html all have a quality param of 0.9 ? Or does it mean that application/xml and application/xhtml+xml have the default ( q=1 ) and text/html has the q=0.9 param? I'm assuming the former, but was hoping someone knew more definitively. No, if the quality parameter is missing q=1.0 is assumed: Each media-range MAY be followed by one or more accept-params,