Wikifunctions:Project chat

Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:

• Wikifunctions:Administrators' noticeboard
• Wikifunctions:Report a technical problem
• Wikifunctions:FAQ

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.

edit
Archives
2023/08 2023/09 2023/10 2023/11 2023/12 2024/01 2024/02 2024/03 2024/04 2024/05 2024/06 2024/07 2024/08 2024/09 2024/10 2024/11 2024/12 2025/01 2025/02 2025/03 2025/04 2025/05 2025/06 2025/07 2025/08 2025/09 2025/10 2025/11 2025/12 2026/01 2026/02 2026/03 2026/04 2026/05 2026/06 2026/07 2026/08

A proposal on number types on the Wikifunctions project

Hi! We'd like to submit our proposal surrounding the status of numbers in the Wikifunctions ecosystem, Wikifunctions:Proposal for built-in number types! We're open to discussion, advice, ideas, and so on. What we propose, while important, is complex and requires proper approval before we begin thinking about implementing it. Virinas-code (talk) 15:10, 17 August 2026 (UTC)

person lead sentence configuration

A newly-solved phabricator task now means that person lead sentence with occupations (Z38757) can work well. I think it's well-defined and has enough arguments to work for most people. The exception is those with Julian dates for birth/death (we still don't have a Julian type, so can't import Julian WD values). Please configure config for person description (Z32826) in your language! Wherever possible, follow the language wiki manual of style for this lead sentence. Please make noise if there's a conceptual/definitional problem for your language. --99of9 (talk) 05:13, 20 August 2026 (UTC)

Wikifunctions & Abstract Wikipedia Newsletter #261: Mayors and the North

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we have an essay from Denny about accidental gaps in languages, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Enjoy the reading! -- User:Sannita (WMF) (talk) 09:41, 21 August 2026 (UTC)

Coincidentally, I just made an abstract article for a different government gato... the initial idea was to write about a racehorse, but maybe I was subconsciously influenced by reading this when Denny posted it on the RfC earlier.
reː translatability of San Francisco is the cultural centre of Northern California, it was always a stupid question. "Northern California" together is the toponym, and "cultural centre" together refer to a concept (not one in WD as far as I can tell, but the concepts of financial and historic centres exist there). So there's no need for "North" as an absolute direction or "centre" as a relative position. YoshiRulz (talk) 13:40, 21 August 2026 (UTC)

"Northern California" is not a stupid question. The preferred way of describing locations varies from culture to culture. For example, a riverine culture might consider the most important aspect of its location to be "at the mouth of the Sacramento River", while an island culture might describe it as "on the coast of North America". "Northern California" is the map-centric description of its location.

Even within map-centric cultures, the borders vary. For example, when preparing a test case for Z26570, I discovered that Spanish places the United Arab Emirates in "Oriente Próximo", and "Oriente Medio" is seen as an Americanism to be avoided. Carnildo (talk) 21:52, 21 August 2026 (UTC)

You've missed the pointː the labels for items, including Northern California (Q1066807), have no restrictions and don't have to be word-for-word translations of the native label (P1705). Beijing (Q956) is not "Northern Capital" and Sotavento Islands (Q500453) is not "Leeward Islands". Describing where a place is in relation to other places is a separate problem (shares border with (P47) + direction relative to location (P654) qual. seems to be how that's modelled, so that might be limiting for some languages). Choosing how to group countries/regions is a separate problem (there's a Near East (Q48214), but United Arab Emirates (Q878):part of (P361)=Middle East (Q7204) only). YoshiRulz (talk) 06:39, 22 August 2026 (UTC)

Language-specific guideline pages

Is it possible to create guideline pages for each language, or do they already exist?

Rather than translating a single English page using the Translate extension, it would be better to have standalone pages (subpages are acceptable). Naming conventions and similar rules in each language are almost always different from English rules. 鈴音雨 (talk) 07:04, 23 August 2026 (UTC)

→ WT:Naming conventions#Per-language pages YoshiRulz (talk) 08:39, 23 August 2026 (UTC)

