Annual plan 2026-2027
The draft of the Wikimedia Foundation 2026-2027 annual plan
<https://meta.wikimedia.org/wiki/Wikimedia%20Foundation%20Annual%20Plan/2026…>
has
been published for discussion. This includes an objective for Abstract
Wikipedia
<https://meta.wikimedia.org/wiki/Wikimedia%20Foundation%20Annual%20Plan/2026…>
:
*Demonstrate Abstract Wikipedia's viability as a scalable, human-centered
way to create multilingual encyclopedic content.*
Context: The Internet is increasingly shaped by automatically produced text
that is often opaque and unverifiable. At the same time, manually created
knowledge alone cannot adequately fill multilingual content gaps. Can
Wikipedia’s human-led model of knowledge creation scale across languages
without sacrificing trust, transparency, or community control? By making
one contribution reusable across many languages, Abstract Wikipedia seeks
to answer that question.
This objective is initially broken down into four key results:
*Key Result: By the end of Q1, ensure that fragment rendering performance
of the integration into Wikipedias is maintained without regression as
deployment expands from the first demonstration into the initial target
language Wikipedias, so that the system remains responsive and welcoming to
editors as they draft changes.*
Context: Deepen multilingual viability for Abstract Wikipedia by ensuring
that expansion of availability and usage does not impair performance. To
make sure that Abstract Wikipedia is viable as a platform for users and
sustainable for the Foundation, we will rebuild our prototype integration
into Wikipedias, expanding from the work done in FY26Q4 into one that
supports and scales successfully to our envisioned 5–10 additional early
adopter Wikipedias, in a way that keeps down the operational cost for
Wikimedia in terms of server time and so production load/scale.
*Key Result: By the end of Q1, increase the number of sentences and core
elements in Abstract Wikipedia articles, with more articles receiving
follow-up edits.*
Context: This KR builds on our current focus on supporting the core
community by strengthening the building blocks that enable richer, longer
articles. It shifts the emphasis from simply increasing article volume to
fostering meaningful article development that aligns with community
expectations around quality. At the same time, it deepens editor engagement
while keeping flexibility to adapt based on evolving community needs.
*Key Result: By the end of Q2, one proof of concept article is created on
Abstract Wikipedia and integrated in three Wikipedias*
Context: This KR area defines measures for content growth and maintenance
rates for the different relevant contents of Abstract Wikipedia, and based
on these, measures that indicate that contributor communities will be able
to to create and maintain Abstract Wikipedia articles, Wikifunctions
language functions, relevant Wikidata Lexemes, and/or integration into
Wikipedia at a rate that can meet the threshold for scalable content
viability. We also develop an understanding of second-order effects on the
development of existing Wikipedia language communities.
*Key Result: By the end of Q1, 100% of pilot cohort users have migrated
away from Blazegraph endpoints.*
Context: The Wikidata Platform backend replacement will be ready to serve
production traffic by end of FY25/26. The new system will offer capacity
improvements for Wikidata, Wikidata Query Service (WDQS), and all systems
integrated with either tool. We are beginning our migration with a small
group of pilot users to baseline migration efforts and user impact of the
new backend. The learnings we collect during Q1 will be used to support the
Abstract Wikipedia use case in Q2.
Note that the language isn’t final, especially because we are asking for
feedback and discussion
<https://meta.wikimedia.org/wiki/Talk:Wikimedia%20Foundation%20Annual%20Plan…>
to
amend the language based on the community's input.
Wikipediapodden Episode #368 with James Forrester
In the latest episode of the Podcast about Wikipedia, Wikipediapodden
<https://wikipediapodden.se/>, Jan Ainali
<https://wikipediapodden.se/abstract-wikipedia-james-forrester-368/> is
interviewing James Forrester. They are discussing the progress of Abstract
Wikipedia and Wikifunctions since the last episode that was centered around
Abstract Wikipedia four years ago, #154
<https://wikipediapodden.se/episode-154-abstract-wikipedia-and-wikifunctions/>
.
Recent Changes in the software
This week, we made improvements across Abstract Wikipedia and
Wikifunctions. On Abstract Wikipedia, edit and history pages now show the
article title as well as the QID, which should make it easier to understand
which article you are looking at (T424265
<https://phabricator.wikimedia.org/T424265> & T424095
<https://phabricator.wikimedia.org/T424095>). In addition, references
created by functions can now also include working links to non-Wikimedia
websites, so external citations work as expected (T423180
<https://phabricator.wikimedia.org/T423180>).
On Wikifunctions, we also added a new filter to Special:ListObjectsByType,
so you can now filter functions based on what kind of result they return (
T301712 <https://phabricator.wikimedia.org/T301712>). Finally, we ran a
script to try to clean up out-of-date Test case results, though it doesn't
seem to have fully fixed things (T422300
<https://phabricator.wikimedia.org/T422300>).
Two notes about forthcoming changes: we are planning to raise the version
of the Python codebase we're using on the evaluator service, moving to
approximately Python 3.14 equivalence, up from 3.13 (T426353
<https://phabricator.wikimedia.org/T426353>). We're saying "approximately"
as technically this is RustPython, for performance and security reasons. We
don't think this change will break anything, but we wanted to alert you
ahead of the changes in the next week or two. Secondly, we are going to
drop the pre-defined Function Z831/Validate against schema, which has not
been available since the re-write of the orchestrator service, and we
believe is unused (T418886 <https://phabricator.wikimedia.org/T418886>).
Fresh Functions weekly: 65 new Functions
This week we had 65 new functions! Here is an incomplete list of functions
with implementations and passing tests to get a taste of what functions
have been created. Thanks everybody for contributing!
- multiply complex128 by float64 (Z35072)
<https://www.wikifunctions.org/wiki/Z35072>
- divide complex128 by float64 (Z35073)
<https://www.wikifunctions.org/wiki/Z35073>
- reference HTML marker from reference (Z35085)
<https://www.wikifunctions.org/wiki/Z35085>
- reference HTML marker content from reference (Z35087)
<https://www.wikifunctions.org/wiki/Z35087>
- claims of Wikidata reference (Z35090)
<https://www.wikifunctions.org/wiki/Z35090>
- emphasize (Z35094) <https://www.wikifunctions.org/wiki/Z35094>
- does Wikidata property have data type external-ID? (Z35126)
<https://www.wikifunctions.org/wiki/Z35126>
- construct Wikidata property claim from PID and QID (Z35133)
<https://www.wikifunctions.org/wiki/Z35133>
- Toki Pona defining role sentence (Z35139)
<https://www.wikifunctions.org/wiki/Z35139>
- defining role sentence in Croatian (Z35151)
<https://www.wikifunctions.org/wiki/Z35151>
- Croatian genitive singular from item (Z35154)
<https://www.wikifunctions.org/wiki/Z35154>
- Dutch nominative def article + noun from Item (Z35158)
<https://www.wikifunctions.org/wiki/Z35158>
- is neutral grammatical gender (Z35161)
<https://www.wikifunctions.org/wiki/Z35161>
- infobox for person as item (Z35167)
<https://www.wikifunctions.org/wiki/Z35167>
- natural language from langcode and aliases (Z35171)
<https://www.wikifunctions.org/wiki/Z35171>
- name + native name as HTML fragment (Z35176)
<https://www.wikifunctions.org/wiki/Z35176>
- Wikidata claim pair (Z35188)
<https://www.wikifunctions.org/wiki/Z35188>
- display Wikidata date from statement (Z35192)
<https://www.wikifunctions.org/wiki/Z35192>
- defining role sentence in Dutch (Z35196)
<https://www.wikifunctions.org/wiki/Z35196>
- density (Z35219) <https://www.wikifunctions.org/wiki/Z35219>
- average speed (Z35221) <https://www.wikifunctions.org/wiki/Z35221>
- lateral surface area of a prism (Z35222)
<https://www.wikifunctions.org/wiki/Z35222>
- surface area of a prism (Z35223)
<https://www.wikifunctions.org/wiki/Z35223>
- average flow rate (Z35224) <https://www.wikifunctions.org/wiki/Z35224>
- SCBA cylinder autonomy (Z35241)
<https://www.wikifunctions.org/wiki/Z35241>
- format ISBN-10 (Z35256) <https://www.wikifunctions.org/wiki/Z35256>
- format ISBN-13 (Z35261) <https://www.wikifunctions.org/wiki/Z35261>
- display ratio (Z35269) <https://www.wikifunctions.org/wiki/Z35269>
A complete list of all functions sorted by when they were created
<https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderb…>
is
available.
The on-wiki version of this newsletter can be found here:
https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-05-15
----
A higher meaning
One of the big questions about Abstract Wikipedia is: how many functions
constructing fragments
<https://www.wikifunctions.org/wiki/Wikifunctions:Abstract_Wikipedia/2025_fr…>
will
we need? Because if that number is large, doesn’t that mean that we will
need many functions implementing these fragments in many languages? And
that would increase the effort needed for each language, and at some point
it might be easier to just translate and validate the translations of the
texts, instead of creating all these functions?
We don’t know how big that number will be. But today I want to discuss one
reason why I think it will remain limited: not every fragment will need to
be implemented through language-specific functions.
How would that be the case? Don’t we need to implement every fragment with
a language-specific function in every language we want to support?
Well, yes, but sometimes these implementations can be compositions of other
abstract functions!
Here is a concrete example: Year-specific sentence from statement (Z28436)
<https://www.wikifunctions.org/wiki/Z28436> creates a sentence from a
statement with a point in time property. For example, a sentence such as
“The population of North Epping was 4657 in 2021.” or "The population of
Donji Humac was 157 in 2011."
The function Z28436 is implemented using a configuration object, currently
with implementations in English and Bangla.
Now, let’s take a look at the function Most recent year-specific sentence
about item (Z28445) <https://www.wikifunctions.org/wiki/Z28445>. Instead of
taking an object and a statement, it takes an object and a property, and
returns the value for the statement with the most recent point in time for
that property. So if we do run this for Donji Humac and population, it will
result in "The population of Donji Humac was 173 in 2021.", as this was the
most recent population statement we have in Wikidata for Donji Humac.
And if we now look at the implementation of Z28445, we don’t see a
configuration. Instead, we see a function that is composed of the function
above, Z28436, and Most recent qualified statement from item (WIP) (Z28446)
<https://www.wikifunctions.org/wiki/Z28446>. Nothing in this implementation
is language specific. Instead, the language is being passed through to the
underlying function.
So we see here an abstract function that has an entirely abstract
implementation.
This is a general pattern that can be reused: given we have a solid
foundation, it is hopefully often possible to have “higher” abstract
functions be grounded in more foundational functions, which are
nevertheless abstract.
For example, consider the sentences
- “The Huns attacked the Roman empire in the 5th century.”
- “John Wilkes Booth assassinated Abraham Lincoln on April 14, 1865.”
- “John Lennon met Yoko Ono on November 7, 1966.”
- “Leonard Cohen wrote ‘Hallelujah’ in 1984.”
- “Microsoft launched Windows 3.1 on August 24, 1995.”
- “Hubble discovered Osiris on November 28, 2001.”
They all describe very different events, but in the end, in English, they
all have a very similar structure, involving a predicate, a subject, a
direct object, and a more or less specific point in time. All of these
sentences could, in English, be created by a single function.
Maybe it will turn out that all of these sentences could be created through
a single abstract function in several languages. Let’s call this a grounded
function.
And now we could have several higher-level functions, implemented through
grounded functions like these, and all we have to do is pick the right
predicate.
This won’t always work. But the good thing is that if we have these
higher-level functions, we can try to capture the exception at that higher
level, redirect it for the relevant language, and otherwise select the
right predicate and just use the grounded function.
For example, in English we would usually say
- “Goldie Hawn gave birth to Kate Hudson on April 19, 1979.”
Which is a slightly different grammatical structure than the one above. The
grammatical structure we have above would lead to “Goldie Hawn birthed Kate
Hudson on April 19, 1979.” – which would be an unusual sentence in English,
but works in some other languages, e.g. Croatian, without problems.
So a function that creates that sentence could choose for this use case a
different grounded function, or could even have a one-off implementation,
for English and other languages where the grounded function introduced
above wouldn’t work, and use the grounded function for the other languages.
This kind of pattern could considerably reduce the number of language
specific implementations needed for Abstract Wikipedia to work, making our
goal more viable.
Recent Changes in the software
This week, we added support in Wikifunctions for several dozen natural
languages that were already supported by TranslateWiki.net
<https://translatewiki.net/> (and used for translating Wikimedia software)
but not yet supported by Wikifunctions. We also updated Abstract pages to
display a copyable QID next to the page title, making it easier to quickly
copy the corresponding Wikidata QID, similar to the copyable ZID shown next
to titles in Wikifunctions (T423651
<https://phabricator.wikimedia.org/T423651>, T424265
<https://phabricator.wikimedia.org/T424265>).
News in Types: way forward for natural language generation types
I have been reading and thinking about the currently open proposals and
their discussion for types supporting natural language generation
<https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-04-10>
for
a while, and I am honestly not sure about the best approach forward. But I
am getting the feeling that figuring out the best answer might be getting
in the way of moving forward. Given that, I would suggest that within the
next two weeks we get the following three types specific enough to
implement them, then actually implement them, then use them, and learn from
their usage:
- Semantic Unit
<https://www.wikifunctions.org/wiki/Wikifunctions:Type_proposals/Semantic_un…>
- Syntactic Unit
<https://www.wikifunctions.org/wiki/Wikifunctions:Type_proposals/Syntactic_u…>
- Syntactic table
<https://www.wikifunctions.org/wiki/Wikifunctions:Type_proposals/Syntactic_t…>
All three proposals have garnered some, but not unanimous approval, and I
think they all have advantages and disadvantages. But I wonder if instead
of thinking through these in detail, we just try them out, and see what
works.
If anyone has better proposals moving forward, I am all ears.
Recording of the May 11 Volunteers’ Corner
This Monday’s volunteer’s corner (11 May 2026) is now available as a
recording on Commons
<https://commons.wikimedia.org/wiki/File:Abstract%20Wikipedia%20Volunteer%20…>.
Thank you for the lively conversation, and for the well-attended meeting.
Fresh Functions weekly: 40 new Functions
This week we had 40 new functions. Here is an incomplete list of functions
with implementations and passing tests to get a taste of what functions
have been created. Thanks everybody for contributing!
- signum (float64) (Z34780) <https://www.wikifunctions.org/wiki/Z34780>
- run-length encoding (Z34790)
<https://www.wikifunctions.org/wiki/Z34790>
- most common element(s) in list (Z34793)
<https://www.wikifunctions.org/wiki/Z34793>
- is valid pinyin for single character (Z34797)
<https://www.wikifunctions.org/wiki/Z34797>
- short form of label for Type (Z34802)
<https://www.wikifunctions.org/wiki/Z34802>
- short form of label for Type, English (Z34804)
<https://www.wikifunctions.org/wiki/Z34804>
- label of persistent Type in language or fallback (Z34810)
<https://www.wikifunctions.org/wiki/Z34810>
- is float64 finite? (Z34827) <https://www.wikifunctions.org/wiki/Z34827>
- Monolingual stringset equality (Z832)
<https://www.wikifunctions.org/wiki/Z832>
- Natural language equality (Z862)
<https://www.wikifunctions.org/wiki/Z862>
- select Forms with given features from Lexeme (Z34899)
<https://www.wikifunctions.org/wiki/Z34899>
- select Monolingual texts in any of several langs (Z34902)
<https://www.wikifunctions.org/wiki/Z34902>
- Wikifunctions sitelink for Wikidata item (Z34914)
<https://www.wikifunctions.org/wiki/Z34914>
- string from lexeme or label given item ref. & lang (Z34927)
<https://www.wikifunctions.org/wiki/Z34927>
- better matching multilingual text form from lexeme (Z34943)
<https://www.wikifunctions.org/wiki/Z34943>
- best monolingual text of multilang, with lang list (Z34947)
<https://www.wikifunctions.org/wiki/Z34947>
- monolingual text from multilingual with fallback (Z34953)
<https://www.wikifunctions.org/wiki/Z34953>
- writing direction(s) of script as WD Item(s) (Z34993)
<https://www.wikifunctions.org/wiki/Z34993>
- length of Typed map <entity, entity> (Z34999)
<https://www.wikifunctions.org/wiki/Z34999>
- get element of entity-keyed map (Z35004)
<https://www.wikifunctions.org/wiki/Z35004>
- Bengali -এ suffix form (Z35010)
<https://www.wikifunctions.org/wiki/Z35010>
- display year in Bangla no খ্রিস্টাব্দ after 1899 (Z35013)
<https://www.wikifunctions.org/wiki/Z35013>
- wrap HTML fragment in cell (td/th) element (Z35017)
<https://www.wikifunctions.org/wiki/Z35017>
- Year specific sentence from statement in Bangla (Z35018)
<https://www.wikifunctions.org/wiki/Z35018>
- inception sentence (Z35022) <https://www.wikifunctions.org/wiki/Z35022>
- inception sentence, English (Z35023)
<https://www.wikifunctions.org/wiki/Z35023>
- abstractwiki 18-col periodic table to nth period (Z35031)
<https://www.wikifunctions.org/wiki/Z35031>
- wrap an HTML fragment in a simple tag (Z35049)
<https://www.wikifunctions.org/wiki/Z35049>
A complete list of all functions sorted by when they were created
<https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderb…>
is
available.
The on-wiki version of this newsletter is available here:
https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-05-08
----
References from Wikidata now available
As of this Wednesday, references in Wikidata statements are being passed
through to Wikifunctions. We are excited about this new ability, as this
allows the use of the more than 1.3 billion references available in
Wikidata and adding them as citations to individual statements in Abstract
Wikipedia. Citations are a crucial element of a reliable encyclopedia, and
so we are happy to make it easier to have them available in Abstract
Wikipedia.
Note that in related capabilities, links to external sites are still not
displayed as links. We are working on relaxing that constraint for the
content of references. For now, most hyperlinks can only be displayed as
text.
Recording of Toby Hudson’s talk at WikiCon Australia
Toby Hudson <https://www.wikifunctions.org/wiki/User:99of9> presented
*Wikifunctions
in Practice: Reusable Logic for Wikimedia
<https://meta.wikimedia.org/wiki/Event:WikiCon%20Australia%202026/Submission…>*
at WikiCon Australia
<https://meta.wikimedia.org/wiki/Event:WikiCon%20Australia%202026> on 11
April 2026. The recording is available on Commons
<https://commons.wikimedia.org/wiki/File:Wikifunctions%20in%20practice%20-%2…>
and on YouTube <https://www.youtube.com/watch?v=ViOkEYQLggM>.
Toby gives a great motivation for Abstract Wikipedia and Wikifunctions, and
gives in 23 minutes a quick, but thorough overview of both projects, and
then answers questions from the in-person audience. Here is the description
of the talk:
*Wikifunctions promises something simple but ambitious: write logic once,
and make it reusable across Wikimedia projects and languages. Small,
well-chosen functions can have outsized impact and eliminate some updating,
copy-pasting, or even translation.*
*This talk focuses on goals and practical usage rather than internals or
programming, but will allow plenty of time for questions from the audience
to dig into the details. We'll see what Wikifunctions is and what it's for.
We will test a range of existing functions on Wikifunctions directly. We
will see how to embed the result of a function call in a regular Wiki page
elsewhere on a sister project. Then we will look ahead to how Wikifunctions
will play a key role in the future Abstract Wikipedia.*
Abstract data dashboard
David Santamaria has published a tool to help understand the state of
Abstract Wikipedia: "Abstract Data" <https://abstract-data.toolforge.org/>,
a Website that tracks both language coverage and Wikifunctions function
usage across all abstract articles.
The main view shows all abstract articles and the number of
languages/Wikipedias each can currently be rendered in. There is also a
Languages view that ranks languages (Wikipedia's represented languages) by
how many articles they can render, making it easy to see where coverage is
strongest and where there is still work to do. Figuring out Lexeme coverage
is not perfect yet.
On the functions side, the tool lists the top 100 most-used Wikifunctions
functions and shows which articles call each one, useful for assessing the
impact of a change before making it. It also flags functions without an
implementation or with failing tests, making it easy to spot when a broken
function is blocking content from rendering.
The data is based on the database dumps that are being generated twice a
month.
The tool is still in its early days, so it may not always work perfectly,
and there are likely bugs. If you run into anything unexpected or have
ideas for features you would find useful, please do let David know on his
user talk page
<https://www.wikifunctions.org/wiki/User_talk:DSantamaria-WMF>. This is not
an official tool, but we hope you find it useful.
Admins on Abstract Wikipedia?
Now that Abstract Wikipedia has been around for more than a month, we would
like to invite the Abstract Wikipedia community to consider whether they
wish to begin a process of choosing administrators, so that the wiki
becomes more self-sufficient.
Recent Changes in the software
As mentioned above, the main change this week is that we have enabled
references on statements when fetching items from Wikidata (T404652
<https://phabricator.wikimedia.org/T404652>). We hope that this new feature
will help you write Functions that add references for Abstract Wikipedia
when using Wikidata statements. We do not expect this to add much more load
to the system, but if something is now slow or broken please let us know.
Items (and other entities) fetched from Wikidata may contain statements,
and each Wikidata statement (Z6003)
<https://www.wikifunctions.org/wiki/Z6003>, in its Z6003K6/references key,
may now contain zero or more instances of Wikidata reference (Z6008)
<https://www.wikifunctions.org/wiki/Z6008>. For more information about
Wikidata’s practices regarding references for statements, Wikidata's
Help:Sources page <https://www.wikidata.org/wiki/Help:Sources> provides a
useful discussion.
We've added two new pre-defined equality Functions with built-in
Implementations, to make it easier to work with natural languages. Firstly,
we've added Natural language equality (Z862)
<https://www.wikifunctions.org/wiki/Z862>, which should let you check if
the language of an item for which you asked from Wikidata is what you
received back, *etc.* (T424289 <https://phabricator.wikimedia.org/T424289>).
Secondly, we've added Monolingual stringset equality (Z832)
<https://www.wikifunctions.org/wiki/Z832>, which will let you see if two
sets of labels (most used for Wikidata item aliases) are the same (T424461
<https://phabricator.wikimedia.org/T424461>).
Finally, we fixed one bug that you might have noticed. Occasionally, the
system might not reply to MediaWiki correctly, such as when the network
connection was interrupted. In these rare cases, we now emit a proper error
that should come through to you with a better explanation, rather than a
mysterious breakage (T414062 <https://phabricator.wikimedia.org/T414062>).
Volunteers’ Corner on May 11
The next Volunteers’ Corner will be on Monday, 11 May 2026 at 17:30 UTC
<https://zonestamp.toolforge.org/1776101400>. We plan to have the following
agenda: there will be time to ask questions and discuss all matters
arising. If we have time, we will write a function together. Everyone is
welcome to join us on Google Meet <https://meet.google.com/xuy-njxh-rkw>.
Fresh Functions weekly: 39 new Functions
This week we had 39 new functions. Here is an incomplete list of functions
with implementations and passing tests to get a taste of what functions
have been created. Thanks everybody for contributing!
- classifying sentence - entity (Z34282)
<https://www.wikifunctions.org/wiki/Z34282>
- All booleans equal to (Z34293)
<https://www.wikifunctions.org/wiki/Z34293>
- Bulgarian cardinal with gender (Z34308)
<https://www.wikifunctions.org/wiki/Z34308>
- is Natural number odd? (Z34353)
<https://www.wikifunctions.org/wiki/Z34353>
- any boolean equal to (Z34367)
<https://www.wikifunctions.org/wiki/Z34367>
- Is element of a set (Z34378)
<https://www.wikifunctions.org/wiki/Z34378>
- is subset of a set (Z34380) <https://www.wikifunctions.org/wiki/Z34380>
- is probably proper noun? (Z34394)
<https://www.wikifunctions.org/wiki/Z34394>
- Predecessor of von Neumann ordinal (Z34409)
<https://www.wikifunctions.org/wiki/Z34409>
- read Natural number leniently, place-value decimal (Z34419)
<https://www.wikifunctions.org/wiki/Z34419>
- Czech subject is instance of (string) (Z34427)
<https://www.wikifunctions.org/wiki/Z34427>
- Classifying sentence in French (Z34434)
<https://www.wikifunctions.org/wiki/Z34434>
- subject is kind of (Monolingual text), Czech (Z34487)
<https://www.wikifunctions.org/wiki/Z34487>
- Q5 is male? (Z34510) <https://www.wikifunctions.org/wiki/Z34510>
- Append element to set (Z34519)
<https://www.wikifunctions.org/wiki/Z34519>
- Union of sets (Z34538) <https://www.wikifunctions.org/wiki/Z34538>
- generate alternating sign terms for summation (Z34575)
<https://www.wikifunctions.org/wiki/Z34575>
- Is von Neumann ordinal greater than (Z34585)
<https://www.wikifunctions.org/wiki/Z34585>
- Hyperoperation of von Neumann ordinals (Z34620)
<https://www.wikifunctions.org/wiki/Z34620>
- part-of sentence - entity (Z34637)
<https://www.wikifunctions.org/wiki/Z34637>
- part-of sentence in English (Z34638)
<https://www.wikifunctions.org/wiki/Z34638>
- item is part of these items (Z34641)
<https://www.wikifunctions.org/wiki/Z34641>
- join list of monolingual texts with Oxford comma (Z34644)
<https://www.wikifunctions.org/wiki/Z34644>
- coerce text-like object to Monolingual text (Z34663)
<https://www.wikifunctions.org/wiki/Z34663>
- join list of Monolingual texts with delimiter (Z34669)
<https://www.wikifunctions.org/wiki/Z34669>
- same multilingual stringset (Z34736)
<https://www.wikifunctions.org/wiki/Z34736>
A complete list of all functions sorted by when they were created
<https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderb…>
is
available.