Last modified: 2014-09-24 13:41:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 36881 - Wiktionary needs usable API
Wiktionary needs usable API
Status: NEW
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 21450 (view as bug list)
Depends on:
Blocks: 11996 11998 12213 noncoreapi
  Show dependency treegraph
 
Reported: 2012-05-15 23:55 UTC by MZMcBride
Modified: 2014-09-24 13:41 UTC (History)
12 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2012-05-15 23:55:22 UTC
I can't seem to find a pre-existing bug, but Wiktionary needs a usable API.

Currently Wiktionary relies on MediaWiki's api.php, but that was (largely) built for Wikipedia. A proper Wiktionary API would allow retrieving definitions in a particular language from a language version of Wiktionary. Probably a few other things as well. ;-)
Comment 1 Mark A. Hershberger 2012-05-16 16:11:03 UTC
This should be a tracking bug.  But I don't know of any other issues to put here.
Comment 2 Quim Gil 2013-03-25 01:02:33 UTC
This idea has been suggested by Siebrand as a potential Google Summer of Code projects at http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Wiktionary_APIs

Does this make sense? Has there been any discussion in the Wiktionary community about specific API needs? I just want to know whether we would have a roughly defined project for a student. If the students should start by going to English Wiktionary and ask then this is not a feasible project proposal for GSOC 2013.

https://www.mediawiki.org/wiki/Summer_of_Code_2013#Project_ideas

If the idea makes sense we would also need at least one mentor.
Comment 3 Bawolff (Brian Wolff) 2013-03-25 01:15:33 UTC
(In reply to comment #2)
> This idea has been suggested by Siebrand as a potential Google Summer of Code
> projects at
> http://www.mediawiki.org/wiki/Mentorship_programs/
> Possible_projects#Wiktionary_APIs
> 
> Does this make sense? Has there been any discussion in the Wiktionary
> community
> about specific API needs? I just want to know whether we would have a roughly
> defined project for a student. If the students should start by going to
> English
> Wiktionary and ask then this is not a feasible project proposal for GSOC
> 2013.
> 
> https://www.mediawiki.org/wiki/Summer_of_Code_2013#Project_ideas
> 
> If the idea makes sense we would also need at least one mentor.

Note Ive previously tried to do this. Well part of the reason my attempt semi failed was that I was a newbie at the time I would like to state this is not the easiest problem to solve (esp. If you intend to keep wiktionary the same as it is currently without any explicit machine readable annotations)
Comment 4 Bawolff (Brian Wolff) 2013-03-25 01:24:32 UTC
Btw for reference my  http://en.wikinews.org/w/index.php?title=User:Bawolff/sandbox/Wiktionary_query (don't view on mobile site)

Its not exactly an api, but does similar things to an api. Part of the reason it sucks so much were naive design choices that were horrid (younger me was stupid. If you read the code don't judge too hard). Anyhow as a result of my experiance with that, I wouldn't reccomend this as a gsoc project unless the student already had quite a bit of proper experiance with parsing.
Comment 5 Amgine 2013-03-25 03:18:52 UTC
Side note: the usual first approach to this is look at existing dictionary api standards. There are a large number of existing, mostly proprietary, systems currently in production using en.Wiktionary mapped to existing standards. There are almost no efforts doing so with other languages.
Comment 6 Mark A. Hershberger 2013-03-25 15:14:55 UTC
If someone would just implement RFC 2229, that would be awesome.  https://tools.ietf.org/html/rfc2229

Alternatively, make the api calls as compatible as possible with that RFC.
Comment 8 Andre Klapper 2013-06-13 17:26:41 UTC
*** Bug 21450 has been marked as a duplicate of this bug. ***
Comment 9 Lydia Pintscher 2014-09-24 13:41:09 UTC
To make this happen Wiktionary needs to store its data in a structured and machine readable format. We have proposals for how to make this happen at https://www.wikidata.org/wiki/Wikidata:Wiktionary/Development. Once that is done the API will be done as well.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links