- Abstract-Wikipedia - lists.wikimedia.org

A few early mock-ups
by Denny Vrandečić 22 Jul '20

22 Jul '20

Hello all, I put a few early mock-ups on the wiki. It might be helpful to understand where we are planning to go. Also, I am not a designer, and we will have real designers go through them and there will be millions of improvements on the way, and probably also one or two complete rethinks. https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Early_mockups So this is all very preliminary. Nothing of this is set in stone yet, it is just slideware. Comments, inspirations, and discussion is very welcome. I plan to add more, incorporating feedback, and also to show a few workflows. Stay safe, Denny

3 4

Runtime considerations: Introducing GraalEneyj
by Lucas Werkmeister 22 Jul '20

22 Jul '20

Hi folks! Since people have started talking about runtimes for the functions defined in Wikilambda (see: V8 Engine andor WebAssembly thread), I figured I should mention the project I’ve been working on for a few weeks: GraalEneyj.[1] It’s supposed to be(come) a GraalVM-based (re)implementation of the eneyj language/runtime[2] that Denny wrote and which is currently part of the AbstractText extension. GraalVM,[3] for those who haven’t heard of it yet, is a Java-based project to build high-performance language implementations. There are already GraalVM-based implementations of JavaScript,[4] R,[5] Ruby,[6] LLVM,[7] WebAssembly,[8] and more,[9] and code snippets in any of these languages can run in the same (J)VM ((Java) Virtual Machine) and call each other with no performance penalty. This is of course interesting if we’re thinking about Wikilambda holding function implementations in different languages – with GraalEneyj, it should be possible to seamlessly compose functions implemented in any language for which a GraalVM implementation is available. GraalVM is also supposed to deliver highly optimized language implementations with relatively little development effort, but so far GraalEneyj is not yet at a point where I could benchmark it. If that sounds interesting to you, please get in touch! You can also explore the code that I have so far (there’s not a ton of documentation yet, but hopefully the README[10] is at least enough to get a basic idea and run the tests), or watch the GraalEneyj walkthrough[11] that I recorded last month. (At some point I should record another one, since the code keeps changing, but for now that’s all I have to offer.) Cheers, Lucas Werkmeister PS: In my day job I’m a software developer at Wikimedia Deutschland e. V., but all of this is private-time activity so far, not work related. [1]: https://github.com/lucaswerkmeister/graaleneyj/ [2]: https://github.com/google/abstracttext/tree/master/eneyj [3]: https://www.graalvm.org/ [4]: https://github.com/graalvm/graaljs [5]: https://github.com/oracle/fastr/ [6]: https://github.com/oracle/truffleruby [7]: https://github.com/oracle/graal/tree/master/sulong [8]: https://github.com/oracle/graal/tree/master/wasm [9]: https://github.com/oracle/graal/blob/master/truffle/docs/Languages.md [10]: https://github.com/lucaswerkmeister/graaleneyj/#readme [11]: https://www.youtube.com/watch?v=mQVpcBMjSaw

11 26

A Document Abstraction Layer
by Adam Sobieski 21 Jul '20

21 Jul '20

Introduction A document abstraction layer (DAL) could provide an API for natural language generation output while encapsulating a configurable and mechanical transformation to specific wikitext implementations. Natural language generation software could, then, output through a DAL to wikitext and this would facilitate certain conveniences and features. Feature 1: Provenance, Sources and Derivations A DAL could include a means for annotating portions of natural language with provenance data, sources or derivations. A DAL could provide an API for easily attaching provenance data to document elements (e.g. words, phrases, sentences, paragraphs, sections) and it would encapsulate handing the correct outputting of wikitext (e.g. <ref> and <references> elements) for output articles [1][2][3][4]. That is, one could attach provenance data, sources or derivations, to a particular sentence in a DAL object model and the DAL’s configurable, mechanical transformation to wikitext would encapsulate a specific implementation of outputting a <ref> element at the end of the sentence and ensuring that the automatically-generated wikitext article contained a <references> element in a “References” section. Furthermore, a DAL could encapsulate the naming of citation instances (<ref name="multiple">) [2] to ensure proper formatting of the references section when materials are cited multiple times. Feature 2: Computational Traces and Diagnostics A DAL could include a means of attaching computational traces and diagnostic messages or information to specific portions of generated natural language output (e.g. words, phrases, sentences, paragraphs, sections). While viewing articles which were automatically-generated in a “debug mode” or “developer mode”, developers could view and interact with content-specific computational traces or diagnostic messages or information in a number of ways (hoverboxes, margin notes, et cetera). That is, a DAL could encapsulate outputting specific wikitext implementations for providing developers with a means of interacting with automatically-generated articles to view and to understand the computational processes involved in generating specific portions of natural language. As citations and references are implemented by means of an extension [1], this set of features might require a new MediaWiki extension. Feature 3: Versioning a Document Abstraction Layer One could version a DAL, adding features to it, without impacting any existing natural language generation software code. One could also adjust specific output wikitext implementations for particular scenarios without impacting any natural language generation software code. Conclusion Should natural language generation output directly to wikitext or instead make use of an abstraction layer? What do you think of these ideas? Best regards, Adam Sobieski [1] https://www.mediawiki.org/wiki/Extension:Cite [2] https://www.mediawiki.org/wiki/Help:Cite [3] https://en.wikipedia.org/wiki/Help:Cite_link_labels [4] https://github.com/SemanticMediaWiki/SemanticCite/blob/master/README.md

