Abstract Wikipedia/Ideas

Structured comments, attributes and decorators could be utilized by Wikifunctions to provide features such as: function metadata, facilitating searching for functions, and the automatic generation of documentation.

Structured comments are programming language comments which utilize syntactic patterns or XML so that the contents of the comments can be mechanically processed.

• https://docs.microsoft.com/en-us/dotnet/csharp/codedoc
• https://docs.microsoft.com/en-us/visualstudio/ide/xml-documentation-comments-javascript?view=vs-2015

Attributes can be attached to functions and their parameters in programming languages such as C# and Java.

• https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/attributes/

Decorators are a proposed JavaScript language feature.

• https://github.com/tc39/proposal-decorators
• https://github.com/tc39/proposal-decorators#metadata
• https://tc39.es/proposal-decorators/

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

Utilizing structured comments, attributes, or decorators, versioning-related metadata can simplify versioning scenarios on evolving crowdsourced resources.

• https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/attributes/general#obsolete-attribute

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

Namespaces and modules can be useful when organizing large collections of functions. With namespaces or modules, multiple paradigms or ecosystems of functions could more readily coexist in a crowdsourced resource.

• https://v8.dev/features/modules
• https://www.typescriptlang.org/docs/handbook/namespaces-and-modules.html

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

With modern scripting engines such as V8, it is relatively easy to create and provide scripting environments.

Resembling how Web browsers provide scripting environments and API for Web scenarios, we can envision providing scripting environments and API for natural language generation scenarios.

Discussion topics pertaining to scripting environments for renderers include: (1) API and object models for accessing and working with input Wikidata data, (2) API and object models for accessing and working with the rendering context, (3) API and object models for accessing and working with intermediate knowledge representations, (4) API and object models for generating output natural language content.

• https://v8.dev/
• https://developer.mozilla.org/en-US/docs/Web/API
• https://developer.mozilla.org/en-US/docs/Web/API/Window
• https://developer.mozilla.org/en-US/docs/Web/API/Document
• https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

As Wikidata is a sourced knowledgebase, API and object models should include means for annotating any intermediate representations and portions of natural language with sources. In automatically-generated articles, statements’ sources could appear as referenced materials in articles’ "References" sections with numbered citations appearing inline, near relevant content.

Should Wikidata come to include support for automated reasoning, any reasoning, argumentation, derivations and/or proofs supporting statements could similarly appear in articles’ "References" sections with numbered citations appearing inline, near relevant content. Readers could click on hyperlinks to navigate to automatically-generated documents which indicate supporting reasoning, argumentation, derivations and/or proofs for one or more statements.

• https://www.wikidata.org/wiki/Help:Sources
• https://www.wikidata.org/wiki/Wikidata:WikiProject_Reasoning
• https://en.wikipedia.org/wiki/Wikipedia:Citing_sources

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

When editing/developing Wikifunctions content for use on Abstract Wikipedia, it would be convenient to be able to output to multiple streams, to log, and/or to raise typed events. Such features are part of the scripting environment provided to functions.

It would also be useful to be able to aggregate, organize and view diagnostic outputs with a configurable granularity or verbosity.

• https://developer.mozilla.org/en-US/docs/Web/API/Console

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

Editors/developers could have a means of toggling a "developer mode" or "debugging mode" on Abstract Wikipedia so that they could, while viewing articles, either: (1) hover over portions of natural language to view relevant traces of computation and diagnostic messages in hoverboxes, (2) view visual indicators for traces of computation and diagnostic messages in a margin so that they could then interact with the visual indicators to view expanded data, or (3) otherwise select or indicate portions of natural language content to view relevant traces of computation and diagnostic messages.

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

We can consider adding feedback mechanisms for Abstract Wikipedia readers such as commenting upon, liking, upvoting, or otherwise providing feedback with respect to specific portions of automatically-generated natural language content.

Also possible is that readers could "post-edit" automatically-generated content. For automatically-generated articles, there could be wiki versions of the articles for purposes of crowdsourcing the fine-tuning of the articles. These "wiki post-edited" versions of automatically-generated articles could be navigated to via tab user-interface elements. Data from this variety of crowdsourced feedback on automatically-generated articles, "wiki post-editing", could be collected and aggregated for use by Wikifunctions editors/developers.

• https://en.wikipedia.org/wiki/Postediting
• https://www.aclweb.org/anthology/W05-1615.pdf
• https://ehudreiter.com/2020/06/08/human-editing-of-nlg-texts/

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

Software tools in the categories of automatic essay scoring, grammar checking, readability measurement, and/or natural language evaluation could be of use for automatically measuring articles in a number of ways. Coh-Metrix 3.0, for instance, measures natural language on 108 indices.

Perhaps bots could measure articles as they are updated and report their data to editors/developers using a platform API.

• http://cohmetrix.com/

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

Resembling question-answering systems, articles could be generated for Wikidata queries or after users navigate to articles from Web searches. Beyond highlighting relevant content, articles could be generated while utilizing this context data.

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

Resembling hypertext-based dialogue systems, one could place follow-up questions which might interest a reader in a section near the bottom of articles, each being a hyperlink to another article. One could hyperlink to articles which could be dynamically generated, if they are not already created and cached.

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

There exists a CSS Speech Module W3C Candidate Recommendation.

With respect to pronunciation, one can utilize pronunciation lexicons with hypertext documents. Also, resembling EPUB3, one can utilize SSML-based attributes on generated hypertext outputs to provide pronunciation data.

• https://www.w3.org/TR/css-speech-1/
• https://www.w3.org/TR/pronunciation-lexicon/
• https://www.w3.org/publishing/epub3/epub-contentdocs.html#sec-xhtml-ssml-attrib
• https://www.w3.org/TR/speech-synthesis11/

AdamSobieski (talk) 22:15, 15 July 2020 (UTC) [reply ]

Use GPT-3 style API's to automatically translate normal language into the syntax of Abstract Wikipedia. ChristianKl ❪✉❫ 16:15, 16 January 2021 (UTC) [reply ]

• Abstract Wikipedia