Thank you (I didn't know that discussion exists). I'll write a draft for naming conventions for Japanese. 鈴音雨 (talk) 08:48, 23 August 2026 (UTC)

Wikifunctions & Abstract Wikipedia Newsletter #262: Wikifunctions Object Reference

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss a new Type implemented after a community request, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Enjoy the reading! -- User:Sannita (WMF) (talk) 12:32, 28 August 2026 (UTC)

Draft policy for language fallback strategies

Help:Language fallback
I'd appreciate any comments, but I'm particularly seeking approval for this planned mass edit:

• 'limited' in all Category:Display functions
• 'none' in all Category:Reading functions
• 'limited' in all Category:Abstract description functions
• NEW STRATEGY 'insistent' in all Category:Semantic fragment functions (including the ones I haven't categorised yet)
• 'insistent' in all Category:Hatnote functions
• 'insistent' in all Category:Multilingual captioned image functions
• 'none' in all Category:Conjugation tables
• 'none' in all (experimental) Syntactic table (Z36462)-producing functions? @Denny
• 'limited' in everything else: punctuation helpers, lexeme and inflection helpers, partial sentence functions...

YoshiRulz (talk) 15:42, 30 August 2026 (UTC)

I am happy that see that you want to structure the language fallback strategies. I can't oversee the consequences, but I trust you in this plan. HenkvD (talk) 11:46, 30 August 2026 (UTC)

At first read, the policy looks great (even if a person speaking fr-CA will probably be angry with that example, despite being largely true). I also approve the planned mass edit so far, it's good to test that. Thanks for the work! Ornithorynque liminaire (she/they) (talk) 16:20, 30 August 2026 (UTC)

It would also be very great to have a schema and more examples so the policy could be more understandable for newcomers. Ornithorynque liminaire (she/they) (talk) 16:22, 30 August 2026 (UTC)

None for the Syntactic tables is a good idea, I think that one will go from experimental right to deprecated anyway. I am not sure yet about the Semantic fragment functions, and would like to see the effect once we have a few more. --Denny (talk) 11:48, 3 September 2026 (UTC)

Can you provide some examples of things that will change? --99of9 (talk) 04:52, 11 September 2026 (UTC)

'None' → 'Limited': display Gregorian calendar date (Z20780) will use the Dutch implementation when Afrikaans is requested, instead of the ISO 8601 fallback.
'None' → 'Insistent': main articles (Z36083) will use the English implementation when German is requested, instead of the fallback that's just an arrow.
Improvements are very much dependent on how the fallback language lists are configured. And the Z14294s themselves—yesterday I went through and replaced hardcoded [ en, en-GB ] with English variants (Z33034), but in a world where I hadn't, the 'Limited' strategy would be helpful in routing the dialects to en. YoshiRulz (talk) 17:13, 11 September 2026 (UTC)

New visualisation templates to help editors navigate Configuration of functions for given languages (Z14294)

I've got summary table with examples for Configuration (Z40885) mostly working and I hacked together a version of a tree view that's usable: take a look at Talk:Z25091 and Talk:Z39262. YoshiRulz (talk) 02:35, 3 September 2026 (UTC)

Native implementations reading Z12 labels broken after recent deploy

Tracked in Phabricator:
Task T436918

Native (JS/Python) implementations that read labels from their argument now get an empty Z12K1, so they return 0 items. Composition implementations are unaffected.

Example: label-list from item for languages, JavaScript (Z24116) (JS impl of label strings from Wikidata item for language-list (Z24114)) with Q1 + [en, mul] returns 0 items, while composition label texts from selected labels, composition (Z26569) returns ["universe"].

Cause: orchestrator commit "Strip Z12 labels when resolving WFObjects" (Aug 26), deployed in the 2026-09-02 services deploy. fullyRealize() now strips Z12K1, and native implementation arguments go through it (WFImplementation.js).

I've temporarily disconnected Z24116/Z24770 from Z24114 so the working composition Z26569 is used.

Question: Is stripping labels from native arguments intentional? How should native code access labels going forward?

(FYI: Z24114 tester large list of labels and late element (Z36529) is separately failing; Q30 has no no label; it's under nb/nn now.) 鈴音雨 (talk) 08:49, 3 September 2026 (UTC)

label of item in language, javascript (Z23769) is also broken. 鈴音雨 (talk) 09:46, 3 September 2026 (UTC)

It was intentional to remove some, but not intentional to remove all (or at least we didn't understand the effect). The development team are aware. --99of9 (talk) 09:58, 3 September 2026 (UTC)

Should now be fixed. GrounderUK (talk) 11:20, 4 September 2026 (UTC)

Wikifunctions & Abstract Wikipedia Newsletter #263: 5,000 Functions, passing Z40000

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we mark the 5,000th function on Wikifunction, we explore a new Type for functions, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Also, we remind you that if you have questions or ideas to discuss, the next Volunteers' Corner will be held on September 7, at 17:30 UTC (link to the meeting).

Enjoy the reading! -- User:Sannita (WMF) (talk) 11:00, 4 September 2026 (UTC)

i can create my own function?

i need enable my implementation for my function Z38065 Spider077 (talk) 05:40, 6 September 2026 (UTC)

Please request connections at Wikifunctions:Requests for connection and disconnection.

I do not think this particular implementation should be connected.

1. The function has no test cases, so its intended purpose is not entirely clear.
2. The function appears to be a duplicate of string identity (Z11602).
3. The implementation will return an error because Text is undefined.
4. In any event, print() returns the value None, so the implementation would end up returning void (Z24).

Please feel free to reply here if you need any help. GrounderUK (talk) 10:24, 6 September 2026 (UTC)

Help for optimizing functions

I developed infobox for smartphone, composition (Z41075), but in many cases, Reached rate limit in evaluator (Z571) or Reached time limit in orchestrator (Z574) occurs. I understand that this function is trying to do a lot, but I am trying to find a way to make it lighter. Any advice would be appreciated. 鈴音雨 (talk) 06:47, 8 September 2026 (UTC)

I made a few changes, of which I think making all the fetch calls identical would have the most impact. YoshiRulz (talk) 17:55, 8 September 2026 (UTC)

Incorrect number formatting with uselang on Main Page

{{formatnum:{{NUMBEROFFUNCTIONS}}}} on Wikifunctions:Main_Page (or to be precise, on Template:Main page) evaluates using PAGELANGUAGE (en) by default, not USERLANGUAGE. Setting Polish as the interface language and/or appending ?uselang=pl leaves English digit grouping (5,634, not Polish grouping: 5634). Is there a way to fix this? Because right now in Polish, technically speaking, it says there are "5.634 functions" (five and six hundred thirty-four thousandths), since a comma is used as a decimal separator in Polish. Wcalenieja (talk) 19:45, 9 September 2026 (UTC)

This problem has been repeatedly raised on the talk page and ignored every time. YoshiRulz (talk) 21:32, 9 September 2026 (UTC)

Oh, yeah, you're right :/ Wcalenieja (talk) 22:32, 9 September 2026 (UTC)

Will admin rights help with this? Or where should the change be? I take it we can't use an embedded call: 5634?--99of9 (talk) 00:44, 10 September 2026 (UTC)

Yep, admin rights are needed to edit Template:Main page, since it's edit-protected. Hardcoding a static string defeats the purpose of using {{NUMBEROFFUNCTIONS}}, which automatically updates as new functions are added. AFAIK users should be navigated to language subpages (e.g., Wikifunctions:Main_Page/pl). On subpages, PAGELANGUAGE is explicitly pl, so standard {{formatnum:...}} works correctly. But to be honest I'm not that technical, so I may be wrong. Wcalenieja (talk) 10:45, 10 September 2026 (UTC)

I guess I didn't mean hardcoding, I was more asking about using our own functional formatting by calling display natural number (Z14280) with an embedded function call. It might look more like 5783 --99of9 (talk) 10:53, 10 September 2026 (UTC)

That makes sense. Apologies, I misread your comment as suggesting a hardcoded string rather than a function call. But we should use {{#function:Z14280|{{NUMBEROFFUNCTIONS}}|{{int:lang}}}} instead of hardcoding pl :) Wcalenieja (talk) 11:03, 10 September 2026 (UTC)

Indeed. I think it is now working. This does risk the first visitor in each language seeing "function is being called"... So let's see if we get lots of complaints.--99of9 (talk) 11:20, 10 September 2026 (UTC)

Wikifunctions & Abstract Wikipedia Newsletter #264: Your code can now call back to the Wikidata fetch functions

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we introduce the possibility of calling Wikidata fetch functions, we present a new Type, we celebrate more than 200 new functions this week, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Enjoy the reading! -- User:Sannita (WMF) (talk) 13:13, 11 September 2026 (UTC)

Maybe with "call back to the Wikidata fetch functions" it would be possible to craate an implmentation for infobox rows taxonomy (Z38960) as described in its discussion page. Who can help? HenkvD (talk) 12:43, 14 September 2026 (UTC)

module:citation and templates

template:cite encyclopedia requires it Arlo Barnes (talk) 02:28, 13 September 2026 (UTC)

WF:AN to request imports from another wiki. YoshiRulz (talk) 02:59, 13 September 2026 (UTC)

Thanks, moved to WF:administrators' noticeboard#importing module:citation and associated templates. Arlo Barnes (talk) 19:55, 13 September 2026 (UTC)

Calculadora de Obras de Artista por Periodo

Hola, necesito una función que calcule a partir de dadas

• Una fecha de inicio (dd/mm/aaaa)
• Una fecha de final (dd/mm/aaaa)
• Un artista o grupo de artistas

La cantidad de obras hechas en ese periodo de tiempo por ese artista o grupo de artistas. Jackie SMG (talk) 05:40, 13 September 2026 (UTC)

Something like (Q41264, 1650-01-01, 1659-12-31) → 7? That's not currently possible, because it needs to jump from the artist's Item to the works' Items (backlinks), which SPARQL can do but Wikifunctions cannot.
Something that is currently possible would be to take a list of works as arguments and filter them by date: example. YoshiRulz (talk) 19:06, 13 September 2026 (UTC)

Más o menos algo así quiero, que se haga mediante Wikidata. Aunque igualmente, ustedes son los que saben programar, por algo estoy aquí solicitando. Muchas gracias de igual forma.

Esto es para un proyecto que tengo llamado m:Wikimuseum ~ Art, entonces necesito funciones para ese proyecto para no tener que calcular todo a mano. Les voy a dar actualizaciones si algo pasa.

Atte: Jackie SMG (talk) 19:14, 13 September 2026 (UTC)

Hola, soy yo de nuevo. Quiero darle las gracias a la comunidad de Wikifuntions por responder a mis dudas y les quiero avisar que, por motivo de m:Wikimuseum ~ Art, les voy a estar pidiendo funciones de forma continua para poder desarrollar este nuevo proyecto, el cual planea convertirse en un proyecto hermano. Muchas gracias por su atención.

Atte: Jackie SMG (talk) 19:51, 15 September 2026 (UTC)

The next Natural Language Generation Special Interest Group meeting is tomorrow!

Hi all! A quick message to inform you that Denny will lead a quick first introduction to syntactic phrase functions in the next Natural Language Generation Special Interest Group meeting, that will be held tomorrow, September 15, at 16:00 UTC (link to the meeting).

See you at the meeting! In case you can't join, the meeting will be recorded and made available on Commons. -- User:Sannita (WMF) (talk) 13:27, 14 September 2026 (UTC)

Categories, classifiers, tags and the Function catalogue

Functions are manually classified within the Function-catalogue sub-pages. Objects in the main namespace, including functions, may also be organized into traditional Wikimedia categories by categorizing their Talk pages. In addition, objects may also be grouped together using their labels or aliases; for example, equality functions are likely to have "==" as an alias. There may be other mechanisms that I have overlooked.

These approaches share the drawback that they are essentially monolingual and, in practice, mainly restricted to English. I suggest that we should replace the English strings used for such purposes with Multilingual text (Z12) objects and link to these wherever feasible. In the future, it may be possible to link directly from any Persistent object (Z2) to such a “tag” object, but I think we would need to create a Feature request on Phabricator for this. In the meantime, maybe we should explore using embedded function calls to provide headings within the Function catalogue? GrounderUK (talk) 10:26, 16 September 2026 (UTC)

Great ideas. I support all. --99of9 (talk) 10:33, 16 September 2026 (UTC)