2 4

Wikispore Sunday mini-conference
by Pharos 19 Jul '20

19 Jul '20

The event is Sunday July 19, hosted on Wikipedia Weekly Network. Time in select zones: 1:00–3:00 pm (New York City time) 17:00–19:00 UTC/GMT 19:00–21:00 Berlin time https://wikispore.wmflabs.org/wiki/Wikispore_Day You can participate on the Youtube livestream here, and text chat with the presenters and ask questions, etc: https://www.youtube.com/watch?v=q75Fv7Snc_w I also invite you to sign up for a lightning talk, and I will be glad to send interested individuals with related topics to present the on-air link: https://wikispore.wmflabs.org/wiki/Wikispore_Day#Interested_participants Thanks, Richard (User:Pharos)

1 0

Related work: The Function hub
by Jose Emilio Labra Gayo 18 Jul '20

18 Jul '20

One project that I think is related to Wikilambda's goal of developing a comprehensive repository of functions is the "Function hub" ( https://fno.io/hub/search) that was developed during Ben de Meester's Phd as part of the Function ontology (https://fno.io/). I think it can be considered as part of the related work and maybe gather some inspiration from it. -- -- Best regards, Jose Labra -- http://labra.weso.es

5 4

Wikidata Statement Provenance, Automated Reasoning, and Natural Language Generation
by Adam Sobieski 18 Jul '20

18 Jul '20

I would like to indicate, for discussion, some theoretical topics pertaining to natural language generation from Wikidata. An interesting feature of Wikidata is that it has sourced statements [1]. We can envision these sources and materials, the provenance of statements, propagating from the statements, through potential intermediate representations, to output natural language articles. In automatically-generated articles, these sources and materials could appear – as one might expect – as citations referring to referenced sources and materials which appear in “References” sections. Also interesting is that, should Wikidata come to support automated reasoning [2], it could be implemented in such a way that the enhanced provenance data (e.g. reasoning supporting, argumentation, proofs) for statements could similarly propagate from the statements, through intermediate representations, to output natural language articles. That is, automatically-generated articles could provide reasoning supporting, arguments for, and/or proofs of the contents of natural language sentences in a manner similar to how they can provide referenced sources and materials. Any thoughts on these topics? Best regards, Adam [1] https://www.wikidata.org/wiki/Help:Sources [2] https://www.wikidata.org/wiki/Wikidata:WikiProject_Reasoning

6 19

Development Part PP2 Suggestion
by Chris Cooley 16 Jul '20

16 Jul '20

There is a list of development tasks for this project at https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Tasks. I suggest we add a series of tasks to the above document in a new development part named PP2 that would start concurrently with part P1. Part PP2 would be "about producing a broad spectrum of ideas and alternatives from which a program for natural language generation from abstract descriptions would be selected." I have created a draft part PP2 at https://meta.wikimedia.org/wiki/Talk:Abstract_Wikipedia/Tasks#Development_P… . As I am sure there are many problems with this very initial draft, I would ask that the community edit the draft and provide comments, objections, etc. in the talk page as they see fit. Thanks, Chris Cooley

3 3

Re: [Abstract-wikipedia] [Wikispore] Abstract Wikipedia / Wikilambda on Wikispore?
by Samuel Klein 15 Jul '20

15 Jul '20

That sounds like a fine crossover question for both lists :) It feels like initial hypothetical examples could be fleshed out into separate articles / pages right away. And tool / extension / gadget designs could reference those. On Wed, Jul 15, 2020 at 7:17 AM Thomas Shafee <thomas.shafee(a)gmail.com> wrote: > Sounds excellent - and I look forward to seeing it grow. Do you think > specialised extensions/gadgets will be needed initially, or will it be > possible to start making example/prototype articles straight away? > > Thomas > > On Wed, 15 Jul 2020 at 21:11, Stuart Prior <stuart.prior(a)wikimedia.org.uk> > wrote: > >> Glad to hear this as it was my initial thought! >> >> S >> >> On Wed, 15 Jul 2020 at 03:24, Denny Vrandečić <dvrandecic(a)wikimedia.org> >> wrote: >> >>> I started a conversation today to consider Wikispore as a possible place >>> for hosting the early content for Abstract Wikipedia. >>> >>> >>> https://lists.wikimedia.org/pipermail/abstract-wikipedia/2020-July/thread.h… >>> >>> Feel free to chime in. >>> >>> Stay safe, >>> Denny >>> _______________________________________________ >>> Wikispore mailing list >>> Wikispore(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/wikispore >>> >> >> >> -- >> *Stuart Prior* >> *Project Coordinator* >> *Wikimedia UK* >> +44 203 372 0769 >> +44 7879 015 385 (text me otherwise I might screen the call) >> >> Wikimedia UK is the national chapter for the global Wikimedia open >> knowledge movement. We rely on donations from individuals to support our >> work to make knowledge open for all. Have you considered supporting >> Wikimedia? https://donate.wikimedia.org.uk >> >> Wikimedia UK is a Company Limited by Guarantee registered in England and >> Wales, Registered No. 6741827. Registered Charity No.1144513. Registered >> Office Ground Floor, Europoint, 5 - 11 Lavington Street, London SE1 0NZ >> <https://maps.google.com/?q=5+-+11+Lavington+Street,+London+SE1+0NZ&entry=gm…> >> . >> >> Wikimedia UK is the UK chapter of a global Wikimedia movement. The >> Wikimedia projects are run by the Wikimedia Foundation (who operate >> Wikipedia, amongst other projects). *Wikimedia UK is an independent >> non-profit charity with no legal control over Wikipedia nor responsibility >> for its contents.* >> _______________________________________________ >> Wikispore mailing list >> Wikispore(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikispore >> > _______________________________________________ > Wikispore mailing list > Wikispore(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikispore > -- Samuel Klein @metasj w:user:sj +1 617 529 4266

