On Wed, Mar 14, 2012 at 9:07 AM, Dr. Trigon dr.trigon@surfeu.ch wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 13.03.2012 17:05, Tim Landscheidt wrote:
Even if only for PHP there would be a critical mass, it'd be still useful to Perl, Python and other developers. For example, I think it is a common problem to normalize links - e. g., are "[[Diskussion:ABC_abc#.C3.A4.C3.B6.C3.BC]]" and "[[de:Talk:aBC abc#äöü]]" pointing at the same resource? Most developers start with the easy bits and end up with something that works for most of their use cases, but fails if that line is overstepped (for example "Image:" -> "File:"). If there was an existing module for this, you wouldn't have to think about all the fringe cases yourself, but could base upon the sweat poured by others :-). If Me- diaWiki got updated, you would just have to look at the changes in the PHP module and port them to your language of choice.
That is the reason why I occasionally use pywikipedia framework with toolserver tools also... ;) So use the pywikipedia as starting point for such a python library.
+1
Last thing I remember to miss (nice to have) was the toolserver notice [1] or a module to check if a given URL is safe (e.g. no "file:///etc/passwd")
At the risk of over-designing, would it be worth to gather language-independent requirements for a module/library, on the toolserver wiki or on meta, and then keep implementations of that standard (yes, I know, "one more standard") available on the toolserver? At the very least, a language-neutral brainstorming might prevent design flaws, especially with database-with-API-fallback in mind.
Magnus