-
mkramer So many improvements I'd like. I want the wikidata API to be as straightforward as Freebase's used to be. Also...Permalink On twitter.com
❤️ 1 Favorite
Mood +3 🙂
-
mkramer ... I would love it if sections in a story, visible in the ToC on a page, were represented as separate objects in the JSON outputPermalink On twitter.com
❤️ 1 Favorite
Mood +3 🙂
-
mkramer I had a huge problem last time I used the wikimedia API because different articles use diff section names, headers, dividers...Permalink On twitter.com
❤️ 1 Favorite
Mood -1 🙁
-
mkramer It became a huge task to build a script that could separate out the pieces of content, which was annoying b/c wikimedia...Permalink On twitter.com
❤️ 1 Favorite
Mood -1 🙁
-
mkramer ... totally knows how to separate that stuff out on the backend, and it would be super useful if it was in the response. ...Permalink On twitter.com
❤️ 1 Favorite
Mood +5 🙂
-
mkramer Also, search is way too complicated, I should be able to limit search in various ways (if I want only book articles for example)...Permalink On twitter.com
❤️ 1 Favorite
Mood +1 🙂
-
mkramer ...& returning response should allow should support embedding in the response, so I can get whole objects in the search responsePermalink On twitter.com
❤️ 1 Favorite
Mood +3 🙂
-
mkramer Right now, using wikimedia data through a search via API is a minimum of 2, sometimes 3 requests, which is painful.Permalink On twitter.com
❤️ 1 Favorite
Mood -2 🙁
-
mkramer Those are the big ones! Decreasing query processing & responses would be very useful.Permalink On twitter.com
❤️ 1 Favorite
Mood +3 🙂
-
mkramer Wikidata absorbed Freebase, but it is so much harder to use. Getting to parity would be huge for appliances that used Freebase.On twitter.com
❤️ 1 Favorite
Mood +2 🙂