3 ms·
I'd rather see "SPARQL[1][2] as an API language" myself. SPARQL is criminally under-appreciated. BTW, if anybody wants to play around with SPARQL and see some
by mindcrime 8y ago
I'd rather see "SPARQL[1][2] as an API language" myself. SPARQL is criminally under-appreciated.
BTW, if anybody wants to play around with SPARQL and see some of what it can do, the Wikidata public SPARQL endpoint[3] is very nice and comes preloaded with some great examples[4].
[1]: https://en.wikipedia.org/wiki/SPARQL https://en.wikipedia.org/wiki/SPARQL
[2]: https://www.w3.org/TR/sparql11-overview/ https://www.w3.org/TR/sparql11-overview/
[3]: https://query.wikidata.org/ https://query.wikidata.org/
[4]: https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/queries/examples https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/...
- owyn 8y agoThis may just be down to wikidata's implementation, but the reliance on hardcoded unique id's everywhere is... bleh The following query uses these: Items: hospital (Q16917) Properties: instance of (P31) coordinate location (P625) 2 #defaultView:Map 3 SELECT * WHERE { 4 ?item wdt:P31*/wdt:P279* wd:Q16917; 5 wdt:P625 ?geo . 6 }
- mindcrime 8y agoYou always need unique identifiers for things, that's pretty much core to the whole Semantic Web idea. But what makes the Wikidata approach frustrating to me is that they use these identifiers that are totally opaque. I can sort of understand why they did it that way, but it does make for ugly queries.