Abstract Wikipedia abstractwiki https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page MediaWiki 1.47.0-wmf.15 first-letter Media Special Talk User User talk Abstract Wikipedia Abstract Wikipedia talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk TimedText TimedText talk Module Module talk Translations Translations talk 4 6 14647 14585 2026-08-13T15:55:40Z MediaWiki message delivery 61 /* Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 */ new section 14647 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> 56ug0c65qu9vyims2x3s7uxcjywpiya 14678 14647 2026-08-14T06:50:16Z Theki 2698 /* Translations */ time to go 14678 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> mc17h1vthlnb4kglp5jydckv7jjeqo5 14680 14678 2026-08-14T06:51:15Z Theki 2698 /* Policy drafts */ 14680 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> 8af8a06txzu2kv9kg4sh5ysxd2rxqnr 14681 14680 2026-08-14T06:51:31Z Theki 2698 /* Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 */ 14681 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> lc1y9o0muw0la1sdq9b8u1a4jv9u1gu 14684 14681 2026-08-14T06:52:24Z Theki 2698 /* To abstract Wikipedia or be the Abstract Wikipedia */ 14684 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> ehuhd9g391zqiw7u3fz7ltkxmuum7pw 14686 14684 2026-08-14T06:53:25Z Theki 2698 /* template suggestion */ 14686 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> 4d29errhr9qxcefmwubi0otfnge3jqf 14688 14686 2026-08-14T06:53:46Z Theki 2698 /* Marking NLG Default text */ 14688 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> 7q9m5u505ezmrz5urwww8d14rsktxde 14690 14688 2026-08-14T06:54:16Z Theki 2698 /* Ratification of the deletion policy proposal? */ 14690 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> ghhwp6n5ca1x2c2ts3io027718uaaae 14691 14690 2026-08-14T06:54:49Z Theki 2698 /* Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward */ 14691 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> akg7xu7cxcu0ji7vgul5s0kshx6n4kc 14693 14691 2026-08-14T06:56:04Z Theki 2698 14693 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> f8x063veqpvopq9xa5z6gbwn81kf5h5 14696 14693 2026-08-14T06:57:14Z Theki 2698 /* Spaces between sentences, another attempt */ 14696 wikitext text/x-wiki {{#ifexist:Abstract Wikipedia:Project chat/Header/{{USERLANGUAGE}}|{{/Header/{{USERLANGUAGE}}}}|{{/Header}}}} {{/Archives}} <!-- Add your discussion below this line --> == Wikifunctions & Abstract Wikipedia Newsletter #252 is out: Improved loading and display of Test results == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-12|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you an improvement in loading and display of Test results, we talk about our next events, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that Denny will lead a discussion on the [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15#News in Types: way forward for natural language generation types|new NLG types]] in the next '''Natural Language Generation Special Interest Group meeting''', that will be held on '''[https://zonestamp.toolforge.org/1781625600 June 16, at 16:00 UTC]''' ([https://meet.google.com/xzn-kqer-mah link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:29, 12 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Add Z32962 to the list of suggested functions? == I think Z32962 would be a useful addition to the list of suggested functions. Can an admin please add it if others agree? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:25, 15 June 2026 (UTC) : Please comment on [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:48, 15 June 2026 (UTC) == Native labels == English Wikipedia usually displays native labels whenever applicable. Should we modify Z28016 to do the same or make a new function? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 04:39, 15 June 2026 (UTC) == readiness indicator == It occurred to me that an abstract page that works well enough for one language output might be broken for another, so it would be good to have some sort of indicator in the UI of which languages might be ready for transwiki and which still need preliminaries. I'm not sure if it would be better to do this as part of the testing and error-handling, or manually (like patrolling versions, but language-specific). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:12, 15 June 2026 (UTC) :: The function [[f:Z35921|NLG default text]] will be able to indicate on the target Wikipedia that the text in this language is not ready yet. Maybe sentences with this indicator, or even lemma's with this indicator could be excluded from the target Wikipedia. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:52, 15 June 2026 (UTC) :::I see that in the [[#Marking NLG Default text]] section, but I am thinking more at the whole-article level; dropping a problematic fragment from the final render could change the overall meaning. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:20, 15 June 2026 (UTC) == Add an LLM generator, where you can generate the schema == Hi. Please add an LLM generator, where you can ask AI to generate a schema for Abstract wikipedia. [[User:ChippyTimeCom|ChippyTimeCom]] ([[User talk:ChippyTimeCom|talk]]) 01:18, 17 June 2026 (UTC) :Do you mean an AI model to translate natural language input to abstract output? This was tinkered with before, I believe, last year—see [[f:Wikifunctions:Status updates/2025-05-09]] if you would like to read about it. This idea remained a mockup and not much more from what I can tell, but they may revisit the idea someday. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:40, 18 June 2026 (UTC) :: The main thing stoping one from pulling up a chatbot is that it has no knowledge of what wikifunctions are available, meaning it will probably just hallucinate them. I know Gemini has an ability to upload files, but all of Wikifunctions would be too large. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:58, 18 June 2026 (UTC) :::We have no obligation to use an LLM, that's just the main thing associated with the buzzword that is AI now. We can really come up with any AI model—''in a general sense''—that will fit our needs. You can do a ''lot'' with simple neural networks. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:33, 18 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #253 is out: The or not the, this is (the?) question == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-19|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a delicate question regarding grammatical framework, we talk about our next events and about the results of our latest online meetings, we discuss news about Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:34, 19 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30701693 --> == This needs to be fixed == On tennis [[Q847]], it says "Tennis is the country of origin of England." [[Special:Contributions/&#126;2026-36465-63|&#126;2026-36465-63]] ([[User talk:&#126;2026-36465-63|talk]]) 07:31, 23 June 2026 (UTC) :Thanks, I've switched it around. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 09:51, 23 June 2026 (UTC) == HTML, monolingual text or String for fragments == I think there is an important issue on the Output type of parts for text segments. Currently some sentences produce String output (like [[f:Z26039]] ) or monolingual text output ( like [[:f:Z26570]] ) pr HTML output ( like [[f:Z36200]] ). Apart from not being consistent I think there is even a bigger issue: these types don't allow text to be set in bold (in the introduction sentence for instance), or wikilinks to other AW articles. Am I correct that is only allowed in HTML text? If so I think we should change ALL languages functions to output type HTML as soon as possible. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:51, 24 June 2026 (UTC) :Currently, I am exploring this function for converting all of these to HTML fragment [[f:Z36303]]. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 16:46, 24 June 2026 (UTC) ::OK, thanks. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 24 June 2026 (UTC) :I agree that new sentence functions should be HTML. For now the old ones should be wrapped by a converter (which is best done on WF). Then all calls from AW can be to HTML producing functions. When we need bold we could either try to inject it, or write equivalent functions that will eventually replace the usage of the string ones. The string ones may still be valuable for processing some of the new NLG types, so we shouldn't actually flip the original functions. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:30, 24 June 2026 (UTC) ::I think wrapping the functions to HTML is delaying the solution. We either need to flip all (NLG) functions or all functions should be copied to HTML versions (and the all functions shoule not be used therafter) ::{| class=wikitable ! Option !! Pro !! Con |- | A. Wrap all fuctions to HTML || Easy to perform || This is delaying the solution |- | B. Flip all functions to HTML || Keeps tracebility || Huge impact/disturbance, especialy when cached |- | C. Copy all functions to HTML || No disturbance || Looses tracability |} :: The most practical soulution would be option C. I woluld perfer that as soon as possbile. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:05, 25 June 2026 (UTC) :::I like your suggestions. Based on my personal experience with different result types from Wikifunctions, I would suggest that AW support all three and convert the results to HTML using built-in functions. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 05:19, 25 June 2026 (UTC) ::::The reason why function need to change is because the current string functions don't allow HLTM features like bold text, wikilinks etc. AW supporting all 3 type pf output could easily be avoiding by option A. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:29, 25 June 2026 (UTC) :::C is fine by me. The easiest first-implementation of a copied function C is a wrapper of the monolingual/string, so A is sort of the first step of C. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:20, 25 June 2026 (UTC) ::::OK, good suggestion. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:13, 25 June 2026 (UTC) :No. I really don't see why we should. These are functions that generate text fragments in a single language—the monolingual text type is the most appropriate return type for them. It is just text. They can be coerced to HTML extremely easily and doing that step ahead of time, hardcoded, for the sole purpose of making abstract articles ''marginally'' easier to write, is just not worth the effort and foregoes what makes the functions' return types suitable in the first place. If there is some argument that can be made for hard pivoting to HTML fragments then I am all ears, but I really don't see a reason for it. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:53, 25 June 2026 (UTC) ::I like to contradict. These functions create complete sentences, nd those should be able to use HLTM features like bold text, wikilinks etc. My current interest is to add HTML texts like <nowiki><span lang="mul ">NLG Default text</span></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 06:05, 25 June 2026 (UTC) :::These additional features (bold/links etc) would benefit from additional parameters to control them. I still don't know how to do this best. I tried once at [[:f:Z32496]] and [[:f:Z32410]], but it may not be right, and may not be a complete solution anyway. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:26, 25 June 2026 (UTC) ::::A newer idea I had is to add all the links in the language-configured function, then call link-removing functions like [[:f:Z36853]] or [[:f:Z36831]] when composing them into AW. This could extend to swapping links for bold. Instead of an initial link, the QIDs could be wrapped with HTML spans with a QID ID, which could then be selectively converted into links or bolded etc. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:16, 25 June 2026 (UTC) ::Simple wrapping is just to benefit the AW editor. IMO it's worth it because it's pretty easy to make a new function, so is very low cost, and for the new editors on AW, they don't have to understand composing or our WF Types. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:30, 25 June 2026 (UTC) :::OK, let's start with option A, as a first step for option C. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 07:16, 25 June 2026 (UTC) ::::I have made wrappers (option A) for some general functions like [[f:Z36983]], [[f:Z36983]]. [[f:Z36987]], [[f:Z36993]] and [[f:Z37011]]. [[f:Z32965]] already existed, but as well as the monolingual [[f:Z26095]] both have an error: Error in evaluation. Can somebody fix this? On the AW articles I have updated a few lemmas by replacing the old functions to HTML functions, but find this quite cumbersome. A few hundred lemmas should be updated, but I have no time and/or no desire to do so. In the coming weeks (or so) I will start on Option C for these functions. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:51, 27 June 2026 (UTC) :::::Thanks. I'll try to help replace some of the usage. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:12, 29 June 2026 (UTC) :::::I think I've sorted out [[:f:Z32965]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 07:45, 29 June 2026 (UTC) :::So a bunch of bespoke functions on Wikifunctions that offer some marginal improvement over their more generalized counterparts, and we expect to do all of our language generation functions ''this way'' now or something, god forbid we expend ''one'' extra function call to just wrap the output if an injection function is really that scary to you. Wrapping the functions to HTML is not 「delaying the solution」 more than it's just the least disruptive way to approach this completely frivolous problem. Are we to write all of our NLG functions to output HTML now? That is what makes sense for us now, in the future? What? We have a type for this, it's called Monolingual text. We have Python and JavaScript at our disposal, and they are wicked biznasty at string manipulation (i.e. they are very good at it), so injecting formatting into a larger sentence instead of porting the whole thing over to use HTML exclusively is really not that big of an ask. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:23, 7 July 2026 (UTC) ::::Then please try to have [https://www.wikifunctions.org/wiki/Z37011?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37011%22%2C%22Z37011K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q90%22%7D%2C%22Z37011K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z37011K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q142%22%7D%2C%22Z37011K4%22%3A%22Z1216%22%7D this] error in HTML. Currently it is ❌≪Parys (is the) haadstêd (of) Frankryk .≫❌ Please have it changed to <span style="color:magenta;">Parys (is the) haadstêd (of) Frankryk .</span> [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:02, 7 July 2026 (UTC) :::::Thinking about this. One way we could do this particular markup would be for default monolingual functions to return a result with special language code (perhaps mul, zxx, ...). This would require wider discussion. Then the HTML function could detect that and wrap accordingly. But it doesn't solve the general problem of injections IMO. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:13, 8 July 2026 (UTC) ::::::This is now working (using [mul]) at [[:f:Z37462]]. This should work for all monolingual base functions, but not for those starting with strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:49, 9 July 2026 (UTC) :::::::I updated [[f:Z36911]] and [[f:Z36909]]. I am not sure if this works as a lot is cached. The string version will probably not work yet, so I left that one using ❌≪ ≫❌. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 08:09, 9 July 2026 (UTC) ::::::::After my post I actually made that function and test even more complicated to include a call to action (CTA): a link to the function that is not configured in the requested language. I am starting to like where this is going, and think I can even get it done with strings by recognising your ❌≪ pattern, stripping it, and replacing it with a span (and a CTA link) when it turns to HTML. Unfortunately the linking requires passing in a ZID, so might need a new general conversion function with an extra parameter. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 08:40, 9 July 2026 (UTC) :::::::::Here's what I did with a string function: [[:f:Z37497]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:31, 9 July 2026 (UTC) ::::For me, injections are not so easy. A simple one is trying to inject a link to Sydney into en:"Sydney Harbour Bridge is the closest to the ocean in Sydney." (In all languages, so sometimes the subject-object order will be reversed.) But even still, I'd really like to have good injection functions, so if you're up for making them, I'll definitely use them. If they work reliably on all NLG monolingual strings, then we can use them in the wrappers (even if you think the wrappers are frivolous), and the configurations can remain deeper on the monolingual strings. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 01:56, 8 July 2026 (UTC) :::::I've added this test at [[:f:Z37479]]. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:29, 9 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #254: Working on Functions, together == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-26|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on new collaborative patterns emerging in our community, we discuss news in Types, we share some events that relate to Wikifunctions and Abstract Wikipedia at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:58, 27 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30724999 --> == Wikifunctions & Abstract Wikipedia Newsletter #255: Integration on test wiki and annual plan == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss integration of Abstract Wikipedia in Test Wiki and our objectives for the new Wikimedia Foundation Fiscal Year, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1783359000 July 6, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 08:22, 2 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Response to English Wikipedia criticism == Hi all, you might be aware of [[:w:en:Wikipedia:Village pump (WMF)#Abstract Wikipedia goes somewhat live and already hosts unattributed enwiki copies...|this discussion on English Wikipedia]], that raised several criticisms about the project. As a team, we [[Abstract Wikipedia:Response to English Wikipedia criticism|drafted an initial response]], that we want to run through you. If you want to suggest changes or edits, please [[Abstract Wikipedia talk:Response to English Wikipedia criticism|use the talk page]]. Please, keep a polite and constructive tone. The editing period will be '''open until July 17'''. The final result of this editing will be published on Meta, and will be linked to the English Wikipedia community. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:18, 6 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #256: Moving toward our first Abstract Wikipedia integration milestone == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss further our objectives for the new Wikimedia Foundation Fiscal Year, we show the latest community tool, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:43, 9 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Infoboxes == I changed layout of the infoboxes, to be more in line with Wikipedia's infoboxes. See for example [[f:Z36678|Z36678]] "infobox for city" used in [[Q90]] "Paris". I would like [[f:Z37625|Z37625]] "infobox row" to check if a claim exists in Wikidata, but I have difficulties with he parameters for [[f:Z27299|Z27299]] "Wikidata item has claim?". With with literal input it works but with argument references it gives an error. Who can fix this?<br> Furthermore I think it would be nice it we could add a pen-icon next to the values to be able to edit the claim on Wikidata, and pen-icon at the property to edit the label. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:04, 12 July 2026 (UTC) :I was able to fix my error. Infobox rows will now only be shown when a claim exists. That will prevent errors a particular claim is missing for a particular city. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 13:56, 13 July 2026 (UTC) ::Looks awesome. Though I was trying it with other cities (such as Chicago and Moscow) in English, and it was throwing orchestrator rate limit errors. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:41, 14 July 2026 (UTC) :I am struggling to find a function that indicates a Wikidata property type, like Property:P569 (date of birth) is a date type (Point in time?). Can anybody help? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 09:25, 17 July 2026 (UTC) == Lexemes of property names == {{ping|HenkvD|feeglgeef|GrounderUK}} Hello. Please could anybody tell me their opinion on this question? It may be necessary to find a lexeme corresponding to the name of a property. For instance, [[f:Z28445|Z28445]] "most recent year-specific sentence about item" has a property reference as argument and needs the name of the property to be rendered in the output; the particular property could be {{Q|P1082}}. In the English implementation, the name of the property "population" is found from the WikiData property attributes, but for other languages other syntactical information such as gender may be needed, so I suppose that a link to the lexeme is required. How should the rendering function find a link to the lexeme? Is there a way to find the item corresponding to the property? Or should the syntactical information be found some other way? [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:14, 12 July 2026 (UTC) :Ah. Now I've found {{Q|P1629}}, so i suppose that that provides a solution. Sorry to disturb you. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:44, 12 July 2026 (UTC) == Feedback needed on constructing a new abstract article == Hi all, I wanted to ask a couple of questions to the community regarding how easy or difficult is to construct a new abstract article. Consider I'm a newbie that wants to create a new abstract article about my home city. What would you suggest I do first? Is there a sufficiently good example I can copy and adapt? Can I add already almost everything that I would like to add (say, number of inhabitants, region where my city is, mayor of the city, stuff like that) or is there something I ''cannot'' add still? What is there and what is missing at the moment? Thanks in advance for your answers! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:51, 13 July 2026 (UTC) :Sannita, in general it is very difficult (even for me) to construct a new abstract article from scratch. Copying from an existing article is easier, as also mentioned in [[Help:How to create an article]]. That example is also a city, so we better make that article a good example. The information you mention could be in the infobox, which is also available to use and extend (if performance permits). Creating a article by copy/paste should be done for each sentence or paragraph. Add additional sentences is still very difficult. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:08, 13 July 2026 (UTC) :The biggest challenge for me would be finding the right functions to do the job. It's kinda to the point where the help article, mentioned by HenkvD, is just saying to copy other articles. The issue is with trying to add more "unique" sentence structures that may not be in every article. For example, take this: :<code>New York is known for being the financial hub for the United States</code> :More abstractly: <code>X is known for being Y for the Z</code> :If a function that does something like that doesn't exist, that pushes the user into a weird space where they may have to use a different function that may sound more robotic or be grammatically incorrect. :It's not hard to create a stub abstract article, but anything beyond that takes a lot of time and effort to find the right functions for the job. Additionally, dealing with different data types (ex: Wikidata item reference vs Wikidata item) may turn off people who aren't familiar with computer science principles. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 02:21, 14 July 2026 (UTC) ::The problem with copying other articles is that you need to somehow know that the article you're copying from is correct. If I wanted, for example, to make an article about some root vegetable like [[Q188614]] and copied [[Q81]] I'd be doing a very bad job because the second paragraph is written in a way that is completely untranslatable in its structure (by that I mean it is not fixable by changing [[f:Z18845]] to a function that work for all languages, the fragment itself integrates features of English grammar, such as SVO word order, and therefore needs a rewrite). ::What you probably need is a collection of Featured Articles that are written in accordance with best practices and are safe to copy from. This would make it so novice users don't start picking up anti-patterns and propagating them all over abstract Wikipedia, making them harder to fix. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 15:32, 15 July 2026 (UTC) :::Absolutely correct. I've deleted that paragraph with an explanation that that kind of work is better done on Wikifunctions to construct an English renderer. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:20, 17 July 2026 (UTC) :I'm throwing together some thoughts at [[User:99of9/ArticleWriting]]. It's still very much a draft, but I hope the ideas help. Asking questions about it may help me focus on what you want. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 11:53, 17 July 2026 (UTC) :To be honest I don't think we are ready to start adding new articles at full speed. Only a few functions can be used properly, and not many functions can be used in enough other languages. Furthermore the performance is so bad that most of the functions will time-out. Personally i consider the AW articles as sandboxes to experiment on, not yet articles that are well constructed. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:33, 17 July 2026 (UTC) {{tracked|T430898}} ::Single fragments usually don't time out when you first put them in. So you can usually edit productively in your first session. But then 24 hours later, the whole thing gets re-cached in a single go, none of them complete, and the errors all get cached. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:42, 17 July 2026 (UTC) ==Discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]== [[File:Symbol watching blue lashes high contrast.svg|20px|link=|alt=]]&nbsp;You are invited to join the discussion at [[Meta:Requests_for_comment/The_future_of_Abstract_Wikipedia|Meta Requests for comment: The future of Abstract Wikipedia]]. <!-- Template:Please see --> [[User:Qcne|Qcne]] ([[User talk:Qcne|talk]]) 11:34, 14 July 2026 (UTC) == Feedback on function I created == I would ask this in the Telegram channel, but this is a longwinded question that I would like to get more detailed feedback on. First and foremost, it is seriously important that we get the ability to call functions with python/JS implementations. It would make creating these types of functions ten times faster, with the additional benefit of being easier to read. I'm relatively close to completion on a function that will create a brief introductory paragraph for species articles: '''[[wikifunctions:Z37793|Intro for species in English composition]]'''. It contains the following: * Intro (e.g. "'''''Homo sapiens''''', also known as the '''Human''', is a species of primate in the family [[Q635162|Hominidae]].") **The word "primate" in this case is a string supplied by the user and is optional - it could be anything they want (ex: humanoid, animal, bipedal creature, etc) * Year of description (e.g. "The species was described in 1758 by Carl Linnaeus.") * IUCN conservation status (e.g. "''C. lupus'' has been assessed as Least Concern by the [[Q48268|International Union for Conservation of Nature]] (IUCN).") So all together: <blockquote> '''''Dionaea muscipula''''', also known as the '''Venus flytrap''', is a species of carnivorous plant in the family [[Q156185|Droseraceae]]. The species was described in 1768 by John Ellis. ''D. muscipula'' has been assessed as Vulnerable by the [[Q48268|International Union for Conservation of Nature]] (IUCN). </blockquote> It also works when there is a lot of taxon authors:<blockquote> The species was described in 2026 by Anh Van Pham, Chung Van Hoang, Nguyen Quang Truong, Thuy Thu Thi Nguyen, Ky Danh Nguyen, Toan Canh Thai and Thomas Ziegler.</blockquote> The composition itself is basically stringing together a lot of html fragments - if you want to find a specific bit, you just scroll down to around the section of the paragraph you want. Each HTML fragment is roughly a sentence. I originally intended to add a sentence about distribution, but I didn't know how nicely that would play when [[wikidata:Property:P9714|P9714]] has a million values attached to it. Eventually I plan to integrate this translation into a system like the [[wikifunctions:Z20898|one that exists for year articles]]. I have a couple questions: * Is there any other additions to this function that I should make? Ideally, this should be data I can fetch from Wikidata. * What are the best practices to make the function easier to translate? I've tried to rely on other functions which can work with different languages (and making my own, including [[wikifunctions:Z37833|Z37833]]) * I'm still relatively new to Wikifunctions. If someone could take a look and see if there is any glaring errors or functions that exist and do what I am already doing, that'd be awesome. I am aware of a couple bugs: * The error handling is not great, and the sentence about description date has a hardcoded true value in the if function. I'm looking for a better way to deal with the errors - the main idea for this is to stop the function from generating sentences if the necessary values don't exist in Wikidata. * A function I made ([[wikifunctions:Z37808|Z37808]]) that fetches the describing authority crashes if the person does not have a label in the given language. Feel free to edit/fix anything if you want to. Thanks a ton! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 08:32, 17 July 2026 (UTC) :Nice one. I'll take a look. My general comment is that the extra supplied string (e.g. for the family) should not be a string, it should be a different QID. This is because in Abstract Wikipedia we can't pass in single-language strings. The function needs to somehow get from the QIDs all the way to the HTML by itself. Once you've got the structure ready, the next thing you can do is include your examples as Tests. The easiest way to make an HTML test for a function which already has a configuration is to make one with an empty validation comparison, run it, then copy the stuff it failed with into the validation. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:21, 17 July 2026 (UTC) ::Oh, one more structural change. Even though this is for "English", it's usually best to accept an extra parameter for the "language variant", because there are a bunch of variants of English (which, for example, may have different common names). You may not use it for now, but it's a pain to change the arguments after the function has a lot of use. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:24, 17 July 2026 (UTC) ::And if you need the "of primate" hypernym to be optional, you could include a boolean parameter to say whether or not to print whatever QID is supplied. Or another idea, (this may be controversial) you could decide that if both QIDs were the same, that was when to drop the "of human". This second method would work particularly well in AW IMHO, because it would autofill both to be the same as the page QID, so it would work from the start without even clicking a boolean (and editors could then pick another QID if they wanted a hypernym). --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:31, 17 July 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #257: Beyond syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss syntactic tables and news in Types, we show some community blogposts and tools, we remind you of the Wikifunctions and Abstract Wikipedia events at Wikimania 2026, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:55, 17 July 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30755600 --> == Wikifunctions Reached rate limit == When I open [[Q408]], the article is full of "Wikifunctions returned a failed response: Reached rate limit in evaluator" except for some titles and images. This happens on many other pages. [[User:Steven Sun|Steven Sun]] ([[User talk:Steven Sun|talk]]) 12:11, 21 July 2026 (UTC) :This issue is tracked in https://phabricator.wikimedia.org/T430898 . The error codes sometimes get recategorised, but it ultimately seems to be some kind of rate issue. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:46, 21 July 2026 (UTC) == The problem of categories == As it stands, categories require you to physically type the link into the source editor (e.g. <code><nowiki>[[Category:Living people]]</nowiki></code>), which would require a page to be made, thereby nullifying the abstract page. I predict many wikis would like to be able to categorize Abstract articles, as in my opinion, any page that has substantial content (even if it doesn't exist yet) is worth categorizing. They may not populated in normal categorizes, but it could be something like this: * [[:Category:Abstract articles about living people]] * [[:Category:Abstract articles about STEM]] * [[:Category:Abstract articles about health]] * [[:Category:Abstract articles about geographic places]] * [[:Category:Abstract articles about extant species]] * and more, at the choice of the language's community <small>(similar to that of draft categories)</small><br /> Additionally, regarding only Abstract Wikipedia, it would be nice to be able to add (and see) local categories to abstract pages. We have over 2000 pages already, and the only way to find any of them is to go to [[Special:AllPages]], [[Special:LongPages]], or to click the random page button. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 00:09, 25 July 2026 (UTC) :Good suggestion. Can you put in a Phabricator feature request to figure out how to categorise? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:40, 25 July 2026 (UTC) ::Sure! [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 06:56, 25 July 2026 (UTC) == Suggested functions changed == I've swapped the suggested functions per the discussion on the talk page at [[MediaWiki talk:AbstractWikiSuggestedWikifunctions.json]]. Please let me know if this causes any trouble editing. In particular @[[User:Denny]], [[User:DVrandecic (WMF)]], [[User:Sannita (WMF)]], [[User:Jdforrester_(WMF)]] if will hinder your presentation, I'm happy to revert for a while if you are relying on the old list. If you're not relying on it, I'm confident that the new list is better for newcomers. Too many of them have been misled by the previous list. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:36, 25 July 2026 (UTC) :@[[User:99of9|99of9]]: Thanks! That looks great. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 07:12, 25 July 2026 (UTC) == "replace Abstract Wikipedia link to QID with bold" doesn't work if the label of QiD is the same of the dependency == HI, I'm creating some stubs about the capitals of the world. In case like [[Q1842|Luxembourg]] or [[Q55115|Monaco-Ville]] the funcion above doesn't work, probably because it reads twice the words Luxembourg and Monaco [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:54, 25 July 2026 (UTC) :I've fixed by replacing the literal value with the QID [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 16:31, 26 July 2026 (UTC) == Expanding FAQ to correct common misconceptions == re: The ongoing closure RfC on Meta, I thought it might help to make a {{Q|4345841}} for AW. I didn't feel it was my place to do so, so I gathered [[Project_talk:Frequently_Asked_Questions#Correcting_common_misconceptions,_possibly_needs_a_separate_page_AW:NOT|a list of misconceptions on the FAQ's talk page]] which can be used as a starting point. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:52, 28 July 2026 (UTC) :The points all have an answer now, ready for copyediting. And there's still the question of where to put them. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:05, 11 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #258: Abstract Wikipedia at Wikimania == <div lang="en" dir="ltr" class="mw-content-ltr">There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss the presentations and workshops at Wikimania, including a features feedback request based on what we heard there, and highlight new features shipped this week including diffs for Wikifunctions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! [[m:user:Quiddity (WMF)|Quiddity (WMF)]] 19:05, 30 July 2026 (UTC) </div> <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> == Suggestions wanted for early pilot articles to make available cross-wiki == Hey all, We're building up to the first pilot release of cross-wiki abstract articles, where one community's sysops will be able to pick some (or none) of certain abstract articles onto their wiki for their readers to see. To demonstrate the system at all, we picked five general topics: Paris and London, Wikipedia, and our commonly-used "example" topics of Douglas Adams and Jupiter. (You can see the available list at [https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].) However, these are probably not the best or only topics to get started with. We're going to be only making a small selection available to start with, but we'd love your ideas of what articles are the best early demonstrators of the work you're all doing. (I appreciate that this may be influenced by which pilot wiki or wikis are using them, so happy for you to have further ideas later, of course!) What 3–5 articles do you collectively think we should add to this list? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 21:16, 5 August 2026 (UTC) : I think the proposed articles are already available on the target pilot communities/pilot Wikipedia's. I therefore propose other type or articles :* an Italian politician, only available in Italian language :* small towns in the smaller target Wikipedia's :* a species only available in one language : Furthermore I don't think the larger wikipedia's (en/de/fr/es) are open for this kind of experiments, but I could be wrong. :[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 05:34, 6 August 2026 (UTC) ::Yeah, I heavily doubt enwiki will be open to Abstract Wikipedia integration given the fiasco that has been happening. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 21:54, 6 August 2026 (UTC) :I really like the diverse range of these five selected articles ([https://abstract.wikipedia.org/wiki/Special:PreviewAbstract?uselang=en Special:PreviewAbstract].). I feel that we can further expand the list. We currently have [[f:User:Jsamwrites/Infoboxes|infoboxes]] covering topics such as astronomy, chemistry, media, GLAM, history, computer science, and Wikimedia movements (including Wikimania). We also have infoboxes for languages alongside inflection tables, which should particularly interest Wiktionary communities. For example, article on [https://abstract.wikipedia.org/view/en/Q11923 French grammar]. :Additionally, some of the recent articles on AW are multilingual, while others are bilingual (English and French, showcasing how we can handle tenses and pronoun usage). A more detailed selection of articles is a great way to demonstrate that Wikifunctions and Abstract Wikipedia can effectively support both simple and complex articles. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 18:55, 6 August 2026 (UTC) :: Just for your information, the French grammar article is incorrect, because both sub-level articles about pronouns are incorrect and therefore the table found on all three is wrong. "on" is a singular, third person pronoun, and always conjugated as such. Its use as a plural, first person one is purely informal/colloquial and should absolutely never be seen anywhere on Wikipedia. It is a very basic mistake that no French speaker of even rudimentary proficiency would have missed, so I wonder how this table was generated. If that is the kind of example you plan to showcase as proof of concept, or integrate into Wiktionary, I would seriously reconsider, especially since French is one of the biggest languages in the movement, not one of the much smaller ones supposedly targeted by abstractwiki. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:09, 7 August 2026 (UTC) :::Thank you for pointing this out. This content actually comes directly from a Wikifunctions function, so I’ll fix that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:56, 8 August 2026 (UTC) ::::{{ping|Choucas}} thanks for letting us know but I disagree and [[:en:Personal pronouns in French]] disagrees too. The fact it's informal and colloquial means it shouldn't be used in sentences but on a table showing all the possibilities, it should absolutely be present. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:48, 10 August 2026 (UTC) ::::: If you clicked on the interwiki link on my userpace, you have probably seen that like you, I am a native speaker, so there is no need to explain to me how personal pronouns work in French. If the table looked the same as on the enwiki page, with the additional columns and footnotes, then yes, there would be no harm in showing the subtleties around the use of "on". However, currently the table is three rows and two columns, with no explanation whatsoever, and within the rest of the page it clearly implied it is conjugated as a plural first person pronoun. Either there is a full table, or there is a simplified one and "on" is put in singular third person, but having it only in first person plural was just wrong. That is really the only thing I was pointing at, albeit in way less many words. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 09:44, 10 August 2026 (UTC) ::::::Yes, that (I hope) was the fix I applied on Wikifunctions. The inclusion of “on” as a third-person singular pronoun was reversed this morning. Hopefully we’ll see an expanded table in due course! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 10 August 2026 (UTC) :::::::@[[User:GrounderUK|GrounderUK]] We will need a detailed table to avoid confusion. I temporarily removed it from the table. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:18, 10 August 2026 (UTC) ::::::@[[User:Choucas|Choucas]] For the time being, I removed "on" since it requires a detailed explanation (I will add when we are able to add more complex sentences.). However, English Wikipedia article needs to be corrected as well: https://en.wikipedia.org/wiki/Personal_pronouns_in_French#Subject_pronouns [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 10:17, 10 August 2026 (UTC) :I think we need a process (like this but more structured) where the AW community decides which articles are ready to be "released", before they can be taken up by other wikis. Otherwise (as Choucas highlighted above), we risk losing credibility by making available drafts or serious errors. I'm not saying they need to be perfect before release, but I think it should be a community decision at this end as well as the other end (the language-wiki embedding them). Since this batch is the first, I think we should even vote on whether we support each of the 5 the team chose as ready. What do others think? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:14, 8 August 2026 (UTC) ::I agree that we might need a process now in the early days, but we should when creating such policy document the ambition that we eventually would like to make it solely in the hands of the reusing community. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 09:52, 8 August 2026 (UTC) :::I fully agree that we need a clear process, including a decision by the AW community on the quality of the pilot articles before they are released to the target wikis. It should also be explicit which target wikis and communities are in scope. :::On [[Help:Abstract articles]], I read that English, German, French, and Spanish Wikipedias are in scope as target communities. Does this mean that, for example, the English Wikipedia community has expressed interest in participating as a pilot? :::Regarding Dagbani, Igbo, and Hausa, these languages currently have either no configured language functions or only one. Before selecting pilot articles, the process should begin with configuring and testing the necessary language functions in those languages. Only after that foundation is in place would it make sense to start identifying and evaluating potential pilot articles. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 10:21, 8 August 2026 (UTC) ::::It’s not very clear. I think it just means that during the pilot period, any pilot community’s language would be added to the limited set of languages for which previews would be available. From the final paragraph in [[Help:Abstract articles#Language coverage]], it appears that the Abstract Wikipedia community would ultimately control which languages are supported (expecting most or all). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:27, 8 August 2026 (UTC) :::I think Abstract Wikipedia contributors need some way to indicate that an article is a draft or otherwise inadequate, based on the quality of the information it currently provides. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:41, 8 August 2026 (UTC) ::::Perhaps, but I hope we won't try for a system that requires us to that manually article by article. I imagine that we will create, for example, one good set of functions to create an abstract article about tennis players or lakes and then bot create tens of thousands in one go. And obviously we should have some high standards for when to run the bot, but it will then be unrealistic to check them one by one by hand. A tool that says which ones renders flawlessly and in which languages would be great (and even better if it can also give reports for what is missing for those who can't, like missing data on Wikidata or lexemes or lables in that language). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 21:34, 8 August 2026 (UTC) :::::I’m not in favour of bot-created articles. But the quality-assurance challenges exist even with changes to a single Wikifunctions function or Wikidata lexeme (for example). That’s why we will need article diffs that show how the rendered content has changed over time, not just the article structure. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:49, 9 August 2026 (UTC) ::::::Early on in the development, there was talk about "template articles" to be used for all articles of a certain topic (like soccer players or lakes). That is not in the development plan any longer. And if we neither have that nor going to create articles in bulk, I don't think I have any interest in this project any longer. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 10:29, 9 August 2026 (UTC) :::::::I’m just expressing my personal reservations about bot-articles. Templates and information-rich functions (like infoboxes or introductory content) are a different matter. Ultimately, I think the development plan needs to align with the needs of the content creators and content consumers, rather than the other way around (recognizing that resources are always limited, of course). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:42, 9 August 2026 (UTC) ::::::::I'm sorry, I didn't mean templates in the traditional Wikipedia sense. Rather that we have an entire abstract article as a template. Like the "canonical lake article". Which would mean that an improvement of the template improved all abstract articles about lakes (that hadn't been subst:ed and individually developed because it was a lake someone cared extra about). <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 11:14, 9 August 2026 (UTC) :::::::::We don't have templates, but instead we do already have some intro sentences, like [[f:Z37922|Z37922]] (intro for species) and [[f:Z38757|Z38757]] (person lead sentence with occupations). Personally I think that once enough functions are available in enough languages we could create thousands of bot articles for cities, species, soccer players, lakes etc.Into senetences combined with infoboxes that would provide enough basic information in my opinion. Details information can then be added on article by article basis. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:46, 9 August 2026 (UTC) :::::::::Yes, that’s what I thought. I don’t think it’s technically difficult, but the subject-specific content would generally have to come from Wikidata or Commons, wouldn’t it? I’d be more inclined to say: here are the editorial “facts” (which may or may not be present on Wikidata), and here is one standard representation of those facts (which may or may not be an article, as such). But I appreciate this is off-topic. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:50, 9 August 2026 (UTC) ::Yes. I don’t think the team have already decided that those articles are ready, but that is clearly a community decision. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:45, 8 August 2026 (UTC) :There is 2 different things here. The topics and the content. :For the topics, the list is good, albeit too general. Adding a place (maybe a small town or a building like a small chapel), a species (some kind of fish) a more mundane person (some John Doe unlike the famous Douglas Adams) would be better to demonstrate the diversity of possibilities (the "template" works for every/most human, not just for "famous" ones). I think it needs to be topics that have no article yet on most Wikipedia (unlike London that already exists on most Wikipedia). :For the content, it's an other separate matter entirely. There is improvements but we are still a bit far from the minimum expected. We should keep working on that :Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:41, 10 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate Wikimedian of the Year and we discuss his favourite article in relation to Abstract Wikipedia, we introduce a new Type of function on Wikifunctions, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! We also remind you that in the next weeks these newsletter reminders will be paused, and that they will resume in mid-August. Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:19, 10 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> : While I understand the point this little apple story is trying to make, I am afraid this whole thing falls flat for a very simple reason: we are not in 2002 anymore. Wikipedia is not a wild new idealistic thing, that only years of work by passionate volunteers will prove can succeed. Even worse, this is actually showing that this new start of the road in 2026 is even rougher and less promising than how it was in 2002: indeed, at that time, absolutely anyone could come in any newly set up Wikipedia in their own language and type the equivalent of "an apple is a fruit" and be done in a matter of fifteen seconds. That is why all these apples grew: because it was as simple as adding more words in your own language, and correcting the words of others, and that was (and still is) the magic of it. Instead, Abstract is starting from scratch again, with an impossibly high technical complexity to add even the most basic sentence or correct the simplest typo, making the growth of any article an exponentially more complex endeavor. I am not blind to the charm of the idea behind Abstract, but it is hard to look at what it involves in practice and see how it makes sense in 2026. [[User:Choucas|Choucas]] ([[User talk:Choucas|talk]]) 15:33, 10 August 2026 (UTC) ::I see you've come here from the RfC.<br>The method of producing articles by translating individual sentences [[Special:Permalink/14399|is possible on AW]], but is of course antithetical to the "improve every language at once" nature of the project.<br>It's always going to be more work to add to an abstract article than just writing text, and that's acceptable because that work has a greater impact too. It will be the choice of each editor whether they want to contribute here or to a local wikitext article. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:03, 11 August 2026 (UTC) :::{{ping|Choucas|YoshiRulz}} you make a good point, looked at in isolation: writing one sentence is easier than writing one Wikifunction. But on Abstract Wikipédia you don't write sentence (nor translate), you set up pattern (a Wikifunction) that can be used on many articles (potentially all of them, we can imagine a point not so far away where all abstract Wikipedia pages would simply call one big general function "make an article", you can have a look at [[Q18498]]). The difference is like making an addition 1+1+1+1+... (Wikipedia method) and making a multiplication 5000*1 (Wikifunctions method). So at the start, it may seems to be more work but very quickly it's better and faster with much less work. And yes, Wikifunctions are not for everyone (just like Wiktionary, Wikimedia Commons, Wikidata are not for everyone) and won't replace Wikipedia (it goes without saying, but since it reuse the "Wikipedia" name, it should probably be said). Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 07:03, 13 August 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #260: Shoutout to User:99of9 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we congratulate our own User:99of9 for his extensive work with the Wikifunctions & Abstract Wikipedia communities, we discuss what happened at Wikimania, we introduce a document for interested communities to join Abstract Wikipedia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:55, 13 August 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30870212 --> 24zgww0c2zk2p9y2mqmna8nh0defv8y 4 10 14665 14031 2026-08-13T23:42:52Z EatingCarBatteries 1378 14665 wikitext text/x-wiki This is to become a list of the Abstract Wikipedia community's policies and guidelines. == Wikimedia-wide policies == * See [[m:Meta:Policies and guidelines|Meta-wiki's Policies and guidelines]] == Policies == * [[Abstract Wikipedia:Deletion policy]] == Drafts == * [[Abstract Wikipedia:Manual of Style]] * [[Abstract Wikipedia:Notability]] [[Category:Abstract Wikipedia administration| ]] i4tndb37nnhbayd959vhmm281tc0lfv 14666 14665 2026-08-13T23:43:15Z EatingCarBatteries 1378 14666 wikitext text/x-wiki This is to become a list of the Abstract Wikipedia community's policies and guidelines. == Wikimedia-wide policies == * See [[m:Meta:Policies and guidelines|Meta-wiki's Policies and guidelines]] == Policies == * [[Abstract Wikipedia:Deletion policy]] == Drafts == * [[Abstract Wikipedia:Manual of Style]] * [[Abstract Wikipedia:Notability]] [[Category:Abstract Wikipedia administration| ]] [[Category:Abstract Wikipedia policies and guidelines| ]] 6ntn210cid9vlceglr2a06d4lw1x24z 10 457 14634 14342 2026-08-13T15:41:28Z Sannita (WMF) 48 update 14634 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;<translate><!--T:1--> Volunteer's Corners</translate> * <translate><!--T:2--> The next Volunteers' Corner will be at <tvar name="date-and-time"><bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi></tvar> on <tvar name="platform"><bdi lang="en" dir="ltr">Google Meet</bdi></tvar> at <tvar name="link"><bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi></tvar>.</translate> * <translate><!--T:3--> The [[<tvar name="1">:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm</tvar>|most recent Volunteer's Corner]] is available on Commons.</translate> ; <translate><!--T:4--> Recent status updates about Wikifunctions</translate> <!--Keep this to the most recent 5 entries--> * <translate>[[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13</tvar>|2026-08-13]]: Shoutout to 99of9!</translate> * <translate>[[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05</tvar>|2026-08-05]]: Congratulations Jules*: An apple is a fruit</translate> * <translate><!--T:27--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29</tvar>|2026-07-29]]: Abstract Wikipedia at Wikimania</translate> * <translate><!--T:26--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16</tvar>|2026-07-16]]: Beyond syntactic tables</translate> * <translate><!--T:25--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08</tvar>|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone</translate> </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small"><translate><!--T:10--> More news</translate></span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> 0my8we4jfu11evxm0c0wv2xex019ygq 14635 14634 2026-08-13T15:41:43Z Sannita (WMF) 48 Marked this version for translation 14635 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;<translate><!--T:1--> Volunteer's Corners</translate> * <translate><!--T:2--> The next Volunteers' Corner will be at <tvar name="date-and-time"><bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi></tvar> on <tvar name="platform"><bdi lang="en" dir="ltr">Google Meet</bdi></tvar> at <tvar name="link"><bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi></tvar>.</translate> * <translate><!--T:3--> The [[<tvar name="1">:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm</tvar>|most recent Volunteer's Corner]] is available on Commons.</translate> ; <translate><!--T:4--> Recent status updates about Wikifunctions</translate> <!--Keep this to the most recent 5 entries--> * <translate><!--T:29--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13</tvar>|2026-08-13]]: Shoutout to 99of9!</translate> * <translate><!--T:30--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05</tvar>|2026-08-05]]: Congratulations Jules*: An apple is a fruit</translate> * <translate><!--T:27--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29</tvar>|2026-07-29]]: Abstract Wikipedia at Wikimania</translate> * <translate><!--T:26--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16</tvar>|2026-07-16]]: Beyond syntactic tables</translate> * <translate><!--T:25--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08</tvar>|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone</translate> </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small"><translate><!--T:10--> More news</translate></span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> 1875dz9cycv8ydui14xt2liaxbj73xr 0 641 14629 2982 2026-08-13T13:53:01Z Podroužek 6903 +image 14629 abstractwiki text/plain { "qid": "Q61", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M50896572" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q475050" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } rbifz6nnzpb2yuisfs4b9njwirfqky1 0 708 14617 13838 2026-08-13T12:18:10Z Feedmepaperr 1398 named after-sentence 14617 abstractwiki text/plain { "qid": "Q17198982", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M116676749" }, "Z36038K2": { "Z1K1": "Z7", "Z7K1": "Z36270", "Z36270K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36270K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q17343829" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q156623" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q627236" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P137" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z27849", "Z27849K1": { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q1081138" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q7533756" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, "Z27849K2": { "Z1K1": "Z7", "Z7K1": "Z38542", "Z38542K1": "https://npgallery.nps.gov/NRHP/GetAsset/6a1e79e0-9859-41a4-a86c-153dfa92b667", "Z38542K2": { "Z1K1": "Z6091", "Z6091K1": "Q7533756" }, "Z38542K3": { "Z1K1": "Z6091", "Z6091K1": "Q3719" }, "Z38542K4": { "Z1K1": "Z18", "Z18K1": "Z825K3" }, "Z38542K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z38443K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37464", "Z37464K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q3214840" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37464K2": { "Z1K1": "Z6", "Z6K1": "Z37273" }, "Z37464K3": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q3214840" } ], "Z37464K4": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q3214840" } ], "Z37464K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2044" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32839", "Z32839K1": { "Z1K1": "Z6091", "Z6091K1": "Q123705" }, "Z32839K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M179234881" }, "Z36038K2": { "Z1K1": "Z7", "Z7K1": "Z36270", "Z36270K1": { "Z1K1": "Z6091", "Z6091K1": "Q140562310" }, "Z36270K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q140562314" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q123705" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q140562310" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q123705" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q123705" } ] }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q140562314" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P137" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q140562310" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P137" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32839", "Z32839K1": { "Z1K1": "Z6091", "Z6091K1": "Q11298016" }, "Z32839K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37840", "Z37840K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q137785666" }, { "Z1K1": "Z6091", "Z6091K1": "Q61997217" }, { "Z1K1": "Z6091", "Z6091K1": "Q6174965" } ], "Z37840K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 444rvydirig61agbwjwmf76ae71pyox 0 755 14608 14590 2026-08-13T12:04:10Z 99of9 614 height of Mount Rainier 14608 abstractwiki text/plain { "qid": "Q1223", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M15949813" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q6664848" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M439001" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q731163" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q35657" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q12603" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1449" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q131684213" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P138" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q846295" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q11756" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q551700" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q10855061" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q844033" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q98681686" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37661", "Z37661K1": { "Z1K1": "Z7", "Z7K1": "Z37065", "Z37065K1": { "Z1K1": "Z6091", "Z6091K1": "Q2340694" }, "Z37065K2": { "Z1K1": "Z6091", "Z6091K1": "Q19269277" }, "Z37065K3": { "Z1K1": "Z6091", "Z6091K1": "Q394067" }, "Z37065K4": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37065K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37661K2": { "Z1K1": "Z6091", "Z6091K1": "Q2340694" }, "Z37661K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z37840", "Z37840K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q7324" }, { "Z1K1": "Z6091", "Z6091K1": "Q2109952" }, { "Z1K1": "Z6091", "Z6091K1": "Q548355" }, { "Z1K1": "Z6091", "Z6091K1": "Q1628203" }, { "Z1K1": "Z6091", "Z6091K1": "Q205485" } ], "Z37840K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q18350273" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P571" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "42" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12943371" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q106458883" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M187451298" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q5083" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q20429931" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37065", "Z37065K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37065K2": { "Z1K1": "Z6091", "Z6091K1": "Q5491373" }, "Z37065K3": { "Z1K1": "Z6091", "Z6091K1": "Q106458883" }, "Z37065K4": { "Z1K1": "Z6091", "Z6091K1": "Q578170" }, "Z37065K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P13574" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2927" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "18" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q106458883" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q3297259" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q3297259" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q3297259" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q82794" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3297259" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1082" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3297259" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q3046581" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q3046581" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q3046581" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q82794" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3046581" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P13574" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z6091", "Z6091K1": "Q187805" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "2" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, "Z36831K2": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q187805" } ] }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q1069" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M93987125" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q194057" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q3123499" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P610" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z6091", "Z6091K1": "Q194057" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q169358" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q194057" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2044" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q7937" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P7422" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P6591" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q2725376" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1082" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1538" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P4442" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z34250", "Z34250K1": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z34250K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q38838" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q159810" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q5333805" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "47" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q16042592" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q1787954" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z38542", "Z38542K1": "https://www.bls.gov/web/laus/laumstrk.htm", "Z38542K2": { "Z1K1": "Z6091", "Z6091K1": "Q15132699" }, "Z38542K3": { "Z1K1": "Z6091", "Z6091K1": "Q2928428" }, "Z38542K4": { "Z1K1": "Z18", "Z18K1": "Z825K3" }, "Z38542K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "9" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q12638" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z38542", "Z38542K1": "https://www.bea.gov/data/gdp/gdp-state", "Z38542K2": { "Z1K1": "Z6091", "Z6091K1": "Q137829618" }, "Z38542K3": { "Z1K1": "Z6091", "Z6091K1": "Q1443033" }, "Z38542K4": { "Z1K1": "Z18", "Z18K1": "Z825K3" }, "Z38542K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } gc61wnos5ilvam6be0le0g4a3cu8ed5 14616 14608 2026-08-13T12:16:45Z Feedmepaperr 1398 named after-sentence is cleaner 14616 abstractwiki text/plain { "qid": "Q1223", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M15949813" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q6664848" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M439001" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q731163" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q35657" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q12603" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1449" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q131684213" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q846295" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q11756" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q551700" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q10855061" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q844033" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q98681686" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37661", "Z37661K1": { "Z1K1": "Z7", "Z7K1": "Z37065", "Z37065K1": { "Z1K1": "Z6091", "Z6091K1": "Q2340694" }, "Z37065K2": { "Z1K1": "Z6091", "Z6091K1": "Q19269277" }, "Z37065K3": { "Z1K1": "Z6091", "Z6091K1": "Q394067" }, "Z37065K4": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37065K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37661K2": { "Z1K1": "Z6091", "Z6091K1": "Q2340694" }, "Z37661K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z37840", "Z37840K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q7324" }, { "Z1K1": "Z6091", "Z6091K1": "Q2109952" }, { "Z1K1": "Z6091", "Z6091K1": "Q548355" }, { "Z1K1": "Z6091", "Z6091K1": "Q1628203" }, { "Z1K1": "Z6091", "Z6091K1": "Q205485" } ], "Z37840K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q18350273" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P571" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "42" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12943371" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q106458883" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M187451298" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q5083" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q20429931" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37065", "Z37065K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37065K2": { "Z1K1": "Z6091", "Z6091K1": "Q5491373" }, "Z37065K3": { "Z1K1": "Z6091", "Z6091K1": "Q106458883" }, "Z37065K4": { "Z1K1": "Z6091", "Z6091K1": "Q578170" }, "Z37065K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P13574" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2927" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "18" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q106458883" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q3297259" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q3297259" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q3297259" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q82794" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3297259" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1082" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3297259" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q3046581" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q3046581" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q3046581" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q82794" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3046581" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P13574" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z6091", "Z6091K1": "Q187805" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "2" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, "Z36831K2": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q187805" } ] }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q1069" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M93987125" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q194057" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q3123499" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P610" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z6091", "Z6091K1": "Q194057" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q169358" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q194057" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2044" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33690", "Z33690K1": { "Z1K1": "Z6091", "Z6091K1": "Q7937" }, "Z33690K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P7422" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P6591" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q2725376" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1082" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1538" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P4442" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z34250", "Z34250K1": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z34250K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q38838" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q159810" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36083", "Z36083K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q5333805" } ], "Z36083K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "47" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q16042592" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q1787954" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z38542", "Z38542K1": "https://www.bls.gov/web/laus/laumstrk.htm", "Z38542K2": { "Z1K1": "Z6091", "Z6091K1": "Q15132699" }, "Z38542K3": { "Z1K1": "Z6091", "Z6091K1": "Q2928428" }, "Z38542K4": { "Z1K1": "Z18", "Z18K1": "Z825K3" }, "Z38542K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "9" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q12638" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z38542", "Z38542K1": "https://www.bea.gov/data/gdp/gdp-state", "Z38542K2": { "Z1K1": "Z6091", "Z6091K1": "Q137829618" }, "Z38542K3": { "Z1K1": "Z6091", "Z6091K1": "Q1443033" }, "Z38542K4": { "Z1K1": "Z18", "Z18K1": "Z825K3" }, "Z38542K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } q41ulh3p0xqk22adc7l310o8nrqe2gq 0 1162 14624 14570 2026-08-13T12:25:00Z Feedmepaperr 1398 language infobox 14624 abstractwiki text/plain { "qid": "Q7850", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38329", "Z38329K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38329K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q152559" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q148" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } } ] } } } bued1o2fnx77w9f952730npzn6paq4w 12 1502 14667 14409 2026-08-13T23:49:12Z EatingCarBatteries 1378 14667 wikitext text/x-wiki == Python library == This library allows you to interface with the Wikifunctions API (including to make Abstract Wikipedia calls) in your Python code. Link: * Internal: [[f:User:Feeglgeef/wikifunctions-pip]] * External: [https://pypi.org/project/wikifunctions/ https://pypi.org/project/wikifunctions/] == AbstractWikipediaEditor == A member of the community created a project to make editing Abstract Wikipedia feel more like editing a traditional Wikipedia, that is, without clicking through GUIs to select functions. You write human-readable wikitext templates, see a live English preview of what the article will say, and publish it. This project is no longer maintained as of June 2026. Link: * Internal: [[User:Immanuelle/Abstract Wikipedia Editor]] * External: [https://emmaleonhart.github.io/AbstractWikipediaEditor/ https://emmaleonhart.github.io/AbstractWikipediaEditor/] ==Abstract Data == This website allows you to view language and lexeme coverage, and issues for Abstract Wikipedia articles. As an example, given a language you can view the highest impact function configurations that need an implementation in that language. Link: * [https://abstract-data.toolforge.org/ abstract-data.toolforge.org] [[Category:Help]] 1vbhodu8sqo7cdmpt9wj0wwmaz9peif 14668 14667 2026-08-13T23:49:28Z EatingCarBatteries 1378 /* Abstract Data */ 14668 wikitext text/x-wiki == Python library == This library allows you to interface with the Wikifunctions API (including to make Abstract Wikipedia calls) in your Python code. Link: * Internal: [[f:User:Feeglgeef/wikifunctions-pip]] * External: [https://pypi.org/project/wikifunctions/ https://pypi.org/project/wikifunctions/] == AbstractWikipediaEditor == A member of the community created a project to make editing Abstract Wikipedia feel more like editing a traditional Wikipedia, that is, without clicking through GUIs to select functions. You write human-readable wikitext templates, see a live English preview of what the article will say, and publish it. This project is no longer maintained as of June 2026. Link: * Internal: [[User:Immanuelle/Abstract Wikipedia Editor]] * External: [https://emmaleonhart.github.io/AbstractWikipediaEditor/ https://emmaleonhart.github.io/AbstractWikipediaEditor/] ==Abstract Data == This website allows you to view language and lexeme coverage, and issues for Abstract Wikipedia articles. As an example, you can view the highest impact function configurations that need an implementation in a given language. Link: * [https://abstract-data.toolforge.org/ abstract-data.toolforge.org] [[Category:Help]] 5tjck17663d8bi730y9akvgd43fyc11 0 1748 14633 14586 2026-08-13T14:44:40Z Jsamwrites 874 14633 abstractwiki text/plain { "qid": "Q15777", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M127716370" }, "Z36038K2": "Logo of C" }, { "Z1K1": "Z7", "Z7K1": "Z35972", "Z35972K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35972K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32123", "Z32123K1": { "Z1K1": "Z7", "Z7K1": "Z32234", "Z32234K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q9143" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, " ", { "Z1K1": "Z7", "Z7K1": "Z32053", "Z32053K1": "https://www.britannica.com/technology/computer-programming-language", "Z32053K2": "https://www.britannica.com/technology/computer-programming-language", "Z32053K3": "britannica.com", "Z32053K4": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "2026" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16104" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "11" } } }, "Z32053K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } }, { "Z1K1": "Z7", "Z7K1": "Z39339", "Z39339K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39339K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39339K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z39339K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z38388", "Z38388K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38388K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z38388K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37945", "Z37945K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37945K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z37945K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39280", "Z39280K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39280K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39235", "Z39235K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39235K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39235K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39235K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q138861968" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37840", "Z37840K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q9143" }, { "Z1K1": "Z6091", "Z6091K1": "Q275596" }, { "Z1K1": "Z6091", "Z6091K1": "Q1418502" }, { "Z1K1": "Z6091", "Z6091K1": "Q4306983" } ], "Z37840K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } bw3wsz83mamqzt2ds4kd9lzz78j9nfk 0 1749 14632 14588 2026-08-13T14:43:47Z Jsamwrites 874 14632 abstractwiki text/plain { "qid": "Q2407", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M62851110" }, "Z36038K2": "C++ logo" }, { "Z1K1": "Z7", "Z7K1": "Z35972", "Z35972K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35972K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38388", "Z38388K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38388K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z38388K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39339", "Z39339K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39339K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39339K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z39339K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39253", "Z39253K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39253K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39253K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39280", "Z39280K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39280K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39238", "Z39238K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39238K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39238K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39238K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39235", "Z39235K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39235K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39235K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39235K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q138861968" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37840", "Z37840K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q9143" }, { "Z1K1": "Z6091", "Z6091K1": "Q79872" }, { "Z1K1": "Z6091", "Z6091K1": "Q193076" }, { "Z1K1": "Z6091", "Z6091K1": "Q1418502" }, { "Z1K1": "Z6091", "Z6091K1": "Q4306983" } ], "Z37840K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } rzfg2uzszqqysido8e785ctjshlvyn0 10 1883 14641 14349 2026-08-13T15:41:45Z FuzzyBot 563 Updating to match new version of source page 14641 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;Volunteer's Corners * The next Volunteers' Corner will be at <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi> on <bdi lang="en" dir="ltr">Google Meet</bdi> at <bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi>. * The [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|most recent Volunteer's Corner]] is available on Commons. ; Recent status updates about Wikifunctions <!--Keep this to the most recent 5 entries--> * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9! * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstract Wikipedia at Wikimania * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Beyond syntactic tables * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small">More news</span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> 0swr8cutp0ybeisiy1rjuamnkrd4pbk 10 1989 14639 14346 2026-08-13T15:41:44Z FuzzyBot 563 Updating to match new version of source page 14639 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;স্বেচ্ছাসেবক সভা * পরবর্তী স্বেচ্ছাসেবক সভা <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi>-এ <bdi lang="en" dir="ltr">Google Meet</bdi>-এ <bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi>-এ হবে। * [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|সর্বশেষ স্বেচ্ছাসেবক সভা]] কমন্সে পাওয়া যাবে। ; উইকিফাংশন্স সম্পর্কে সাম্প্রতিক হালনাগাদ <!--Keep this to the most recent 5 entries--> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9!</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstract Wikipedia at Wikimania</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Beyond syntactic tables</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone</span> </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small">আরও সংবাদ</span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> 6vrxp4mrwhowzvovubrswfgj2mb2iu5 10 2061 14638 14526 2026-08-13T15:41:44Z FuzzyBot 563 Updating to match new version of source page 14638 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;Freiwilligentreffen * Das nächste Freiwilligentreffen findet um <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi> auf <bdi lang="en" dir="ltr">Google Meet</bdi> unter <bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi> statt. * Das [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|letzte Freiwilligentreffen]] ist auf Commons verfügbar. ; Aktuelle Neuigkeiten zum Status von Wikifunctions <!--Keep this to the most recent 5 entries--> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9!</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstrakte Wikipedia bei der Wikimania * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Über syntaktische Tabellen hinaus * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: Auf dem Weg zu unserem ersten Meilenstein bei der Integration der Abstrakten Wikipedia </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small">Weitere Neuigkeiten</span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> a4ozhn1c3a2797f6vfjqjj2dmnsqb7s 10 2080 14640 14348 2026-08-13T15:41:45Z FuzzyBot 563 Updating to match new version of source page 14640 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;ركن المتطوعين * سيكون ركن المتطوعين التالي في <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi> على <bdi lang="en" dir="ltr">Google Meet</bdi> في <bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi>. * [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|أحدث ركن المتطوعين]] متاح على كومنز. ; تحديثات الحالة الأخيرة حول ويكي الدوال <!--Keep this to the most recent 5 entries--> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9!</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstract Wikipedia at Wikimania</span> * <span class="mw-translate-fuzzy">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]] ما وراء الجداول النحوية</span> * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: المضي قدماً نحو أولى محطات دمج ويكيبيديا المجردة </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small">المزيد من الأخبار</span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> gy1i9xe0j3cz6fro467pjxttqltyubs 0 2236 14663 7937 2026-08-13T22:57:19Z Omar M. Ghaly 6856 Added an info box function 14663 abstractwiki text/plain { "qid": "Q85", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q79" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } t70yxde4trsg9hcnizscu50ul678ui1 14664 14663 2026-08-13T23:03:24Z Omar M. Ghaly 6856 Added an image thumbnail function 14664 abstractwiki text/plain { "qid": "Q85", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M66239095" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q79" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } cig14grjf22s81s5gqvqnepgiwvqwc6 14669 14664 2026-08-14T00:11:46Z Omar M. Ghaly 6856 Added superlative definition and population 14669 abstractwiki text/plain { "qid": "Q85", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M66239095" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q79" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37065", "Z37065K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37065K2": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37065K3": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37065K4": { "Z1K1": "Z6091", "Z6091K1": "Q79" }, "Z37065K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } od0dj2cadaigt38m2l4e8z6pbp9useo 14673 14669 2026-08-14T02:15:30Z EatingCarBatteries 1378 14673 abstractwiki text/plain { "qid": "Q85", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M66239095" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q79" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37065", "Z37065K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37065K2": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37065K3": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37065K4": { "Z1K1": "Z6091", "Z6091K1": "Q79" }, "Z37065K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q515" }, { "Z1K1": "Z6091", "Z6091K1": "Q79" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } oknqugvxlmfpt8c31f0bn7duiamiswy 10 2278 14646 14354 2026-08-13T15:41:46Z FuzzyBot 563 Updating to match new version of source page 14646 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;-{A|zh-hans:志愿者;zh-hant:志工;}-角落 * 下一期志愿者角将于<bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi>在 <bdi lang="en" dir="ltr">Google Meet</bdi> 的<bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi>举行。 * [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|最近的志愿者角]]已发布在维基共享资源上。 ; 维基函数最新动态 <!--Keep this to the most recent 5 entries--> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9!</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstract Wikipedia at Wikimania</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Beyond syntactic tables</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone</span> </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small">更多新闻</span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> t8aigxiic2c5b1s3lnxszg49jygsxsi 10 2418 14644 14352 2026-08-13T15:41:46Z FuzzyBot 563 Updating to match new version of source page 14644 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;Volontärshörnan * Nästa volontärshörna kommer hållas på <bdi lang="en" dir="ltr">Google Meet</bdi> <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi>, på <bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi>. * Den [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|förra volontärshörnan]] finns att se på Commons. ; Senaste nytt om Wikifunctions <!--Keep this to the most recent 5 entries--> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9!</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstract Wikipedia at Wikimania</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Beyond syntactic tables</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone</span> </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small">Fler nyheter</span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> bkgx4zgnabr6hrxi3rxor27xzeooqu2 10 2805 14642 14350 2026-08-13T15:41:45Z FuzzyBot 563 Updating to match new version of source page 14642 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;<span lang="en" dir="ltr" class="mw-content-ltr">Volunteer's Corners</span> * A következő Önkéntes Sarok <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi>-kor lesz <bdi lang="en" dir="ltr">Google Meet</bdi> oldalon a <bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi> linken. * <span lang="en" dir="ltr" class="mw-content-ltr">The [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|most recent Volunteer's Corner]] is available on Commons.</span> ; <span lang="en" dir="ltr" class="mw-content-ltr">Recent status updates about Wikifunctions</span> <!--Keep this to the most recent 5 entries--> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9!</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstract Wikipedia at Wikimania</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Beyond syntactic tables</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone</span> </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small"><span lang="en" dir="ltr" class="mw-content-ltr">More news</span></span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> obsubjojtih2f79tdy3750efbp1qupv 4 2999 14694 9380 2026-08-14T06:56:34Z Theki 2698 14694 wikitext text/x-wiki <div style="border:var(--border-style-base, 1px solid #A2A9B1);clear:right;float:right;padding:1em;text-align:center;"> <span style="font-weight:bold;">{{LangSwitch|en=Archives|tok=toki majuna}}</span> <ul style="list-style:none;margin-inline:0;"> <li>[[Abstract Wikipedia:Project chat/Archives/2026/03|2026/03]]</li> <li>[[Abstract Wikipedia:Project chat/Archives/2026/04|2026/04]]</li> <li>[[Abstract Wikipedia:Project chat/Archives/2026/05|2026/05]]</li> <li>[[Abstract Wikipedia:Project chat/Archives/2026/05|2026/06]]</li> </ul> </div><noinclude> <div style="clear:both;"></div> {{UsesLangSwitch}} </noinclude> ivtidae3zaf39ht5g0coof0zzz3t1i6 10 3056 14645 14353 2026-08-13T15:41:46Z FuzzyBot 563 Updating to match new version of source page 14645 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;kulupu pi jan pali * <span lang="en" dir="ltr" class="mw-content-ltr">The next Volunteers' Corner will be at <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi> on <bdi lang="en" dir="ltr">Google Meet</bdi> at <bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi>.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|most recent Volunteer's Corner]] is available on Commons.</span> ; sona sin pi lipu Wikiwilo <!--Keep this to the most recent 5 entries--> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9!</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstract Wikipedia at Wikimania</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Beyond syntactic tables</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone</span> </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small"><span lang="en" dir="ltr" class="mw-content-ltr">More news</span></span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> gh0j5145v58lhnw6ebnm1s8dyrnq432 0 3506 14606 12240 2026-08-13T12:00:40Z Jsamwrites 874 14606 abstractwiki text/plain { "qid": "Q173136", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M46544944" }, "Z36038K2": "Logo of Blender" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38488", "Z38488K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38488K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z38488K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z38488K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32839", "Z32839K1": { "Z1K1": "Z6091", "Z6091K1": "Q241317" }, "Z32839K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39232", "Z39232K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39232K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39232K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39232K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 534qhfup5ph3cyufdoabyxwb76amchu 14609 14606 2026-08-13T12:05:17Z Jsamwrites 874 14609 abstractwiki text/plain { "qid": "Q173136", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M46544944" }, "Z36038K2": "Logo of Blender" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38488", "Z38488K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38488K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z38488K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z38488K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32839", "Z32839K1": { "Z1K1": "Z6091", "Z6091K1": "Q241317" }, "Z32839K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39232", "Z39232K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39232K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39232K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39232K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q7562091" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39283", "Z39283K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39283K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39203", "Z39203K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39203K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39203K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39203K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } lkyy55s78nfzsn9k6hx551lgnyjkdyt 4 3513 14677 10693 2026-08-14T06:50:13Z Theki 2698 /* Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning */ 14677 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) :Thank you! That’s great and I’ll look at it more soon. I’m still taking a bit of a wikibreak. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:32, 14 May 2026 (UTC) :Is there anything I've written [[f:User:Theki/best_practices#Abstract_Wikipedia|here]] that you think would make for a good technical section of the page? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 00:04, 15 May 2026 (UTC) ::I've added some of them. Thank you for your list of best practices by the way, I generally agree with them (I can't endorse connecting WD items currently in hope of a better technical solution, but otherwise I do). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:58, 15 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) == [[MediaWiki:Wikimedia-copyright-footer]] == The copyright message has a few issues, mainly that it does not address abstract content (which is not "text"), nor object labels (which are under CC0). Proposed text: "<nowiki> Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. </nowiki>" Which, when rendered, looks like: Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. The message is somewhat inspired by the current one and WF's. Thoughts? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:30, 12 May 2026 (UTC) :@[[User:Feeglgeef|Feeglgeef]]: As you probably imagine, this text is very tightly controlled by the Wikimedia Foundation's Legal department. I think the first port of call should be a discussion about why you might want to change things, rather than a rush to specific re-wordings, before approaching them for sign-off. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:28, 12 May 2026 (UTC) ::Well I briefly summarized my justification, my proposed text was just an idea for a starting point. Basically, the abstract content is not really "text", so the footer doesn't actually tell the reader what they're allowed to do with it, and I argue that the current wording implies that the labels are licensed under CC-BY-SA 4, when they aren't. I think a change is critical as otherwise we're not showing the reader a license, or, arguably, in the case of labels, showing users a license that ''does not apply'', which is a pretty bad thing. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:51, 12 May 2026 (UTC) == [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]] == I'd think we should add [[f:Z33068]] here. The function allows you to form a paragraph out of sentences and handles languages having different standards of whether to add a space between them, and adding it here would make finding it easier. I'm not sure what policy we want to have for the suggested functions, this idea might help formulate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:06, 12 May 2026 (UTC) :[[User:Jdforrester (WMF)]] tells me the page has been changed to [[Special:CommunityConfiguration/AbstractWikiSuggestedWikifunctions]] on the telegram. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:25, 12 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]]: Yup, see the weekly update on [[f:Wikifunctions:Status_updates/2026-05-02|2026-05-02]]. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:35, 12 May 2026 (UTC) :I also believe Z33068 should be added to the list. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 12 May 2026 (UTC) {{done}} see [[Special:Diff/7692]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 09:08, 20 May 2026 (UTC) == Abstract Wikipedia statistics site source code == https://abstract-data.toolforge.org/ is a very useful tool, but it doesn't seem to have anything pointing to the location of its source code. Is it closed-source or unfree? While I'm at it I feel I should suggest having language pages' paths formatted differently from how they are currently—at the moment it's <code>/languages/Toki%20Pona</code> when something like <code>/languages/tok</code> would be more suitable. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; : See [[:gitlab:toolforge-repos/abstract-data]]. Also pinging {{ping|DSantamaria-WMF|p=}} (thanks for the tool, by the way). [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 00:25, 13 May 2026 (UTC) ::Thank you. I think a link to that repository should be put in a footer somewhere on the website as I wouldn't have found that if not for you. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:30, 13 May 2026 (UTC) :::{{ping|Theki}} For the record, I found that repo by searching for "abstract-data" on [[:toolhub:|Toolhub]]. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:34, 13 May 2026 (UTC) :::Thanks for the feedback and the report, fixed both things, we have now the link to the repo in the side bar footer, and also the language codes are used in the URLs. Thanks! [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 11:46, 13 May 2026 (UTC) ::::Are you particularly attached to keeping country flag emojis next to the language names? Some consider it an [https://flagsarenotlanguages.com/blog anti-pattern]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 16:17, 14 May 2026 (UTC) :::::I think the use of flags is not really harmful since this is not a ''language selector'', it is just a list of languages. Of course not every language has an associated flag, for example Latin, which does look a bit awkward, but it can't be helped. Maybe give languages without a flag a unique icon from Wikimedia Commons? e.g. <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;">[[File:Toki pona.svg|16px]] Toki Pona</div> instead of <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;"><span>🌐</span>Toki Pona</div>. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:37, 14 May 2026 (UTC) ::::::I thought I saw 🏛️ being used for Latin earlier. But of course, as far as the Unicode Consortium is concerned, [[Q65300415|🇬🇧]] doesn't mean '[[Q1680|English]]', no more than [[Q100587670|🏳️‍🌈]] means '[[Q1359130|Polari]]'; technically, it doesn't even mean '[[Q145|United Kingdom]]', just the letters 🇺 and 🇰 next to each other (which linguistically would indicate [[Q8798|Ukrainian]] in ISO 639, but these are 'regional indicator symbols'). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:21, 14 May 2026 (UTC) :::::::As seems (from this comment and also [[f:User_talk:DSantamaria-WMF#c-%E9%AD%94%E7%90%B4-20260513063700-Country_flags_in_abstract-data|others' comments]]) that flags are a little bit controversial, I just removed them, IMHO it was just an aesthetic concept, I like the look and feel that flags bring to the language labels, but happy to remove them if make some people feel uncomfortable with the concept. [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 05:54, 15 May 2026 (UTC) == Make it more user Friendly == Make it more user-friendly by adding drag-and-drop compenots and one click additions, and make it similar to a visual macro buidler. [[User:ChippyTechGH|ChippyTechGH]] ([[User talk:ChippyTechGH|talk]]) 01:00, 15 May 2026 (UTC) :Could you file something like this on [[phab:|phabricator]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:01, 15 May 2026 (UTC) == Person infoboxes == Hi all, I've just created [[f:Z35167|infobox for person (Z35167)]]. All it can really do presently is display the name of the person in the chosen language and in the person's native language, but it's a good start. I started writing it as a composition but chose to switch to writing it in JavaScript instead, which ended up being less headache-inducing (managing a large list of strings to concatenate together is not fun, plus compositions bring lots of additional overhead). Unfortunately, this means that the actual ''useful'' parts of the infobox—the information about the person themself—is not really doable. I'd need to dereference the Wikidata property references to get their label in the requested language, but since they're references and I'm working with code, not compositions, I can't just call [[f:Z6822|fetch Wikidata property (Z6822)]] and be done with it. If there's a WikiLambda API to do this inside of the JS itself that would be great and would solve everything, but at the moment that alone is what's holding it back, or so it seems. I can get the actual ''values'' of statements just fine, though. If I am missing some amazing WikiLambda API function that will solve this problem for me by letting me dereference the PID, then please let me know because that would be great. If you want to look at an example of the infobox right meow, you can view [https://abstract.wikipedia.org/view/tok/Q317521 Q317521 in Toki Pona] and see how it states Musk's name in both Toki Pona ''and'' his native English name. COOL! My hope is that this can be made less barebones in the near future. Infoboxes are a great way to get quick information on a subject and can fill in the informational gaps in the presently sparse articles we have at the moment, all while staying in the user's requested language. Feedback is appreciated! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:58, 15 May 2026 (UTC) :Thank you for this! I wonder if perhaps it would be better to create one "infobox" function and then have compositions call that, making wd retrival possible? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:38, 15 May 2026 (UTC) ::Working on that at the moment, I think I've got it working but I'm hitting a ratelimit in the orchestrator so I don't know for sure. The main issue with it now is that the actual [[f:Z35175|infobox template (Z35175)]] wrapper was programmed in JS so as to not be a pain in the ass, so this means that it can only take in strings, HTML fragments, etc. so the retrieval of Wikidata stuff still needs to be done by the caller and is rather verbose (see [[f:Z35168|the main implementation]]). The niceties will come soon later once I know that it all works at a lower level, though. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:04, 15 May 2026 (UTC) ::So the problem now seems to be that when [[f:Z29825|label of Wikidata property in language (Z29825)]] isn't being faulty, it's being incredibly slow. Considering retrieving Wikidata items from their references seems to take, like, four to five seconds, and we'll have tens of statements in these infoboxes, I don't see how the property names could be retrieved in a way that doesn't cause the orchestrator to time out or hit a ratelimit. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:01, 15 May 2026 (UTC) :::I think I figured something out? I'm just going to try calling [[f:Z35036|fetch Wikidata property or parts (Z35036)]], it seems to be much faster for whatever reason. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:05, 15 May 2026 (UTC) :::It works now, a little rough around the edges, also very slow, but I think I'm mostly happy with it. Of course it would be great if all you needed to provide to the template function to get a label-statement row was the property reference itself, but I'm too sleep-deprived to figure that out at the moment. I made five bespoke functions specifically for this infobox, more than I would like, but it's probably not ''that'' bad. I'm just hoping I didn't duplicate any functionality in trying to make the composition less verbose and repetitive. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:15, 15 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:36, 15 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) dept2hzircnogb2dfgfdei2vza3uzfs 14679 14677 2026-08-14T06:51:13Z Theki 2698 /* Translations */ 14679 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) :Thank you! That’s great and I’ll look at it more soon. I’m still taking a bit of a wikibreak. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:32, 14 May 2026 (UTC) :Is there anything I've written [[f:User:Theki/best_practices#Abstract_Wikipedia|here]] that you think would make for a good technical section of the page? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 00:04, 15 May 2026 (UTC) ::I've added some of them. Thank you for your list of best practices by the way, I generally agree with them (I can't endorse connecting WD items currently in hope of a better technical solution, but otherwise I do). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:58, 15 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) == [[MediaWiki:Wikimedia-copyright-footer]] == The copyright message has a few issues, mainly that it does not address abstract content (which is not "text"), nor object labels (which are under CC0). Proposed text: "<nowiki> Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. </nowiki>" Which, when rendered, looks like: Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. The message is somewhat inspired by the current one and WF's. Thoughts? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:30, 12 May 2026 (UTC) :@[[User:Feeglgeef|Feeglgeef]]: As you probably imagine, this text is very tightly controlled by the Wikimedia Foundation's Legal department. I think the first port of call should be a discussion about why you might want to change things, rather than a rush to specific re-wordings, before approaching them for sign-off. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:28, 12 May 2026 (UTC) ::Well I briefly summarized my justification, my proposed text was just an idea for a starting point. Basically, the abstract content is not really "text", so the footer doesn't actually tell the reader what they're allowed to do with it, and I argue that the current wording implies that the labels are licensed under CC-BY-SA 4, when they aren't. I think a change is critical as otherwise we're not showing the reader a license, or, arguably, in the case of labels, showing users a license that ''does not apply'', which is a pretty bad thing. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:51, 12 May 2026 (UTC) == [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]] == I'd think we should add [[f:Z33068]] here. The function allows you to form a paragraph out of sentences and handles languages having different standards of whether to add a space between them, and adding it here would make finding it easier. I'm not sure what policy we want to have for the suggested functions, this idea might help formulate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:06, 12 May 2026 (UTC) :[[User:Jdforrester (WMF)]] tells me the page has been changed to [[Special:CommunityConfiguration/AbstractWikiSuggestedWikifunctions]] on the telegram. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:25, 12 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]]: Yup, see the weekly update on [[f:Wikifunctions:Status_updates/2026-05-02|2026-05-02]]. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:35, 12 May 2026 (UTC) :I also believe Z33068 should be added to the list. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 12 May 2026 (UTC) {{done}} see [[Special:Diff/7692]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 09:08, 20 May 2026 (UTC) == Abstract Wikipedia statistics site source code == https://abstract-data.toolforge.org/ is a very useful tool, but it doesn't seem to have anything pointing to the location of its source code. Is it closed-source or unfree? While I'm at it I feel I should suggest having language pages' paths formatted differently from how they are currently—at the moment it's <code>/languages/Toki%20Pona</code> when something like <code>/languages/tok</code> would be more suitable. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; : See [[:gitlab:toolforge-repos/abstract-data]]. Also pinging {{ping|DSantamaria-WMF|p=}} (thanks for the tool, by the way). [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 00:25, 13 May 2026 (UTC) ::Thank you. I think a link to that repository should be put in a footer somewhere on the website as I wouldn't have found that if not for you. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:30, 13 May 2026 (UTC) :::{{ping|Theki}} For the record, I found that repo by searching for "abstract-data" on [[:toolhub:|Toolhub]]. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:34, 13 May 2026 (UTC) :::Thanks for the feedback and the report, fixed both things, we have now the link to the repo in the side bar footer, and also the language codes are used in the URLs. Thanks! [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 11:46, 13 May 2026 (UTC) ::::Are you particularly attached to keeping country flag emojis next to the language names? Some consider it an [https://flagsarenotlanguages.com/blog anti-pattern]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 16:17, 14 May 2026 (UTC) :::::I think the use of flags is not really harmful since this is not a ''language selector'', it is just a list of languages. Of course not every language has an associated flag, for example Latin, which does look a bit awkward, but it can't be helped. Maybe give languages without a flag a unique icon from Wikimedia Commons? e.g. <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;">[[File:Toki pona.svg|16px]] Toki Pona</div> instead of <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;"><span>🌐</span>Toki Pona</div>. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:37, 14 May 2026 (UTC) ::::::I thought I saw 🏛️ being used for Latin earlier. But of course, as far as the Unicode Consortium is concerned, [[Q65300415|🇬🇧]] doesn't mean '[[Q1680|English]]', no more than [[Q100587670|🏳️‍🌈]] means '[[Q1359130|Polari]]'; technically, it doesn't even mean '[[Q145|United Kingdom]]', just the letters 🇺 and 🇰 next to each other (which linguistically would indicate [[Q8798|Ukrainian]] in ISO 639, but these are 'regional indicator symbols'). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:21, 14 May 2026 (UTC) :::::::As seems (from this comment and also [[f:User_talk:DSantamaria-WMF#c-%E9%AD%94%E7%90%B4-20260513063700-Country_flags_in_abstract-data|others' comments]]) that flags are a little bit controversial, I just removed them, IMHO it was just an aesthetic concept, I like the look and feel that flags bring to the language labels, but happy to remove them if make some people feel uncomfortable with the concept. [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 05:54, 15 May 2026 (UTC) == Make it more user Friendly == Make it more user-friendly by adding drag-and-drop compenots and one click additions, and make it similar to a visual macro buidler. [[User:ChippyTechGH|ChippyTechGH]] ([[User talk:ChippyTechGH|talk]]) 01:00, 15 May 2026 (UTC) :Could you file something like this on [[phab:|phabricator]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:01, 15 May 2026 (UTC) == Person infoboxes == Hi all, I've just created [[f:Z35167|infobox for person (Z35167)]]. All it can really do presently is display the name of the person in the chosen language and in the person's native language, but it's a good start. I started writing it as a composition but chose to switch to writing it in JavaScript instead, which ended up being less headache-inducing (managing a large list of strings to concatenate together is not fun, plus compositions bring lots of additional overhead). Unfortunately, this means that the actual ''useful'' parts of the infobox—the information about the person themself—is not really doable. I'd need to dereference the Wikidata property references to get their label in the requested language, but since they're references and I'm working with code, not compositions, I can't just call [[f:Z6822|fetch Wikidata property (Z6822)]] and be done with it. If there's a WikiLambda API to do this inside of the JS itself that would be great and would solve everything, but at the moment that alone is what's holding it back, or so it seems. I can get the actual ''values'' of statements just fine, though. If I am missing some amazing WikiLambda API function that will solve this problem for me by letting me dereference the PID, then please let me know because that would be great. If you want to look at an example of the infobox right meow, you can view [https://abstract.wikipedia.org/view/tok/Q317521 Q317521 in Toki Pona] and see how it states Musk's name in both Toki Pona ''and'' his native English name. COOL! My hope is that this can be made less barebones in the near future. Infoboxes are a great way to get quick information on a subject and can fill in the informational gaps in the presently sparse articles we have at the moment, all while staying in the user's requested language. Feedback is appreciated! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:58, 15 May 2026 (UTC) :Thank you for this! I wonder if perhaps it would be better to create one "infobox" function and then have compositions call that, making wd retrival possible? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:38, 15 May 2026 (UTC) ::Working on that at the moment, I think I've got it working but I'm hitting a ratelimit in the orchestrator so I don't know for sure. The main issue with it now is that the actual [[f:Z35175|infobox template (Z35175)]] wrapper was programmed in JS so as to not be a pain in the ass, so this means that it can only take in strings, HTML fragments, etc. so the retrieval of Wikidata stuff still needs to be done by the caller and is rather verbose (see [[f:Z35168|the main implementation]]). The niceties will come soon later once I know that it all works at a lower level, though. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:04, 15 May 2026 (UTC) ::So the problem now seems to be that when [[f:Z29825|label of Wikidata property in language (Z29825)]] isn't being faulty, it's being incredibly slow. Considering retrieving Wikidata items from their references seems to take, like, four to five seconds, and we'll have tens of statements in these infoboxes, I don't see how the property names could be retrieved in a way that doesn't cause the orchestrator to time out or hit a ratelimit. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:01, 15 May 2026 (UTC) :::I think I figured something out? I'm just going to try calling [[f:Z35036|fetch Wikidata property or parts (Z35036)]], it seems to be much faster for whatever reason. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:05, 15 May 2026 (UTC) :::It works now, a little rough around the edges, also very slow, but I think I'm mostly happy with it. Of course it would be great if all you needed to provide to the template function to get a label-statement row was the property reference itself, but I'm too sleep-deprived to figure that out at the moment. I made five bespoke functions specifically for this infobox, more than I would like, but it's probably not ''that'' bad. I'm just hoping I didn't duplicate any functionality in trying to make the composition less verbose and repetitive. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:15, 15 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:36, 15 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) 8pn0sr0e4oms48mvekvqsaodihvvkd8 14682 14679 2026-08-14T06:51:34Z Theki 2698 /* Policy drafts */ 14682 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) :Thank you! That’s great and I’ll look at it more soon. I’m still taking a bit of a wikibreak. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:32, 14 May 2026 (UTC) :Is there anything I've written [[f:User:Theki/best_practices#Abstract_Wikipedia|here]] that you think would make for a good technical section of the page? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 00:04, 15 May 2026 (UTC) ::I've added some of them. Thank you for your list of best practices by the way, I generally agree with them (I can't endorse connecting WD items currently in hope of a better technical solution, but otherwise I do). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:58, 15 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) == [[MediaWiki:Wikimedia-copyright-footer]] == The copyright message has a few issues, mainly that it does not address abstract content (which is not "text"), nor object labels (which are under CC0). Proposed text: "<nowiki> Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. </nowiki>" Which, when rendered, looks like: Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. The message is somewhat inspired by the current one and WF's. Thoughts? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:30, 12 May 2026 (UTC) :@[[User:Feeglgeef|Feeglgeef]]: As you probably imagine, this text is very tightly controlled by the Wikimedia Foundation's Legal department. I think the first port of call should be a discussion about why you might want to change things, rather than a rush to specific re-wordings, before approaching them for sign-off. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:28, 12 May 2026 (UTC) ::Well I briefly summarized my justification, my proposed text was just an idea for a starting point. Basically, the abstract content is not really "text", so the footer doesn't actually tell the reader what they're allowed to do with it, and I argue that the current wording implies that the labels are licensed under CC-BY-SA 4, when they aren't. I think a change is critical as otherwise we're not showing the reader a license, or, arguably, in the case of labels, showing users a license that ''does not apply'', which is a pretty bad thing. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:51, 12 May 2026 (UTC) == [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]] == I'd think we should add [[f:Z33068]] here. The function allows you to form a paragraph out of sentences and handles languages having different standards of whether to add a space between them, and adding it here would make finding it easier. I'm not sure what policy we want to have for the suggested functions, this idea might help formulate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:06, 12 May 2026 (UTC) :[[User:Jdforrester (WMF)]] tells me the page has been changed to [[Special:CommunityConfiguration/AbstractWikiSuggestedWikifunctions]] on the telegram. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:25, 12 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]]: Yup, see the weekly update on [[f:Wikifunctions:Status_updates/2026-05-02|2026-05-02]]. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:35, 12 May 2026 (UTC) :I also believe Z33068 should be added to the list. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 12 May 2026 (UTC) {{done}} see [[Special:Diff/7692]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 09:08, 20 May 2026 (UTC) == Abstract Wikipedia statistics site source code == https://abstract-data.toolforge.org/ is a very useful tool, but it doesn't seem to have anything pointing to the location of its source code. Is it closed-source or unfree? While I'm at it I feel I should suggest having language pages' paths formatted differently from how they are currently—at the moment it's <code>/languages/Toki%20Pona</code> when something like <code>/languages/tok</code> would be more suitable. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; : See [[:gitlab:toolforge-repos/abstract-data]]. Also pinging {{ping|DSantamaria-WMF|p=}} (thanks for the tool, by the way). [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 00:25, 13 May 2026 (UTC) ::Thank you. I think a link to that repository should be put in a footer somewhere on the website as I wouldn't have found that if not for you. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:30, 13 May 2026 (UTC) :::{{ping|Theki}} For the record, I found that repo by searching for "abstract-data" on [[:toolhub:|Toolhub]]. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:34, 13 May 2026 (UTC) :::Thanks for the feedback and the report, fixed both things, we have now the link to the repo in the side bar footer, and also the language codes are used in the URLs. Thanks! [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 11:46, 13 May 2026 (UTC) ::::Are you particularly attached to keeping country flag emojis next to the language names? Some consider it an [https://flagsarenotlanguages.com/blog anti-pattern]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 16:17, 14 May 2026 (UTC) :::::I think the use of flags is not really harmful since this is not a ''language selector'', it is just a list of languages. Of course not every language has an associated flag, for example Latin, which does look a bit awkward, but it can't be helped. Maybe give languages without a flag a unique icon from Wikimedia Commons? e.g. <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;">[[File:Toki pona.svg|16px]] Toki Pona</div> instead of <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;"><span>🌐</span>Toki Pona</div>. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:37, 14 May 2026 (UTC) ::::::I thought I saw 🏛️ being used for Latin earlier. But of course, as far as the Unicode Consortium is concerned, [[Q65300415|🇬🇧]] doesn't mean '[[Q1680|English]]', no more than [[Q100587670|🏳️‍🌈]] means '[[Q1359130|Polari]]'; technically, it doesn't even mean '[[Q145|United Kingdom]]', just the letters 🇺 and 🇰 next to each other (which linguistically would indicate [[Q8798|Ukrainian]] in ISO 639, but these are 'regional indicator symbols'). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:21, 14 May 2026 (UTC) :::::::As seems (from this comment and also [[f:User_talk:DSantamaria-WMF#c-%E9%AD%94%E7%90%B4-20260513063700-Country_flags_in_abstract-data|others' comments]]) that flags are a little bit controversial, I just removed them, IMHO it was just an aesthetic concept, I like the look and feel that flags bring to the language labels, but happy to remove them if make some people feel uncomfortable with the concept. [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 05:54, 15 May 2026 (UTC) == Make it more user Friendly == Make it more user-friendly by adding drag-and-drop compenots and one click additions, and make it similar to a visual macro buidler. [[User:ChippyTechGH|ChippyTechGH]] ([[User talk:ChippyTechGH|talk]]) 01:00, 15 May 2026 (UTC) :Could you file something like this on [[phab:|phabricator]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:01, 15 May 2026 (UTC) == Person infoboxes == Hi all, I've just created [[f:Z35167|infobox for person (Z35167)]]. All it can really do presently is display the name of the person in the chosen language and in the person's native language, but it's a good start. I started writing it as a composition but chose to switch to writing it in JavaScript instead, which ended up being less headache-inducing (managing a large list of strings to concatenate together is not fun, plus compositions bring lots of additional overhead). Unfortunately, this means that the actual ''useful'' parts of the infobox—the information about the person themself—is not really doable. I'd need to dereference the Wikidata property references to get their label in the requested language, but since they're references and I'm working with code, not compositions, I can't just call [[f:Z6822|fetch Wikidata property (Z6822)]] and be done with it. If there's a WikiLambda API to do this inside of the JS itself that would be great and would solve everything, but at the moment that alone is what's holding it back, or so it seems. I can get the actual ''values'' of statements just fine, though. If I am missing some amazing WikiLambda API function that will solve this problem for me by letting me dereference the PID, then please let me know because that would be great. If you want to look at an example of the infobox right meow, you can view [https://abstract.wikipedia.org/view/tok/Q317521 Q317521 in Toki Pona] and see how it states Musk's name in both Toki Pona ''and'' his native English name. COOL! My hope is that this can be made less barebones in the near future. Infoboxes are a great way to get quick information on a subject and can fill in the informational gaps in the presently sparse articles we have at the moment, all while staying in the user's requested language. Feedback is appreciated! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:58, 15 May 2026 (UTC) :Thank you for this! I wonder if perhaps it would be better to create one "infobox" function and then have compositions call that, making wd retrival possible? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:38, 15 May 2026 (UTC) ::Working on that at the moment, I think I've got it working but I'm hitting a ratelimit in the orchestrator so I don't know for sure. The main issue with it now is that the actual [[f:Z35175|infobox template (Z35175)]] wrapper was programmed in JS so as to not be a pain in the ass, so this means that it can only take in strings, HTML fragments, etc. so the retrieval of Wikidata stuff still needs to be done by the caller and is rather verbose (see [[f:Z35168|the main implementation]]). The niceties will come soon later once I know that it all works at a lower level, though. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:04, 15 May 2026 (UTC) ::So the problem now seems to be that when [[f:Z29825|label of Wikidata property in language (Z29825)]] isn't being faulty, it's being incredibly slow. Considering retrieving Wikidata items from their references seems to take, like, four to five seconds, and we'll have tens of statements in these infoboxes, I don't see how the property names could be retrieved in a way that doesn't cause the orchestrator to time out or hit a ratelimit. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:01, 15 May 2026 (UTC) :::I think I figured something out? I'm just going to try calling [[f:Z35036|fetch Wikidata property or parts (Z35036)]], it seems to be much faster for whatever reason. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:05, 15 May 2026 (UTC) :::It works now, a little rough around the edges, also very slow, but I think I'm mostly happy with it. Of course it would be great if all you needed to provide to the template function to get a label-statement row was the property reference itself, but I'm too sleep-deprived to figure that out at the moment. I made five bespoke functions specifically for this infobox, more than I would like, but it's probably not ''that'' bad. I'm just hoping I didn't duplicate any functionality in trying to make the composition less verbose and repetitive. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:15, 15 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:36, 15 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> sm32cmxl9erym0uuid8fkd7iioou4y1 14683 14682 2026-08-14T06:52:21Z Theki 2698 /* Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 */ 14683 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) :Thank you! That’s great and I’ll look at it more soon. I’m still taking a bit of a wikibreak. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:32, 14 May 2026 (UTC) :Is there anything I've written [[f:User:Theki/best_practices#Abstract_Wikipedia|here]] that you think would make for a good technical section of the page? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 00:04, 15 May 2026 (UTC) ::I've added some of them. Thank you for your list of best practices by the way, I generally agree with them (I can't endorse connecting WD items currently in hope of a better technical solution, but otherwise I do). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:58, 15 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) == [[MediaWiki:Wikimedia-copyright-footer]] == The copyright message has a few issues, mainly that it does not address abstract content (which is not "text"), nor object labels (which are under CC0). Proposed text: "<nowiki> Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. </nowiki>" Which, when rendered, looks like: Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. The message is somewhat inspired by the current one and WF's. Thoughts? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:30, 12 May 2026 (UTC) :@[[User:Feeglgeef|Feeglgeef]]: As you probably imagine, this text is very tightly controlled by the Wikimedia Foundation's Legal department. I think the first port of call should be a discussion about why you might want to change things, rather than a rush to specific re-wordings, before approaching them for sign-off. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:28, 12 May 2026 (UTC) ::Well I briefly summarized my justification, my proposed text was just an idea for a starting point. Basically, the abstract content is not really "text", so the footer doesn't actually tell the reader what they're allowed to do with it, and I argue that the current wording implies that the labels are licensed under CC-BY-SA 4, when they aren't. I think a change is critical as otherwise we're not showing the reader a license, or, arguably, in the case of labels, showing users a license that ''does not apply'', which is a pretty bad thing. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:51, 12 May 2026 (UTC) == [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]] == I'd think we should add [[f:Z33068]] here. The function allows you to form a paragraph out of sentences and handles languages having different standards of whether to add a space between them, and adding it here would make finding it easier. I'm not sure what policy we want to have for the suggested functions, this idea might help formulate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:06, 12 May 2026 (UTC) :[[User:Jdforrester (WMF)]] tells me the page has been changed to [[Special:CommunityConfiguration/AbstractWikiSuggestedWikifunctions]] on the telegram. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:25, 12 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]]: Yup, see the weekly update on [[f:Wikifunctions:Status_updates/2026-05-02|2026-05-02]]. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:35, 12 May 2026 (UTC) :I also believe Z33068 should be added to the list. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 12 May 2026 (UTC) {{done}} see [[Special:Diff/7692]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 09:08, 20 May 2026 (UTC) == Abstract Wikipedia statistics site source code == https://abstract-data.toolforge.org/ is a very useful tool, but it doesn't seem to have anything pointing to the location of its source code. Is it closed-source or unfree? While I'm at it I feel I should suggest having language pages' paths formatted differently from how they are currently—at the moment it's <code>/languages/Toki%20Pona</code> when something like <code>/languages/tok</code> would be more suitable. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; : See [[:gitlab:toolforge-repos/abstract-data]]. Also pinging {{ping|DSantamaria-WMF|p=}} (thanks for the tool, by the way). [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 00:25, 13 May 2026 (UTC) ::Thank you. I think a link to that repository should be put in a footer somewhere on the website as I wouldn't have found that if not for you. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:30, 13 May 2026 (UTC) :::{{ping|Theki}} For the record, I found that repo by searching for "abstract-data" on [[:toolhub:|Toolhub]]. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:34, 13 May 2026 (UTC) :::Thanks for the feedback and the report, fixed both things, we have now the link to the repo in the side bar footer, and also the language codes are used in the URLs. Thanks! [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 11:46, 13 May 2026 (UTC) ::::Are you particularly attached to keeping country flag emojis next to the language names? Some consider it an [https://flagsarenotlanguages.com/blog anti-pattern]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 16:17, 14 May 2026 (UTC) :::::I think the use of flags is not really harmful since this is not a ''language selector'', it is just a list of languages. Of course not every language has an associated flag, for example Latin, which does look a bit awkward, but it can't be helped. Maybe give languages without a flag a unique icon from Wikimedia Commons? e.g. <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;">[[File:Toki pona.svg|16px]] Toki Pona</div> instead of <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;"><span>🌐</span>Toki Pona</div>. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:37, 14 May 2026 (UTC) ::::::I thought I saw 🏛️ being used for Latin earlier. But of course, as far as the Unicode Consortium is concerned, [[Q65300415|🇬🇧]] doesn't mean '[[Q1680|English]]', no more than [[Q100587670|🏳️‍🌈]] means '[[Q1359130|Polari]]'; technically, it doesn't even mean '[[Q145|United Kingdom]]', just the letters 🇺 and 🇰 next to each other (which linguistically would indicate [[Q8798|Ukrainian]] in ISO 639, but these are 'regional indicator symbols'). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:21, 14 May 2026 (UTC) :::::::As seems (from this comment and also [[f:User_talk:DSantamaria-WMF#c-%E9%AD%94%E7%90%B4-20260513063700-Country_flags_in_abstract-data|others' comments]]) that flags are a little bit controversial, I just removed them, IMHO it was just an aesthetic concept, I like the look and feel that flags bring to the language labels, but happy to remove them if make some people feel uncomfortable with the concept. [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 05:54, 15 May 2026 (UTC) == Make it more user Friendly == Make it more user-friendly by adding drag-and-drop compenots and one click additions, and make it similar to a visual macro buidler. [[User:ChippyTechGH|ChippyTechGH]] ([[User talk:ChippyTechGH|talk]]) 01:00, 15 May 2026 (UTC) :Could you file something like this on [[phab:|phabricator]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:01, 15 May 2026 (UTC) == Person infoboxes == Hi all, I've just created [[f:Z35167|infobox for person (Z35167)]]. All it can really do presently is display the name of the person in the chosen language and in the person's native language, but it's a good start. I started writing it as a composition but chose to switch to writing it in JavaScript instead, which ended up being less headache-inducing (managing a large list of strings to concatenate together is not fun, plus compositions bring lots of additional overhead). Unfortunately, this means that the actual ''useful'' parts of the infobox—the information about the person themself—is not really doable. I'd need to dereference the Wikidata property references to get their label in the requested language, but since they're references and I'm working with code, not compositions, I can't just call [[f:Z6822|fetch Wikidata property (Z6822)]] and be done with it. If there's a WikiLambda API to do this inside of the JS itself that would be great and would solve everything, but at the moment that alone is what's holding it back, or so it seems. I can get the actual ''values'' of statements just fine, though. If I am missing some amazing WikiLambda API function that will solve this problem for me by letting me dereference the PID, then please let me know because that would be great. If you want to look at an example of the infobox right meow, you can view [https://abstract.wikipedia.org/view/tok/Q317521 Q317521 in Toki Pona] and see how it states Musk's name in both Toki Pona ''and'' his native English name. COOL! My hope is that this can be made less barebones in the near future. Infoboxes are a great way to get quick information on a subject and can fill in the informational gaps in the presently sparse articles we have at the moment, all while staying in the user's requested language. Feedback is appreciated! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:58, 15 May 2026 (UTC) :Thank you for this! I wonder if perhaps it would be better to create one "infobox" function and then have compositions call that, making wd retrival possible? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:38, 15 May 2026 (UTC) ::Working on that at the moment, I think I've got it working but I'm hitting a ratelimit in the orchestrator so I don't know for sure. The main issue with it now is that the actual [[f:Z35175|infobox template (Z35175)]] wrapper was programmed in JS so as to not be a pain in the ass, so this means that it can only take in strings, HTML fragments, etc. so the retrieval of Wikidata stuff still needs to be done by the caller and is rather verbose (see [[f:Z35168|the main implementation]]). The niceties will come soon later once I know that it all works at a lower level, though. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:04, 15 May 2026 (UTC) ::So the problem now seems to be that when [[f:Z29825|label of Wikidata property in language (Z29825)]] isn't being faulty, it's being incredibly slow. Considering retrieving Wikidata items from their references seems to take, like, four to five seconds, and we'll have tens of statements in these infoboxes, I don't see how the property names could be retrieved in a way that doesn't cause the orchestrator to time out or hit a ratelimit. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:01, 15 May 2026 (UTC) :::I think I figured something out? I'm just going to try calling [[f:Z35036|fetch Wikidata property or parts (Z35036)]], it seems to be much faster for whatever reason. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:05, 15 May 2026 (UTC) :::It works now, a little rough around the edges, also very slow, but I think I'm mostly happy with it. Of course it would be great if all you needed to provide to the template function to get a label-statement row was the property reference itself, but I'm too sleep-deprived to figure that out at the moment. I made five bespoke functions specifically for this infobox, more than I would like, but it's probably not ''that'' bad. I'm just hoping I didn't duplicate any functionality in trying to make the composition less verbose and repetitive. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:15, 15 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:36, 15 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) 1p0fm5ltg5bheibpywukqdoquti9vm8 14685 14683 2026-08-14T06:53:23Z Theki 2698 /* To abstract Wikipedia or be the Abstract Wikipedia */ 14685 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) :Thank you! That’s great and I’ll look at it more soon. I’m still taking a bit of a wikibreak. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:32, 14 May 2026 (UTC) :Is there anything I've written [[f:User:Theki/best_practices#Abstract_Wikipedia|here]] that you think would make for a good technical section of the page? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 00:04, 15 May 2026 (UTC) ::I've added some of them. Thank you for your list of best practices by the way, I generally agree with them (I can't endorse connecting WD items currently in hope of a better technical solution, but otherwise I do). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:58, 15 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) == [[MediaWiki:Wikimedia-copyright-footer]] == The copyright message has a few issues, mainly that it does not address abstract content (which is not "text"), nor object labels (which are under CC0). Proposed text: "<nowiki> Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. </nowiki>" Which, when rendered, looks like: Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. The message is somewhat inspired by the current one and WF's. Thoughts? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:30, 12 May 2026 (UTC) :@[[User:Feeglgeef|Feeglgeef]]: As you probably imagine, this text is very tightly controlled by the Wikimedia Foundation's Legal department. I think the first port of call should be a discussion about why you might want to change things, rather than a rush to specific re-wordings, before approaching them for sign-off. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:28, 12 May 2026 (UTC) ::Well I briefly summarized my justification, my proposed text was just an idea for a starting point. Basically, the abstract content is not really "text", so the footer doesn't actually tell the reader what they're allowed to do with it, and I argue that the current wording implies that the labels are licensed under CC-BY-SA 4, when they aren't. I think a change is critical as otherwise we're not showing the reader a license, or, arguably, in the case of labels, showing users a license that ''does not apply'', which is a pretty bad thing. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:51, 12 May 2026 (UTC) == [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]] == I'd think we should add [[f:Z33068]] here. The function allows you to form a paragraph out of sentences and handles languages having different standards of whether to add a space between them, and adding it here would make finding it easier. I'm not sure what policy we want to have for the suggested functions, this idea might help formulate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:06, 12 May 2026 (UTC) :[[User:Jdforrester (WMF)]] tells me the page has been changed to [[Special:CommunityConfiguration/AbstractWikiSuggestedWikifunctions]] on the telegram. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:25, 12 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]]: Yup, see the weekly update on [[f:Wikifunctions:Status_updates/2026-05-02|2026-05-02]]. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:35, 12 May 2026 (UTC) :I also believe Z33068 should be added to the list. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 12 May 2026 (UTC) {{done}} see [[Special:Diff/7692]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 09:08, 20 May 2026 (UTC) == Abstract Wikipedia statistics site source code == https://abstract-data.toolforge.org/ is a very useful tool, but it doesn't seem to have anything pointing to the location of its source code. Is it closed-source or unfree? While I'm at it I feel I should suggest having language pages' paths formatted differently from how they are currently—at the moment it's <code>/languages/Toki%20Pona</code> when something like <code>/languages/tok</code> would be more suitable. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; : See [[:gitlab:toolforge-repos/abstract-data]]. Also pinging {{ping|DSantamaria-WMF|p=}} (thanks for the tool, by the way). [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 00:25, 13 May 2026 (UTC) ::Thank you. I think a link to that repository should be put in a footer somewhere on the website as I wouldn't have found that if not for you. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:30, 13 May 2026 (UTC) :::{{ping|Theki}} For the record, I found that repo by searching for "abstract-data" on [[:toolhub:|Toolhub]]. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:34, 13 May 2026 (UTC) :::Thanks for the feedback and the report, fixed both things, we have now the link to the repo in the side bar footer, and also the language codes are used in the URLs. Thanks! [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 11:46, 13 May 2026 (UTC) ::::Are you particularly attached to keeping country flag emojis next to the language names? Some consider it an [https://flagsarenotlanguages.com/blog anti-pattern]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 16:17, 14 May 2026 (UTC) :::::I think the use of flags is not really harmful since this is not a ''language selector'', it is just a list of languages. Of course not every language has an associated flag, for example Latin, which does look a bit awkward, but it can't be helped. Maybe give languages without a flag a unique icon from Wikimedia Commons? e.g. <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;">[[File:Toki pona.svg|16px]] Toki Pona</div> instead of <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;"><span>🌐</span>Toki Pona</div>. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:37, 14 May 2026 (UTC) ::::::I thought I saw 🏛️ being used for Latin earlier. But of course, as far as the Unicode Consortium is concerned, [[Q65300415|🇬🇧]] doesn't mean '[[Q1680|English]]', no more than [[Q100587670|🏳️‍🌈]] means '[[Q1359130|Polari]]'; technically, it doesn't even mean '[[Q145|United Kingdom]]', just the letters 🇺 and 🇰 next to each other (which linguistically would indicate [[Q8798|Ukrainian]] in ISO 639, but these are 'regional indicator symbols'). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:21, 14 May 2026 (UTC) :::::::As seems (from this comment and also [[f:User_talk:DSantamaria-WMF#c-%E9%AD%94%E7%90%B4-20260513063700-Country_flags_in_abstract-data|others' comments]]) that flags are a little bit controversial, I just removed them, IMHO it was just an aesthetic concept, I like the look and feel that flags bring to the language labels, but happy to remove them if make some people feel uncomfortable with the concept. [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 05:54, 15 May 2026 (UTC) == Make it more user Friendly == Make it more user-friendly by adding drag-and-drop compenots and one click additions, and make it similar to a visual macro buidler. [[User:ChippyTechGH|ChippyTechGH]] ([[User talk:ChippyTechGH|talk]]) 01:00, 15 May 2026 (UTC) :Could you file something like this on [[phab:|phabricator]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:01, 15 May 2026 (UTC) == Person infoboxes == Hi all, I've just created [[f:Z35167|infobox for person (Z35167)]]. All it can really do presently is display the name of the person in the chosen language and in the person's native language, but it's a good start. I started writing it as a composition but chose to switch to writing it in JavaScript instead, which ended up being less headache-inducing (managing a large list of strings to concatenate together is not fun, plus compositions bring lots of additional overhead). Unfortunately, this means that the actual ''useful'' parts of the infobox—the information about the person themself—is not really doable. I'd need to dereference the Wikidata property references to get their label in the requested language, but since they're references and I'm working with code, not compositions, I can't just call [[f:Z6822|fetch Wikidata property (Z6822)]] and be done with it. If there's a WikiLambda API to do this inside of the JS itself that would be great and would solve everything, but at the moment that alone is what's holding it back, or so it seems. I can get the actual ''values'' of statements just fine, though. If I am missing some amazing WikiLambda API function that will solve this problem for me by letting me dereference the PID, then please let me know because that would be great. If you want to look at an example of the infobox right meow, you can view [https://abstract.wikipedia.org/view/tok/Q317521 Q317521 in Toki Pona] and see how it states Musk's name in both Toki Pona ''and'' his native English name. COOL! My hope is that this can be made less barebones in the near future. Infoboxes are a great way to get quick information on a subject and can fill in the informational gaps in the presently sparse articles we have at the moment, all while staying in the user's requested language. Feedback is appreciated! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:58, 15 May 2026 (UTC) :Thank you for this! I wonder if perhaps it would be better to create one "infobox" function and then have compositions call that, making wd retrival possible? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:38, 15 May 2026 (UTC) ::Working on that at the moment, I think I've got it working but I'm hitting a ratelimit in the orchestrator so I don't know for sure. The main issue with it now is that the actual [[f:Z35175|infobox template (Z35175)]] wrapper was programmed in JS so as to not be a pain in the ass, so this means that it can only take in strings, HTML fragments, etc. so the retrieval of Wikidata stuff still needs to be done by the caller and is rather verbose (see [[f:Z35168|the main implementation]]). The niceties will come soon later once I know that it all works at a lower level, though. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:04, 15 May 2026 (UTC) ::So the problem now seems to be that when [[f:Z29825|label of Wikidata property in language (Z29825)]] isn't being faulty, it's being incredibly slow. Considering retrieving Wikidata items from their references seems to take, like, four to five seconds, and we'll have tens of statements in these infoboxes, I don't see how the property names could be retrieved in a way that doesn't cause the orchestrator to time out or hit a ratelimit. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:01, 15 May 2026 (UTC) :::I think I figured something out? I'm just going to try calling [[f:Z35036|fetch Wikidata property or parts (Z35036)]], it seems to be much faster for whatever reason. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:05, 15 May 2026 (UTC) :::It works now, a little rough around the edges, also very slow, but I think I'm mostly happy with it. Of course it would be great if all you needed to provide to the template function to get a label-statement row was the property reference itself, but I'm too sleep-deprived to figure that out at the moment. I made five bespoke functions specifically for this infobox, more than I would like, but it's probably not ''that'' bad. I'm just hoping I didn't duplicate any functionality in trying to make the composition less verbose and repetitive. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:15, 15 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:36, 15 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) 70zx8kwzr003wvmye9o0zk1fu7vdhxv 14687 14685 2026-08-14T06:53:42Z Theki 2698 /* template suggestion */ 14687 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) :Thank you! That’s great and I’ll look at it more soon. I’m still taking a bit of a wikibreak. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:32, 14 May 2026 (UTC) :Is there anything I've written [[f:User:Theki/best_practices#Abstract_Wikipedia|here]] that you think would make for a good technical section of the page? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 00:04, 15 May 2026 (UTC) ::I've added some of them. Thank you for your list of best practices by the way, I generally agree with them (I can't endorse connecting WD items currently in hope of a better technical solution, but otherwise I do). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:58, 15 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) == [[MediaWiki:Wikimedia-copyright-footer]] == The copyright message has a few issues, mainly that it does not address abstract content (which is not "text"), nor object labels (which are under CC0). Proposed text: "<nowiki> Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. </nowiki>" Which, when rendered, looks like: Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. The message is somewhat inspired by the current one and WF's. Thoughts? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:30, 12 May 2026 (UTC) :@[[User:Feeglgeef|Feeglgeef]]: As you probably imagine, this text is very tightly controlled by the Wikimedia Foundation's Legal department. I think the first port of call should be a discussion about why you might want to change things, rather than a rush to specific re-wordings, before approaching them for sign-off. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:28, 12 May 2026 (UTC) ::Well I briefly summarized my justification, my proposed text was just an idea for a starting point. Basically, the abstract content is not really "text", so the footer doesn't actually tell the reader what they're allowed to do with it, and I argue that the current wording implies that the labels are licensed under CC-BY-SA 4, when they aren't. I think a change is critical as otherwise we're not showing the reader a license, or, arguably, in the case of labels, showing users a license that ''does not apply'', which is a pretty bad thing. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:51, 12 May 2026 (UTC) == [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]] == I'd think we should add [[f:Z33068]] here. The function allows you to form a paragraph out of sentences and handles languages having different standards of whether to add a space between them, and adding it here would make finding it easier. I'm not sure what policy we want to have for the suggested functions, this idea might help formulate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:06, 12 May 2026 (UTC) :[[User:Jdforrester (WMF)]] tells me the page has been changed to [[Special:CommunityConfiguration/AbstractWikiSuggestedWikifunctions]] on the telegram. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:25, 12 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]]: Yup, see the weekly update on [[f:Wikifunctions:Status_updates/2026-05-02|2026-05-02]]. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:35, 12 May 2026 (UTC) :I also believe Z33068 should be added to the list. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 12 May 2026 (UTC) {{done}} see [[Special:Diff/7692]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 09:08, 20 May 2026 (UTC) == Abstract Wikipedia statistics site source code == https://abstract-data.toolforge.org/ is a very useful tool, but it doesn't seem to have anything pointing to the location of its source code. Is it closed-source or unfree? While I'm at it I feel I should suggest having language pages' paths formatted differently from how they are currently—at the moment it's <code>/languages/Toki%20Pona</code> when something like <code>/languages/tok</code> would be more suitable. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; : See [[:gitlab:toolforge-repos/abstract-data]]. Also pinging {{ping|DSantamaria-WMF|p=}} (thanks for the tool, by the way). [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 00:25, 13 May 2026 (UTC) ::Thank you. I think a link to that repository should be put in a footer somewhere on the website as I wouldn't have found that if not for you. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:30, 13 May 2026 (UTC) :::{{ping|Theki}} For the record, I found that repo by searching for "abstract-data" on [[:toolhub:|Toolhub]]. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:34, 13 May 2026 (UTC) :::Thanks for the feedback and the report, fixed both things, we have now the link to the repo in the side bar footer, and also the language codes are used in the URLs. Thanks! [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 11:46, 13 May 2026 (UTC) ::::Are you particularly attached to keeping country flag emojis next to the language names? Some consider it an [https://flagsarenotlanguages.com/blog anti-pattern]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 16:17, 14 May 2026 (UTC) :::::I think the use of flags is not really harmful since this is not a ''language selector'', it is just a list of languages. Of course not every language has an associated flag, for example Latin, which does look a bit awkward, but it can't be helped. Maybe give languages without a flag a unique icon from Wikimedia Commons? e.g. <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;">[[File:Toki pona.svg|16px]] Toki Pona</div> instead of <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;"><span>🌐</span>Toki Pona</div>. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:37, 14 May 2026 (UTC) ::::::I thought I saw 🏛️ being used for Latin earlier. But of course, as far as the Unicode Consortium is concerned, [[Q65300415|🇬🇧]] doesn't mean '[[Q1680|English]]', no more than [[Q100587670|🏳️‍🌈]] means '[[Q1359130|Polari]]'; technically, it doesn't even mean '[[Q145|United Kingdom]]', just the letters 🇺 and 🇰 next to each other (which linguistically would indicate [[Q8798|Ukrainian]] in ISO 639, but these are 'regional indicator symbols'). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:21, 14 May 2026 (UTC) :::::::As seems (from this comment and also [[f:User_talk:DSantamaria-WMF#c-%E9%AD%94%E7%90%B4-20260513063700-Country_flags_in_abstract-data|others' comments]]) that flags are a little bit controversial, I just removed them, IMHO it was just an aesthetic concept, I like the look and feel that flags bring to the language labels, but happy to remove them if make some people feel uncomfortable with the concept. [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 05:54, 15 May 2026 (UTC) == Make it more user Friendly == Make it more user-friendly by adding drag-and-drop compenots and one click additions, and make it similar to a visual macro buidler. [[User:ChippyTechGH|ChippyTechGH]] ([[User talk:ChippyTechGH|talk]]) 01:00, 15 May 2026 (UTC) :Could you file something like this on [[phab:|phabricator]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:01, 15 May 2026 (UTC) == Person infoboxes == Hi all, I've just created [[f:Z35167|infobox for person (Z35167)]]. All it can really do presently is display the name of the person in the chosen language and in the person's native language, but it's a good start. I started writing it as a composition but chose to switch to writing it in JavaScript instead, which ended up being less headache-inducing (managing a large list of strings to concatenate together is not fun, plus compositions bring lots of additional overhead). Unfortunately, this means that the actual ''useful'' parts of the infobox—the information about the person themself—is not really doable. I'd need to dereference the Wikidata property references to get their label in the requested language, but since they're references and I'm working with code, not compositions, I can't just call [[f:Z6822|fetch Wikidata property (Z6822)]] and be done with it. If there's a WikiLambda API to do this inside of the JS itself that would be great and would solve everything, but at the moment that alone is what's holding it back, or so it seems. I can get the actual ''values'' of statements just fine, though. If I am missing some amazing WikiLambda API function that will solve this problem for me by letting me dereference the PID, then please let me know because that would be great. If you want to look at an example of the infobox right meow, you can view [https://abstract.wikipedia.org/view/tok/Q317521 Q317521 in Toki Pona] and see how it states Musk's name in both Toki Pona ''and'' his native English name. COOL! My hope is that this can be made less barebones in the near future. Infoboxes are a great way to get quick information on a subject and can fill in the informational gaps in the presently sparse articles we have at the moment, all while staying in the user's requested language. Feedback is appreciated! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:58, 15 May 2026 (UTC) :Thank you for this! I wonder if perhaps it would be better to create one "infobox" function and then have compositions call that, making wd retrival possible? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:38, 15 May 2026 (UTC) ::Working on that at the moment, I think I've got it working but I'm hitting a ratelimit in the orchestrator so I don't know for sure. The main issue with it now is that the actual [[f:Z35175|infobox template (Z35175)]] wrapper was programmed in JS so as to not be a pain in the ass, so this means that it can only take in strings, HTML fragments, etc. so the retrieval of Wikidata stuff still needs to be done by the caller and is rather verbose (see [[f:Z35168|the main implementation]]). The niceties will come soon later once I know that it all works at a lower level, though. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:04, 15 May 2026 (UTC) ::So the problem now seems to be that when [[f:Z29825|label of Wikidata property in language (Z29825)]] isn't being faulty, it's being incredibly slow. Considering retrieving Wikidata items from their references seems to take, like, four to five seconds, and we'll have tens of statements in these infoboxes, I don't see how the property names could be retrieved in a way that doesn't cause the orchestrator to time out or hit a ratelimit. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:01, 15 May 2026 (UTC) :::I think I figured something out? I'm just going to try calling [[f:Z35036|fetch Wikidata property or parts (Z35036)]], it seems to be much faster for whatever reason. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:05, 15 May 2026 (UTC) :::It works now, a little rough around the edges, also very slow, but I think I'm mostly happy with it. Of course it would be great if all you needed to provide to the template function to get a label-statement row was the property reference itself, but I'm too sleep-deprived to figure that out at the moment. I made five bespoke functions specifically for this infobox, more than I would like, but it's probably not ''that'' bad. I'm just hoping I didn't duplicate any functionality in trying to make the composition less verbose and repetitive. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:15, 15 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:36, 15 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) p64cpniohgljqvcfr7zwryjmh043xya 14689 14687 2026-08-14T06:54:14Z Theki 2698 /* Marking NLG Default text */ 14689 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) :Thank you! That’s great and I’ll look at it more soon. I’m still taking a bit of a wikibreak. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:32, 14 May 2026 (UTC) :Is there anything I've written [[f:User:Theki/best_practices#Abstract_Wikipedia|here]] that you think would make for a good technical section of the page? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 00:04, 15 May 2026 (UTC) ::I've added some of them. Thank you for your list of best practices by the way, I generally agree with them (I can't endorse connecting WD items currently in hope of a better technical solution, but otherwise I do). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:58, 15 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) == [[MediaWiki:Wikimedia-copyright-footer]] == The copyright message has a few issues, mainly that it does not address abstract content (which is not "text"), nor object labels (which are under CC0). Proposed text: "<nowiki> Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. </nowiki>" Which, when rendered, looks like: Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. The message is somewhat inspired by the current one and WF's. Thoughts? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:30, 12 May 2026 (UTC) :@[[User:Feeglgeef|Feeglgeef]]: As you probably imagine, this text is very tightly controlled by the Wikimedia Foundation's Legal department. I think the first port of call should be a discussion about why you might want to change things, rather than a rush to specific re-wordings, before approaching them for sign-off. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:28, 12 May 2026 (UTC) ::Well I briefly summarized my justification, my proposed text was just an idea for a starting point. Basically, the abstract content is not really "text", so the footer doesn't actually tell the reader what they're allowed to do with it, and I argue that the current wording implies that the labels are licensed under CC-BY-SA 4, when they aren't. I think a change is critical as otherwise we're not showing the reader a license, or, arguably, in the case of labels, showing users a license that ''does not apply'', which is a pretty bad thing. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:51, 12 May 2026 (UTC) == [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]] == I'd think we should add [[f:Z33068]] here. The function allows you to form a paragraph out of sentences and handles languages having different standards of whether to add a space between them, and adding it here would make finding it easier. I'm not sure what policy we want to have for the suggested functions, this idea might help formulate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:06, 12 May 2026 (UTC) :[[User:Jdforrester (WMF)]] tells me the page has been changed to [[Special:CommunityConfiguration/AbstractWikiSuggestedWikifunctions]] on the telegram. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:25, 12 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]]: Yup, see the weekly update on [[f:Wikifunctions:Status_updates/2026-05-02|2026-05-02]]. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:35, 12 May 2026 (UTC) :I also believe Z33068 should be added to the list. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 12 May 2026 (UTC) {{done}} see [[Special:Diff/7692]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 09:08, 20 May 2026 (UTC) == Abstract Wikipedia statistics site source code == https://abstract-data.toolforge.org/ is a very useful tool, but it doesn't seem to have anything pointing to the location of its source code. Is it closed-source or unfree? While I'm at it I feel I should suggest having language pages' paths formatted differently from how they are currently—at the moment it's <code>/languages/Toki%20Pona</code> when something like <code>/languages/tok</code> would be more suitable. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; : See [[:gitlab:toolforge-repos/abstract-data]]. Also pinging {{ping|DSantamaria-WMF|p=}} (thanks for the tool, by the way). [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 00:25, 13 May 2026 (UTC) ::Thank you. I think a link to that repository should be put in a footer somewhere on the website as I wouldn't have found that if not for you. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:30, 13 May 2026 (UTC) :::{{ping|Theki}} For the record, I found that repo by searching for "abstract-data" on [[:toolhub:|Toolhub]]. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:34, 13 May 2026 (UTC) :::Thanks for the feedback and the report, fixed both things, we have now the link to the repo in the side bar footer, and also the language codes are used in the URLs. Thanks! [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 11:46, 13 May 2026 (UTC) ::::Are you particularly attached to keeping country flag emojis next to the language names? Some consider it an [https://flagsarenotlanguages.com/blog anti-pattern]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 16:17, 14 May 2026 (UTC) :::::I think the use of flags is not really harmful since this is not a ''language selector'', it is just a list of languages. Of course not every language has an associated flag, for example Latin, which does look a bit awkward, but it can't be helped. Maybe give languages without a flag a unique icon from Wikimedia Commons? e.g. <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;">[[File:Toki pona.svg|16px]] Toki Pona</div> instead of <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;"><span>🌐</span>Toki Pona</div>. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:37, 14 May 2026 (UTC) ::::::I thought I saw 🏛️ being used for Latin earlier. But of course, as far as the Unicode Consortium is concerned, [[Q65300415|🇬🇧]] doesn't mean '[[Q1680|English]]', no more than [[Q100587670|🏳️‍🌈]] means '[[Q1359130|Polari]]'; technically, it doesn't even mean '[[Q145|United Kingdom]]', just the letters 🇺 and 🇰 next to each other (which linguistically would indicate [[Q8798|Ukrainian]] in ISO 639, but these are 'regional indicator symbols'). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:21, 14 May 2026 (UTC) :::::::As seems (from this comment and also [[f:User_talk:DSantamaria-WMF#c-%E9%AD%94%E7%90%B4-20260513063700-Country_flags_in_abstract-data|others' comments]]) that flags are a little bit controversial, I just removed them, IMHO it was just an aesthetic concept, I like the look and feel that flags bring to the language labels, but happy to remove them if make some people feel uncomfortable with the concept. [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 05:54, 15 May 2026 (UTC) == Make it more user Friendly == Make it more user-friendly by adding drag-and-drop compenots and one click additions, and make it similar to a visual macro buidler. [[User:ChippyTechGH|ChippyTechGH]] ([[User talk:ChippyTechGH|talk]]) 01:00, 15 May 2026 (UTC) :Could you file something like this on [[phab:|phabricator]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:01, 15 May 2026 (UTC) == Person infoboxes == Hi all, I've just created [[f:Z35167|infobox for person (Z35167)]]. All it can really do presently is display the name of the person in the chosen language and in the person's native language, but it's a good start. I started writing it as a composition but chose to switch to writing it in JavaScript instead, which ended up being less headache-inducing (managing a large list of strings to concatenate together is not fun, plus compositions bring lots of additional overhead). Unfortunately, this means that the actual ''useful'' parts of the infobox—the information about the person themself—is not really doable. I'd need to dereference the Wikidata property references to get their label in the requested language, but since they're references and I'm working with code, not compositions, I can't just call [[f:Z6822|fetch Wikidata property (Z6822)]] and be done with it. If there's a WikiLambda API to do this inside of the JS itself that would be great and would solve everything, but at the moment that alone is what's holding it back, or so it seems. I can get the actual ''values'' of statements just fine, though. If I am missing some amazing WikiLambda API function that will solve this problem for me by letting me dereference the PID, then please let me know because that would be great. If you want to look at an example of the infobox right meow, you can view [https://abstract.wikipedia.org/view/tok/Q317521 Q317521 in Toki Pona] and see how it states Musk's name in both Toki Pona ''and'' his native English name. COOL! My hope is that this can be made less barebones in the near future. Infoboxes are a great way to get quick information on a subject and can fill in the informational gaps in the presently sparse articles we have at the moment, all while staying in the user's requested language. Feedback is appreciated! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:58, 15 May 2026 (UTC) :Thank you for this! I wonder if perhaps it would be better to create one "infobox" function and then have compositions call that, making wd retrival possible? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:38, 15 May 2026 (UTC) ::Working on that at the moment, I think I've got it working but I'm hitting a ratelimit in the orchestrator so I don't know for sure. The main issue with it now is that the actual [[f:Z35175|infobox template (Z35175)]] wrapper was programmed in JS so as to not be a pain in the ass, so this means that it can only take in strings, HTML fragments, etc. so the retrieval of Wikidata stuff still needs to be done by the caller and is rather verbose (see [[f:Z35168|the main implementation]]). The niceties will come soon later once I know that it all works at a lower level, though. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:04, 15 May 2026 (UTC) ::So the problem now seems to be that when [[f:Z29825|label of Wikidata property in language (Z29825)]] isn't being faulty, it's being incredibly slow. Considering retrieving Wikidata items from their references seems to take, like, four to five seconds, and we'll have tens of statements in these infoboxes, I don't see how the property names could be retrieved in a way that doesn't cause the orchestrator to time out or hit a ratelimit. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:01, 15 May 2026 (UTC) :::I think I figured something out? I'm just going to try calling [[f:Z35036|fetch Wikidata property or parts (Z35036)]], it seems to be much faster for whatever reason. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:05, 15 May 2026 (UTC) :::It works now, a little rough around the edges, also very slow, but I think I'm mostly happy with it. Of course it would be great if all you needed to provide to the template function to get a label-statement row was the property reference itself, but I'm too sleep-deprived to figure that out at the moment. I made five bespoke functions specifically for this infobox, more than I would like, but it's probably not ''that'' bad. I'm just hoping I didn't duplicate any functionality in trying to make the composition less verbose and repetitive. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:15, 15 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:36, 15 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) dyb0y1mvyiuhe1hy4umlehvi5lyg083 14695 14689 2026-08-14T06:57:12Z Theki 2698 /* Most used fragments */ 14695 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3">According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?<br>@[[User User:Amire80|Amir E. Aharoni]] Yes, it is correct. For pinyin transliterations, the only way is lemma-based. I'll also encourage you to read in underrepresented [https://en.wikipedia.org/wiki/Varieties_of_Chinese Varieties of Chinese] :-) I am working on them on English Wiktionary. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC)</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) :I avoid [[f:Z33068]] for now, because executing a whole paragraph in a single call would often time out. So my current alternative is inserting [[f:Z35672]] between sentences. Fairly clunky, but it works... --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 06:08, 28 May 2026 (UTC) ::Can you categorize the talk pages of articles you're doing that with? It has major accessibility concerns for our friends using screen readers, so it'd be nice to be able to find those with issues when were able to fix the calls [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:50, 28 May 2026 (UTC) :::I think the new tool can show us this (via dumps). For example, here are the uses of 'paragraph': https://abstract-data.toolforge.org/zid/Z32123 --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:07, 28 May 2026 (UTC) ::::There's more than one way to not use spaces correctly and more than one way to use spaces correctly, this wouldn't catch all of them. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:13, 28 May 2026 (UTC) :::::I'm not totally sure what you want to track, but I'm confident that this will find all my uses. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:10, 29 May 2026 (UTC) ::::I think it slipped past everyone's notice, but I made a template for linking to that sort of information @ [[Template:Zd|<nowiki>{{</nowiki>zd<nowiki>}}</nowiki>]]. {{zd|Z35672|sentence separator}} <span style="font-size:smaller;opacity:0.8">(I don't think the database dumps have noticed the function you're using yet, so it's a 404 at the moment.)</span> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:09, 29 May 2026 (UTC) :::::@[[User:Rae|rae]] Great! Would you be willing to add it to https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Useful_functions_for_article_composition ? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 12:47, 10 July 2026 (UTC) ===Easier solution?=== Maybe a much easier solution would be to replace the "." after each sentence with ". " (a full stop and a space). The paragraghs might add an extra space, but that is displayed as one by the browser. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) :@[[User:HenkvD|HenkvD]]: I originally thought this was a bit hacky, but it actually makes sense -- the spacing is determined by punctuation. For example, English [https://en.wikipedia.org/wiki/Sentence_spacing#cite_ref-Bringhurst_2004._p.28_4-0 used to have] the convention of using two spaces, Chinese uses no spaces, and in Tibetan, ། marks the end of a short phrase or sentence (still needs a space after it), while ༎ marks the end of a paragraph. (Yes, there's a dedicated paragraph-ending punctuation mark!) This at least matches our current abstraction model well. Also, I don't think this will lead to extra spaces. ——[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 11:21, 18 June 2026 (UTC) ::<nowiki><tangent></nowiki> <em>「Yes, there's a dedicated paragraph-ending punctuation mark!」</em> We English folk have used ¶ for that before, so I don't suppose a paragraph mark in Tibetan is all that unusual... <nowiki></tangent></nowiki> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 18 June 2026 (UTC) :An unnecessary space in the end of a text, though invisible, cannot be a good idea. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:43, 18 June 2026 (UTC) ::I agree. We should not change functions which correctly return sentences into functions which return sentences with spaces stuck to them. {{zd|Z35672}} works well until the performance is good enough for {{zd|Z33068}}. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 12:34, 18 June 2026 (UTC) :::I think if the current WL system allowed for ''starting'' tags and then ending them at a later indeterminate point, Z33068's performance issues could be perhaps mitigated slightly. One could use a ''start paragraph'' call, followed by some sentences in some well-established form, and then close the paragraph with an ''end paragraph'' call. An issue I've had with paragraphs is that you can't see the paragraph build itself up sentence-by-sentence, and the failure of a ''single'' function call means the inability of the ''entire'' paragraph to render at all—something that would, of course, be fixed by making paragraphs more granular in this way. Something to think about, although I am sure it's not possible presently (since the abstract HTML renderer doesn't build up the document gradually, and instead expects the HTML to be well-formed from the outset). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:28, 18 June 2026 (UTC) :::: Each fragment is its own div, and you can't do <nowiki><div><p></div><div>[text]</div><div></p></div></nowiki>, it will break the browser's tag grouping. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:55, 18 June 2026 (UTC) :::::Hence why I mentioned that I don't suspect it will be possible. The concept is just something to think about. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:34, 18 June 2026 (UTC) == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) :Thank you! That’s great and I’ll look at it more soon. I’m still taking a bit of a wikibreak. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:32, 14 May 2026 (UTC) :Is there anything I've written [[f:User:Theki/best_practices#Abstract_Wikipedia|here]] that you think would make for a good technical section of the page? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 00:04, 15 May 2026 (UTC) ::I've added some of them. Thank you for your list of best practices by the way, I generally agree with them (I can't endorse connecting WD items currently in hope of a better technical solution, but otherwise I do). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:58, 15 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) == [[MediaWiki:Wikimedia-copyright-footer]] == The copyright message has a few issues, mainly that it does not address abstract content (which is not "text"), nor object labels (which are under CC0). Proposed text: "<nowiki> Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. </nowiki>" Which, when rendered, looks like: Text and abstract content are available under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike License]; the labels of objects from [[f:|Wikifunctions]] are available under the [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 License]; additional terms may apply. See [https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use Terms of Use] for details. The message is somewhat inspired by the current one and WF's. Thoughts? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:30, 12 May 2026 (UTC) :@[[User:Feeglgeef|Feeglgeef]]: As you probably imagine, this text is very tightly controlled by the Wikimedia Foundation's Legal department. I think the first port of call should be a discussion about why you might want to change things, rather than a rush to specific re-wordings, before approaching them for sign-off. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:28, 12 May 2026 (UTC) ::Well I briefly summarized my justification, my proposed text was just an idea for a starting point. Basically, the abstract content is not really "text", so the footer doesn't actually tell the reader what they're allowed to do with it, and I argue that the current wording implies that the labels are licensed under CC-BY-SA 4, when they aren't. I think a change is critical as otherwise we're not showing the reader a license, or, arguably, in the case of labels, showing users a license that ''does not apply'', which is a pretty bad thing. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:51, 12 May 2026 (UTC) == [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]] == I'd think we should add [[f:Z33068]] here. The function allows you to form a paragraph out of sentences and handles languages having different standards of whether to add a space between them, and adding it here would make finding it easier. I'm not sure what policy we want to have for the suggested functions, this idea might help formulate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:06, 12 May 2026 (UTC) :[[User:Jdforrester (WMF)]] tells me the page has been changed to [[Special:CommunityConfiguration/AbstractWikiSuggestedWikifunctions]] on the telegram. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:25, 12 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]]: Yup, see the weekly update on [[f:Wikifunctions:Status_updates/2026-05-02|2026-05-02]]. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 16:35, 12 May 2026 (UTC) :I also believe Z33068 should be added to the list. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:25, 12 May 2026 (UTC) {{done}} see [[Special:Diff/7692]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 09:08, 20 May 2026 (UTC) == Abstract Wikipedia statistics site source code == https://abstract-data.toolforge.org/ is a very useful tool, but it doesn't seem to have anything pointing to the location of its source code. Is it closed-source or unfree? While I'm at it I feel I should suggest having language pages' paths formatted differently from how they are currently—at the moment it's <code>/languages/Toki%20Pona</code> when something like <code>/languages/tok</code> would be more suitable. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; : See [[:gitlab:toolforge-repos/abstract-data]]. Also pinging {{ping|DSantamaria-WMF|p=}} (thanks for the tool, by the way). [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 00:25, 13 May 2026 (UTC) ::Thank you. I think a link to that repository should be put in a footer somewhere on the website as I wouldn't have found that if not for you. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:30, 13 May 2026 (UTC) :::{{ping|Theki}} For the record, I found that repo by searching for "abstract-data" on [[:toolhub:|Toolhub]]. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:34, 13 May 2026 (UTC) :::Thanks for the feedback and the report, fixed both things, we have now the link to the repo in the side bar footer, and also the language codes are used in the URLs. Thanks! [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 11:46, 13 May 2026 (UTC) ::::Are you particularly attached to keeping country flag emojis next to the language names? Some consider it an [https://flagsarenotlanguages.com/blog anti-pattern]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 16:17, 14 May 2026 (UTC) :::::I think the use of flags is not really harmful since this is not a ''language selector'', it is just a list of languages. Of course not every language has an associated flag, for example Latin, which does look a bit awkward, but it can't be helped. Maybe give languages without a flag a unique icon from Wikimedia Commons? e.g. <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;">[[File:Toki pona.svg|16px]] Toki Pona</div> instead of <div style="display:inline-flex;align-items:center;border:1px solid #0002;border-radius:4px;gap:4px;padding:4px;"><span>🌐</span>Toki Pona</div>. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:37, 14 May 2026 (UTC) ::::::I thought I saw 🏛️ being used for Latin earlier. But of course, as far as the Unicode Consortium is concerned, [[Q65300415|🇬🇧]] doesn't mean '[[Q1680|English]]', no more than [[Q100587670|🏳️‍🌈]] means '[[Q1359130|Polari]]'; technically, it doesn't even mean '[[Q145|United Kingdom]]', just the letters 🇺 and 🇰 next to each other (which linguistically would indicate [[Q8798|Ukrainian]] in ISO 639, but these are 'regional indicator symbols'). [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 17:21, 14 May 2026 (UTC) :::::::As seems (from this comment and also [[f:User_talk:DSantamaria-WMF#c-%E9%AD%94%E7%90%B4-20260513063700-Country_flags_in_abstract-data|others' comments]]) that flags are a little bit controversial, I just removed them, IMHO it was just an aesthetic concept, I like the look and feel that flags bring to the language labels, but happy to remove them if make some people feel uncomfortable with the concept. [[User:DSantamaria-WMF|DSantamaria-WMF]] ([[User talk:DSantamaria-WMF|talk]]) 05:54, 15 May 2026 (UTC) == Make it more user Friendly == Make it more user-friendly by adding drag-and-drop compenots and one click additions, and make it similar to a visual macro buidler. [[User:ChippyTechGH|ChippyTechGH]] ([[User talk:ChippyTechGH|talk]]) 01:00, 15 May 2026 (UTC) :Could you file something like this on [[phab:|phabricator]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:01, 15 May 2026 (UTC) == Person infoboxes == Hi all, I've just created [[f:Z35167|infobox for person (Z35167)]]. All it can really do presently is display the name of the person in the chosen language and in the person's native language, but it's a good start. I started writing it as a composition but chose to switch to writing it in JavaScript instead, which ended up being less headache-inducing (managing a large list of strings to concatenate together is not fun, plus compositions bring lots of additional overhead). Unfortunately, this means that the actual ''useful'' parts of the infobox—the information about the person themself—is not really doable. I'd need to dereference the Wikidata property references to get their label in the requested language, but since they're references and I'm working with code, not compositions, I can't just call [[f:Z6822|fetch Wikidata property (Z6822)]] and be done with it. If there's a WikiLambda API to do this inside of the JS itself that would be great and would solve everything, but at the moment that alone is what's holding it back, or so it seems. I can get the actual ''values'' of statements just fine, though. If I am missing some amazing WikiLambda API function that will solve this problem for me by letting me dereference the PID, then please let me know because that would be great. If you want to look at an example of the infobox right meow, you can view [https://abstract.wikipedia.org/view/tok/Q317521 Q317521 in Toki Pona] and see how it states Musk's name in both Toki Pona ''and'' his native English name. COOL! My hope is that this can be made less barebones in the near future. Infoboxes are a great way to get quick information on a subject and can fill in the informational gaps in the presently sparse articles we have at the moment, all while staying in the user's requested language. Feedback is appreciated! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 02:58, 15 May 2026 (UTC) :Thank you for this! I wonder if perhaps it would be better to create one "infobox" function and then have compositions call that, making wd retrival possible? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:38, 15 May 2026 (UTC) ::Working on that at the moment, I think I've got it working but I'm hitting a ratelimit in the orchestrator so I don't know for sure. The main issue with it now is that the actual [[f:Z35175|infobox template (Z35175)]] wrapper was programmed in JS so as to not be a pain in the ass, so this means that it can only take in strings, HTML fragments, etc. so the retrieval of Wikidata stuff still needs to be done by the caller and is rather verbose (see [[f:Z35168|the main implementation]]). The niceties will come soon later once I know that it all works at a lower level, though. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 05:04, 15 May 2026 (UTC) ::So the problem now seems to be that when [[f:Z29825|label of Wikidata property in language (Z29825)]] isn't being faulty, it's being incredibly slow. Considering retrieving Wikidata items from their references seems to take, like, four to five seconds, and we'll have tens of statements in these infoboxes, I don't see how the property names could be retrieved in a way that doesn't cause the orchestrator to time out or hit a ratelimit. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:01, 15 May 2026 (UTC) :::I think I figured something out? I'm just going to try calling [[f:Z35036|fetch Wikidata property or parts (Z35036)]], it seems to be much faster for whatever reason. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 06:05, 15 May 2026 (UTC) :::It works now, a little rough around the edges, also very slow, but I think I'm mostly happy with it. Of course it would be great if all you needed to provide to the template function to get a label-statement row was the property reference itself, but I'm too sleep-deprived to figure that out at the moment. I made five bespoke functions specifically for this infobox, more than I would like, but it's probably not ''that'' bad. I'm just hoping I didn't duplicate any functionality in trying to make the composition less verbose and repetitive. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 07:15, 15 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in Types, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:36, 15 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == Translations == Yes, this question is probably easily answerable through a Web search, but I thought I'd ask here anyways. I am unfortunately not bilingual... I know Toki Pona, but it's a constructed language. I'd love to be a polyglot of some sorts but that is a future thing. I've been trying to translate pages into tok, for funsies mostly. At any rate, I want to convert some of the un-translated pages, namely Feeglgeef's policy drafts, into ones that can be translated (and then translate them into Toki Pona of course). I think I have to be a translation administrator for this? Which is a process that I'd have to ''apply'' for, and I doubt I have the credentials to be accepted for such a role. Regardless, is there a way I can go about this without having to do it through someone else? I can probably easily find documentation on marking pages for translation but I don't know how much I'm actually capable of doing as just a regular user. Should I apply? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:15, 20 May 2026 (UTC) :Most of the process of preparing a page for translation can be done by any editor. See [[:mw:Help:Extension:Translate/Page translation example]]. :The step of marking a page or translation for the first time or after changes must be done by a translation administrator. :I recommend learning the <nowiki><translate> and <tvar></nowiki> syntax and using it on a few pages before applying for this permission. After you do it on a few pages, and you feel confident, and you want to do it more, you can ask for the permission. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:28, 20 May 2026 (UTC) ::Just to confirm, did I mark up [[Special:Diff/8138|this page]] for translation properly? I thought to give the hatnote its own <code>&lt;translate&gt;</code> enclosure so as to exclude the indent and italicization from needing to be included in the translatable text. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:10, 20 May 2026 (UTC) :::Mostly properly, but don't exclude <code><nowiki>''</nowiki></code> for italics from translation. It's generally a good idea to exclude complex markup from translation because it's hard for many people to type, and it usually stays the same in translation anyway. <code><nowiki>''</nowiki></code> for italics is different, however: it's very simple to type and familiar to most editors; italic letters are used differently in different languages, and in some languages they aren't used at all, so translators need the freedom to use them appropriately; this markup can also appear in the middle of a translation unit and not only in the ends. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:35, 20 May 2026 (UTC) ::::Thank you for the guidance. Should the italics be included if they are used over the entire hatnote? I figure that placement of italics should be left up to the discretion of the translators, but the hatnote itself is meant to be entirely italicized, I would think irrespective of the language it's in. Is this the right idea or should they still be kept within the translation unit? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:45, 20 May 2026 (UTC) :::::Yes, italics should be included in the translation unit if they are used over the entire hatnote. Some languages don't use italic writing at all, so it shouldn't be forced. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:36, 20 May 2026 (UTC) :I'd support a translation administrator request ;), for reasons below. I'm not sure why we need a seperate translation administrator right, or why we have to call it an "administrator" (deciding that a page could be translated is a much less important role than, say, page deletion, or blocking). We picked three of them (well, one of them went through the WMF, so we picked two), [https://abstract.wikipedia.org/wiki/Special:Log?type=pagetranslation&user=&page=&excludetempacct=1&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist they don't appear very active, though], only marking 9 times this month, zero (0) of which were for pages marked for the first time. Both community translation admins used their global history and rights to get the role and only stop by occasionally, so having one who ''actually'' edits here would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:06, 20 May 2026 (UTC) ::This reply echos my philosophy of a sort of wiki-[[Q166005|xenophobia]] (the term xenophobia is probably too harsh, and I wouldn't consider myself one in real life, but it's the best word I can think of), I generally distrust users with a lot of global rights (both global sysop etc. and large amounts of local rights) who come make [[m:Metapedianism|metapedian]] contributions, not as people but to their ability to handle Wikifunctions and Abstract Wikipedia as incredibly unique and technically complex projects. I apologize if it my opinions come off as rude or ungrateful, I do appreciate the work of our translation administrators. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:26, 20 May 2026 (UTC) :::You don't bother me, it's fine. I think they definitely have a place, they can be useful and they usually are. Obviously local admins and what have you that earned their roles through the trust and reputation of the specific community they are in are going to occupy a more trusting position in my mind than a global sysop or global ''anything''. Specialized role members are good and healthy in the long term; I think we are giving these privileges to global users sparingly as the project is still in its infancy and as core contributors emerge and take up key positions we will have a more well-rounded and self-sustaining community with less global privileges needed to take up certain tasks. Wikifunctions probably needed some Foundation members or other staff to act as functioneers initially while the general community was still orienting themselves with WikiLambda and working on applying for the role, but now we have [[f:Special:ListUsers/functioneer|74(!) of them]] and the number of normal members using their specialized skills outnumbers those who were "grandfathered" in (for lack of a better term) or similar. The wiki is young—it just needs time. I myself have been considering applying for sysop privileges since they are obviously needed (there being exactly Zero of them at the moment); I've been weighing the pros and cons of such a commitment, it's obviously a lot to take up. I wish your sysop request went through, I think you would have made a great admin here. I'm unsure of what others think of my capabilities, I'm rather in-and-out around these social spaces so I don't know if there's much to go off of. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:55, 20 May 2026 (UTC) ::::Totally agree, and I'd support a sysopship request as well, though I'm apparently not good at assessing what the community considers supportable in admin candidate ;). ::::Off-topic, but interestingly, the sysop toolset allows you to grant yourself translation adminship. I'm not sure if sysops are expected not to grant themselves the permissions (kind of like how on enwiki 'crats are expected not grant themselves any rights without discussion despite having the technical rights), but I did it to myself on WF because [https://www.wikifunctions.org/w/index.php?title=Special:Log&logid=84940 another sysop had]. Additionally, the functioneer right [[Special:ListGroupRights#functioneer|exists on this wiki]], with the same rights on WF, despite all of them not doing anything on this wiki. I believe this is because, on the technical side, both AW and WF are powered by the same MediaWiki extension (Wikilambda), with one wiki set to a mode for abstract articles and another set to a mode for ZObjects. [https://dag.wikipedia.org/wiki/Di%C5%8B%27gahim:ListGroupRights#functioneer Checking the Dagbani Wikipedia] supports this theory. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:00, 20 May 2026 (UTC) :::::It always depends on the local policy. For Wikifunctions it is: ''Administrators do not need to undergo another discussion to become translation administrators; they can self-grant the rights to their account if necessary. Temporary administrators are not allowed to self-grant permanent translation administrator rights.'' :::::The availability of the functioneer right is a bug, see [[phab:T407066]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 19:36, 20 May 2026 (UTC) :::If you don't consider yourself a xenophobe in real life, I would recommend not calling yourself that here, or anywhere really. Especially since it was the ideological capture during the 2010s of the Croatian-language Wikipedia [[w:hr:]] by actual xenophobes that was part of the impetus for Abstract Wikipedia according to [https://simia.net/wiki/Draft:_Collaborating_on_the_sum_of_all_knowledge_across_languages#A_look_on_some_south_Slavic_language_Wikipedias Denny's blog]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:10, 26 May 2026 (UTC) == Policy drafts == Hi all! I've written some draft policies and guidelines over the last few days. We're not a bureaucracy, so the point is not to set some rules but to kick off some discussions as to how our wiki will work. So far, I've created: * [[Abstract Wikipedia:Notability|a notability guideline]] * [[Abstract Wikipedia:Deletion policy|a deletion policy]] I've written them as my opinion on what should happen, but I'm hoping to align them with community consensus as we discuss them more. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:44, 21 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #249 is out: Annual plan 2026-2027 == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-23|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you the current draft of objectives for Wikifunctions and Abstract Wikipedia in the WMF Annual Plan 2026-2027, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:48, 25 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30536976 --> == To abstract Wikipedia or be the Abstract Wikipedia == There is a discussion happening about what the [[Abstract Wikipedia:Notability|notability criteria]] for Abstract Wikipedia should be, and in trying to participate I've found my idea of Abstract Wikipedia is awfully abstract. Is Abstract Wikipedia supposed to abstract Wikipedia, as in abstracting information from existing articles on the language Wikipedias (barring new contributions), or is it supposed to become the Abstract Wikipedia, supporting collaboration across all languages like it's the language Wikipedia to end all language Wikipedias (allowing new contributions)? I thought the answer would be obvious, but the name Abstract Wikipedia is a bit ambiguous. Am I missing something? [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 02:16, 27 May 2026 (UTC) :I think ({{ping|DVrandecic (WMF)|p=?}}) the idea is (and I personally prefer) the latter. I believe that, given the fact that it's much easier to write a concrete article than an abstract article, and the fact that the community of potential future contributors on enwiki is skeptical ''at best'', we ultimately will never expand beyond the size of other wikis, but I see no problem with allowing volunteers to add information not on other wikis (it's probably not the most effective, but they're volunteers, beggars can't be choosers), as long as it's not vandalism, useless, or promotional slop. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:31, 27 May 2026 (UTC) :@[[User:Some helpful person|Some helpful person]] Abstract Wikipedia is a Wikipedia, where people can collaborate across languages on articles, which can then be used to fill gaps in the existing Wikipedias. Whereas I expect that current Wikipedia articles might be used as a convenient starting point for many of the articles in Abstract Wikipedia, this is more a consequence of Wikipedia being one of the best places to go to to find reliable knowledge, but that is not part of how it is supposed to work. So, this is not to abstract the existing Wikipedias, but to collaborate on an Abstract Wikipedia. At no point is this meant to replace existing Wikipedias. (Thanks to @[[User:Feeglgeef|Feeglgeef]] for the ping!) --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 17:01, 27 May 2026 (UTC) ::Thank you, this makes a lot more sense now. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 21:52, 27 May 2026 (UTC) == template suggestion == Some way to mock abstract syntax on talk and project pages, analogous to those in [[d:category:format Template]]. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 15:21, 27 May 2026 (UTC) :Hmm. I agree. :Workshopping ideas for how it works: :* Invokation: <nowiki>{{Call|Z26039|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|{"Z1K1": "Z6091", "Z6091K1": "Q634"}|{"Z1K1": "Z18", "Z18K1": "Z825K1"}|lang=en}}</nowiki> :** This could then be suplemented by helper templates: <nowiki>{{Call|Z26039|{{Wikidata item argument reference}}|{{Wikidata item reference|Q634}}|{{Language argument reference}}}}</nowiki> :* This would result in "[[f:Z26039|subject is instance of (string)]] (wikidata item reference, [[d:Q634|planet]], language)" :** Icons are missing in this example, I'm not sure if we can actually add them :Thoughts? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:04, 27 May 2026 (UTC) == Marking NLG Default text == Some NLG functions give default texts, like [[f:Z33420|Z33420]] will give text like "Paris ∈ {city}". sometimes in other languages the English text is show. Currently there is no visual clue that these texts are not normal text in the requested language. I propose we mark these text with color <span style="color:magenta;">Paris ∈ {city}</span> with something like <nowiki><span style="color:magenta;">Paris ∈ {city}</span></nowiki>. To have this configurable/maintainable this could be included in a function, called NLG default text or so, with a text as input an a text in color as output. The exact formatting like magenta color or gray background or something else can be discussed/decided later. To have it even more configurable on personal stylesheets it could use a class like <nowiki><span class="NLG Default text">Paris ∈ {city}</span></nowiki>. What do you think? Could somebody make such a function already? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 12:00, 29 May 2026 (UTC) :The are technically just monolingual texts in a language called "multiple languages". I threw a prototype together really quickly, [[f:Z35839]]. It will accept strings, monolingual texts, and html fragments as input, so you have to select which type you want. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:59, 29 May 2026 (UTC) ::OK, thanks, I added it to [[f:Z26039]] and works as expected, see [https://www.wikifunctions.org/wiki/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q64%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q515%22%7D%2C%22Z26039K3%22%3A%22Z1555%22%7D here]. The test for the function with default text now fails because it now is in magenta color. That was to be expected. I will leave the tests unchanged if that is OK with you, as we might need to change the exact formatting. ::Is it OK to add this to other NLG functions that produce default output? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:59, 29 May 2026 (UTC) :::Sure, [[w:en:WP:Be bold|be bold]]! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:50, 29 May 2026 (UTC) ::::Feeglgeef, I am struggling with the output. Can you have a look? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:02, 30 May 2026 (UTC) :::::Can you link me to where? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:08, 30 May 2026 (UTC) ::::::{{Q|90}} in a language vls should give a magenta text. Instead it gives "Wikifunctions returned a failed response: Unspecified error". [[f:Z33422]] results "<span style="color: magenta;">Parys ∈ {stad}</span>" (as a string). [[f:Z26039]] also gives "<span style="color: magenta;">Parys ∈ {stad}</span>", but it's test [[f:Z33726]] gives an HTML equivalent, not a string. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:59, 30 May 2026 (UTC) :::::::You shouldn't be returning HTML in string-typed functions. I'm not sure, then, how we implement your proposal, actually. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:54, 30 May 2026 (UTC) ::::::::I tried with [[f:Z35921]] but now the output is the literal text, and not HTML. Does anybody have an idea how to implement the text in a color? ::::::::Alternatively we could use texts like // Parys ∈ {stad} //. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:51, 31 May 2026 (UTC) ::::::::: You need to output [[f:Z89|HTML fragment]], not String. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:16, 31 May 2026 (UTC) :I agree with the above that this should not be applied to functions which return strings or monolingual text. If anything, it might work to insert it into functions returning HTML. The most egregious problems I've seen are when I tried to render into an RTL language (e.g. Hebrew 0 try on [[Q408]]), and it spilled all the formatting all over the article. I will revert the change to the string default at [[:f:Z33421]], but suggest it is tested carefully if implemented elsewhere. In general I prefer just marking with spans rather than colours at this stage. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:49, 3 June 2026 (UTC) :: Perhaps mark with spans given a specific ID and then allow users to use a userscript/gadget to paint them magenta? That seems like the most considerate approach. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:12, 3 June 2026 (UTC) :::[[:f:Z32234]] suggests something like <code>span lang="mul"</code> or similar. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:20, 3 June 2026 (UTC) ::::I will (carefully) try some other alternatives, and use a personal class in my userscript for <nowiki><span class="NLG Default text"></nowiki>. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 14:05, 4 June 2026 (UTC) ::::: If possible, can you use <nowiki><span lang="mul"></nowiki>? This would allow it to also catch some instances automatically. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:14, 4 June 2026 (UTC) ::::::I have done so, but how can I set my personal stylesheet to show color magenta with <nowiki><span lang="mul"></nowiki>? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:20, 4 June 2026 (UTC) ::::::: try adding this to [[Special:MyPage/common.css]]: ::::::: [lang="mul"] {<br> color: magenta;<br> } [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:48, 4 June 2026 (UTC) : I created a new implementation for [[f:Z35921]] using emoji text, resulting in texts like "❌≪Paris ∈ {city}≫❌". It works on [[Q90]] for not yet specified languages like Zeelandic. I will be bold in adding this other functions that use default texts. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 5 June 2026 (UTC) == Ratification of the deletion policy proposal? == I haven't seen any unresolved objections to my proposal for a [[Abstract Wikipedia:Deletion policy|policy for deletion]]. Does anybody have any issues, and, if not, is it ok to ratify as an actual policy? I intend to remove the draft template and replace it with a policy template unless anyone voices any objection within a week. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:55, 29 May 2026 (UTC) :Is it just me or does [[Abstract Wikipedia:Deletion policy#Reasons for deletion]] render blank with only number bullets without the actual text after ''1.'' or ''2.''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 07:13, 30 May 2026 (UTC) ::I see text. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 07:49, 30 May 2026 (UTC) :::I can see on my phone, but it goes blank on my laptop. What is the role of ''<nowiki><span class="anchor" id="1"></nowiki>''? [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 12:15, 30 May 2026 (UTC) ::::{{ping|Bunnypranav}} I can see the text everywhere (I tested connected and not connected, on my phone, laptop, with Chrome or Firefox ; what system do you use?). As the name suggest, the span anchor is here to create an HTML anchor, so you can do link like [[Abstract_Wikipedia:Deletion_policy#7]]. Cheers, [[User:VIGNERON|VIGNERON]] ([[User talk:VIGNERON|talk]]) 13:49, 30 May 2026 (UTC) :::::I'm on Brave browser. Nevertheless, forget it. The culprit might be some random customization I did to my system which I cannot recollect. The reason is the span tag only though, tried a preview kicking out a text to just outside the tag and it worked. [[User:Bunnypranav|Bunnypranav]] ([[User talk:Bunnypranav|talk]]) 14:23, 30 May 2026 (UTC) :Globally, it looks fine. I think that reasons 7 and 8 may need some examples/clarifications. There is no global consensus when it comes to creating categories. For example, categories for building interiors and exteriors. Personally, I feel that they are useful for easier discoverability. [[User:Jsamwrites|John Samuel]] ([[User:Jsamwrites|talk]]) 15:39, 30 May 2026 (UTC) ::I've copied them over from enwiki. They're probably included in "content otherwise not suited for an encyclopedia." Since sysops can't speedy them, it'd be up to commenters on [[Abstract:RFD]] to determine. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:48, 30 May 2026 (UTC) : Done! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:33, 5 June 2026 (UTC) od2vmlo9vkce12inty44my9qwuj1y4e 10 4309 14643 14351 2026-08-13T15:41:45Z FuzzyBot 563 Updating to match new version of source page 14643 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> ;지원자 코너 * 다음 지원자 코너는 <bdi lang="en" dir="ltr">[https://zonestamp.toolforge.org/1788802200 17:30 UTC on 2026-09-07]</bdi>에 <bdi lang="en" dir="ltr">Google Meet</bdi>(<bdi lang="en" dir="ltr">[https://meet.google.com/xuy-njxh-rkw meet.google.com/xuy-njxh-rkw]</bdi>)에서 진행됩니다. * [[:c:File:Abstract Wikipedia Volunteer Corner 2026-07.webm|가장 최근의 지원자 코너 내용]]은 공용에서 확인하실 수 있습니다. ; 위키함수의 현황 업데이트 <!--Keep this to the most recent 5 entries--> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-13|2026-08-13]]: Shoutout to 99of9!</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-08-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstract Wikipedia at Wikimania</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Beyond syntactic tables</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-08|2026-07-08]]: Moving toward our first Abstract Wikipedia integration milestone</span> </div> <span class="plainlinks">[[:f:Special:MyLanguage/Wikifunctions:Status updates|<span class="mw-ui-button mw-ui-constructive mw-ui-small">더 많은 소식</span>]]</span> </div><noinclude>[[Category:templates]]</noinclude> 1sp5xjgz080rau4d726ecivem7n0y1h 0 4459 14649 13856 2026-08-13T16:38:04Z VIGNERON 163 + infobox 14649 abstractwiki text/plain { "qid": "Q123471046", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37827", "Z37827K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37827K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M139106997" }, "Z36038K2": { "Z1K1": "Z7", "Z7K1": "Z36270", "Z36270K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36270K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q34740" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q21358789" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q98961713" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37065", "Z37065K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37065K2": { "Z1K1": "Z6091", "Z6091K1": "Q19269277" }, "Z37065K3": { "Z1K1": "Z6091", "Z6091K1": "Q34740" }, "Z37065K4": { "Z1K1": "Z6091", "Z6091K1": "Q134311" }, "Z37065K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q19269277" }, { "Z1K1": "Z6091", "Z6091K1": "Q34740" }, { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q8269924" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P138" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q588574" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q2531956" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q148" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q588574" }, { "Z1K1": "Z6091", "Z6091K1": "Q2531956" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P171" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36835", "Z36835K1": { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q124005986" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P171" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36835K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36835K3": { "Z1K1": "Z40", "Z40K1": "Z41" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q7205" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2348" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q514" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2043" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q34740" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q134311" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q34740" }, { "Z1K1": "Z6091", "Z6091K1": "Q134311" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } tmbqlxh9dxp9a9z7mf5vu5mvaj0h0xv 0 4504 14626 12422 2026-08-13T12:36:31Z VIGNERON 163 no need to select "big cat" here, is there? 14626 abstractwiki text/plain { "qid": "Q140", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M4782819" }, "Z36038K2": { "Z1K1": "Z7", "Z7K1": "Z23753", "Z23753K1": { "Z1K1": "Z6091", "Z6091K1": "Q41363" }, "Z23753K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z37827", "Z37827K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37827K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32123", "Z32123K1": { "Z1K1": "Z7", "Z7K1": "Z37921", "Z37921K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37921K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } f0r3zf7tx7hkr07en6dahv1ykaxyvlu 0 4517 14610 12241 2026-08-13T12:07:41Z Jsamwrites 874 14610 abstractwiki text/plain { "qid": "Q604945", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39238", "Z39238K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39238K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39238K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39238K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } raxtkqv6lnuouk0fvmr2cfgyh97xjh9 14611 14610 2026-08-13T12:08:27Z Jsamwrites 874 14611 abstractwiki text/plain { "qid": "Q604945", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M79882243" }, "Z36038K2": "Logo of Krita" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39238", "Z39238K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39238K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39238K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39238K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } soub2gqdt5vdwv2dz0u63fggv55w0ni 14612 14611 2026-08-13T12:10:26Z Jsamwrites 874 14612 abstractwiki text/plain { "qid": "Q604945", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M79882243" }, "Z36038K2": "Logo of Krita" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39238", "Z39238K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39238K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39238K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39238K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39253", "Z39253K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39253K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39253K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } kv8140izqlegyrvcsnd6gacv3y9sea2 14614 14612 2026-08-13T12:13:59Z Jsamwrites 874 14614 abstractwiki text/plain { "qid": "Q604945", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M79882243" }, "Z36038K2": "Logo of Krita" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39238", "Z39238K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39238K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39238K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39238K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39253", "Z39253K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39253K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39253K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q138861968" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37840", "Z37840K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q1225029" }, { "Z1K1": "Z6091", "Z6091K1": "Q26262563" }, { "Z1K1": "Z6091", "Z6091K1": "Q1431" } ], "Z37840K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 1mhi9ec61qjehsj2xwzfxku88atgg99 14615 14614 2026-08-13T12:15:11Z Jsamwrites 874 14615 abstractwiki text/plain { "qid": "Q604945", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M79882243" }, "Z36038K2": "Logo of Krita" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39238", "Z39238K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39238K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39238K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39238K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39253", "Z39253K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39253K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39253K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34637", "Z34637K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34637K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q138861968" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37840", "Z37840K1": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q1225029" }, { "Z1K1": "Z6091", "Z6091K1": "Q26262563" }, { "Z1K1": "Z6091", "Z6091K1": "Q1431" } ], "Z37840K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 5slpvuibtvlwxk2hwzvn5c6znelruok 0 4521 14619 14457 2026-08-13T12:20:27Z Jsamwrites 874 14619 abstractwiki text/plain { "qid": "Q1431", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M488621" }, "Z36038K2": "Logo of KDE" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39181", "Z39181K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39181K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z39181K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } nr2ck9r1vj39l6n6yuq3blredtrpgvu 0 4522 14621 12447 2026-08-13T12:22:25Z Jsamwrites 874 14621 abstractwiki text/plain { "qid": "Q44316", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M907416" }, "Z36038K2": "Logo of GNOME" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37951", "Z37951K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37951K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z37951K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } nh1p7glg1oc3mpjjezvtrr3ectqwyua 14625 14621 2026-08-13T12:27:19Z Jsamwrites 874 14625 abstractwiki text/plain { "qid": "Q44316", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M907416" }, "Z36038K2": "Logo of GNOME" }, { "Z1K1": "Z7", "Z7K1": "Z35976", "Z35976K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35976K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34282", "Z34282K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z34282K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37286", "Z37286K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37286K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q7562091" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37873", "Z37873K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37873K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37951", "Z37951K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37951K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z37951K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 03x8dnppttp2v4ws2hha7jy4059gw3l 0 5031 14613 13820 2026-08-13T12:12:34Z Feedmepaperr 1398 added professions 14613 abstractwiki text/plain { "qid": "Q137785666", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36038", "Z36038K1": { "Z1K1": "Z310", "Z310K1": "M181850035" }, "Z36038K2": { "Z1K1": "Z7", "Z7K1": "Z36270", "Z36270K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36270K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z35370", "Z35370K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35370K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27849", "Z27849K1": { "Z1K1": "Z7", "Z7K1": "Z37683", "Z37683K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37683K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z27849K2": { "Z1K1": "Z7", "Z7K1": "Z38542", "Z38542K1": "https://www.nps.gov/articles/000/lucinda-j-davis.htm", "Z38542K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38542K3": { "Z1K1": "Z6091", "Z6091K1": "Q308439" }, "Z38542K4": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "2026" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16107" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "30" } } }, "Z38542K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z38833", "Z38833K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38833K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z38833K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z38833K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } 5lqn05l0f8nsq08lakldr3fwig10yr4 0 5032 14618 13785 2026-08-13T12:19:53Z Feedmepaperr 1398 named after-sentence 14618 abstractwiki text/plain { "qid": "Q42735", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150336056" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q2620186" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1082" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } l5o47q5axjntsbouslogxbogl95r7je 0 5033 14620 14598 2026-08-13T12:21:26Z Feedmepaperr 1398 named after-sentence 14620 abstractwiki text/plain { "qid": "Q5083", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M131840683" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q51929311" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q62049" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q108861" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z38542", "Z38542K1": "https://esd.wa.gov/jobs-and-training/labor-market-information/reports-and-research/labor-market-county-profiles/king-county-profile", "Z38542K2": { "Z1K1": "Z6091", "Z6091K1": "Q108861" }, "Z38542K3": { "Z1K1": "Z6091", "Z6091K1": "Q96414304" }, "Z38542K4": { "Z1K1": "Z18", "Z18K1": "Z825K3" }, "Z38542K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1082" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "18" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "15" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q1907114" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q30" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q30" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2046" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 5cfplj34gjzlw1rlub50c12jih0gxhx 2 5218 14652 14584 2026-08-13T21:23:34Z EatingCarBatteries 1378 14652 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. '''Supported languages:''' {{#function:Z38334|Z26043|en}} === X is a(n) Y Z === Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] '''Supported languages:''' {{#function:Z38334|Z29597|en}} === A(n) X is a(n) [kind of] Y === [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. '''Supported languages:''' {{#function:Z38334|Z26096|en}} === Xs are Ys === [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] '''Supported languages:''' {{#function:Z38334|Z27126|en}} === A(n) X is a(n) Y Z === Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] '''Supported languages:''' {{#function:Z38334|Z29813|en}} === X is the Y of Z === [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. '''Supported languages:''' {{#function:Z38334|Z26043|en}} === X is the Y-est Z in W === [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] '''Supported languages:''' {{#function:Z38334|Z29841|en}} === X is a Y in Z === [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. '''Supported languages:''' {{#function:Z38334|Z36983|en}} === Xs are Ys of Z === [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. '''Supported languages:''' {{#function:Z38334|Z32255|en}} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} '''Supported languages:''' {{#function:Z38334|Z37923|en}} ===Years=== [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] '''Supported languages:''' {{#function:Z38334|Z20896|de}} [[Category:Abstract Wikipedia administration|Useful Functions]] bcga7im0god1lfj8seuduj8cv52dbd7 14653 14652 2026-08-13T21:28:57Z EatingCarBatteries 1378 /* Common sentence templates */ thanks claude 14653 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} '''Supported languages:''' {{#function:Z38334|Z37923|en}} ===Years=== [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] '''Supported languages:''' {{#function:Z38334|Z20896|de}} [[Category:Abstract Wikipedia administration|Useful Functions]] 7tfaikujkksuhhctgpzgbt7x5sdzre4 14654 14653 2026-08-13T21:34:30Z EatingCarBatteries 1378 /* Species */ 14654 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z37923|en}} |} ===Years=== [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] '''Supported languages:''' {{#function:Z38334|Z20896|de}} [[Category:Abstract Wikipedia administration|Useful Functions]] 96i1rsdx4udhpilo4v2k5exxbv8np3g 14655 14654 2026-08-13T21:35:24Z EatingCarBatteries 1378 /* Years */ 14655 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z37923|en}} |} ===Years=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z20896|de}} |} [[Category:Abstract Wikipedia administration|Useful Functions]] 950h9tsvtdwhk7ibg6q8uhggemxizou 14656 14655 2026-08-13T21:35:35Z EatingCarBatteries 1378 /* Years */ 14656 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z37923|en}} |} ===Years=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z20896|en}} |} [[Category:Abstract Wikipedia administration|Useful Functions]] 12eywy8xagtkdau69erv4kycepvb4b8 14657 14656 2026-08-13T21:38:30Z EatingCarBatteries 1378 redoing functions 14657 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 14658 14657 2026-08-13T21:38:36Z EatingCarBatteries 1378 14658 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z37923|en}} |} ===Years=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z20896|en}} |} [[Category:Abstract Wikipedia administration|Useful Functions]] 12eywy8xagtkdau69erv4kycepvb4b8 14659 14658 2026-08-13T21:38:50Z EatingCarBatteries 1378 /* Years */ 14659 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z37923|en}} |} ===Years=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' |} [[Category:Abstract Wikipedia administration|Useful Functions]] aa0duaje6us8kqzml29dbh3k00rs7uf 14660 14659 2026-08-13T21:38:56Z EatingCarBatteries 1378 /* Years */ 14660 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z37923|en}} |} ===Years=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z20896|en}} |} [[Category:Abstract Wikipedia administration|Useful Functions]] 12eywy8xagtkdau69erv4kycepvb4b8 14661 14660 2026-08-13T21:39:49Z EatingCarBatteries 1378 /* Years */ 14661 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z37923|en}} |} ===Years=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' |} [[Category:Abstract Wikipedia administration|Useful Functions]] aa0duaje6us8kqzml29dbh3k00rs7uf 14662 14661 2026-08-13T21:39:54Z EatingCarBatteries 1378 /* Years */ 14662 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Common sentence templates == ::''It is important to pay attention to the output type of a function. If a function does not output an HTML fragment, you may have to use a helper function to convert it to be so. An example of one of these would be [[f:Z29749]].'' === X is a(n) [instance of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z32962|subject is instance of <small>(Z26039)</small>]] creates a sentence in the form {{xt|"X is a(n) [instance of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [instance of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what the entity is being described as. Note that, in some languages, this function converts the first letter of the subject's name to uppercase, which may not always be appropriate. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z37068|describing entity with adjective / class <small>(Z29591)</small>]] creates a sentence in the form {{xt|"X is a(n) Y Z."}} — or abstractly, <code>{{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q925}} : {{color|blue|Adjective}}: {{Q|Q11435}} : {{color|darkorange|Class}}: {{Q|Q11344}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Mercury is a liquid chemical element."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29597|en}} |} === A(n) X is a(n) [kind of] Y === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32965]] creates a sentence in the form {{xt|"A(n) X is a(n) [kind of] Y."}} — or abstractly, <code>{{color|red|entity}} is a(n) [kind of] {{color|blue|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q89}} : {{color|blue|Class}}: {{Q|Q3314483}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"An apple is a fruit."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what it is being described as. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26096|en}} |} === Xs are Ys === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z26627]] creates a sentence in the form {{xt|"Xs are Ys."}} — or abstractly, <code>{{color|red|entities}} are {{color|blue|classes}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q25894}} : {{color|blue|Class}}: {{Q|Q110551885}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Antelopes are mammals."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z27126|en}} |} === A(n) X is a(n) Y Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | Function [[f:Z29743|description of class with adjective and superclass <small>(Z29743)</small>]] creates a sentence in the form {{xt|"A(n) X is a(n) Y Z."}} — or abstractly, <code>A(n) {{color|red|entity}} is a(n) {{color|blue|adjective}} {{color|darkorange|class}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q15783}} : {{color|blue|Adjective}}: {{Q|Q16042592}} : {{color|darkorange|Class}}: {{Q|Q106839123}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"A skateboard is a small means of transport."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29813|en}} |} === X is the Y of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37011]] creates a sentence in the form {{xt|"X is the Y of Z."}} — or abstractly, <code>{{color|red|subject}} is the {{color|blue|role}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q3870}} : {{color|blue|Role}}: {{Q|Q5119}} : {{color|darkorange|Dependency}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is the capital city of Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z26043|en}} |} === X is the Y-est Z in W === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z27243]] creates a sentence in the form {{xt|"X is the Y-est Z in W."}} — or abstractly, <code>{{color|red|entity}} is the {{color|blue|adjectivest}} {{color|darkorange|class}} in {{color|purple|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q5413}} : {{color|blue|Adjective}}: {{Q|Q36253}} : {{color|darkorange|Class}}: {{Q|Q4022}} : {{color|purple|Location}}: {{Q|Q48}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Yangtze is the longest river in Asia."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z29841|en}} |} === X is a Y in Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z36983]] creates a sentence in the form {{xt|"X is a Y in Z."}} — or abstractly, <code>{{color|red|entity}} is a {{color|blue|class}} in {{color|darkorange|location}}</code>. ; Example : {{color|red|Entity}}: {{Q|Q3870}} : {{color|blue|Class}}: {{Q|Q515}} : {{color|darkorange|Location}}: {{Q|Q114}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Nairobi is a city in Kenya."}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML <small>(Z89)</small>]] The '''entity''' field should be the subject (typically, but not always, your abstract article's subject). The '''class''' field should be what is being described as. The '''location''' field should say where it is located. It should only be used for physical locations. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z36983|en}} |} === Xs are Ys of Z === {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z32326]] creates a sentence in the form {{xt|"Xs are Ys of Z."}} — or abstractly, <code>{{color|red|subjects}} are {{color|blue|roles}} of {{color|darkorange|dependency}}</code>. ; Example : {{color|red|Subject}}: {{Q|Q523}} : {{color|blue|Role}}: {{Q|Q31464082}} : {{color|darkorange|Dependency}}: {{Q|Q9128}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"Stars are sources of light."}} : {{color|mediumvioletred|Type}}: [[f:Z11|Monolingual text <small>(Z11)</small>]] The '''subject''' field should be the subject (typically, but not always, your abstract article's subject). The '''role''' field should be which role it serves to the dependency. The '''dependency''' field should be what is related to the subject. | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z32255|en}} |} == Utilities == === Sentence-case section title from Wikidata label === [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. ; Example : {{color|red|Entity}}: {{Q|Q309}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>History</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] [[f:Z32839]] is a plural version of [[f:Z32145]]. ; Example : {{color|red|Entity}}: {{Q|Q121769}} : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki><h2>References</h2></nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] === Join text-like objects into HTML fragments === [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. ===Main articles=== [[f:Z36083]] creates an HTML hatnote pointing the reader to a main article given the article and a language. === Monolingual text as HTML fragment w/ auto-langcode === [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. ===Wikilinks=== [[f:Z32428]] creates an Abstract wikilink (hyperlink) to a given article given the article an a language. To make the label appear different than the link's article name, use [[f:Z36489]]. ===Sentence separators=== [[f:Z35672]] adds an HTML sentence separator between fragments. This function exists because not every language uses a space character - for example, a "space" in Chinese and Japanese should be blank strings. ===Images=== [[f:Z36038]] embeds an image onto the page given a Commons image and an (optional) string alternative text. To make the alt text be the label of a Wikidata item, use [[f:Z38053]] ==Introductory paragraphs == ===Species=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z37922]] creates an introductory paragraph for species articles, including information about the family, conservation, and describing authority. ; Example : {{color|red|Species}}: Canis lupus : {{color|darkorange|Hypernym}}: big cat : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|Panthera leo, also known as the Lion, is a species of big cat in the family Felidae. The species was described in 1758 by Carl Linnaeus. Panthera leo has been assessed as Vulnerable by the International Union for Conservation of Nature (IUCN).}} <br />(''HTML formatting has been removed due to length - for a full example, see [[Q18498]]'') : {{color|mediumvioletred|Type}}: [[f:Z89|HTML fragment <small>(Z89)</small>]] If you do not want to manually add hypernym (describing phrase) to the paragraph, you can use [[f:Z37921]], which will make the word the order of the species. : Result: {{xt|Panthera leo, also known as the Lion, is a species of <mark>Carnivora</mark> in the family Felidae. ...}} | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z37923|en}} |} ===Years=== {| class="wikitable" |- | style="width:70%; vertical-align:top;" | [[f:Z20898]] creates a string paragraph providing basic information about the given year, given a Gregorian year ({{Q|Q39628023}}) and a language. ; Example : {{color|red|Year}}: 2000 : {{color|dimgray|Language}}: English : <hr/> : Result: {{xt|"<nowiki>2000 (MM) was a leap year starting on Saturday of the Gregorian calendar, the 2000th year of the Common Era (CE) and Anno Domini (AD) designations, the 1000th year of the 2nd millennium, the 100th year of the 20th century, and the 1st year of the 2000s decade.</nowiki>"}} : {{color|mediumvioletred|Type}}: [[f:Z6|String <small>(Z6)</small>]] | style="width:30%; vertical-align:top;" | '''Supported languages:''' {{#function:Z38334|Z20896|en}} |} [[Category:Abstract Wikipedia administration|Useful Functions]] 12eywy8xagtkdau69erv4kycepvb4b8 0 5220 14622 14601 2026-08-13T12:22:35Z Feedmepaperr 1398 named after-sentence 14622 abstractwiki text/plain { "qid": "Q430267", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M37611512" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M50468956" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q131553820" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q62049" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q156623" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P571" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1082" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "13" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37464", "Z37464K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q2879598" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37464K2": { "Z1K1": "Z6", "Z6K1": "Z37273" }, "Z37464K3": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q2879598" } ], "Z37464K4": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q2879598" } ], "Z37464K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } rsxt0g4twrtf9bjzjg63k7yrsffb2yz 0 5221 14607 2026-08-13T12:00:58Z Feedmepaperr 1398 Abstract Wikipedia's 2000th article! Includes image and some basic facts. 14607 abstractwiki text/plain { "qid": "Q594387", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M149624201" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q169358" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2044" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "3" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q208826" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q8502" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q1223" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "5" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q208826" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q8502" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q4558" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, { "Z1K1": "Z6091", "Z6091K1": "Q8502" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2660" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P138" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } j17ptt6bfoteu5f5uh0t3kopji4xlb9 14623 14607 2026-08-13T12:23:47Z Feedmepaperr 1398 named after-sentence 14623 abstractwiki text/plain { "qid": "Q594387", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M149624201" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q169358" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39194", "Z39194K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39194K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39194K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z39194K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2044" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "3" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q208826" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q8502" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q1223" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "5" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q208826" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q8502" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q4558" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q1223" }, { "Z1K1": "Z6091", "Z6091K1": "Q8502" } ] }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P2660" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } h09mmdr9yi968cgahuqgpzcx7m8nkw2 0 5222 14627 2026-08-13T13:36:54Z Podroužek 6903 new 14627 abstractwiki text/plain { "qid": "Q1025213", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q15978299" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } f3wyf40nfac4wxchzd6llv13nu31mjp 0 5223 14628 2026-08-13T13:39:43Z Podroužek 6903 new 14628 abstractwiki text/plain { "qid": "Q8385", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q15978299" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } mmtvo2ha4rzof1sb24034r9f3gpxtl6 0 5224 14630 2026-08-13T14:16:54Z NanoCopter 7160 Created the article with the game's genre, developer, platforms, and an infobox 14630 abstractwiki text/plain { "qid": "Q753749", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37403", "Z37403K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37403K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q1422746" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39253", "Z39253K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39253K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39253K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39232", "Z39232K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39232K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39232K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39232K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } ppb23nugz48j7ii9yebo6wanyalpe6l 0 5225 14631 2026-08-13T14:20:37Z Arlo Barnes 953 infobox 14631 abstractwiki text/plain { "qid": "Q1635788", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37922", "Z37922K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37922K2": { "Z1K1": "Z6091", "Z6091K1": "Q10884" }, "Z37922K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 6grjmybn2ehpbdvywcsfstzgtnhugbr 1198 5226 14636 2026-08-13T15:41:44Z FuzzyBot 563 Importing a new version from external source 14636 wikitext text/x-wiki [[$1|2026-08-13]]: Shoutout to 99of9! h9xn33cpxhily3wuobf8fbykw68m86n 1198 5227 14637 2026-08-13T15:41:44Z FuzzyBot 563 Importing a new version from external source 14637 wikitext text/x-wiki [[$1|2026-08-05]]: Congratulations Jules*: An apple is a fruit qfnc1k6ddi7ptra9lpngcd4r22um90b 0 5228 14648 2026-08-13T16:00:07Z NanoCopter 7160 new article 14648 abstractwiki text/plain { "qid": "Q107105860", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z35993", "Z35993K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35993K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q471839" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 0dh30t0ryhd4jpwtb7tv4e2rmj7k4py 3 5229 14650 2026-08-13T21:17:54Z HenkvD 1447 /* Welcome */ new section 14650 wikitext text/x-wiki == Welcome == {{Welcome}} Thanks for your contributions so far. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:17, 13 August 2026 (UTC) t4oyupuoz54r7odhjy54tfj6gbn9d6o 3 5230 14651 2026-08-13T21:19:38Z HenkvD 1447 /* Welcome */ new section 14651 wikitext text/x-wiki == Welcome == {{Welcome}} Thanks for your contributions so far. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 21:19, 13 August 2026 (UTC) dvyrhhvkfqubciz73mkip63z8p6x4y0 0 5231 14670 2026-08-14T00:28:24Z Omar M. Ghaly 6856 Created an article for Egypt 14670 abstractwiki text/plain { "qid": "Q79", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M2258048" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q15" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } } ] } } } 85tbw6unc2gsaff1uqyws328s3rxcd8 14671 14670 2026-08-14T00:56:58Z Omar M. Ghaly 6856 changed the infobox to make it for country instead of the generic "populated place" 14671 abstractwiki text/plain { "qid": "Q79", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M2258048" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38956", "Z38956K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38956K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q15" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } } ] } } } 907l64y7wrnq87e0l36d8kw2zu6pc7n 14672 14671 2026-08-14T02:06:55Z EatingCarBatteries 1378 14672 abstractwiki text/plain { "qid": "Q79", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M2258048" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38956", "Z38956K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38956K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q27381" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39191", "Z39191K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39191K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39191K3": { "Z1K1": "Z6091", "Z6091K1": "Q192613" }, "Z39191K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q85" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] } ] } } } tkv2wxlmrsh2by31de57fbaz4984u8e 0 5232 14674 2026-08-14T03:12:50Z Omar M. Ghaly 6856 Created the article for Palestine 14674 abstractwiki text/plain { "qid": "Q219060", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M31429077" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38956", "Z38956K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38956K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q27293" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39191", "Z39191K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39191K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39191K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39191K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q212938" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] } ] } } } 8vj5ckfcw3g39396oa1ubkiw01fqdsz 0 5233 14675 2026-08-14T04:41:48Z Omar M. Ghaly 6856 Start of the article 14675 abstractwiki text/plain { "qid": "Q6256", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z32965", "Z32965K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32965K2": { "Z1K1": "Z6091", "Z6091K1": "Q16562419" }, "Z32965K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } } ] } } } nq7zympltrmai0o2c4d7vd0m1lv8j1v 0 5234 14676 2026-08-14T05:34:30Z Omar M. Ghaly 6856 Creation of the article 14676 abstractwiki text/plain { "qid": "Q1016", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M58477111" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38956", "Z38956K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38956K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q27381" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39191", "Z39191K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39191K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z39191K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z39191K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q3579" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] } ] } } } 2tgebi02qy7qnbl4vltzpg6jfn4s9ex 4 5235 14692 2026-08-14T06:56:02Z Theki 2698 Created page with "{{archive subpage|link=Abstract Wikipedia:Project chat}} == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activitie..." 14692 wikitext text/x-wiki {{archive subpage|link=Abstract Wikipedia:Project chat}} == Wikifunctions & Abstract Wikipedia Newsletter #250 is out: Looking back and forward == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-30|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present you a recollection of our work so far, now that we celebrate our 250th newsletter, we share with you a summary of our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:04, 1 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Yet another suggested function proposal == Perhaps it's a bit early, but can [[f:Z36049]] be added to [[MediaWiki:AbstractWikiSuggestedWikifunctions.json]]? See [[Q38726]] for an example use. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:54, 4 June 2026 (UTC) : Meh. Consider this withdrawn until we know more about what we want image creation to look like. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 05:06, 5 June 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #251 is out: The illustrated encyclopaedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-06-05|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce our first function to import images on Abstract Wikipedia, we present our Functions of the Week, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1780939800 June 8, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:14, 5 June 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30606821 --> == Questions on a simple fragment example "The Eiffel Tower is a monument" == Moved from [[f:Wikifunctions:Project chat]] Hello. I would like to be able to use the function [[f:Z26039]] to generate sentences like "the Eiffel Tower is a monument" or "la torre Eiffel es un monumento" in Spanish. It already raises a lot of questions. Question 1: I should be able to set the first input "entity" to {{Q|Q243}} and the second input "class" to {{Q|Q4989906}} and get the correct sentence, shouldn't I? Just checking. Question 2: [[f:Z26039]] calls a language-specific function like "Spanish article-less instantiating sentence" [[f:Z26337]], which uses the label of the Wikidata item to get the text for "Eiffel Tower", which is similar to the lemma of the lexeme. But this would not be acceptable in production, would it? The item label "belongs" to all Wikidata users, not to Abstract Wikipedia users, and there is no guarantee what it might contain, such as a parenthesis for disambiguation. Or am I wrong? Question 3a: We need to have a lexeme for the combination "Eiffel Tower" in each language, don't we? For instance in languages with gender, the lexeme is the only place to find the gender. It is true that if we know that the equivalent of "Tower" is the head word, syntactical information can be found under the lexeme for "tower", and it would be good to use a system like that. But the only place that the syntactic dependency information could be located is under the lexeme. Question 3b: At present for [[f:Z26039]] etc. to work, we have to add any forms or syntax information to the lexeme of the whole phrase, such as "Eiffel Tower". But property {{Q|P5238}} with attributes {{Q|P9763}} and {{Q|P9764}} can be used to define the structure and avoid duplicating the syntax information. What lexeme would be used for "Eiffel" in this case? Would it be the same as a lexeme for {{Q|Q20882}}? That makes no sense to me. I propose that there should be a dummy lexeme in each language which could be added to {{Q|P5238}} instead of a real lexeme to mean "invariant element". Question 4: As has already been pointed out elsewhere, the fragment functions do not work well with the initial definite article in languages like English, Spanish and German. Examples: * "'''The Eiffel Tower is a monument.'''" The item label "Eiffel Tower" omits the article and so the result omits the initial "The" in English. French, Spanish and German are similar. * "'''The Sun is a star.'''" Similarly the article is wrongly omitted, also in French, Spanish and German. * "'''Westminster Abbey is a monument.'''" This is OK in English and German as no article is needed, but not in French or Spanish where it is, for instance "La Abadía de Westminster es un monumento". * "'''Latin is a dead language.'''" Also this is OK in English and German but not in French or Spanish, where an article is needed. * "'''Jupiter is a planet.'''". This does not need an article and is OK in all the languages; I include this to show that you cannot assume that there is an article in all cases in French and Spanish. How should the language functions find out whether an article is needed? In some cases, where the lemma is a phrase like "Abadía de Westminster" in Spanish, I think that it could be deduced, but in general there is no rule to give the answer. Using different rendering functions according to the case is '''not''' a solution, although it might work for a few specific languages like these four. It would not be acceptable because there will be many, many other cases of syntactical choices to be made for all the different languages, and we cannot expect the person writing the abstract code to take them all into account. So I suppose that a declaration in the lexeme is needed to solve this problem. I suppose that there must already be linguistic terminology for this problem, but I don't know it. I would be grateful for any comments on any of these questions. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:02, 5 June 2026 (UTC) :@[[User:Strobilomyces|Strobilomyces]] I will try to answer a few of your questions, although I am not linguist. ::@[[User:HenkvD|HenkvD]] Thanks for your answer. I will add my comments in your answers below. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :1. Yes I agree the correct inputs for "entity" is {{Q|243}} and the second input "class" is {{Q|4989906}}. :2. In case no lexeme information is needed (for gender or so) the Wikidata label of {{Q|243}} should be OK. Labels in Wikidata don't contain parentheses for disambiguation. For instance there are many cities called Amsterdam like {{Q|478456}}. {{Q|959016}} and {{Q|727}} :: Well I sometimes add disambiguation parentheses in the case of taxonomic items, for instance I use the label "Sphaerodes (fungus)" because the genus name ''Sphaerodes'' is both a fungus and an insect. As far as I know, it is allowed to add a parenthesis like this to the label. When selecting the item this is not needed, since the description is also visible, but when looking at the genus name on the page, one would not be able to tell whether the link goes to the fungus or the insect, and sometimes such links get muddled up. If there should be a rule that the label must be the same as the lemma text, then I think that needs to be agreed and publicized. :3a. In case gender is needed, for example for gender for La Abadía de Westminster I think we need lexemes :: Yes, so it seems to me that this means that for languages like French and German, every single item needs a lexeme. On the other hand, in a separate conversation it was suggested to me that genders might be established programmatically, and the lexeme would only be needed in exceptional cases. This seems to require an architecture which is different from what I was expecting, and certainly not available at present for the fragment examples (surely the logic will be too complicated for composition code alone). Even in English, many items may need to be used in the plural; the rendering function will need to find the plural of the given item. It can execute a heuristic function (add "s", change "y" to "ies", etc.), and a lexeme is only needed if the label word is "irregular". But note that it has to query the lexeme every single time to see if one exists, in which case it must take precedence. :3b. I don't know what you mean, so I can't answer that. ::It is a detailed question about how to fill in the attributes of {{Q|P5238}}. :4. You are right some examples like Sun is a star" are incorrect and need an article for some languages/some lemmma. I don't know if there is a linguistic terminology or Lexeme property that would indicate it needs an initial definite article. :::Yes. In fact, the strange thing for me is rather that in encyclopedia entries, the article is omitted in the article heading. For instance, in the examples above if the English labels were given as "The Eiffel Tower" and "The Sun", and similarly in the other languages, the fragment examples would work and where would be the problem? In paper encyclopedias, this would mean that many entries would come together under "The". Anyway, I don't think this can be changed and so a property is needed. I would have thought that the property would have to be on a lexeme object. :: On {{Q|727}} in English the noun Netherlands has an additional "the" in English. This is added by [[f:Z32645]] item indicates definite article, English. Functions should be created for each language, and added to the appropriate sentences. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:58, 9 June 2026 (UTC) :::Oh, Z32645 is interesting. The two implementations are very different, aren't they? The function doesn't work for "Eiffel Tower", but the first implementation could do if "the Eiffel Tower" were an alias. That could be instead of the lexeme property(?) But if we are imposing conventions like that, I suppose we need to talk to other Wikidata users. :Even for western languages there are a lot of different rules; What about the many other languages in the world. All this makes it a real challenge. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 22:04, 8 June 2026 (UTC) ::Yes, I think it is an extreme challenge, especially withou being able to call external functions in Python etc. Surely this is too complicated for composition? Thanks again for your answers. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:42, 9 June 2026 (UTC) :::This was discussed at [[:commons:File:Abstract_Wikipedia_Volunteer_Corner_2026-06.webm|Monday’s volunteers’ corner meeting (8 June 2026)]]. It was also discussed to find a place where to discuss this in detail. Please mention that place here if that place is known. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:26, 13 June 2026 (UTC) ::::See also [[f:Wikifunctions:Status updates/2026-06-19#The or not the, this is (the?) question]]. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:39, 19 June 2026 (UTC) :::::@[[User:HenkvD|HenkvD]] Thanks for the links which you have just made here and also thanks to whoever is involved in covering the question in the status update. I don't think that the status update talk page is used for such comments, is it? Until there is another suggestion, I don't know a better place to discuss than here, and so I will carry on here. :::::I am guilty of not getting around to commenting on the status update discussion - there is always more that I want to say before publishing. Now I will try to keep my edits small. :::::My view was that a lexeme would be necessary almost for every item in every language, but in the meeting it was argued that often syntactic information could be found through programmatic "rules of thumb", and that in that way, lexemes would be needed only in cases of irregularity. Note that it is still necessary to search for the lexeme properties in every case; the programmatic rules would only apply if the lexeme property is missing. :::::My main comment now is that a programmatic approach is too complicated for doing everything by composition and so we urgently need to be able to call functions from Python/Javascript. I hope that that will come soon. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:28, 19 June 2026 (UTC) :At the volunteers' meeting it was even suggested that grammatical genders could be determined programmatically sometimes. For instance in Spanish most rivers are masculine and in French trees are generally masculine. This type of rule depends on having a rigorous system to determine the type of item. Example: I believe that an oak tree is {{Q|Q12004}}. For some reason the label for English is "Quercus" (whereas other languages use the common name) - this highlights a problem with using item labels. Q12004 has subclass {{Q|Q148993}}, which has subclass {{Q|Q10884}}, so it is possible to determine that it is a tree, but surely this is too complicated to be worthwhile. Perhaps there are languages where the type of item gives a sort of gender, but I think they would need a property "linguistic item type" rather than trying to maintain the information in the existing item properties. :Sometimes the form of the word indicates the gender, for instance in Spanish words ending in -a are often feminine. But there are many exceptions (el optimista, el tema), for which lexemes would be needed, I suppose. If there are very few exceptions, they could be listed explicitly. :In the case of French, Spanish and German genders, I think that the simplicity of just putting the gender on the lexeme outweighs the possible savings in quantity of data through using "rules of thumb". [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 15:54, 19 June 2026 (UTC) ::As mentioned in the Status Update, it is difficult to decide how to determine whether an item needs a definite article in the simple examples. ::I have a comment: it is strange that we want to leave out the article in the label and the lemma. In normal use, I think the article is only left out in "headline-speak" (for instance "Man falls from Eiffel Tower") or if you are talking to the thing ("Eiffel Tower, I love you"). I don't know where else we want to omit the article in actual text. ::So one proposal for a solution is that the lemma on the lexeme should include the article in these cases. It should be defined as the string which should be the value of ''x'' in the sentence: "''x'' is a thing". That might solve the problem, but we would always need to have a lexeme in these cases and it would be necessary to explain this to all lexeme users. A second proposal is to have a new property on the lexeme which gives the string which we need (or to have an indicator that an article is required, but that would be more complicated as code would be needed to render the article). ::Another possibility, supported in the meeting, would be somehow to work out from the construction of the name whether an article is needed. For instance if the name is constructed as a phrase, it often wants an article ("the Bridge of Sighs", "the Isle of Man"). In English a phrase with "of" is a good indication that the article is needed. Phrases of the form <qualifier> <noun> often want an article (for instance "Eiffel tower", "Irish Sea", "United States"), but they often don't (for example "Beachy Head", "Lake Ontario", "London Bridge", "Westminster Cathedral", "Fair Isle", "Land's End"). So that is no use if we don't know what type of qualifier and noun it is. ::There are rules for specific types of item (for instance in English, I think lakes don't need an article and seas do need an article). If we are going to use rules like that, it will be necessary to maintain the correct categorization in Wikidata. P31 and P279 might be relevant, but since these properties were created in another context, the management of them would be difficult. Lists of exceptions are possible. The solution could vary from one language to another. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 16:26, 19 June 2026 (UTC) :I would like to suggest the following possibilities for holding the definite article requirement information and also other syntactical information such as genders and other language options. They are in order from "more data-driven" to "more programmatic". #Hold the information as a property of a lexeme attached to the item. #Hold the information in the label or description of the item. #Hold the information in a list (per language) in a property of the item. #Use a programmatic rule, based possibly on item properties, with a list of exceptions. The exceptions could be: #*in the lexemes (or the labels/descriptions), #*in Wikidata item properties per language, perhaps using the "tabular data" type, #*as a Wikifunctions list item, similar to the configuration tables used in the fragment examples, or #*hard-coded in the Abstract Wikipedia wikifunctions. :For instance in order to find a French gender, the programmatic rule could be "Assume it is masculine", but exceptions could be flagged in the lexemes. In all cases, the function would have to search for a lexeme for the item, and if found would have to search for a gender property with value "feminine". The advantage of the programmatic rule would be that for a masculine lexeme no gender property, and perhaps no lexeme, would be needed. :From a theoretical modelling point of view, I think that much the best place to put this information is in the lexeme objects. Well, the item label and description are also per language, but I think they do not "belong" to Abstract Wikipedia. In the meeting there was much more sympathy for a programmatic approach, which I would say is more pragmatic. There is a balance between on one hand trying to reduce the number of database elements and properties, and on the other reducing the complexity of the programming and the rules which have to be known by users. [[User:Strobilomyces|Strobilomyces]] ([[User talk:Strobilomyces|talk]]) 18:47, 19 June 2026 (UTC) 3f7yoe8u00tihgg0z9eq7xr4ec52di7 0 5236 14697 2026-08-14T08:07:10Z Omar M. Ghaly 6856 Creation of the article 14697 abstractwiki text/plain { "qid": "Q11016", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M19003350" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q141063001" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q336" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } } ] } } } doo7m41k9n0sloe48gyknllenqplsa0 3 5237 14698 2026-08-14T10:22:29Z 99of9 614 /* Welcome */ new section 14698 wikitext text/x-wiki == Welcome == Welcome, and well done so far. You're using the right functions as intended. Great start. Let us know if you have suggestions, get stuck or need help. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:22, 14 August 2026 (UTC) lhwwdvwx2zdi1nslmvjtqy65onldnp6