2 1

How Can the V8 Engine and/or WebAssembly Be of Use for the Wikilambda Project?
by Adam Sobieski 15 Jul '20

15 Jul '20

With respect to the early discussion topic [1] of the “data and evaluation model for the code repository (Wikilambda)”, I would like to broach, for discussion, that the V8 engine [9] and/or WebAssembly [10] can be of use for the Wikilambda project. While reading the plan [2] and tasks [3] documents, I observed tasks: P1.12 [4], P1.15 [5], O6 [6], O16 [7] and O29 [8]. Task P1.12 [4] indicates JavaScript-based implementations. Task P1.15 [5] indicates Lua implementations. Lua can be compiled to WebAssembly [12]. Task O6 [6] indicates Python implementations. Python can be compiled to WebAssembly [13]. There is a lengthy list of programming languages which already can or are planned to soon be able to compile to WebAssembly [11]. Task O29 [8] indicates compilation for significant speedup. The use of WebAssembly would facilitate task O16 [7], browser-based evaluation scenarios. WebAssembly is broadly supported by Web browsers. The V8 engine is utilized by Chromium-based Web browsers such as Brave, Chrome, Edge, Opera, and Vivaldi [9]. “The V8 engine can be used in a browser or integrated into independent projects” [9]. The V8 engine is utilized by the popular Node.js runtime environment [9]. The V8 engine includes a WebAssembly implementation. With respect to processing JavaScript, the V8 engine “first generates an abstract syntax tree with its own parser. Then, Ignition, the V8 interpreter, generates bytecode from this syntax tree using the internal V8 bytecode format [15]. TurboFan is the V8 optimizing compiler, it takes this bytecode and generates machine code from it. In other words, V8 compiles JavaScript directly to native machine code using just-in-time compilation before executing it. The compiled code is additionally optimized (and re-optimized) dynamically at runtime, based on heuristics of the code's execution profile. Optimization techniques used include inlining, elision of expensive runtime properties, and inline caching” [9]. The V8 engine “can compile to x86, ARM or MIPS instruction set architectures in both their 32- and 64-bit editions; as well, it has been ported to PowerPC and IBM s390 for use in servers” [9]. The V8 engine’s Ignition virtual machine [14] is “a register machine with an accumulator register” [15]. The WebAssembly virtual machine is “a portable virtual stack machine” [10]. In what ways can the V8 engine and/or WebAssembly be of use for the Wikilambda project? Could the V8 engine’s Ignition virtual machine [14][15] and/or the WebAssembly virtual machine [10] be of use as evaluation models or compilation targets for Wikilambda? Best regards, Adam Sobieski [1] https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Early_discussion_topics [2] https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Plan [3] https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Tasks [4] https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Tasks#Task_P1.12:_JavaSc… [5] https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Tasks#Task_P1.15:_Lua-ba… [6] https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Plan#Task_O6:_Python-bas… [7] https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Plan#Task_O16:_Browser-b… [8] https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Tasks#Task_O29:_Implemen… [9] https://en.wikipedia.org/wiki/V8_(JavaScript_engine) [10] https://en.wikipedia.org/wiki/WebAssembly [11] https://github.com/appcypher/awesome-wasm-langs [12] https://github.com/appcypher/awesome-wasm-langs#lua [13] https://github.com/appcypher/awesome-wasm-langs#python [14] https://v8.dev/docs/ignition [15] https://medium.com/dailyjs/understanding-v8s-bytecode-317d46c94775

4 4

Re: [Abstract-wikipedia] Communication channels / locations
by Pharos 15 Jul '20

15 Jul '20

We'd be very glad to host documentation and planning on Wikispore, that very much fits within our mission of fostering new sister projects, and hopefully it can help provide a leading example to other nascent sister project concepts too. Thanks, Richard (User:Pharos)

1 0

2024

2023

2022

2021

2020

Abstract-Wikipedia