Jump to content


From Wikifunctions
This page is a translated version of the page Wikifunctions:About and the translation is 50% complete.
Vikişlev'in öncelikli hedefi Wikimedia projelerini desteklemektir, ancak Vikiveri'de olduğu gibi bunun ötesindeki hedefler de desteklenecektir.
Görev beyanı
Herkesin dünyanın doğal dillerinde ve yapay dillerinde oluşturup yeniden kullanabileceği, Wikimedia projelerini ve dahasını desteklemek için herkesin işbirliği içinde bir kod işlevleri kitaplığı oluşturup sürdürdüğü bir Wikimedia projesi

Vikişlev, herkesin kullanabileceği ve katkıda bulunabileceği açık kod deposudur.

Vikişlev, fonksiyonlardan oluşur. Bir fonksiyon, parametrelerin, test durumlarının, farklı programlama dillerindeki uygulamaların bir listesinin ve daha fazla meta verinin bir listesini içeren birçok dilde (Wikimedia tarafından desteklenenler arasında) açıklamaya sahip olabilir. Uygulamalar diğer yazılım projelerinde (özel uygulamalar veya komut dosyaları) yeniden kullanılabilir, çevrimiçi olarak çağrılabilir ve çalıştırılabilir (sadece tarayıcıda, bulut ortamında veya Jupyter[1] veya PAWS[2] not defterlerinde), daha karmaşık işlevsellik elde etmek için oluşturulabilir, imzalanabilir, analiz edilebilir veya doğrulanabilir ve çok daha fazlası.

Wikifunctions is a project in the spirit of Wikipedia, Wikidata, Wiktionary, and other similar global collaborative free culture projects: it allows contributors from all over the world to create and maintain a multilingual library of functions that can be used by anyone for any purpose. Every function can be supported by multiple implementations in different programming languages, test cases, pre- and post-conditions, documentation, metadata in the form of runtime estimates and complexity guarantees for the different implementations, etc. Users may call a function directly on the website, or from their own code or applications, from a command-line interface, or a local app. The function may be executed locally in the browser, in the cloud, or locally and embedded within the user's application.

Wikifunctions is intended to create both a well-defined common catalog of functions that can be widely reused and an environment where functions can be quickly combined and executed on the fly. Wikifunctions aims to make life easier for developers, who can rely on this repository like on any external library, and for end-users, who can call functions as needed, in a way that is currently only available with a very uneven coverage through specific websites that are often written in the form of 1990s websites with Java applets.

All functions are pure, in order to enable a secure sandboxed execution. Also, every implementation can be annotated with metadata and cryptographically signed. End-users can select and audit which implementation of each function to use, depending on their available hardware resources and web of trust settings.

Wikifunctions will allow easy access to large knowledge bases such as Wikidata, but also to binary input and output files. It is entirely possible to upload an image as an input file and return analysis results such as what is depicted on the image, or how many different colors the image has – or a different binary, e.g. in a different format. This will be made available to workflows on Wikimedia Commons.

Wikifunctions continues the tradition of moving more computation, which has usually happened on the command line or with apps by more computer-savvy users, to the Web and democratizing access to functionality that was not available before. At the same time, it will increase the productivity of developers everywhere, as they can just use a large library of code instead of relying on copying and pasting answers from sites like StackOverflow.

Unlike in Wikipedia, contributors will mostly create new implementations for a function instead of updating existing functions. The implementations can be automatically tested against the given tests, against each other, and further analyzed.

Implementations can be written in a number of different programming languages, but they will be able to call functions implemented in other programming languages. The execution engine can smoothly (although not necessarily with the highest possible performance) operate in different languages. Although in most cases there is a large performance boost in composing functions within a single programming language, there is no requirement to do so. In many cases, the speed of development and the developer's time will be more valuable than the additional computer cycles spent in the execution engine.


  1. m:WikiCite 2017/Jupyter notebooks on Wikimedia sites
  2. PAWS