Chronotope’s avatarChronotope’s Twitter Archive—№ 68,503

              1. …in reply to @vrandezo
                vrandezo mkramer I think SPARQL added after last time I walked through wikidata, and it is an improvement over last time I used API but...
            1. …in reply to @Chronotope
              vrandezo mkramer As a standard SPARQL is magnitudes more complex than the Freebase API was, no? And it handles similar data.
          1. …in reply to @Chronotope
            vrandezo mkramer And encoding the query as a GET param is a pain, difficult to assure quality, and runs into compatibility issues.
        1. …in reply to @Chronotope
          vrandezo mkramer I'm super happy there is a JSON response, and for sure, this is an improvement over the standard Wikimedia API!
      1. …in reply to @Chronotope
        vrandezo mkramer But SPARQL is more academic, MQL ties into knowledge common among web devs. And human-readable queries are sorely missed
    1. …in reply to @Chronotope
      vrandezo mkramer (URL query strings I mean)
  1. …in reply to @Chronotope
    vrandezo mkramer Unrelated to Freebase, being able to POST JSON queries as opposed to encoding them into the URL would be even better.
    1. …in reply to @Chronotope
      vrandezo mkramer Finally, I know it is terribly capitalist of me, but get [string] related terms w/filters was super useful. ...
      1. …in reply to @Chronotope
        vrandezo mkramer ...Use for Freebase for some was to build web content w/common taxonomy, not to do research. Mby we're weirdos? :P
        1. …in reply to @Chronotope
          vrandezo mkramer You all are doing a ton of work w/lot of data & it is much appreciated. I just greedily want best API for my use case! :P


Search tweets' text