• "Wikipedia has more than 50 million articles in approximately 300 languages. The content in these languages is independently created and maintained. The knowledge in Wikipedia is very unevenly distributed over the languages: some languages have more than a million articles, but more than 50 languages have only a few hundred articles or less."
  • This first bit would be very well understood / easier to make meaning from with a visual
• "In order to close these knowledge gaps.." —> Assumption is that AW can close these knowledge gaps
• "Where content is created only once but made available in all languages" —> what do we mean by "content"?
• Assumption: "This will considerably reduce the effort required to create a comprehensive and maintain a current encyclopedia in many languages."
• Assumption: "It will allow more people to share more knowledge in more languages than ever before."
• Assumption: "It will be particularly useful for under-served languages, providing an important way to help improve education and ready access to knowledge in many countries."
• Could someone explain the desiderata section to me?
• Doesn't the architecture need an arrow pointing back to Wikipedia?
• "The most relevant function in Wikifunctions with regards to Abstract Wikipedia is a function to render abstract content in natural language."
• "I glossed over many issues such as agreement, saliency, or register. Wikifunctions will need to implement a natural language generation library taking these issues into account."
• "The primary goal of Wikifunctions is to enable the multilingual Wikipedia: define the constructors for abstract content and implement the rendering function. [Assumption —>] This will lead to the creation of an open, widely usable, and well-tested multilingual natural language generation library."
• "But Wikifunctions also has a secondary goal: to provide a comprehensive library of functions, to allow everyone to create, maintain, run, and reference functions. This will enable people without a programming background to compute answers to many questions, either through Wikifunctions or through third-party sites accessing the functions. It offers a place where scientists collaboratively create models. It provides a persistent identifier scheme for functions, thus allowing processes, scientific publications, and standards to refer to functions unambiguously. New programming languages will be easier to create as they can rely on Wikifunctions for a comprehensive library."
• "One obstacle in the democratization of programming is that most programming languages are based on English. Wikifunctions will use language-independent identifiers, allowing to read and write code in any natural language."
• "A major advantage of splitting up Wikifunctions and Abstract Wikipedia is that it recognizes the risks in the project. Wikifunctions defines a valuable goal by creating a catalog of functions. Abstract Wikipedia provides value by improving on the maintainability of currently bot-created articles. Even if the full vision is not achieved, we identify valuable intermediate milestones. The project is achievable without the need for research breakthroughs."
• I feel like this would be powerful if the language was accessible to more people
  • "Function specifications can have multiple implementations. Implementations can be in a programming language such as JavaScript, WebAssembly, or C++, or composed from other functions. Evaluators can execute different implementations and compare their results and runtime behavior. Evaluators can be implemented in a multitude of backends: the browser, the cloud, the servers of the Wikimedia Foundation, on a distributed peer-to-peer evaluation platform, in a mobile app, or on the user's machine. Function calls to Wikifunctions can be embedded in several contexts. Wikifunctions will provide UIs to call individual functions, but it also lends itself to be used from a Web-based REPL, locally installed CLIs, a RESTful API, as a library imported in a programming language, through dedicated apps, Jupyter notebooks, natural language assistants, or spreadsheet cells."

The example provided:

• Multiple accounts of technical lingo
  • Article
  • Abstracted content
  • Key
  • Constructor
  • Type
  • Instantiation
  • Language-independent identifiers
  • Natural language
  • Parser
  • Localize
  • Form-based editor
  • Lexicographic knowledge
  • Principles of functional programming
  • Calls

Goal of creating a Multilingual Wikipedia through: