From the beginning, our econ-ws (terminology) web services for economics produce tabular output, very much like the results of a SQL query. Not a surprise - they are based on SPARQL, and use the well-defined table-shaped SPARQL 1.1 query results formats in JSON and XML, which can be easily transformed to HTML. But there are services, whose results not really fit this pattern, because they are inherently tree-shaped. This is true especially for the /combined1 and the /mappings service. For the former, see our prior blog post; an example of the latter may be given here: The mappings of the descriptor International trade policy are (in html) shown as:
|<http://zbw.eu/stw/descriptor/10616-4>||"International trade policy" @en||<http://www.w3.org/2004/02/skos/core#exactMatch>||"International trade policies" @en||<http://aims.fao.org/aos/agrovoc/c_31908>||<http://zbw.eu/stw/mapping/agrovoc/target>|
|<http://zbw.eu/stw/descriptor/10616-4>||"International trade policy" @en||<http://www.w3.org/2004/02/skos/core#closeMatch>||"Commercial policy" @en||<http://dbpedia.org/resource/Commercial_policy>||<http://zbw.eu/stw/mapping/dbpedia/target>|
That´s far from perfect - the "concept" and "prefLabel" entries of the source concept(s) of the mappings are identical over multiple rows.