What steps will reproduce the problem? 1. In the mapping builder, load an external ontology whose server supports content negotiation such that it can also respond with a non-ontology format (in particular HTML) if the request happens to use HTML as the main accept header. What is the expected output? A correctly loaded ontology model What do you see instead? An error related with the inability to read the model because it was just provided in a non-ontology format (HTML).
Reason: the default HTTP request uses HTML as the main accept header.
A possible solution (not requiring changes in the UI, that is, to also request the user to indicate the format), is to try a number of possible formats (according to the underlying Jena library) and corresponding accept headers.
From caru...@gmail.com on September 03, 2012 21:50:51
What steps will reproduce the problem? 1. In the mapping builder, load an external ontology whose server supports content negotiation such that it can also respond with a non-ontology format (in particular HTML) if the request happens to use HTML as the main accept header. What is the expected output? A correctly loaded ontology model What do you see instead? An error related with the inability to read the model because it was just provided in a non-ontology format (HTML).
Reason: the default HTTP request uses HTML as the main accept header. A possible solution (not requiring changes in the UI, that is, to also request the user to indicate the format), is to try a number of possible formats (according to the underlying Jena library) and corresponding accept headers.
Original issue: http://code.google.com/p/mmisw/issues/detail?id=298