The proposal of wikilambda at [0] starts with:
Wikilambda is a new Wikimedia project that allows editors to create and maintain code. This is useful in many different ways. It provides a catalog of all kind of functions that anyone can call, write, maintain, and use.
[0] https://meta.wikimedia.org/wiki/Abstract_Wikipedia#Proposal
Then it goes into:
It also provides code that translates the language-independent article from Abstract Wikipedia into the language of a Wikipedia. This allows everyone to read the article in their language. Wikilambda will use knowledge about words and entities from Wikidata.
It seems to me that the first part is much different from the second part. The first part describes some kind of code repository (with versioning I assume). The second part focus on the main use case for that repository and describes to some extent what would be the required or necessary function that can be created inside the repository. The second part can be understood as the procedure required by abstract Wikipedia to do its work.
I want to focus on the first part. If I understand correctly wikilambda is a *wiki for code*, that possibly allows translating procedure/function, documentation, and really any name into multiple natural languages. The programming language itself is not fixed yet. We know that we would like to make it possible to run programs on various existing programming language interpreter/compiler. That is already beyond the scope of this email.
Here is the question: Is that correct that wikilambda is a repository for code that allows us to:
1) create, 2) maintain, 3) localize identifiers and documentation into multiple natural languages
Is that all of wikilambda?
Hi Amirouche,
yes, your understanding is correct.
I am not sure what you mean with "identifiers and documentation", but I interpret is as "names for things" and "text describing them" - and yes, the idea is that you can say something like "Vienna is the capital of Austria", and the names for Vienna and for Austria get localized as does the sentence expressing this information. The code that generates this text will be created, maintained, and localized in the wiki for code.
I hope that helps, Denny
On Sat, Jul 11, 2020 at 8:52 AM Amirouche Boubekki < amirouche.boubekki@gmail.com> wrote:
The proposal of wikilambda at [0] starts with:
Wikilambda is a new Wikimedia project that allows editors to create and
maintain code. This is useful in many different ways. It provides a catalog of all kind of functions that anyone can call, write, maintain, and use.
[0] https://meta.wikimedia.org/wiki/Abstract_Wikipedia#Proposal
Then it goes into:
It also provides code that translates the language-independent article
from Abstract Wikipedia into the language of a Wikipedia. This allows everyone to read the article in their language. Wikilambda will use knowledge about words and entities from Wikidata.
It seems to me that the first part is much different from the second part. The first part describes some kind of code repository (with versioning I assume). The second part focus on the main use case for that repository and describes to some extent what would be the required or necessary function that can be created inside the repository. The second part can be understood as the procedure required by abstract Wikipedia to do its work.
I want to focus on the first part. If I understand correctly wikilambda is a *wiki for code*, that possibly allows translating procedure/function, documentation, and really any name into multiple natural languages. The programming language itself is not fixed yet. We know that we would like to make it possible to run programs on various existing programming language interpreter/compiler. That is already beyond the scope of this email.
Here is the question: Is that correct that wikilambda is a repository for code that allows us to:
- create,
- maintain,
- localize identifiers and documentation into multiple natural languages
Is that all of wikilambda?
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Will the versioning of this code be like versioning of wiki pages and Scribunto modules?
Or something like Git, where you can create forks, branches, merges, pull requests, etc., and where you can (relatively) easily go back to a previous version of several functions in one package?
Or something else entirely?
בתאריך יום א׳, 12 ביולי 2020, 19:36, מאת Denny Vrandečić < dvrandecic@wikimedia.org>:
Hi Amirouche,
yes, your understanding is correct.
I am not sure what you mean with "identifiers and documentation", but I interpret is as "names for things" and "text describing them" - and yes, the idea is that you can say something like "Vienna is the capital of Austria", and the names for Vienna and for Austria get localized as does the sentence expressing this information. The code that generates this text will be created, maintained, and localized in the wiki for code.
I hope that helps, Denny
On Sat, Jul 11, 2020 at 8:52 AM Amirouche Boubekki < amirouche.boubekki@gmail.com> wrote:
The proposal of wikilambda at [0] starts with:
Wikilambda is a new Wikimedia project that allows editors to create and
maintain code. This is useful in many different ways. It provides a catalog of all kind of functions that anyone can call, write, maintain, and use.
[0] https://meta.wikimedia.org/wiki/Abstract_Wikipedia#Proposal
Then it goes into:
It also provides code that translates the language-independent article
from Abstract Wikipedia into the language of a Wikipedia. This allows everyone to read the article in their language. Wikilambda will use knowledge about words and entities from Wikidata.
It seems to me that the first part is much different from the second part. The first part describes some kind of code repository (with versioning I assume). The second part focus on the main use case for that repository and describes to some extent what would be the required or necessary function that can be created inside the repository. The second part can be understood as the procedure required by abstract Wikipedia to do its work.
I want to focus on the first part. If I understand correctly wikilambda is a *wiki for code*, that possibly allows translating procedure/function, documentation, and really any name into multiple natural languages. The programming language itself is not fixed yet. We know that we would like to make it possible to run programs on various existing programming language interpreter/compiler. That is already beyond the scope of this email.
Here is the question: Is that correct that wikilambda is a repository for code that allows us to:
- create,
- maintain,
- localize identifiers and documentation into multiple natural languages
Is that all of wikilambda?
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
For now I am leaning towards "like wiki pages", also because we are building on top of MediaWiki.
Things can change down the line.
On Sun, Jul 12, 2020 at 10:00 AM Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
Will the versioning of this code be like versioning of wiki pages and Scribunto modules?
Or something like Git, where you can create forks, branches, merges, pull requests, etc., and where you can (relatively) easily go back to a previous version of several functions in one package?
Or something else entirely?
בתאריך יום א׳, 12 ביולי 2020, 19:36, מאת Denny Vrandečić < dvrandecic@wikimedia.org>:
Hi Amirouche,
yes, your understanding is correct.
I am not sure what you mean with "identifiers and documentation", but I interpret is as "names for things" and "text describing them" - and yes, the idea is that you can say something like "Vienna is the capital of Austria", and the names for Vienna and for Austria get localized as does the sentence expressing this information. The code that generates this text will be created, maintained, and localized in the wiki for code.
I hope that helps, Denny
On Sat, Jul 11, 2020 at 8:52 AM Amirouche Boubekki < amirouche.boubekki@gmail.com> wrote:
The proposal of wikilambda at [0] starts with:
Wikilambda is a new Wikimedia project that allows editors to create
and maintain code. This is useful in many different ways. It provides a catalog of all kind of functions that anyone can call, write, maintain, and use.
[0] https://meta.wikimedia.org/wiki/Abstract_Wikipedia#Proposal
Then it goes into:
It also provides code that translates the language-independent article
from Abstract Wikipedia into the language of a Wikipedia. This allows everyone to read the article in their language. Wikilambda will use knowledge about words and entities from Wikidata.
It seems to me that the first part is much different from the second part. The first part describes some kind of code repository (with versioning I assume). The second part focus on the main use case for that repository and describes to some extent what would be the required or necessary function that can be created inside the repository. The second part can be understood as the procedure required by abstract Wikipedia to do its work.
I want to focus on the first part. If I understand correctly wikilambda is a *wiki for code*, that possibly allows translating procedure/function, documentation, and really any name into multiple natural languages. The programming language itself is not fixed yet. We know that we would like to make it possible to run programs on various existing programming language interpreter/compiler. That is already beyond the scope of this email.
Here is the question: Is that correct that wikilambda is a repository for code that allows us to:
- create,
- maintain,
- localize identifiers and documentation into multiple natural languages
Is that all of wikilambda?
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Then it is somewhat like the system I was thinking of. It does not rely on a wiki and is meant to work over a peer-to-peer network. I guess I can adapt the design to work in a centralized fashion and rely on a web browser. It is also easier to code, I guess.
I think I will bump it in my todo list.
Le dim. 12 juil. 2020 à 19:00, Amir E. Aharoni amir.aharoni@mail.huji.ac.il a écrit :
Will the versioning of this code be like versioning of wiki pages and Scribunto modules?
Or something like Git, where you can create forks, branches, merges, pull requests, etc., and where you can (relatively) easily go back to a previous version of several functions in one package?
My idea looks like that.
Or something else entirely?
בתאריך יום א׳, 12 ביולי 2020, 19:36, מאת Denny Vrandečić dvrandecic@wikimedia.org:
Hi Amirouche,
yes, your understanding is correct.
I am not sure what you mean with "identifiers and documentation", but I interpret is as "names for things" and "text describing them" - and yes, the idea is that you can say something like "Vienna is the capital of Austria", and the names for Vienna and for Austria get localized as does the sentence expressing this information. The code that generates this text will be created, maintained, and localized in the wiki for code.
I hope that helps, Denny
On Sat, Jul 11, 2020 at 8:52 AM Amirouche Boubekki amirouche.boubekki@gmail.com wrote:
The proposal of wikilambda at [0] starts with:
Wikilambda is a new Wikimedia project that allows editors to create and maintain code. This is useful in many different ways. It provides a catalog of all kind of functions that anyone can call, write, maintain, and use.
[0] https://meta.wikimedia.org/wiki/Abstract_Wikipedia#Proposal
Then it goes into:
It also provides code that translates the language-independent article from Abstract Wikipedia into the language of a Wikipedia. This allows everyone to read the article in their language. Wikilambda will use knowledge about words and entities from Wikidata.
It seems to me that the first part is much different from the second part. The first part describes some kind of code repository (with versioning I assume). The second part focus on the main use case for that repository and describes to some extent what would be the required or necessary function that can be created inside the repository. The second part can be understood as the procedure required by abstract Wikipedia to do its work.
I want to focus on the first part. If I understand correctly wikilambda is a *wiki for code*, that possibly allows translating procedure/function, documentation, and really any name into multiple natural languages. The programming language itself is not fixed yet. We know that we would like to make it possible to run programs on various existing programming language interpreter/compiler. That is already beyond the scope of this email.
Here is the question: Is that correct that wikilambda is a repository for code that allows us to:
- create,
- maintain,
- localize identifiers and documentation into multiple natural languages
Is that all of wikilambda?
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
abstract-wikipedia@lists.wikimedia.org