Abstract Wikipedia abstractwiki https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page MediaWiki 1.47.0-wmf.14 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 5 14382 13266 2026-08-10T19:59:11Z EatingCarBatteries 1378 14382 wikitext text/x-wiki <languages /> [[Category:Abstract Wikipedia{{#translation:}}]] <translate> ==What is Abstract Wikipedia?== <!--T:1--> <!--T:2--> Abstract Wikipedia is a new sister project of Wikipedia. <!--T:3--> Wikipedia's vision is a world in which everyone has access to the sum of all knowledge. Abstract Wikipedia will help the communities of volunteers contributing to Wikipedia and its related projects to more effectively close knowledge gaps. <!--T:4--> Wikipedia has articles about more than 20 million topics in more than 300 languages. But none of these languages alone allow access to the knowledge about these 20 million topics: English has more than seven million articles, Croatian 230,000, and Swahili 100,000. Unless you speak those languages, that knowledge is not easily available to you. And as much as machine translation has improved thanks to recent improvements in AI, it is still not at the point where it can produce translations you can trust for many language pairs. <!--T:5--> Abstract Wikipedia does that without relying on AI. Each step of the way remains under human control, and is accessible and editable by the volunteers. There are no hallucinations, no inexplicable and unfixable mistakes: If anything is wrong, the problem can be traced and dealt with, and there is full transparency about how the text has been created. Sourcing and provenance can be preserved and interrogated. It is not just a probabilistic model choosing the capital of Kenya per chance every time. It is human-curated and owned knowledge. ==How does Abstract Wikipedia work?== <!--T:6--> <!--T:7--> Articles in Abstract Wikipedia are stored in a notation independent of human languages. The interface of Abstract Wikipedia allows volunteer contributors to create and maintain that language-independent notation. In a second step, this notation is being turned into text in human language. The steps required to make this happen are also created and maintained by a community of volunteers, on Wikifunctions. These steps can use the data on [[<tvar name=0>D:</tvar>|Wikidata]], looking up population numbers, dates of birth, or irregular grammatical forms, which have been added to and are maintained on Wikidata by communities of volunteers. <!--T:8--> See [[<tvar name=1>Special:MyLanguage/Help:How to create an article</tvar>|Help:How to create an article]] for a step-by-step guide. <!--T:9--> Let's follow one example: [[<tvar name=2>Q1033</tvar>|Nigeria is the most populous country in Africa.]] In Abstract Wikipedia, this might be stored as: </translate> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], Z27243K5)}} <translate><!--T:10--> Or, if we use English labels for these identifiers:</translate> {{block indent|1=superlative(Nigeria, populous, country, Africa, language)}} <translate><!--T:11--> This is a call to a function on Wikifunctions. Based on the language, another function is being called. For English, we get the following function call:</translate> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1002|Z1002]])}} <translate><!--T:12--> And that results in the English text</translate> {{block indent|1=''"Nigeria is the most populous country in Africa."''}} <translate><!--T:13--> If we had chosen German, another function would be called:</translate> {{block indent|1=[[f:Z27243|Z27243]]([[d:Q1033|Q1033]], [[d:Q138758272|Q138758272]], [[d:Q6256|Q6256]], [[d:Q15|Q15]], [[f:Z1430|Z1430]])}} <translate><!--T:14--> And that in turn would result in the following German text:</translate> {{block indent|1=''"Nigeria ist das bevölkerungsreichste Land Afrikas."''}} <translate><!--T:15--> An example with more languages can be found here.<!-- where?? --> <!--T:16--> Abstract Wikipedia brings together numerous communities from the Wikimedia Movement and allows them to work together. Basic lexical data and structured data about many topics from Wikidata, functions that capture the necessary computations from Wikifunctions, and images and maps from Wikimedia Commons are all tied together in Abstract Wikipedia and made available for the more than 300 language editions of Wikipedia. <!--T:17--> The goal of Abstract Wikipedia is to make more knowledge available to more people in more languages, and to allow volunteer editors to be more effective and work across languages, no matter what language they speak. Improvements to the knowledge will automatically propagate to the Wikipedias, errors will be spotted faster and fixed more effectively, and collaborations across languages become possible. We are tearing down the language barriers which are keeping knowledge apart. </translate> [[Category:Abstract Wikipedia basic information]] ddy1d7fvbmf0d3srboikiou9tvn7d4a 4 6 14340 14337 2026-08-10T13:19:14Z MediaWiki message delivery 61 /* Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit */ new section 14340 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) == 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 --> dcgklv9vj5whreyk8h5meyaekv9n99o 14369 14340 2026-08-10T15:33:28Z Choucas 4768 /* Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit */ reply ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 14369 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) == 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) 52fzafm3s79ewhtvaxapy23j058ghq9 14400 14369 2026-08-11T03:03:43Z YoshiRulz 640 /* Wikifunctions & Abstract Wikipedia Newsletter #259: Congratulations Jules*. An apple is a fruit */ Reply 14400 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) == 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) cizlv2jzj6aaaade0hkzgrzlhj62wv3 14401 14400 2026-08-11T03:05:07Z YoshiRulz 640 /* Expanding FAQ to correct common misconceptions */ Reply 14401 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) 7loxb2u6v0cvxyaby6cgiiqm9f89z3x 4 7 14383 11158 2026-08-10T19:59:25Z EatingCarBatteries 1378 14383 wikitext text/x-wiki <languages /> <translate> == What is Abstract Wikipedia? == <!--T:1--> <!--T:2--> Abstract Wikipedia is a new Wikimedia project that allows communities to collaboratively create language-independent articles in their native language, which others can then access in their own languages. This transformation is done by using functions from Wikifunctions that access structured content from Wikidata. == What is an abstract article? == <!--T:3--> <!--T:4--> An abstract article represents information about a topic in a structured, language-independent form. Contributors combine structured data from Wikidata with language functions from Wikifunctions to produce natural-language sentences that describe the topic. == How is Abstract Wikipedia different from Wikipedia? == <!--T:5--> <!--T:6--> Wikipedia articles are written directly in a specific language. <!--T:7--> Abstract Wikipedia instead stores information in a structured form that can generate text in many languages with the help of Wikifunctions. == How does Abstract Wikipedia relate to Wikidata and Wikifunctions? == <!--T:8--> <!--T:9--> Abstract Wikipedia builds on these Wikimedia projects: </translate> * <translate><!--T:10--> '''Wikidata''' provides structured information about topics, and natural language (lexicographic) data.</translate> * <translate><!--T:11--> '''Wikifunctions''' provides (among other things) functions that generate natural-language text in many languages.</translate> * <translate><!--T:12--> '''Abstract Wikipedia''' combines these elements to create articles that can be generated in many languages.</translate> <translate> == Is Abstract Wikipedia using AI? == <!--T:13--> <!--T:14--> No. Abstract Wikipedia does not automatically generate articles using AI. <!--T:15--> Abstract articles are created and maintained by contributors, and functions written by the community generate the text from structured data. == Does Abstract Wikipedia automatically appear on other Wikipedias? == <!--T:16--> <!--T:17--> No. Abstract Wikipedia does not automatically add content to other Wikipedias. Each Wikipedia community remains fully in control of its content, and existing local articles are never replaced. <!--T:18--> In the future, each Wikipedia community will be able to decide whether they want to use content generated from Abstract Wikipedia. == Who can contribute to Abstract Wikipedia? == <!--T:19--> <!--T:20--> Like other Wikimedia projects, Abstract Wikipedia is edited and maintained by volunteers from the community. <!--T:21--> People can contribute in different ways, including creating or improving abstract articles, writing language functions in Wikifunctions, adding data to Wikidata, improving documentation, and helping shape how the project evolves. == Can I use Abstract Wikipedia today? == <!--T:22--> <!--T:23--> Yes. You can explore our early Beta version of Abstract Wikipedia (this site). You can generate abstract articles and view the generated text in different languages. <!--T:24--> Abstract Wikipedia is still in an '''early stage''' so many parts of the experience will continue to evolve based on community feedback. We will be improving the capabilities and usability of the site considerably in the future. You might encounter bugs, usability issues, time-outs, or other problems in the current version. Please [[<tvar name="1">Abstract Wikipedia:Project chat</tvar>|let us know]] if that happens or if you have ideas for improvements! <!--T:25--> In the future, Wikipedia communities will also be able to integrate content created on Abstract Wikipedia into their own wikis, if they like. </translate> [[Category:Abstract Wikipedia administration{{#translation:}}|Frequently Asked Questions]] [[Category:Abstract Wikipedia basic information]] ipzl1jnmloj6p5mj7d2pp65fdy271t9 10 457 14341 14034 2026-08-10T13:20:47Z Sannita (WMF) 48 update 14341 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3><translate><!--T:1--> Volunteer's Corners</translate></h3> * <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> <h3><translate><!--T:4--> Recent status updates about Wikifunctions</translate></h3> <!--Keep this to the most recent 5 entries--> * <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> * <translate><!--T:24--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01</tvar>|2026-07-01]]: Integration on test wiki and annual plan</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> sk1cglgl5yiytz9ky26zkf49nahdvv7 14342 14341 2026-08-10T13:21:02Z Sannita (WMF) 48 Marked this version for translation 14342 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3><translate><!--T:1--> Volunteer's Corners</translate></h3> * <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> <h3><translate><!--T:4--> Recent status updates about Wikifunctions</translate></h3> <!--Keep this to the most recent 5 entries--> * <translate><!--T:28--> [[<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> * <translate><!--T:24--> [[<tvar name="1">:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01</tvar>|2026-07-01]]: Integration on test wiki and annual plan</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> jxz93thljz1u7xvn2qa26cp4wpsl08c 0 747 14368 14297 2026-08-10T15:22:01Z Sohom Datta 1397 14368 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "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": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "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": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1549" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "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": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z6091", "Z6091K1": "Q6352686" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q129286" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3350705" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P276" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q5283295" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P797" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q48730651" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1308" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q6427307" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1001" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q570116" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z6091", "Z6091K1": "Q1356352" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P276" }, "Z38181K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } djmyorv7wqg0zowhld1bt3t2vi29fwu 14370 14368 2026-08-10T16:41:03Z Sohom Datta 1397 14370 abstractwiki text/plain { "qid": "Q1348", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M150315532" }, "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": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "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": "Q1356" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37071", "Z37071K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37071K2": { "Z1K1": "Z13518", "Z13518K1": "7" }, "Z37071K3": { "Z1K1": "Z6091", "Z6091K1": "Q12935276" }, "Z37071K4": { "Z1K1": "Z6091", "Z6091K1": "Q515" }, "Z37071K5": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z37071K6": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36193", "Z36193K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36193K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1549" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q1071" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z37271", "Z37271K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37271K2": { "Z1K1": "Z6091", "Z6091K1": "Q739687" }, "Z37271K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "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": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q309" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z38443", "Z38443K1": { "Z1K1": "Z6091", "Z6091K1": "Q6352686" }, "Z38443K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z38443K3": { "Z1K1": "Z6091", "Z6091K1": "Q1994301" }, "Z38443K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q129286" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P36" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q3350705" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P276" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q5283295" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P797" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q48730651" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1308" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q6427307" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1001" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32145", "Z32145K1": { "Z1K1": "Z6091", "Z6091K1": "Q570116" }, "Z32145K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q1356352" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q2319498" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z6091", "Z6091K1": "Q1356352" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q33506" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q1356352" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P84" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q1356352" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P186" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } rs1j7khcpj0m3wv8pvd2r7xkseior5s 0 847 14355 2808 2026-08-10T13:23:25Z 99of9 614 14355 abstractwiki text/plain { "qid": "Q251160", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q276944" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } id848rdo5xn6r5cilwx1ybl9c0if1zf 0 848 14356 2809 2026-08-10T13:23:45Z 99of9 614 14356 abstractwiki text/plain { "qid": "Q251682", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q719665" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } lnm1io021srdv3xon3bxv3x8stg060n 0 871 14357 2911 2026-08-10T13:24:08Z 99of9 614 14357 abstractwiki text/plain { "qid": "Q276779", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q644201" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } bkx1ojsxuzflswvb4qyi301eyde7vei 0 873 14358 2913 2026-08-10T13:24:30Z 99of9 614 14358 abstractwiki text/plain { "qid": "Q276830", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q1150151" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } dyh928pfhhtyfl3sfj8jmljfz2ke5ik 0 874 14359 2914 2026-08-10T13:24:50Z 99of9 614 14359 abstractwiki text/plain { "qid": "Q276831", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q2564508" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } o21jiltcgmt4dtzyc63d0q122wscdk2 0 875 14360 2915 2026-08-10T13:25:09Z 99of9 614 14360 abstractwiki text/plain { "qid": "Q283483", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q382005" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } jnislcecex04p2vco657ju6r1qsep6o 0 877 14361 2917 2026-08-10T13:25:25Z 99of9 614 14361 abstractwiki text/plain { "qid": "Q288248", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q455602" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } b5ume79w63phnzu74f7x4yb1qkmfzoq 0 911 14399 11354 2026-08-11T02:47:20Z YoshiRulz 640 Z12 example 14399 abstractwiki text/plain { "qid": "Q138864867", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27926", "Z27926K1": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z32982", "Z32982K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32982K2": { "Z1K1": "Z6091", "Z6091K1": "Q2667186" }, "Z32982K3": { "Z1K1": "Z6091", "Z6091K1": "Q96807071" }, "Z32982K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z89", "Z89K1": " " }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z32425", "Z32425K1": { "Z1K1": "Z6091", "Z6091K1": "Q5" }, "Z32425K2": { "Z1K1": "Z6091", "Z6091K1": "Q109243377" }, "Z32425K3": { "Z1K1": "Z6091", "Z6091K1": "Q1003030" }, "Z32425K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] }, { "Z1K1": "Z7", "Z7K1": "Z32123", "Z32123K1": { "Z1K1": "Z89", "Z89K1": "" } }, { "Z1K1": "Z7", "Z7K1": "Z15728", "Z15728K1": { "Z1K1": "Z26934", "Z26934K1": { "Z1K1": "Z6091", "Z6091K1": "" } }, "Z15728K2": "", "Z15728K3": { "Z1K1": { "Z1K1": "Z9", "Z9K1": "" } }, "Z15728K4": { "Z1K1": { "Z1K1": "Z9", "Z9K1": "" } } }, { "Z1K1": "Z7", "Z7K1": "Z33470", "Z33470K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z22571", "Z22571K1": { "Z1K1": "Z7", "Z7K1": "Z33828", "Z33828K1": { "Z1K1": "Z6091", "Z6091K1": "Q16947045" }, "Z33828K2": { "Z1K1": "Z6091", "Z6091K1": "Q5916" } } } }, "Z33470K2": "h2", "Z33470K3": { "Z1K1": { "Z1K1": "Z7", "Z7K1": "Z883", "Z883K1": "Z6", "Z883K2": "Z1" }, "K1": [ { "Z1K1": "Z7", "Z7K1": "Z882", "Z882K1": "Z6", "Z882K2": "Z1" }, { "Z1K1": { "Z1K1": "Z7", "Z7K1": "Z882", "Z882K1": "Z6", "Z882K2": "Z1" }, "K1": "lang", "K2": "tok" } ] } }, { "Z1K1": "Z7", "Z7K1": "Z30805", "Z30805K1": "MediaWiki icons :OOOOOOOOO", "Z30805K2": { "Z1K1": "Z89", "Z89K1": "<span style=\"color: red;\" class=\"vector-icon mw-ui-icon-move mw-ui-icon-wikimedia-move\"></span>\n<span class=\"vector-icon mw-ui-icon-labFlask mw-ui-icon-wikimedia-labFlask\"></span>\n<span class=\"vector-icon mw-ui-icon-star mw-ui-icon-wikimedia-star\"></span>\n<span class=\"vector-icon mw-ui-icon-wikimedia-unStar\"></span>\n<span class=\"ace_error ace_icon\" style=\"width: 18px; height: 18px;\" aria-label=\"error\" role=\"img\"> </span>\n<span class=\"vector-icon mw-ui-icon-bell mw-ui-icon-wikimedia-bell\"></span>\n<span style=\"background-color:red;\">Hello, Wikipedia!</span>\n<span class=\"vector-icon mw-ui-icon-wikimedia-unStar\" style=\"background-color:yellow;\" title=\"This is a featured abstract article. It, or a previous version of it, has been recognized as one of the best abstract articles EVER!!!!!!\"></span><span style=\"border-radius:100%;background-color:#ded;color:#062;border:2px solid #062;width:20px;height:1.5em;display:inline-block;text-align:center;\" title=\"This is a really good article ngl\">+</span>\n<span class=\"vector-icon mw-ui-icon-language-progressive mw-ui-icon-wikimedia-language-progressive\"></span>" } }, { "Z1K1": "Z7", "Z7K1": "Z801", "Z801K1": { "Z1K1": "Z89", "Z89K1": "<!-- comments work -->" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z34953", "Z34953K1": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "hello everyone" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "bonjour tout le monde" } ] }, "Z34953K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 3fvqnslocf0bb5e5fdrfw3gwnzos9hg 0 914 14362 3048 2026-08-10T13:25:42Z 99of9 614 14362 abstractwiki text/plain { "qid": "Q703904", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z14396", "Z14396K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q386563" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } dqsvl20d1u1i7f52ezuqw8gcqopg725 0 931 14394 3065 2026-08-11T01:42:17Z YoshiRulz 640 Replace string-producing functions with rich text-producing ones 14394 abstractwiki text/plain { "qid": "Q705310", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q1051960" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 8ap2beqcuz8uvoj8xoo6rfvtldbkd6g 14408 14394 2026-08-11T04:14:56Z 99of9 614 link formatting 14408 abstractwiki text/plain { "qid": "Q705310", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q845945" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q17" }, "Z36983K4": { "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": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q1051960" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q11591100" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] } ] } } } 3rzpmrmi8uax9s2miqedtejncwkp5sz 0 965 14395 3268 2026-08-11T01:46:54Z YoshiRulz 640 Replace string-producing function with rich text-producing one 14395 abstractwiki text/plain { "qid": "Q11591100", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32965", "Z32965K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32965K2": { "Z1K1": "Z6091", "Z6091K1": "Q524158" }, "Z32965K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26955", "Z26955K1": { "Z1K1": "Z6091", "Z6091K1": "Q66305721" }, "Z26955K2": { "Z1K1": "Z6091", "Z6091K1": "Q1589492" }, "Z26955K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26955K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } 3bb99heuoyz8nzbfiv2i1br17nlsdy8 14396 14395 2026-08-11T01:50:06Z YoshiRulz 640 I think this is what the deprecated fragment was meant to be 14396 abstractwiki text/plain { "qid": "Q11591100", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32965", "Z32965K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32965K2": { "Z1K1": "Z6091", "Z6091K1": "Q524158" }, "Z32965K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z34637", "Z34637K1": { "Z1K1": "Z6091", "Z6091K1": "Q1589492" }, "Z34637K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } 8uh6bowcza26jps1qjhsdqlg99y0woz 14414 14396 2026-08-11T06:42:31Z 99of9 614 that's an example rather than a part 14414 abstractwiki text/plain { "qid": "Q11591100", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32965", "Z32965K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32965K2": { "Z1K1": "Z6091", "Z6091K1": "Q524158" }, "Z32965K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } npqce7r711ohfvz306lrqfwsgszcb4t 0 1024 14387 11238 2026-08-10T23:13:07Z YoshiRulz 640 Fix formatting 14387 abstractwiki text/plain { "qid": "Q718", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q131436" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11410" }, "Z36993K3": { "Z1K1": "Z6091", "Z6091K1": "Q185451" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } tdv2d6alldotmy2924r6b294ucfrhi7 14388 14387 2026-08-10T23:14:50Z YoshiRulz 640 Add image 14388 abstractwiki text/plain { "qid": "Q718", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M162188020" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q10873124" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q131436" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11410" }, "Z36993K3": { "Z1K1": "Z6091", "Z6091K1": "Q185451" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 5tjfbitkew4t5zhdxbmpby2fv0yrw48 14389 14388 2026-08-10T23:30:42Z YoshiRulz 640 Add history paragraph 14389 abstractwiki text/plain { "qid": "Q718", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M162188020" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q10873124" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q131436" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11410" }, "Z36993K3": { "Z1K1": "Z6091", "Z6091K1": "Q185451" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P144" }, "Z38181K3": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "650" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "1500" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 85ynjlii3ndtdrfs3wmrv7wl0ohvt9v 14397 14389 2026-08-11T02:18:32Z YoshiRulz 640 Add paragraph on FIDE and the world championship 14397 abstractwiki text/plain { "qid": "Q718", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M162188020" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q10873124" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q131436" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11410" }, "Z36993K3": { "Z1K1": "Z6091", "Z6091K1": "Q185451" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P144" }, "Z38181K3": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "650" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "1500" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11422536" }, "Z36993K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P571" } ] }, "Z39106K2": { "Z1K1": "Z7", "Z7K1": "Z39110", "Z39110K1": { "Z1K1": "Z7", "Z7K1": "Z39108", "Z39108K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P571" } ] } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q105269" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1027" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q10290970" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1027" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q118112582" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1346" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 4pkk2p190lepb9volrepopf0dx57b2n 14411 14397 2026-08-11T05:20:21Z 99of9 614 past tense 14411 abstractwiki text/plain { "qid": "Q718", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M162188020" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q10873124" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q131436" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11410" }, "Z36993K3": { "Z1K1": "Z6091", "Z6091K1": "Q185451" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P144" }, "Z38181K3": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "650" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "1500" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11422536" }, "Z36993K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P571" } ] }, "Z39106K2": { "Z1K1": "Z7", "Z7K1": "Z39110", "Z39110K1": { "Z1K1": "Z7", "Z7K1": "Z39108", "Z39108K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P571" } ] } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q105269" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1027" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q10290970" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1027" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q118112582" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P1346" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 83au8lexbdtkxvthk6vn3ewq3io4w5k 14412 14411 2026-08-11T05:34:10Z 99of9 614 14412 abstractwiki text/plain { "qid": "Q718", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M162188020" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q10873124" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q131436" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37068", "Z37068K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37068K2": { "Z1K1": "Z6091", "Z6091K1": "Q185451" }, "Z37068K3": { "Z1K1": "Z6091", "Z6091K1": "Q11410" }, "Z37068K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q11410" } ] }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P144" }, "Z38181K3": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "650" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "1500" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11422536" }, "Z36993K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P571" } ] }, "Z39106K2": { "Z1K1": "Z7", "Z7K1": "Z39110", "Z39110K1": { "Z1K1": "Z7", "Z7K1": "Z39108", "Z39108K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P571" } ] } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q105269" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1027" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q10290970" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1027" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q118112582" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P1346" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } clhf41h6nk5toul3ddvoswia5kbxaxq 14413 14412 2026-08-11T06:22:27Z 99of9 614 link control 14413 abstractwiki text/plain { "qid": "Q718", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M162188020" }, "Z38053K2": { "Z1K1": "Z6091", "Z6091K1": "Q10873124" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q131436" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37068", "Z37068K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37068K2": { "Z1K1": "Z6091", "Z6091K1": "Q185451" }, "Z37068K3": { "Z1K1": "Z6091", "Z6091K1": "Q11410" }, "Z37068K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" }, { "Z1K1": "Z6091", "Z6091K1": "Q11410" } ] }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z38181", "Z38181K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38181K2": { "Z1K1": "Z6092", "Z6092K1": "P144" }, "Z38181K3": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z38181K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q206230" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "650" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z30120K2": [ "Z6030", "Z6033" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092" ] }, "Z39106K2": { "Z1K1": "Z20420", "Z20420K1": { "Z1K1": "Z20159", "Z20159K1": { "Z1K1": "Z17813", "Z17813K1": "Z17814" }, "Z20159K2": { "Z1K1": "Z13518", "Z13518K1": "1500" } }, "Z20420K2": { "Z1K1": "Z20342", "Z20342K1": { "Z1K1": "Z16098", "Z16098K1": "Z16101" }, "Z20342K2": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z36993", "Z36993K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z36993K2": { "Z1K1": "Z6091", "Z6091K1": "Q11422536" }, "Z36993K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36993K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z39106", "Z39106K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P571" } ] }, "Z39106K2": { "Z1K1": "Z7", "Z7K1": "Z39110", "Z39110K1": { "Z1K1": "Z7", "Z7K1": "Z39108", "Z39108K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z6091", "Z6091K1": "Q102178" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": { "Z1K1": "Z7", "Z7K1": "Z24144", "Z24144K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" }, "Z24144K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z24144K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P571" } ] } } }, "Z39106K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37661", "Z37661K1": { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q105269" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1027" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37661K2": { "Z1K1": "Z6091", "Z6091K1": "Q105269" }, "Z37661K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z37661", "Z37661K1": { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z6091", "Z6091K1": "Q10290970" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P1027" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37661K2": { "Z1K1": "Z6091", "Z6091K1": "Q10290970" }, "Z37661K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q102178" } ] }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z6091", "Z6091K1": "Q118112582" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P1346" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } m9byakn53j6q2efnfx7y4diuwtpo7k3 0 1110 14363 3412 2026-08-10T13:28:22Z 99of9 614 14363 abstractwiki text/plain { "qid": "Q3783", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q4022" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q18" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } } ] } } } hwpl69fo77qa3kf0ymgzgv997l9wsac 2 1117 14419 14146 2026-08-11T09:20:15Z HenkvD 1447 14419 wikitext text/x-wiki {| border="1" style="float: right; margin-left: 1em; margin-bottom: 0.5em; border: #99B3FF solid 1px; background: #F1F8F1; border-collapse: collapse; color:black" | | colspan="10" style="text-align:center;" | <div class="plainlinks">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''Gebruiker:HenkvD''' op [[commons:Template talk:Sisterlinks|zusterprojecten]]</div> |- | valign="top" align="center" | [[Image:Wikipedia-logo.png|18px]]<br>Wikipedia<br>[[:de:Benutzer:HenkvD|de:]] [[:en:User:HenkvD|en:]] [[:fr:Utilisateur:HenkvD|fr:]] '''[[:nl:User:HenkvD|nl:]]''' | valign="top" align="center" | [[Image:Wiktionary-logo-en.png|17px]]<br>Wiktionary<br>[[:wikt:en:User:HenkvD|en:]]<br />[http://www.omegawiki.org/index.php/User:HenkvD ΩWiki] | valign="top" align="center" | [[Image:Wikinews-logo.png|35px]]<br>Wikinews<br>[[wikinews:User:HenkvD|en:]] [[:n:nl:User:HenkvD|nl:]]<br><div class="plainlinks">[http://incubator.wikimedia.org/w/index.php?title=User:HenkvD nl: in incubator]</div> | valign="top" align="center" | [[Image:Wikiquote-logo.png|16px]]<br>Wikiquote<br>[[:q:en:User:HenkvD|en:]] |- | valign="top" align="center" | [[Image:Wikibooks-logo.png|18px]]<br>Wikibooks<br>[[:b:en:User:HenkvD|en:]] | valign="top" align="center" | [[Image:Wikisource-logo.png|18px]]<br>Wikisource<br>[[:s:en:User:HenkvD|en:]] '''[[:s:nl:Gebruiker:HenkvD|nl:]]''' <div class="plainlinks">[http://wikisource.org/wiki/User:HenkvD old]</div> | valign="top" align="center" | [[Image:Wikiversity-logo-en.svg|18px]]<br>Wikiversity<br>[[:de:v:User:HenkvD|de:]] [[:en:v:User:HenkvD|en:]] | valign="top" align="center" | [[Image:Wikimedia-logo.png|18px]]<br>[[:meta:User:HenkvD|Meta]]<br><div class="plainlinks">[http://strategy.wikimedia.org/wiki/User:HenkvD Strategy]<br><div class="plainlinks">'''[http://nl.wikimedia.org/wiki/Gebruiker:HenkvD nl:]'''</div></div> |- | valign="top" align="center" | [[Image:Wikivoyage-Logo-v3-icon.svg|16px]]<br>Wikivoyage<br>[[:en:voy:User:HenkvD|en:]] | valign="top" align="center" | [[File:Wikidata-logo.svg|19px|Wikidata]]<br><div class="plainlinks">[http://www.wikidata.org/wiki/User:HenkvD Wikidata]</div> | valign="top" align="center" | [[Image:Commons-logo.svg|14px]]<br>[[:Commons:User:HenkvD|Commons]] | valign="top" align="center" | [[File:Wikifunctions-logo.svg|14px]] [[File:Abstract-Wikipedia-wordmark.svg|42px]]<br>[[f:User:HenkvD|Wikifunctions]] <br>'''AbstractWiki''' |} My name is Henk, from [[Q55|the Netherlands]] ([[:nl:Gebruiker:HenkvD]]). I am interested in Abstract Wikipedia functionality and have general knowledge of the Dutch language (as native speaker). As most other Dutch persons I have good knowledge of English and some of German and a bit of French and Romance languages.<br> I have an IT background, and try to understand the programming in Wikifunctions.<br> I am contributing on language functions at Wikifunctions including Infoboxes, are active on Abstract Wikipedia, and a bit on Wikidata, including lexemes. I am active on other Wikimedia projects, mostly on Commons. In my opinion the initial goal is to have Abstract Wikipedia pages with simple lead section (like stubs), an infobox fully from Wikidata, one or more images and maybe some simple lists. The simple lead sentences should function for as many languages as possible. That will also need that many languages will have labels in Wikidata and lexemes with genders. That will be a difficult enough to achieve. In my opinion extensive prose will be very hard to achieve. <br clear=all> {{#babel:nl|en-3|de-2|fr-1}} See also [[User:HenkvD/Tasks per language]] {{User:HenkvD/Infoboxes}} ===Overview of NLG functions I work(ed) upon=== {| class="wikitable" ! ZID !! Example !! English !! Dutch || Other simple languages || Default |- | [[f:Z37782|Z37782]] infobox row, date || [[Q2407]] || || OK || Maybe to merge into general infobox row || N/A |- | [[f:Z37830|Z37830]] infobox row, string or quantity || [[Q140]] || || OK || Maybe to merge into general infobox row || N/A |- | [[f:Z38086|Z38086]] infobox for row, coordinate hyperlinked || [[Q90]] || || OK || Maybe to merge into general infobox row || N/A |- | [[f:Z38960|Z38960]] infobox rows taxonomy || || Requeted for Python implementation || || || N/A |- | [[f:Z37640|Z37640]] if (HTML output) || || || OK || || N/A |- | [[f:Z36625|Z36625]] third-person singular form of to be (simple) || || is || is || [[f:Z36627|f:]] en nl fy af bar bs eo frr is hsb mk nds os pap sr +fi +cs hr id zea || (is) |- | [[f:Z36622|Z36622]] indefinite article (simple) || || N/A || een || [[f:Z36624|f:]] nl af fy bar bs eo frr is hsb mk nds os pap sr +fi +cs hr id zea || (a) |- | [[f:Z36610|Z36610]] definite article (simple) || || the || N/A || [[f:Z36620|f:]] en af eo pap +fi +cs hr id || (the) |- | [[f:Z37311|Z37311]] String<br>and (indicating last entry of list) Simple || || and || en || 40 simple languages || (and) |- | [[f:Z32962|Z32962]] HTML [[f:Z26039|Z26039]] String<br>A is a B. || [[Q8739]] || Paris is a city. || Parijs is een stad || [[f:Z35523|f:]] af bar bs eo frr fy hsb is mk nds os pap sr +fi +zea || Y Magenta 🔧 |- | [[f:Z32965|Z32965]] HTML [[f:Z26095|Z26095]] Monlingual<br>an A is a B. || [[Q2102]] || A frog is an amphibian. || een hond is een dier || [[f:Z36875|f:]] af bar bs eo frr fy hsb is (nds) mk nl os pap sr +fi +id zea || Y Magenta 🔧 with ❌ |- | [[f:Z36983|Z36983]] HTML [[f:Z26570|Z26570]] String<br>A is a B in C. || [[Q55]] || Netherlands is a country in Europe || Nederland is een land in Europa. || [[f:Z35618|f:]] af bar eo frr fy mk pap +hr zea || Y magenta 🔧 |- | [[f:Z36987|Z36987]] HTML [[f:Z32581|Z32581]] Monolingual<br>A is a B by C. || [[Q12418]] || Mona Lisa is a painting by Leonardo da Vinci. || Mona Lisa is een schilderij van Leonardo da Vinci. || [[f:Z36168|f:]] af eo fy is mk os pap +cs hr id zea || Y Magenta 🔧 with ❌ |- | [[f:Z36993|Z36993]] HTML [[f:Z32982|Z32982]] Monlingual<br>A is a B of C. || [[Q718]] || Chess is a game of strategy. || Schaken is een spel van strategie. || [[f:Z36528|f:]] af eo fy mk nl pap +cs hr id zea || Y Magenta 🔧 with ❌ |- | [[f:Z37011|Z37011]] HTML [[f:Z28016|Z28016]] Monolingual<br>A is the B of C. || [[Q90]] || Paris is the capital of France. || Parijs is de hoofdstad van Frankrijk<br>❗Lexemes needed for nouns || [[f:Z36339|f:]] af eo mk pap +hr zea || Y Magenta 🔧 with ❌ |- | [[f:Z34282|Z34282]] A is a B. (automatic based on Wikidata class) || [[Q13924]] || Adriatic Sea is a sea || Adriatische Zee is een zee. || WIP Wrapper || N |- | [[f:Z34637|Z34637]] A is part of the B. (automatic based on Wikidata class) || [[Q13924]] || Adriatic Sea is part of the Mediterranean Sea. || || || Y |- | [[f:Z27243|Z27243]] Monolingual<br>Superlative A is the B-est C in D || [[Q319]] || Jupiter is the largest planet in the Solar System. || [[f:Z37022|f:]] Jupiter is de grootste planeet van het zonnestelsel.<br>❗Lexemes needed for nouns || [[f:Z37033|:f:]] eo || Y ⤒ large { planet ∩ Solar System } = Jupiter. |- | [[f:Z29591|Z29591]] Monolingual<br>entity with adjective / class || [[Q177749]] || Jupiter is a big planet || || || Y A ∈ { B ∩ C. }. |- | [[f:Z37005|Z37005]] Monolingual<br>A has parts (automatic based on Wikidata) || [[Q211391]] || Weekend consists of Saturday and Sunday. || Weekeinde bestaat uit zaterdag en zondag. || [[f:Z37328|f:]] 25 languages || Y |- | [[f:Z37289|Z37289]] Monolingual<br>join list of monolingual texts without Oxford comma || || A, B and C || A, B en C || 40 languages || Y |- | || [[Q11750]] || list of sovereign states || || || N/A |- | [[f:Z36218|Z36218]] specific property of subject is value from WD || [[Q922]]<br> [[Q408]] (load time might be long) || The area of Australia is 7,692,024 km². || De oppervlakte van Australië is 7692024 km²<br>❗Lexemes not yet available for nouns of almost all used properties || [[f:Z36684|f:]] af eo mk pap +cs hr id || Y oppervlakte(Australië) = 7692024 km². |- ! '''NLG Default''' !! !! !! !! !! |- | [[f:Z35921|Z35921]] NLG default text (string) || || OK || || || N/A |- | [[f:Z36911|Z36911]] NLG default text (monolingual text) || || OK || || || language "mul" |- | [[f:Z36909|Z36909]] NLG default text (HTML) || || OK || || || span lang="mul" style="color: #FF00FF;" |- | [[f:Z37454|Z37454]] monolingual text as HTML with lang & colour span || [[Q1370]] || || || || language daz <span lang="mul" style="color: #FF00FF;">⤒ Q138758272 { Q28575 ∩ Virginia } = Q341915</span> |} Natural Language * [[f:Wikifunctions:NLG functions|Wikifunctions:NLG functions]] * [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions|Wikifunctions:Catalogue/Natural language operations/Global language functions]] Dutch language * [[f:Wikifunctions:Catalogue/Natural language operations/Dutch|Wikifunctions:Catalogue/Natural language operations/Dutch]] Wikidata queries * [https://query.wikidata.org/#%23%20Gender%20of%20City%20per%20langague%0ASELECT%20%3Fl%20%3Flemma%20%3Fsense%20%3Fgender%20%3FgenderLabel%20%28LANG%28%3Flemma%29%20AS%20%3Flanguage%29%0AWHERE%20%7B%0A%20%20%20%20%20%20%3Fsense%20wdt%3AP5137%20wd%3AQ515.%20%20%20%23%20City%0A%20%20%20%20%20%20%3Fl%20ontolex%3Asense%20%3Fsense.%0A%20%20%20%20%20%20%3Fl%20wikibase%3Alemma%20%3Flemma.%20%20%20%23%20FILTER%28LANG%28%3Flemma%29%3D%22de%22%29%0A%20%20%20%20%20%20%3Fl%20wdt%3AP5185%20%3Fgender.%0A%20%20%20%20%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%7D Gender of City per langague ] {{AbstractTestLemma}} {| class="wikitable" ! Function !! English !! Z1157 Dutch !! Z60 Local language |- | <nowiki>{{#function:</nowiki>[[f:Z26039|Z26039]]<nowiki>|Q64|Q515|Z1002}}</nowiki> | {{#function:Z26039|Q64|Q515|Z1002}} || {{#function:Z26039|Q64|Q515|Z1157}} || {{#function:Z26039|Q64|Q515|Z60}} |} Testing different NLG Default texts : <span lang="mul" style="color: #FF00FF;">NLG Default text</span> : ❌≪NLG Default text≫❌ 5mga13mz9ufwae951tgd7aoexlz6hrz 0 1120 14366 3426 2026-08-10T13:50:21Z 99of9 614 14366 abstractwiki text/plain { "qid": "Q34932", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q36074" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } g55rzfjjz57dydetp54mdxhldthfxg0 14367 14366 2026-08-10T13:51:16Z 99of9 614 14367 abstractwiki text/plain { "qid": "Q34932", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q36074" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } } ] } } } k6qwlpronf3o7z3pzw5y5j2k84cerac 0 1130 14364 14172 2026-08-10T13:32:18Z 99of9 614 14364 abstractwiki text/plain { "qid": "Q884", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q3624078" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q48" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q8684" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q9176" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q23492" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "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": "P6" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q202040" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q8142" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } d1svopkliihfwn57v97ty9owdwb0dti 0 1217 14365 3567 2026-08-10T13:42:28Z 99of9 614 14365 abstractwiki text/plain { "qid": "Q6186", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q12909644" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q273005" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } r8tfrgx5wtquhjqynj0vgm3mjnuc4na 0 1323 14338 12916 2026-08-10T12:04:02Z HenkvD 1447 Replaced all sentences of occupations by Person lead sentence with occupations 14338 abstractwiki text/plain { "qid": "Q7243", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z35370", "Z35370K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z35370K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38757", "Z38757K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38757K2": [ "Z6091" ], "Z38757K3": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q214917" }, { "Z1K1": "Z6091", "Z6091K1": "Q4964182" }, { "Z1K1": "Z6091", "Z6091K1": "Q6625963" }, { "Z1K1": "Z6091", "Z6091K1": "Q1231865" }, { "Z1K1": "Z6091", "Z6091K1": "Q11774202" }, { "Z1K1": "Z6091", "Z6091K1": "Q12144794" }, { "Z1K1": "Z6091", "Z6091K1": "Q4853732" }, { "Z1K1": "Z6091", "Z6091K1": "Q18939491" }, { "Z1K1": "Z6091", "Z6091K1": "Q6051619" }, { "Z1K1": "Z6091", "Z6091K1": "Q860918" }, { "Z1K1": "Z6091", "Z6091K1": "Q16003550" }, { "Z1K1": "Z6091", "Z6091K1": "Q49757" }, { "Z1K1": "Z6091", "Z6091K1": "Q15949613" } ], "Z38757K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32123", "Z32123K1": { "Z1K1": "Z7", "Z7K1": "Z32234", "Z32234K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z33975", "Z33975K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z33975K2": { "Z1K1": "Z6091", "Z6091K1": "Q36180" }, "Z33975K3": { "Z1K1": "Z6091", "Z6091K1": "Q34266" }, "Z33975K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32053", "Z32053K1": "https://cs.isabart.org/person/15659", "Z32053K2": "https://cs.isabart.org/person/15659", "Z32053K3": "cs.isabart.org", "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": "16" } } }, "Z32053K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32053", "Z32053K1": "http://www.tandfonline.com/doi/pdf/10.1080/00905999708408490", "Z32053K2": "http://www.tandfonline.com/doi/pdf/10.1080/00905999708408490", "Z32053K3": "tandfonline.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": "16" } } }, "Z32053K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32053", "Z32053K1": "http://www.tandfonline.com/doi/pdf/10.1080/13507486.2011.574682", "Z32053K2": "http://www.tandfonline.com/doi/pdf/10.1080/13507486.2011.574682", "Z32053K3": "tandfonline.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": "16" } } }, "Z32053K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } ] } } } h2gbkz3m08cbh6dj4438b6004wymomd 0 1341 14402 5391 2026-08-11T03:28:20Z 99of9 614 Misused for "part of" 14402 abstractwiki text/plain { "qid": "Q1051960", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32123", "Z32123K1": { "Z1K1": "Z7", "Z7K1": "Z32234", "Z32234K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q524158" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } }, { "Z1K1": "Z7", "Z7K1": "Z32123", "Z32123K1": { "Z1K1": "Z7", "Z7K1": "Z32234", "Z32234K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q66305721" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q56347075" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } ] } } } eocxtv5wi8zkwztxtcpdee1u5svfcex 0 1371 14390 4290 2026-08-11T01:07:32Z YoshiRulz 640 Split paragraph 14390 abstractwiki text/plain { "qid": "Q11081", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q112193867" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q2397106" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q438962" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33457", "Z33457K1": { "Z1K1": "Z7", "Z7K1": "Z26095", "Z26095K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26095K2": { "Z1K1": "Z6091", "Z6091K1": "Q12136" }, "Z26095K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } pg8ps7bpi5qrndhqhviz9gvcuy3x6mf 14391 14390 2026-08-11T01:11:01Z YoshiRulz 640 Replace string-producing functions with rich text-producing ones 14391 abstractwiki text/plain { "qid": "Q11081", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q112193867" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32965", "Z32965K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32965K2": { "Z1K1": "Z6091", "Z6091K1": "Q2397106" }, "Z32965K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32965", "Z32965K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32965K2": { "Z1K1": "Z6091", "Z6091K1": "Q438962" }, "Z32965K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32965", "Z32965K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32965K2": { "Z1K1": "Z6091", "Z6091K1": "Q12136" }, "Z32965K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } l5rdsa9eg6g70p0y2l2aei71vo3bltq 14410 14391 2026-08-11T04:40:49Z 99of9 614 14410 abstractwiki text/plain { "qid": "Q11081", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q112193867" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q438962" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q2397106" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } sts50jh42xhczr0lm64xn0i1aa9smk9 12 1502 14404 4584 2026-08-11T04:07:03Z EatingCarBatteries 1378 EatingCarBatteries moved page [[Abstract Wikipedia:Tools]] to [[Help:Tools]] 4584 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/] == Desktop editor == Right now it is extremely difficult to actually edit. There is no source editor, no wikitext mode, and no way to see what you're writing until you publish. The visual editor is a custom Vue.js app that works nothing like a traditional wiki, and articles frequently fail to render in the browser at all. This project exists to make editing Abstract Wikipedia feel more like editing a traditional Wikipedia. You write human-readable wikitext templates, see a live English preview of what the article will say, and publish with one click. Link: * Internal: [[User:Immanuelle/Abstract Wikipedia Editor]] * External: [https://emmaleonhart.github.io/AbstractWikipediaEditor/ https://emmaleonhart.github.io/AbstractWikipediaEditor/] [[Category:Abstract Wikipedia administration]] o2wt9vh34c000ygeezzabautky9auqi 14406 14404 2026-08-11T04:07:31Z EatingCarBatteries 1378 14406 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/] == Desktop editor == Right now it is extremely difficult to actually edit. There is no source editor, no wikitext mode, and no way to see what you're writing until you publish. The visual editor is a custom Vue.js app that works nothing like a traditional wiki, and articles frequently fail to render in the browser at all. This project exists to make editing Abstract Wikipedia feel more like editing a traditional Wikipedia. You write human-readable wikitext templates, see a live English preview of what the article will say, and publish with one click. Link: * Internal: [[User:Immanuelle/Abstract Wikipedia Editor]] * External: [https://emmaleonhart.github.io/AbstractWikipediaEditor/ https://emmaleonhart.github.io/AbstractWikipediaEditor/] [[Category:Help]] 54v12yimm2g8vixzfg7rl5moyo24b85 14409 14406 2026-08-11T04:25:25Z EatingCarBatteries 1378 14409 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/] [[Category:Help]] jugzfgyfvnk272vbs31igdmm1nriq49 4 1710 14374 9361 2026-08-10T19:14:13Z EatingCarBatteries 1378 14374 wikitext text/x-wiki <languages/> <translate><!--T:1--> A WikiProject is a group of contributors who want to work together as a team to improve Wikipedia. These groups often focus on a specific topic area, a specific part of the encyclopedia, or a specific kind of task.</translate> == <translate><!--T:2--> Function</translate> == <translate><!--T:3--> A WikiProject collaborates to improve a particular topic area. The group uses its WikiProject pages to develop ideas, discuss sources, maintain various collaborative processes, and keep track of work that needs to be done. <!--T:4--> The discussion pages attached to a project page are a convenient venue for those involved in that project to talk about what they are doing, to ask questions, and to receive advice from other people interested in the group's work. <!--T:5--> They typically are areas of interest or expertise and can be used for collaboration, coordination, competitions, outreach, decision-making, integration and mutual assistance. <!--T:6--> WikiProjects are not rule-making organizations, nor can they assert ownership of articles within a specific topic area. WikiProjects have no special rights or privileges compared to other editors and may not impose their preferences on articles. A WikiProject is fundamentally a social construct: its success depends on its ability to function as a cohesive group of editors working towards a common goal.</translate> [[Category:WikiProjects{{#translation:}}| ]] [[Category:Abstract Wikipedia administration]] k1smli7q25py6fbgz86qwhtu0uihatl 10 1883 14349 13961 2026-08-10T13:21:05Z FuzzyBot 563 Updating to match new version of source page 14349 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3>Volunteer's Corners</h3> * 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. <h3>Recent status updates about Wikifunctions</h3> <!--Keep this to the most recent 5 entries--> * [[: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 * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: Integration on test wiki and annual plan </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> ng2vqtjjq8kehiiwitrhb70zvumv4o0 10 1989 14346 13957 2026-08-10T13:21:04Z FuzzyBot 563 Updating to match new version of source page 14346 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3>স্বেচ্ছাসেবক সভা</h3> * পরবর্তী স্বেচ্ছাসেবক সভা <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|সর্বশেষ স্বেচ্ছাসেবক সভা]] কমন্সে পাওয়া যাবে। <h3>উইকিফাংশন্স সম্পর্কে সাম্প্রতিক হালনাগাদ</h3> <!--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-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> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: Integration on test wiki and annual plan</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> 0rcg3hg220nequucgdj1ilkm55zcfhp 0 2006 14393 5364 2026-08-11T01:29:22Z YoshiRulz 640 Replace string-producing functions with rich text-producing ones 14393 abstractwiki text/plain { "qid": "Q36", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q46" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z6091", "Z6091K1": "Q270" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z37011K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } ikq8hs5p7y3p7uuzt0up9p83wp6zk9m 14407 14393 2026-08-11T04:10:14Z 99of9 614 improve 14407 abstractwiki text/plain { "qid": "Q36", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q46" }, "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": "P36" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } k5t3wwob9opwrwcwh77pu8zstzxwnek 4 2049 14375 6820 2026-08-10T19:15:38Z EatingCarBatteries 1378 Don't think we need categories for this page 14375 wikitext text/x-wiki <templatestyles src="Template:Flatlist/styles.css"/> ''A list of archived requests for permissions:'' === 2026 === <div class="hlist"> {{Special:PrefixIndex/Abstract:Requests for permissions/Archive/2026/|stripprefix=1|hideredirects=1}}</div> arjk317rrne3znhdvgbwd855i899rks 10 2061 14347 14106 2026-08-10T13:21:04Z FuzzyBot 563 Updating to match new version of source page 14347 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3>Freiwilligentreffen</h3> * 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. <h3>Aktuelle Neuigkeiten zum Status von Wikifunctions</h3> <!--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-05|2026-08-05]]: Congratulations Jules*: An apple is a fruit</span> * <span class="mw-translate-fuzzy">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-29|2026-07-29]]: Abstrakte Wikipedia bei der Wikimania</span> * <span class="mw-translate-fuzzy">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-16|2026-07-16]]: Über syntaktische Tabellen hinaus</span> * [[: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 * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: Integration im Test-Wiki und Jahresplan </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> tl6koo48fnbzxoqrmrrul1slna4up5h 10 2080 14348 13959 2026-08-10T13:21:04Z FuzzyBot 563 Updating to match new version of source page 14348 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3>ركن المتطوعين</h3> * سيكون ركن المتطوعين التالي في <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|أحدث ركن المتطوعين]] متاح على كومنز. <h3>تحديثات الحالة الأخيرة حول ويكي الدوال</h3> <!--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-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]]: المضي قدماً نحو أولى محطات دمج ويكيبيديا المجردة * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: الدمج في ويكي الاختبار والخطة السنوية </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> a67d6dwbuicjmkgojjcrn593q6wl89t 10 2278 14354 13965 2026-08-10T13:21:06Z FuzzyBot 563 Updating to match new version of source page 14354 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3>-{A|zh-hans:志愿者;zh-hant:志工;}-角落</h3> * 下一期志愿者角将于<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|最近的志愿者角]]已发布在维基共享资源上。 <h3>维基函数最新动态</h3> <!--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-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> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: Integration on test wiki and annual plan</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> ld45qmuzytubrd782pnq5tioisb8fc8 10 2418 14352 13963 2026-08-10T13:21:05Z FuzzyBot 563 Updating to match new version of source page 14352 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3>Volontärshörnan</h3> * 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. <h3>Senaste nytt om Wikifunctions</h3> <!--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-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> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: Integration on test wiki and annual plan</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> gba73h9c1u9fuer3toogy2vc69d4235 0 2494 14392 6491 2026-08-11T01:22:44Z YoshiRulz 640 Replace string-producing function with rich text-producing one 14392 abstractwiki text/plain { "qid": "Q2440952", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z6091", "Z6091K1": "Q160381" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } l72orfo01xh5khubuyd4lt0dhpgxzcx 14403 14392 2026-08-11T04:06:42Z 99of9 614 definition & links 14403 abstractwiki text/plain { "qid": "Q2440952", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z37011", "Z37011K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37011K2": { "Z1K1": "Z6091", "Z6091K1": "Q11042" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q408" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } } ] } } } lve4sq3xit9culxraho2x2da8amp1ni 12 2505 14416 14326 2026-08-11T07:53:08Z Ameisenigel 31 Created page with "Suche nach dem Thema, zu dem du einen Artikel erstellen möchtest." 14416 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|Start]] Klicke auf das Symbol mit den drei Punkten und wähle dann "In die Zwischenablage kopieren". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|In die Zwischenablage kopieren]] Suche nach dem Thema, zu dem du einen Artikel erstellen möchtest. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Create new article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == Um einen Artikel von Grund auf zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] erkn2feuz2761kjtoe2xw7sx1jz2yqh 14418 14416 2026-08-11T07:53:27Z Ameisenigel 31 Created page with "Einen neuen Artikel erstellen" 14418 wikitext text/x-wiki <languages/> In der Abstrakten Wikipedia kannst du nur Artikel zu Themen erstellen, die bereits ein Wikidata-Datenobjekt haben. Falls das Thema noch nicht in Wikidata existiert, was du über die [[d:special:search|Suche]] feststellen kannst, befolge [[d:Special:MyLanguage/help:items#Creating a new item|diese Hilfeseite]], um ein neues Datenobjekt dafür zu erstellen. Diese Hilfeseite beschreibt zwei Methoden zum Erstellen eines neuen Artikels # Einen Artikel durch Kopieren und Einfügen erstellen # Einen Artikel von Grund auf erstellen <span id="Steps_to_create_an_article_by_copy_and_paste"></span> == Schritte zur Erstellung eines Artikels durch Kopieren und Einfügen == Suche zunächst einen bereits vorhandenen Artikel in der Abstrakten Wikipedia, der dem ähnelt, den du erstellen möchtest. Du kannst dazu die Suchfunktion nutzen und auf einen Eintrag klicken, bei dem der Zusatz "- AW" steht. Sobald du ihn gefunden hast, klicke auf "Bearbeiten". [[File:AW Help Copy Paste step 01.png|center|frameless|800px|Start]] Klicke auf das Symbol mit den drei Punkten und wähle dann "In die Zwischenablage kopieren". [[File:AW Help Copy Paste step 02.png|center|frameless|800px|In die Zwischenablage kopieren]] Suche nach dem Thema, zu dem du einen Artikel erstellen möchtest. [[File:AW Help Copy Paste step 03.png|center|frameless|800px|Einen neuen Artikel erstellen]] <span lang="en" dir="ltr" class="mw-content-ltr">This will take you to the "Create a New Abstract Article" page. Click the plus ("+") button and select "Add empty fragment".</span> [[File:AW Help Copy Paste step 04.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Add empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the three-dot menu icon within the new fragment, then select "Paste from clipboard".</span> [[File:AW Help Copy Paste step 05.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Select the copied fragment from the top row.</span> [[File:AW Help Copy Paste step 06.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Paste from clipboard</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Expand the function's details by clicking on the chevron (">") icons.</span>[[File:AW Help Copy Paste step 07.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Expand the function(s)</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Update the arguments to reflect your topic. As pictured, change the entity and location to "Utrecht" and "Netherlands". The preview will now display the updated text in the language you select (e.g., "Utrecht is a city in the Netherlands"). Do not click "Publish" just yet.</span> [[File:AW Help Copy Paste step 08.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Update arguments</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">It is highly recommended to check the preview in other languages, to ensure the abstract translates correctly. Once reviewed, click "Publish".</span> [[File:AW Help Copy Paste step 09.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Check other language</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Complete the process by entering a brief edit summary describing your changes, and click "Publish" once more.</span> [[File:AW Help Copy Paste step 10.png|center|frameless|400px|<span lang="en" dir="ltr" class="mw-content-ltr">Publish</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> The first version of your article is now live. You can click "Edit" at any time to add more information. </div> <span id="Steps_to_create_an_article_from_scratch"></span> == Schritte zur Erstellung eines Artikels von Grund auf == Um einen Artikel von Grund auf zu erstellen, kannst du auf [[Special:CreateAbstract|Einen neuen Abstrakten Artikel erstellen]] gehen. [[File:aw-tutorial-step-1.png|center|frameless|800px|Wähle ein Thema aus]] Gib ein Thema ein und klicke auf „Erstellen“. [[File:aw-tutorial-step-2.png|center|frameless|800px|Leerer abstrakter Artikel]] Du gelangst zu einem neuen Bildschirm. Auf der rechten Seite siehst Du die Vorschau in der ausgewählten Sprache, auf der linken Seite den zusammenfassenden Inhalt. [[File:aw-tutorial-step-3.png|center|frameless|800px|Klicke auf das Pluszeichen, um ein Fragment hinzuzufügen.]] Klicke im linken Bereich auf die Plus-Schaltfläche, um ein neues Fragment hinzuzufügen. Zunächst fügen wir ein leeres Fragment hinzu. [[File:aw-tutorial-step-4.png|center|frameless|800px|Ein leeres Fragment]] Das sieht dann so aus und zeigt einen Funktionsaufruf, ohne dass eine Funktion ausgewählt ist. Wir klicken auf das Symbol neben dem roten Text „Funktion auswählen“. [[File:aw-tutorial-step-5.png|center|frameless|800px|Funktionsauswahl geöffnet]] Dadurch wird die Funktionsauswahl geöffnet. [[File:aw-tutorial-step-6.png|center|frameless|800px|Eine Funktion auswählen]] Wir wählen eine Funktion aus. Diese muss auf Wikifunctions vorhanden sein und derzeit ein HTML-Fragment zurückgeben. In diesem Beispiel wählen wir die Funktion "Zeichenkette zu HTML", da wir damit entweder eine Zeichenkette eingeben oder eine Funktion auswählen können, die eine Zeichenkette erzeugt. [[File:aw-tutorial-step-7.png|center|frameless|800px|Ausgewählte Funktion "Zeichenkette zu HTML"]] Wir haben nun eine Funktion ausgewählt. Wir erhalten Felder für die Argumente. Anstatt eine Zeichenkette einzugeben, möchten wir eine weitere Funktion hinzufügen. [[File:aw-tutorial-step-8.png|center|frameless|800px|Ändern des Modus des Arguments]] Dazu ändern wir den Modus des Arguments mit dem Namen Zeichenkette, indem wir auf die drei Punkte neben Zeichenkette klicken. Dadurch können wir vom aktuellen Modus Literal zu einem Funktionsaufruf wechseln. [[File:aw-tutorial-step-9.png|center|frameless|800px|Die innere Funktion auswählen]] Hier können wir nun eine Funktion auswählen, die eine Zeichenkette zurückgibt. [[File:aw-tutorial-step-10.png|center|frameless|800px|Eine Funktion auswählen, die eine Zeichenkette zurückgibt]] Wir wählen die Funktion "Instanziierungssatz ohne Artikel" -- eine Funktion, die Sätze wie "Paris ist eine Stadt." erzeugt. Die Auswahl der Funktion “Article-less instantiating HTML fragment” hätte es uns ermöglicht, die Funktion “Zeichenkette zu HTML” zu überspringen. [[File:aw-tutorial-step-10.png|center|frameless|800px|Argumente für die Funktion zur artikellosen Instanziierung von Fragmenten]] Nun sehen wir die Argumente dieser Funktion. Außerdem werden automatisch passende Argumente eingefügt. Dies führt zu dem Satz "Paris ist ein Paris.", da die Argumente "Entität" und "Klasse" jeweils mit dem Datenobjekt, über das wir schreiben, vorausgefüllt werden. [[File:aw-tutorial-step-11.png|center|frameless|800px|Ändern des Modus des Arguments "Klasse"]] Wir müssen den Modus des Arguments "Klasse" von einem automatisch ausgefüllten Wert (einer Argumentreferenz) auf ein Literal ändern. [[File:aw-tutorial-step-12.png|center|frameless|800px|Modus von "Klasse" wurde in Literal geändert.]] Damit haben wir nun ein Feld, um ein Wikidata-Datenobjekt für den Wert des Arguments "Klasse" auszuwählen. [[File:aw-tutorial-step-13.png|center|frameless|800px|Auswahl der Stadt als Klassenargument]] Wir wählen das Datenobjekt „Stadt“ als Klassenargument aus. [[File:aw-tutorial-step-14.png|center|frameless|800px|Der erste Satz ist erstellt.]] Sobald dies ausgewählt ist, sollte der erste Satz des Artikels fertig sein. Jetzt kannst Du auf „Veröffentlichen“ klicken und eine erste Version des Artikels ist verfügbar. Anschließend kannst Du auf „Bearbeiten“ klicken, um weitere Informationen hinzuzufügen. <span id="This_is_far_too_complicated!"></span> == Das ist viel zu kompliziert! == Ja, einverstanden. Es gibt zwei Möglichkeiten, dies zu vereinfachen: * die Benutzerfreundlichkeit verbessern * den Funktionskatalog verbessern Während sich das Entwicklungsteam der Wikimedia Foundation auf den ersten Ansatz konzentriert (und UX-Ideen stets begrüßt), kann die Community an einem umfassenderen und benutzerfreundlicheren Funktionskatalog in Wikifunctions arbeiten. Hierbei zeigt sich, dass die Benennung von Funktionen und Argumenten wichtig ist und dass wir im obigen Ablauf möglichst viele Funktionen vermeiden sollten, die einen Datentyp in einen anderen umwandeln. Aber ja, am wichtigsten ist, dass sich die Abstrakte Wikipedia derzeit in einer frühen öffentlichen Beta-Phase befindet und das Erstellen und Bearbeiten von Artikeln momentan schwierig ist. Wir müssen alle zusammenarbeiten, um dies zu verbessern. Wenn Du Ideen für neue Funktionen hast, schlage diese bitte unter [[Abstract Wikipedia:Suggested functions|Vorgeschlagene Funktionen]] vor. <span id="See_also"></span> == Siehe auch == * [[Abstract Wikipedia:Useful functions for article composition]] [[Category:Help{{#translation:}}]] 5u3f8qjxwfcipgl2d2lnh0xz8m9xlj1 10 2805 14350 13960 2026-08-10T13:21:05Z FuzzyBot 563 Updating to match new version of source page 14350 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3><span lang="en" dir="ltr" class="mw-content-ltr">Volunteer's Corners</span></h3> * 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> <h3><span lang="en" dir="ltr" class="mw-content-ltr">Recent status updates about Wikifunctions</span></h3> <!--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-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> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: Integration on test wiki and annual plan</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> lpjwb2oaud88uhvfzuchiiyh7od1u2y 4 2883 14377 11986 2026-08-10T19:47:52Z EatingCarBatteries 1378 14377 wikitext text/x-wiki {{Shortcut|Abstract:MOS}} {{Policy draft}} This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. This manual is a target, apply common sense and be aware that technical limitations may make compliance impossible or unreasonable. == Summary == {{Shortcut|Abstract:MOS/S}} We're writing... * an encyclopedia; * in all languages; * accessibly and aesthetically. == Section organization == {{Shortcut|Abstract:MOS/SO}} Because articles are linked to Wikidata items and share the same Q-number, their titles are simply the labels on Wikidata. See the [[d:help:label#Labels in other languages|guidance]] there. An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). For now, this is technically enforced by the software. == Section headings == {{Shortcut|Abstract:MOS/SH}} All section headings should be their own fragment. Section headings should: * not redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * not refer to a higher-level heading, unless doing so is shorter or clearer * not be numbered or lettered as an outline * not use question format, e.g., Languages, not What languages are spoken? * not use color, unusual fonts, markup (such as bold or italics), images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages except in ones with exceptionally limited vocabulary (e.g. Toki Pona). == Quotations == {{Shortcut|Abstract:MOS/Q}} Quotations should be used sparingly, as a quote can only be on one language, whereas an article in many. They should be used only when you would naturally use a foreign language quote. Consider paraphrasing quotations abstractly (while being aware that close paraphrasing can still violate copyright). == Media == {{Shortcut|Abstract:MOS/M}} Only media directly pertinent to the subject matter of the article should be included; remember that Abstract Wikipedia articles often have a narrower topical scope than the corresponding articles at the natural language wikis, since they are tied to Wikidata concepts. == Links == {{Shortcut|Abstract:MOS/LINK}} * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == {{Shortcut|Abstract:MOS/P}} Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. === Paragraph tags === {{Shortcut|Abstract:MOS/PTAG}} Each paragraph should have a <code><nowiki><p></nowiki></code> tag for accesibility reasons. === Spaces between sentences === {{Shortcut|Abstract:MOS/SPACES}} Be mindful of the fact that Japanese and Chinese languages do not have spaces between sentences. As such, you should use functions like [[f:Z33068]] and [[f:Z35672]] to ensure that your content is accurate in these languages. == Functions == {{Shortcut|Abstract:MOS/FUNC}} Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use functions in the literal sense of their scope. Do not use them for metaphors or abstract concepts. Just because the output in English (or any one language) is correct does not make a use acceptable. For example, only use [[f:Z26570]] for physical locations, and not for metaphorical ones. Do not use a sequence of functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. == Monolingual content == {{Shortcut|Abstract:MOS/MONO}} Monolingual content (content that can only be rendered in one language) should be avoided on Abstract Wikipedia to the greatest extent possible. (Not to be confused with [[:f:Z11|monolingual text]]; its content should simply be translated depending on the user's language.) [[Category:Abstract Wikipedia administration]] [[Category:Abstract Wikipedia draft policies and guidelines]] itp5v1sajo0n9k2lt1k23znlyla3spe 14380 14377 2026-08-10T19:51:31Z EatingCarBatteries 1378 /* Monolingual content */ 14380 wikitext text/x-wiki {{Shortcut|Abstract:MOS}} {{Policy draft}} This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. This manual is a target, apply common sense and be aware that technical limitations may make compliance impossible or unreasonable. == Summary == {{Shortcut|Abstract:MOS/S}} We're writing... * an encyclopedia; * in all languages; * accessibly and aesthetically. == Section organization == {{Shortcut|Abstract:MOS/SO}} Because articles are linked to Wikidata items and share the same Q-number, their titles are simply the labels on Wikidata. See the [[d:help:label#Labels in other languages|guidance]] there. An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). For now, this is technically enforced by the software. == Section headings == {{Shortcut|Abstract:MOS/SH}} All section headings should be their own fragment. Section headings should: * not redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * not refer to a higher-level heading, unless doing so is shorter or clearer * not be numbered or lettered as an outline * not use question format, e.g., Languages, not What languages are spoken? * not use color, unusual fonts, markup (such as bold or italics), images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages except in ones with exceptionally limited vocabulary (e.g. Toki Pona). == Quotations == {{Shortcut|Abstract:MOS/Q}} Quotations should be used sparingly, as a quote can only be on one language, whereas an article in many. They should be used only when you would naturally use a foreign language quote. Consider paraphrasing quotations abstractly (while being aware that close paraphrasing can still violate copyright). == Media == {{Shortcut|Abstract:MOS/M}} Only media directly pertinent to the subject matter of the article should be included; remember that Abstract Wikipedia articles often have a narrower topical scope than the corresponding articles at the natural language wikis, since they are tied to Wikidata concepts. == Links == {{Shortcut|Abstract:MOS/LINK}} * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == {{Shortcut|Abstract:MOS/P}} Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. === Paragraph tags === {{Shortcut|Abstract:MOS/PTAG}} Each paragraph should have a <code><nowiki><p></nowiki></code> tag for accesibility reasons. === Spaces between sentences === {{Shortcut|Abstract:MOS/SPACES}} Be mindful of the fact that Japanese and Chinese languages do not have spaces between sentences. As such, you should use functions like [[f:Z33068]] and [[f:Z35672]] to ensure that your content is accurate in these languages. == Functions == {{Shortcut|Abstract:MOS/FUNC}} Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use functions in the literal sense of their scope. Do not use them for metaphors or abstract concepts. Just because the output in English (or any one language) is correct does not make a use acceptable. For example, only use [[f:Z26570]] for physical locations, and not for metaphorical ones. Do not use a sequence of functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. == Monolingual content == {{Shortcut|Abstract:MOS/MONO}} Monolingual content (content that can only be rendered in one language) should be avoided on Abstract Wikipedia to the greatest extent possible. (Not to be confused with [[:f:Z11|monolingual text]]; its content should simply be translated depending on the user's language.) An example of this would be embedding English sentences directly into an Abstract Wikipedia page, instead of calling a function which will ''then'' generate the English. [[Category:Abstract Wikipedia administration]] [[Category:Abstract Wikipedia draft policies and guidelines]] 192kt5tbkawk2yb2vwl74fx4qdag9qu 4 3025 14372 8050 2026-08-10T19:08:38Z EatingCarBatteries 1378 draft 14372 wikitext text/x-wiki {{policy draft}} All encyclopedic content on Abstract Wikipedia must be written from a neutral point of view (NPOV), which means representing fairly, proportionately, and, as far as possible, without editorial bias, all the significant views that have been published by reliable sources on a topic. [[Category:Abstract Wikipedia administration]] qmjzi33gt6ih6yfs6f0kiqwvoy7ms4o 4 3026 14378 9293 2026-08-10T19:48:04Z EatingCarBatteries 1378 14378 wikitext text/x-wiki {{Policy draft}} On Abstract Wikipedia, notability is a test used by editors to decide whether a given topic warrants its own article. On Abstract Wikipedia, articles are technically limited to topics with Wikidata items. Wikidata requires items to meet any of [[:d:Special:MyLanguage/Wikidata:Notability|three criteria]] to be eligible for an item. Articles on Abstract Wikipedia must meet the ''second criterion'' to be considered notable. That criterion says "[the item] refers to an instance of a clearly identifiable conceptual or material entity that can be described using serious and publicly available references." If a topic already has at least one article on a language Wikipedia, it is likely to warrant its own article. Reliable sources are especially needed to prove the notability of a topic if it does not yet have an article in any language. Whether a topic has an article or not creates only an assumption, not a guarantee, that it should or should not have its own abstract article. [[Category:Abstract Wikipedia administration{{#translation:}}|Notability]] [[Category:Abstract Wikipedia draft policies and guidelines]] kayclp5h3748opfn5vlfz1uki197t70 10 3056 14353 13964 2026-08-10T13:21:05Z FuzzyBot 563 Updating to match new version of source page 14353 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3>kulupu pi jan pali</h3> * <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> <h3>sona sin pi lipu Wikiwilo</h3> <!--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-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> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: Integration on test wiki and annual plan</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> 3o0oe5u0o4rvptgy00vltz0vgt40jfq 4 3067 14376 10430 2026-08-10T19:47:21Z EatingCarBatteries 1378 14376 wikitext text/x-wiki <languages/> {{policy}} <translate> <!--T:25--> The '''deletion policy''' describes how articles, media, and other pages that do not meet the relevant criteria for content of the encyclopedia are identified and removed from Abstract Wikipedia. <!--T:26--> Deletion of an Abstract Wikipedia article removes the current version and all previous versions from public view. Page blanking can be performed (or reverted) by any user, but only administrators can perform deletion, view deleted pages, and reverse ("undelete") any deletion. All such actions (other than viewing) are recorded in the deletion log. If in doubt as to whether there is consensus to delete a page, administrators will not normally delete it. == Reasons for deletion == <!--T:27--> </translate> <!--NOTE: I've consciously chosen not to include: * content forks (should be addressed on WD, or the article repurposed if an item is misused) * articles that cannot possibly be attributed to reliable sources, including neologisms, original theories and conclusions, and hoaxes (should be addressed on WD) * Files that are unused, obsolete, or violate the non-free policy (we get our files exclusively from commons, so this might not be needed) * --> # <span class="anchor" id="1"><translate><!--T:28--> Copyright violations</translate></span> # <span class="anchor" id="2"><translate><!--T:29--> Vandalism</translate></span> # <span class="anchor" id="3"><translate><!--T:30--> Advertising or spam</translate></span> # <span class="anchor" id="4"><translate><!--T:31--> Articles for which thorough attempts to find reliable sources to verify them have failed</translate></span> # <span class="anchor" id="5"><translate><!--T:32--> Articles with subjects that fail [[<tvar name="1">Special:MyLanguage/Project:Notability</tvar>|notability guidelines]]</translate></span> # <span class="anchor" id="6"><translate><!--T:33--> Biographies of living people that fail verifiability</translate></span> # <span class="anchor" id="7"><translate><!--T:34--> Redundant or otherwise useless templates</translate></span> # <span class="anchor" id="8"><translate><!--T:35--> Categories representing over-categorization</translate></span> # <span class="anchor" id="9"><translate><!--T:36--> Any other use of the article, template, project, or user namespace that is contrary to the established separate policy for that namespace</translate></span> # <span class="anchor" id="10"><translate><!--T:37--> Articles that interfere with or cause disruption to the software that powers Abstract Wikipedia or WMF infrastructure</translate></span> # <span class="anchor" id="11"><translate><!--T:38--> Any other content not suitable for an encyclopedia</translate></span> <translate> == Processes == <!--T:39--> === Copyright violations === <!--T:40--> <!--T:41--> For legal reasons, Abstract Wikipedia cannot host copyright violations. Just because text has been converted to abstract form does not mean the author loses the copyright, unless it is a basic statement of fact. <!--T:42--> Copyright violations may be deleted by any administrator regardless of discussion. If you discover a copyright violation, report it on [[<tvar name="1">Abstract Wikipedia:Requests for deletion</tvar>|the deletion requests page]] or on [[<tvar name="2">Abstract Wikipedia:Administrators' noticeboard</tvar>|the administrators' noticeboard]]. <!--T:43--> Before deleting a page due to copyright violations, consider removing the copyright violation from the page history if any of the page content is salvageable. Also consider contacting the owner of the work and see if they are willing to release the work under an applicable license or into the public domain. === Speedy deletion === <!--T:44--> </translate> <!--NOTE: consider more strict rules when necessary--> <translate> <!--T:45--> Pages that are obvious and unambiguous violations of deletion reasons 2 through 3 and 9 through 11 are eligible for speedy deletion. Any administrator can delete any page that is eligible for speedy deletion. Non-abstract pages can be nominated for speedy deletion by using the <tvar name="1">{{tl|delete}}</tvar> template. === Deletion discussion === <!--T:46--> <!--T:47--> In all other cases, deletion occurs through a discussion at [[<tvar name="1">Abstract Wikipedia:Requests for deletion</tvar>|Abstract Wikipedia:Requests for deletion]]. The nominator of a page for deletion must inform the creator of the page upon nominating the article for deletion. If there is a consensus to remove the article, the article will be deleted, otherwise it will be kept. </translate> [[Category:Abstract Wikipedia administration{{#translation:}}|Deletion policy]] [[Category:Abstract Wikipedia policies and guidelines]] 31bl73s1vwslq8y33oojfyh75w1wa9a 3 3288 14423 14210 2026-08-11T10:46:24Z 99of9 614 /* unexpected type in Z36212 */ Reply 14423 wikitext text/x-wiki == Welcome to Abstract Wikipedia! == <div style="border:solid medium lightgrey; border-width: medium; padding: 0.3em 0.5em;"> <div class="lang-en" lang="en"> Hello, 99of9. Welcome to '''[[Abstract Wikipedia:About|Abstract Wikipedia]]'''! View the [[Abstract Wikipedia:Community portal|Community portal]] or post to the [[Abstract Wikipedia:Project chat|Project chat]] if you need help with something. Please remember to sign your messages on talk pages by typing four tildes <nowiki>(~~~~)</nowiki>; this will automatically insert your username and the date. Happy editing! </div> </div><!-- Template:Welcome -->[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 07:09, 25 May 2026 (UTC) == unexpected type in Z36212 == Hi, try to have a look [[Q1140026|here]], "The opening ceremony of Azadi Tower is unexpected type in Z36212." [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:41, 27 July 2026 (UTC) :Thanks. Good catch. I have not implemented dates in this function yet. I've added your example as a test [[:f:Z38358]]. So this will remind me to get it done. But for now, do you mind deleting that sentence until it's working? Thanks for your work! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 14:46, 27 July 2026 (UTC) ::Ok, I'm temporaly removing it [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:49, 27 July 2026 (UTC) :::I just had a go at this, but it looks like something we had working ages ago [[:f:Z35327]] has stopped working. So this might take a while! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:53, 9 August 2026 (UTC) ::::All done! It turned out the error was shallower than I thought. I've put the sentence back in. Nice informative little article - thanks! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 10:46, 11 August 2026 (UTC) == "The member of Tehran is League of Historical Cities" == Hi, I wanted to use [[f:Z36218]] in [[Q3616]] to take the property "member of", but I get the sentence above. Instead, I would expect something like "Tehran is a member of the League of Historical Cities" [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 14:20, 8 August 2026 (UTC) :PS: Can you suggest me some functions for past tence? For example in [[Q5753]] I'd like to create a paragraph about history: "Samarkand was a city of the Silk Road", "Samarkand was the capital of Timurid Empire", "Samarkand was part of Russian Empire/Bukhara's Emirate" and so on [[User:Mastrocom|Mastrocom]] ([[User talk:Mastrocom|talk]]) 17:25, 8 August 2026 (UTC) ::We haven't really made many past tense fragments yet. (Partly because as your "member of" example shows, we need to figure them out in present tense first!) Two I'm aware of are: ::* [[:f:Z37104]] ::* [[:f:Z34224]] ::--[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:37, 9 August 2026 (UTC) :::So, for example, you can make [https://www.wikifunctions.org/wiki/Z37104?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z37104%22%2C%22Z37104K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q484195%22%7D%2C%22Z37104K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P36%22%7D%2C%22Z37104K3%22%3A%22Z1002%22%7D The capital city of Timurid Empire was Samarkand.]. [[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:39, 9 August 2026 (UTC) mpe3e1qeo7nbgp5qncbnom9k6do78gl 10 4309 14351 13962 2026-08-10T13:21:05Z FuzzyBot 563 Updating to match new version of source page 14351 wikitext text/x-wiki <noinclude><languages /></noinclude> <div style="margin: auto; vertical-align:top"> <div class="mainpage_boxcontents_small"> <h3>지원자 코너</h3> * 다음 지원자 코너는 <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|가장 최근의 지원자 코너 내용]]은 공용에서 확인하실 수 있습니다. <h3>위키함수의 현황 업데이트</h3> <!--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-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> * [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-07-01|2026-07-01]]: 테스트 위키 통합 및 연간 계획 </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> e3wsjilimj3bexj1pfdf2igsq77rzp2 1198 4508 14345 12201 2026-08-10T13:21:03Z FuzzyBot 563 Importing a new version from external source 14345 wikitext text/x-wiki [[$1|2026-07-16]]: Beyond syntactic tables la2y573wuwy774zeea1e0uznxg265hv 0 4793 14422 13486 2026-08-11T10:43:23Z 99of9 614 14422 abstractwiki text/plain { "qid": "Q1140026", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M66793974" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q1140026" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q12518" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q3616" }, "Z36983K4": { "Z1K1": "Z60", "Z60K1": "en", "Z60K2": [ "Z6", "it" ] } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36218", "Z36218K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36218K2": { "Z1K1": "Z6092", "Z6092K1": "P84" }, "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": "P1435" }, "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": "P2043" }, "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": "P2048" }, "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": "P149" }, "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": "P186" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P1619" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 3ls5da0s3q3kaf07xq0nz9imyg07p0b 14424 14422 2026-08-11T10:47:02Z 99of9 614 bold title 14424 abstractwiki text/plain { "qid": "Q1140026", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M66793974" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37726", "Z37726K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q1140026" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q12518" }, "Z36983K3": { "Z1K1": "Z6091", "Z6091K1": "Q3616" }, "Z36983K4": { "Z1K1": "Z60", "Z60K1": "en", "Z60K2": [ "Z6", "it" ] } }, "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": "P84" }, "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": "P1435" }, "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": "P2043" }, "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": "P2048" }, "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": "P149" }, "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": "P186" }, "Z36218K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z35672", "Z35672K1": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z37104", "Z37104K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z37104K2": { "Z1K1": "Z6092", "Z6092K1": "P1619" }, "Z37104K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } sjipijp30fl75pnnszps06x17ffgtij 0 4794 14339 14209 2026-08-10T12:55:23Z 99of9 614 needs to be abstract, not English only 14339 abstractwiki text/plain { "qid": "Q3616", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z36678", "Z36678K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36678K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M82910237" }, "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": "Q5119" }, "Z37011K3": { "Z1K1": "Z6091", "Z6091K1": "Q794" }, "Z37011K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z37726K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" } }, { "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": "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": "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": "Z32839", "Z32839K1": { "Z1K1": "Z6091", "Z6091K1": "Q4989906" }, "Z32839K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z36831", "Z36831K1": { "Z1K1": "Z7", "Z7K1": "Z36983", "Z36983K1": { "Z1K1": "Z6091", "Z6091K1": "Q1140026" }, "Z36983K2": { "Z1K1": "Z6091", "Z6091K1": "Q4989906" }, "Z36983K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z36983K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z36831K2": [ "Z6091", { "Z1K1": "Z18", "Z18K1": "Z825K1" } ] } ] } } } 6ikl6wpmcwswtq425qke3lyri1un876 5 4980 14398 13886 2026-08-11T02:42:27Z YoshiRulz 640 /* Correcting common misconceptions, possibly needs a separate page AW:NOT */ re: diversity of syntactic rules 14398 wikitext text/x-wiki == Correcting common misconceptions, possibly needs a separate page AW:NOT == Inspired by [[meta:Requests for comment/The future of Abstract Wikipedia]] and the comments on it. Here are some misconceptions I've drawn out from the subtext (plus a couple extra I heard from Wikimania participants): * AW has been going for 6 years and has little to show for it! *: {{SITENAME}} launched for public contributions on {{#formatdate:2026-03-19|ISO 8601}}. Due to the complexity of the project compared to a traditional wikitext wiki, there will be significantly more time before substantial content is on this platform. The bulk of the work is happening at Wikifunctions, where the community is creating and translating new functions. And Wikifunctions itself wasn't able to handle Lexemes until {{#formatdate:2024-10-25|ISO 8601}}. * After a collaboration between Google.org and the AW team in 2022, the outgoing Googlers predicted AW's failure, and it's come true *: The Googlers' criticisms were mostly predicated on the idea that {{SITENAME}} should be a monolith encompassing the NLG infrastructure as well as all the articles. The WMF decided it was worth building Wikifunctions first, so that it could attract its own community and become [[f:WF:NOT#Wikifunctions_is_not_(only)_the_boiler_room_for_Abstract_Wikipedia|a valuable project in its own right]]. * The functions used in abstract articles are deprecated / known to be untranslatable in certain languages *: That will continue to happen (see [section re: deprecation]), and it's not a huge problem. Wikidata uses deprecated properties a lot, and other wikis are full of deprecated templates and article message boxes. When a limitation is discovered in an <abbr title="natural language generation">NLG</abbr> function, it should absolutely be deprecated and replaced with a better one, but the old function can remain in place in the meantime and be useful in the languages where it was working. * Turning each statement on a Wikidata Item into a sentence will not result in a useful article; why not build a reader mode for Wikidata? *: There's [https://reasonator.toolforge.org/#/Q42 only so much visual flair] you can add to a list of RDF triples. If you try building it into a story, you'll have to start [https://autodesc.toolforge.org/?q=Q42&lang=en&mode=long&links=wiki&format=html introducing <abbr title="natural language generation">NLG</abbr> aspects], which brings us to {{SITENAME}}. * I clicked Special:Random and all I got was two sentences and a picture... *: Yes, most articles in any edition aren't as complete or high-quality as the best articles. Like regular wiki articles, abstract articles can be improved by editing. * I found an article which is grammatically sound but factually inaccurate! I thought these were backed by Wikidata? *: Wikidata [[wikidata:Wikidata:General disclaimer|has no guarantee of validity]], same as every other Wikimedia project. If there is an issue with Wikidata, you're encouraged to [[wikidata:Help:Items#Editing_an_item_page|contribute and correct the error]]! Changes will take a while to propagate through the various caches. It may also be that Wikidata already had the correct information, but it's represented using a combination of [[d:Help:Q|qualifiers]] which the functions don't recognise. Contributions there are welcome too! * This output is far from fluent English, and in some places it's ungrammatical; how is this useful to enwp? *: First of all, being useful to the English Wikipedia is not one of the project's goals. enwp has a large base of contributors who write many articles in fluent English. This isn't true for all language editions, where even something that would be considered a stub on enwp can be valued because there would otherwise be nothing at all. And finally, when the output in English (or any other language) is stilted, you can go to Wikifunctions and fix it! * If abstract articles don't produce good English, the output in other languages must be far worse *: At the moment this is a sound generalisation. Many of the functions to render abstract content in natural language are first configured in English. Once a function is configured in any language, the quality of prose depends on the quality and complexity of the implementation in that language. * Some articles may be worse than others, but until they're all good, any Wikipedia would object to having AW integration enabled *: No Wikimedia project is perfect, all suffering from low quality content to some degree. {{SITENAME}} articles work on an opt-in basis, meaning that communities, not the WMF or {{SITENAME}} editors, choose which articles to include in their wikis. For an example of this system, see [[testwiki:Special:CommunityConfiguration/AbstractWikiOptedInArticles|this special page on the Wikipedia Test wiki]]. 'Integration' in this context means that the special page is enabled on your wiki.<br>Editors will also be able to create a local article using the abstract article as a starting point, once integration is enabled, or they could use individual functions in an existing article via [[f:Wikifunctions:Embedded_function_calls|embedded function calls]]. * An abstract article can't be mapped to every language because there are huge differences in the way languages divide sentences into parts of speech (syntax) *: Human languages can be very different (even without considering "constructed" languages), but at their core they are methods of ''communication'', where an utterance/sentence is a message which encodes some information that the speaker/writer wants to convey. This is the 'semantic' part: the objects and concepts being referred to and the relationships between them. (There are a few concepts which are hard to translate, but not impossible. See [section re: untranslatability].) The rest, the 'syntax' and 'grammar', is where the differences are.<br>{{SITENAME}}'s content is "abstract" in the sense that it contains only the semantic information of a sentence; in order to actually produce text, it relies on a complex set of <abbr title="natural language generation">NLG</abbr> algorithms from Wikifunctions. These algorithms are each dedicated to a particular language/dialect in order for them to best handle the grammatical rules of that language. * Other NLG projects have tried and failed to solve the problem of when to include "the" (the definite article) *: This idea seems to have stemmed from a misunderstanding of an anecdote in [[f:WF:Status_updates/2026-06-19|Wikifunctions' newsletter]], where one of [[d:Q5593683|<abbr title="Grammatical Framework">GF</abbr>]]'s developers is said to have called the definite article problem <q>one of the hardest puzzles they had to solve</q>. That issue of the newsletter set out the problem as it applied to WF, and [[f:Z36580|a heuristic solution]] was provided [[f:WF:Project_chat/Archive/2026/06#Wikifunctions_&_Abstract_Wikipedia_Newsletter_#253_is_out:_The_or_not_the,_this_is_(the?)_question|within a day]]. That solution is of course imperfect, but perfection was never the goal of {{SITENAME}}. * Some concepts are simply untranslatable; languages are in some way limited by culture/worldview *: This is an idea linguists call "[[d:Q10359037|linguistic relativity]]", though historically the debate has been over whether ''worldview'' is limited by ''language''. Both that conjecture and the reverse turn out to be false in most aspects. On the idea of 'untranslatability', [[w:en:Untranslatability|enwp says]] <q>difficulty of translation does not always carry deep linguistic relativity implications; denotation [i.e. identification of concepts by words] can virtually always be translated, given enough [[d:Q1095194|circumlocution]]</q>. For example, the label of [[d:Property:P10|the Wikidata property 'video']] in {{#language:kcg}} is '<span lang="kcg">ghwughwu a̱guguut</span>' which means something like "movement of shadows".^{[TODO have someone confirm that, or find a better example]} * AW is trying to create an IAL / universal language *: While IALs or areal auxlangs could be target languages, the LISP-like syntax does not itself constitute an auxiliary language. Natural language text is considered the end product of work on an abstract article. * The foundation of AW is a model of linguistics which is discredited by the current consensus of linguists *: {{SITENAME}} as a platform does not assume any particular model or theory. All the linguistic information and processing is stored in Wikidata and Wikifunctions, so even if that were the case, the foundations could be swapped out and the project salvaged. This idea may have arisen from [section re: definite article]. See also [section re: known bad functions]. * By accepting contributions, AW leeches volunteer man-hours from sister projects *: We volunteers own the time we spend. If we consider it best spent here, we are obviously aligned with the aims and viability of this project. Closing it would not encourage us to contribute more. Some of us have contributed to Wikimedia projects for decades, and the variety of projects or contributions is one of the things that can help us to motivate and maintain such commitment. {{SITENAME}} relies on the content in Wikifunctions and Wikidata to produce output, so it pushes contributors to those projects. * Volunteer time would be better spent using [https://www.mediawiki.org/wiki/Extension:ContentTranslation Extension:ContentTranslation] *: Since article integration hasn't been rolled out yet, this is definitely true for a lone editor with the goal of making knowledge accessible to more people, and it will likely be true for a while. But if all goes well, {{SITENAME}} (or rather, Wikifunctions) will accrue the functions needed to generate text in many languages. Then that lone editor will have the choice between translating a high-quality article into one language, or converting some of it into an abstract article which is then available in many languages. * The server resources would be better spent on training LLMs for under-resourced languages *: Other organisations already do this, so WMF-funded machine translation development would be duplicative. Also, it isn't in the competency area of the Wikimedia movement, which is volunteer-led content. The suggestion to "just" train LLMs for all the under-resourced languages doesn't account for the scale of the problem either: At time of writing, ~250 languages are offered in Google Translate, while there are several ''thousand'' living languages. * It was already possible to create formulaic articles from Wikidata using templates and/or modules, an entirely new system is unnecessary *: Certainly it was possible, some Wikipedias did build systems which failed and others built systems which worked and are still in use. Like the current {{SITENAME}}, these had a high learning curve for those looking to contribute to the system, but unlike {{SITENAME}} they are all limited to their own wikis. * If it succeeds, AW will bring about a sort of "digital neo-colonialism" in which small language communities get enwp translated into their language *: {{SITENAME}} is a blank slate, not based on enwp. It uses (via Wikifunctions) a multilingual labelling system similar to Wikidata, enabling volunteers to translate the interface which other volunteers can then use to edit articles. We will continue working at lowering the barriers to entry, so that readers of small wikis can feel comfortable clicking <q>{{int:wikilambda-abstract-tab-edit}}</q> and sharing the knowledge which is most important to them.<br>On the subject of [[w:electronic colonialism|electronic colonialism]]: This is a significant problem for the Wikimedia movement as a whole, not just {{SITENAME}}. For example, for our language codes we use [[w:ISO 639]], originally developed by SIL Global (an organisation derived from the evangelical missionary group Summer Institute of Linguistics which has a goal of translating Christian Bibles into many languages^[relevance?]). By foregrounding the volunteer editors of a target language and enabling self-governance of the individual wikis, these sociopolitical influences may be mitigated. * When a new set of NLG functions emerges to fix the flaws of the previous set, every abstract article will need to be rewritten *: Yes, that process is what's known as a 'deprecation cycle' and it's a part of any serious software project. Other wikis will have encountered something similar, for example the [[w:en:WP:PARSOIDMIGRATION|migration to Parsoid]] and the maintenance tasks it created.<br>Regarding flawed NLG functions specifically: The old function(s) can remain in place and be useful in the languages where they were working, until a replacement exists and an editor swaps it out. And we can be more confident that the replacement(s) will last, because they will have been born from community discussion and fortified with a growing corpus of test cases for catching regressions. * Even the most fluent machine-generated text will remain soulless compared to a human-written article, so why bother? *: The point of writing an encyclopedia is conveying factual information, and for {{SITENAME}}, specifically in the languages where human resources are scarce; the quality of prose is a separate concern, addressed at [[abstract:WikiProject Encyclopedic Quality]]. The option of having a human write the whole article will always be there, see [section on article integration]. * Some languages have a lot of inflected forms of words; just storing them on Wikidata is hard, to say nothing of using them in Wikifunctions *: Those languages with many inflections tend to also have consistent rules for how to generate them (which makes sense when you remember that humans find rote memorisation hard, but learning patterns easy). Programmers can use those inflection rules to "compress" the list. * AW is an automated/machine translation service, something that everyone else is now using LLMs for *: {{SITENAME}} does not translate between languages. It uses community-defined algorithms to transform an ''abstract'' representation of concepts into [[d:Q2568869|rich text]] in a particular written language ([[d:Q1513879|<abbr title="natural language generation">NLG</abbr>]]).<br>The reason why AW uses functions it that it gives users complete control over how content is displayed and translated. Whereas LLMs can be unpredictable, hard to properly diagnose issues, and very difficult for volunteers to fix. * Reading AW requires running huge JavaScript blobs in your browser *: When articles are eventually selected for display in language editions of Wikipedia, the reading experience will be similar to any other page on that wiki. The AW site is primarily designed for content development. The editor is currently a 0.5 MiB download. The site itself is also under development, so the current state does not necessarily represent a long-term ideal. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 02:25, 28 July 2026 (UTC) :Thanks, good summary. Should we prepare answers individually here (separate sections?) then add them to the page when done? --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 02:51, 28 July 2026 (UTC) ::You're welcome to chop up by above comment for organisational purposes. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 03:00, 28 July 2026 (UTC) :::Okay, I'll write as though it's the answer, anyone should feel free to overwrite and improve. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 03:29, 28 July 2026 (UTC) :re: assignment of language codes, I can see how that process was Eurocentric, but I don't see what negative impact it's had on those communities who didn't get a memorable code. They're 2- and 3-letter identifiers used mainly by machines. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 22:42, 28 July 2026 (UTC) ::Well, it depends on what you call 'negative'. The main controversies have been about [[w:lumpers and splitters|lumping and splitting]]: <code>zh</code> encompasses a wide range of languages, whereas <code>nb</code> and <code>nn</code> are mutually-intelligible varieties of the same language. It doesn't end up being that big a deal since as you say mostly humans don't need to encounter the codes all the time, and there are ways to append the codes to make them more specific. And while WMF bases codes on ISO 639, there are custom decisions like <code>be-tarask</code>. Meanwhile, Abstract Wikipedia uses Wikifunctions identifiers, which are yet a third system. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 22:47, 28 July 2026 (UTC) See also [[f:WF:NOT]]. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:30, 28 July 2026 (UTC) 4gwmlkob850f85ymsb29tre9h224jdo 1198 5068 14344 13956 2026-08-10T13:21:03Z FuzzyBot 563 Importing a new version from external source 14344 wikitext text/x-wiki [[$1|2026-07-29]]: Abstract Wikipedia at Wikimania 48kzqlcenw86oxd5nwiy0a7ucd1qp62 4 5115 14384 14157 2026-08-10T19:59:38Z EatingCarBatteries 1378 14384 wikitext text/x-wiki = Abstract Wikipedia for Interested Wikipedia Communities = This guide is for Wikipedia language communities considering whether to integrate abstract articles. It explains how Abstract Wikipedia could support your community, how integration of abstract articles works, and what your community may need to do. == What is Abstract Wikipedia, and how could it support your community? == It is difficult for each Wikipedia community to create local articles on every topic their readers might be interested in reading about. Abstract Wikipedia lets contributors across language communities work together on one shared, language-independent article that can be rendered in multiple languages. In this way, work on one article can help fill gaps across several Wikipedias. Contributors create and maintain articles in a language-independent form using data from Wikidata and functions from Wikifunctions. This allows contributors from different language communities to improve the same underlying article together. Abstract articles can then be rendered as text in any language that has the language specific functions for it. For your Wikipedia, abstract articles could fill selected gaps where no local article exists. Your community could also make knowledge about its region, culture, and areas of expertise available in other languages. Learn more about [[Abstract Wikipedia:About|Abstract Wikipedia]]. === A few important distinctions === Abstract Wikipedia is: * '''Not a translation tool:''' Abstract articles are created in a language-independent form rather than translated from a source language into a target language. * '''Not generative AI writing:''' Wikimedia contributors create and maintain the content, data, and functions used to produce the text. * '''Not a replacement for your Wikipedia:''' Abstract articles can fill selected gaps, but never overwrite locally written articles. == Where is Abstract Wikipedia today? == Abstract Wikipedia launched as an early beta in March 2026. Contributors are creating initial abstract articles and testing how they render in different languages. Article quality and language support currently vary, and not every article is ready for integration. At this stage, abstract articles work best for structured, fact-based topics such as cities, countries, and species. == How does integration work? == An integrated abstract article would appear in your Wikipedia in your language where no local article exists and your community decided to fill this gap with an abstract article. The integration model gives your communities full control over which abstract articles they use: * A locally written article always takes precedence. * Your community chooses which abstract articles to integrate, article by article. * An integrated article can be removed at any time. * Readers can see that the content comes from Abstract Wikipedia and when it was last updated. * Editors can improve the underlying abstract article or create a local article to replace it. Learn more about [[Help:Abstract articles|abstract articles and how the integration works.]] == What can your community explore first? == ==== Review existing articles ==== Browse some abstract articles to see how they look: * Country: [[Q408|Australia]] * City: [[Q17198982|Diablo]] * Species: [[Q123471046|Tujiaaspis]] * [[Special:AllPages|Browse more abstract articles]] '''Identify potentially useful article gaps''' You can use the Abstract data tool to compare existing abstract articles with articles missing from your Wikipedia to identify gaps that would be useful to your readers. Please note, some listed articles might still be early drafts and not ready for integration yet. '''Contribute knowledge from your community''' Your community can also create or improve abstract articles, making that knowledge available to readers in other languages. See [[Help:How to create an article|how to write abstract articles]]. == What work might be needed to integrate abstract articles? == The main work is ensuring that selected articles render clearly and correctly in your language. What is needed will depend on the language support already available. {| class="wikitable" |'''Area''' |'''What might be needed''' |'''Who can help''' |'''Learn more''' |- |Wikidata |Add or improve the labels and  lexeme data needed by the selected articles. |Language speakers comfortable contributing to Wikidata | * [https://abstract-data.toolforge.org/ Abstract data tool] provides you an overview of which data is missing for your languages for a given article. * [[f:Wikifunctions:Creating_lexemes_in_Wikidata|Creating lexemes in Wikidata]] * [[d:Wikidata:Lexicographical_data/Documentation|Lexicographical data · Lexeme documentation]] |- |Wikifunctions |Test and improve the functions that turn abstract content into natural sentences in your language. |Language speakers with strong understanding of grammar and basic technical knowledge | * [[f:Wikifunctions:Introduction|Introduction to Wikifunctions]] * [[f:Wikifunctions:Working_with_Configuration_of_functions_for_given_languages|Creating language specific functions]] |- |Language and content review |Review the rendered articles for clear language, and alignment with local policies before integrating articles. |Local-language speakers and admins | * [[Help:Abstract articles|Abstract Articles]] |} We would be glad to support your community through this process. == Pre-requisites == * Start a discussion on your village pump or an on-wiki RFC (Request for Comment) to gather community feedback on integrating Abstract articles * Identify a contact person from your community for this pilot * Identify 3-4 community members interested in improving lexemes on Wikidata * Identify 2-3 community members with a deep knowledge of the grammar of your language, to support Lexemes and Wikifunctions * Commit to attend 4-5 workshops focused on Lexemes and Wikifunctions in the next 3-6 months * At-least 1 community member with a working knowledge of English or one of the languages which has an interpreter in the Organization communications translators group == Expression of Interest == Once you have completed the above steps, submit your interest to join the pilot. Currently, we are looking for around 2-3 language communities. Please leave a message in the [[Abstract Wikipedia:Project chat|Project Chat]]. == Get help and learn more == * [[Abstract Wikipedia:Project chat|Ask a question in the project chat]] * [[f:Wikifunctions:Status_updates|See the latest project updates]] * [[Help:How to create an article|Contribute to Abstract Wikipedia]] * [[f:Wikifunctions:Introduction|Contribute to Wikifunctions]] == Participating pilot communities == * [[Category:Abstract Wikipedia basic information]] ppybhhrz3xr88e0b36fa5tghmn0stt8 14420 14384 2026-08-11T09:38:10Z SGill (WMF) 654 14420 wikitext text/x-wiki This guide is for Wikipedia language communities considering whether to integrate abstract articles. It explains how Abstract Wikipedia could support your community, how integration of abstract articles works, and what your community may need to do. == What is Abstract Wikipedia, and how could it support your community? == It is difficult for each Wikipedia community to create local articles on every topic their readers might be interested in reading about. Abstract Wikipedia lets contributors across language communities work together on one shared, language-independent article that can be rendered in multiple languages. In this way, work on one article can help fill gaps across several Wikipedias. Contributors create and maintain articles in a language-independent form using data from Wikidata and functions from Wikifunctions. This allows contributors from different language communities to improve the same underlying article together. Abstract articles can then be rendered as text in any language that has the language specific functions for it. For your Wikipedia, abstract articles could fill selected gaps where no local article exists. Your community could also make knowledge about its region, culture, and areas of expertise available in other languages. Learn more about [[Abstract Wikipedia:About|Abstract Wikipedia]]. === A few important distinctions === Abstract Wikipedia is: * '''Not a translation tool:''' Abstract articles are created in a language-independent form rather than translated from a source language into a target language. * '''Not generative AI writing:''' Wikimedia contributors create and maintain the content, data, and functions used to produce the text. * '''Not a replacement for your Wikipedia:''' Abstract articles can fill selected gaps, but never overwrite locally written articles. == Where is Abstract Wikipedia today? == Abstract Wikipedia launched as an early beta in March 2026. Contributors are creating initial abstract articles and testing how they render in different languages. Article quality and language support currently vary, and not every article is ready for integration. At this stage, abstract articles work best for structured, fact-based topics such as cities, countries, and species. == How does integration work? == An integrated abstract article would appear in your Wikipedia in your language where no local article exists and your community decided to fill this gap with an abstract article. The integration model gives your communities full control over which abstract articles they use: * A locally written article always takes precedence. * Your community chooses which abstract articles to integrate, article by article. * An integrated article can be removed at any time. * Readers can see that the content comes from Abstract Wikipedia and when it was last updated. * Editors can improve the underlying abstract article or create a local article to replace it. Learn more about [[Help:Abstract articles|abstract articles and how the integration works.]] == What can your community explore first? == ==== Review existing articles ==== Browse some abstract articles to see how they look: * Country: [[Q408|Australia]] * City: [[Q17198982|Diablo]] * Species: [[Q123471046|Tujiaaspis]] * [[Special:AllPages|Browse more abstract articles]] '''Identify potentially useful article gaps''' You can use the Abstract data tool to compare existing abstract articles with articles missing from your Wikipedia to identify gaps that would be useful to your readers. Please note, some listed articles might still be early drafts and not ready for integration yet. '''Contribute knowledge from your community''' Your community can also create or improve abstract articles, making that knowledge available to readers in other languages. See [[Help:How to create an article|how to write abstract articles]]. == What work might be needed to integrate abstract articles? == The main work is ensuring that selected articles render clearly and correctly in your language. What is needed will depend on the language support already available. {| class="wikitable" |'''Area''' |'''What might be needed''' |'''Who can help''' |'''Learn more''' |- |Wikidata |Add or improve the labels and  lexeme data needed by the selected articles. |Language speakers comfortable contributing to Wikidata | * [https://abstract-data.toolforge.org/ Abstract data tool] provides you an overview of which data is missing for your languages for a given article. * [[f:Wikifunctions:Creating_lexemes_in_Wikidata|Creating lexemes in Wikidata]] * [[d:Wikidata:Lexicographical_data/Documentation|Lexicographical data · Lexeme documentation]] |- |Wikifunctions |Test and improve the functions that turn abstract content into natural sentences in your language. |Language speakers with strong understanding of grammar and basic technical knowledge | * [[f:Wikifunctions:Introduction|Introduction to Wikifunctions]] * [[f:Wikifunctions:Working_with_Configuration_of_functions_for_given_languages|Creating language specific functions]] |- |Language and content review |Review the rendered articles for clear language, and alignment with local policies before integrating articles. |Local-language speakers and admins | * [[Help:Abstract articles|Abstract Articles]] |} We would be glad to support your community through this process. == Pre-requisites == * Start a discussion on your village pump or an on-wiki RFC (Request for Comment) to gather community feedback on integrating Abstract articles * Identify a contact person from your community for this pilot * Identify 3-4 community members interested in improving lexemes on Wikidata * Identify 2-3 community members with a deep knowledge of the grammar of your language, to support Lexemes and Wikifunctions * Commit to attend 4-5 workshops focused on Lexemes and Wikifunctions in the next 3-6 months * At-least 1 community member with a working knowledge of English or one of the languages which has an interpreter in the Organization communications translators group == Expression of Interest == Once you have completed the above steps, submit your interest to join the pilot. Currently, we are looking for around 2-3 language communities. Please leave a message in the [[Abstract Wikipedia:Project chat|Project Chat]]. == Get help and learn more == * [[Abstract Wikipedia:Project chat|Ask a question in the project chat]] * [[f:Wikifunctions:Status_updates|See the latest project updates]] * [[Help:How to create an article|Contribute to Abstract Wikipedia]] * [[f:Wikifunctions:Introduction|Contribute to Wikifunctions]] == Participating pilot communities == * [[Category:Abstract Wikipedia basic information]] nkubuy3msn5bs6hh8p0jae15yuc7h6w 14421 14420 2026-08-11T09:49:18Z SGill (WMF) 654 /* Participating pilot communities */ 14421 wikitext text/x-wiki This guide is for Wikipedia language communities considering whether to integrate abstract articles. It explains how Abstract Wikipedia could support your community, how integration of abstract articles works, and what your community may need to do. == What is Abstract Wikipedia, and how could it support your community? == It is difficult for each Wikipedia community to create local articles on every topic their readers might be interested in reading about. Abstract Wikipedia lets contributors across language communities work together on one shared, language-independent article that can be rendered in multiple languages. In this way, work on one article can help fill gaps across several Wikipedias. Contributors create and maintain articles in a language-independent form using data from Wikidata and functions from Wikifunctions. This allows contributors from different language communities to improve the same underlying article together. Abstract articles can then be rendered as text in any language that has the language specific functions for it. For your Wikipedia, abstract articles could fill selected gaps where no local article exists. Your community could also make knowledge about its region, culture, and areas of expertise available in other languages. Learn more about [[Abstract Wikipedia:About|Abstract Wikipedia]]. === A few important distinctions === Abstract Wikipedia is: * '''Not a translation tool:''' Abstract articles are created in a language-independent form rather than translated from a source language into a target language. * '''Not generative AI writing:''' Wikimedia contributors create and maintain the content, data, and functions used to produce the text. * '''Not a replacement for your Wikipedia:''' Abstract articles can fill selected gaps, but never overwrite locally written articles. == Where is Abstract Wikipedia today? == Abstract Wikipedia launched as an early beta in March 2026. Contributors are creating initial abstract articles and testing how they render in different languages. Article quality and language support currently vary, and not every article is ready for integration. At this stage, abstract articles work best for structured, fact-based topics such as cities, countries, and species. == How does integration work? == An integrated abstract article would appear in your Wikipedia in your language where no local article exists and your community decided to fill this gap with an abstract article. The integration model gives your communities full control over which abstract articles they use: * A locally written article always takes precedence. * Your community chooses which abstract articles to integrate, article by article. * An integrated article can be removed at any time. * Readers can see that the content comes from Abstract Wikipedia and when it was last updated. * Editors can improve the underlying abstract article or create a local article to replace it. Learn more about [[Help:Abstract articles|abstract articles and how the integration works.]] == What can your community explore first? == ==== Review existing articles ==== Browse some abstract articles to see how they look: * Country: [[Q408|Australia]] * City: [[Q17198982|Diablo]] * Species: [[Q123471046|Tujiaaspis]] * [[Special:AllPages|Browse more abstract articles]] '''Identify potentially useful article gaps''' You can use the Abstract data tool to compare existing abstract articles with articles missing from your Wikipedia to identify gaps that would be useful to your readers. Please note, some listed articles might still be early drafts and not ready for integration yet. '''Contribute knowledge from your community''' Your community can also create or improve abstract articles, making that knowledge available to readers in other languages. See [[Help:How to create an article|how to write abstract articles]]. == What work might be needed to integrate abstract articles? == The main work is ensuring that selected articles render clearly and correctly in your language. What is needed will depend on the language support already available. {| class="wikitable" |'''Area''' |'''What might be needed''' |'''Who can help''' |'''Learn more''' |- |Wikidata |Add or improve the labels and  lexeme data needed by the selected articles. |Language speakers comfortable contributing to Wikidata | * [https://abstract-data.toolforge.org/ Abstract data tool] provides you an overview of which data is missing for your languages for a given article. * [[f:Wikifunctions:Creating_lexemes_in_Wikidata|Creating lexemes in Wikidata]] * [[d:Wikidata:Lexicographical_data/Documentation|Lexicographical data · Lexeme documentation]] |- |Wikifunctions |Test and improve the functions that turn abstract content into natural sentences in your language. |Language speakers with strong understanding of grammar and basic technical knowledge | * [[f:Wikifunctions:Introduction|Introduction to Wikifunctions]] * [[f:Wikifunctions:Working_with_Configuration_of_functions_for_given_languages|Creating language specific functions]] |- |Language and content review |Review the rendered articles for clear language, and alignment with local policies before integrating articles. |Local-language speakers and admins | * [[Help:Abstract articles|Abstract Articles]] |} We would be glad to support your community through this process. == Pre-requisites == * Start a discussion on your village pump or an on-wiki RFC (Request for Comment) to gather community feedback on integrating Abstract articles * Identify a contact person from your community for this pilot * Identify 3-4 community members interested in improving lexemes on Wikidata * Identify 2-3 community members with a deep knowledge of the grammar of your language, to support Lexemes and Wikifunctions * Commit to attend 4-5 workshops focused on Lexemes and Wikifunctions in the next 3-6 months * At-least 1 community member with a working knowledge of English or one of the languages which has an interpreter in the Organization communications translators group == Expression of Interest == Once you have completed the above steps, submit your interest to join the pilot. Currently, we are looking for around 2-3 language communities. Please leave a message in the [[Abstract Wikipedia:Project chat|Project Chat]]. == Get help and learn more == * [[Abstract Wikipedia:Project chat|Ask a question in the project chat]] * [[f:Wikifunctions:Status_updates|See the latest project updates]] * [[Help:How to create an article|Contribute to Abstract Wikipedia]] * [[f:Wikifunctions:Introduction|Contribute to Wikifunctions]] == Participating pilot communities == *[[Abstract Wikipedia:For interested communities/Malayalam|Malayalam]] *[[Abstract Wikipedia:For interested communities/Dagbanli|Dagbanli]] [[Category:Abstract Wikipedia basic information]] cb5e6rmmz4slzeuzzfpvncukcmu6fsh 1198 5167 14343 2026-08-10T13:21:03Z FuzzyBot 563 Importing a new version from external source 14343 wikitext text/x-wiki [[$1|2026-08-05]]: Congratulations Jules*: An apple is a fruit qfnc1k6ddi7ptra9lpngcd4r22um90b 0 5168 14371 2026-08-10T17:18:10Z VivianIsBee 793 Created page with "{ "qid": "Q106852836", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z32982", "Z32982K1": {..." 14371 abstractwiki text/plain { "qid": "Q106852836", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z32982", "Z32982K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32982K2": { "Z1K1": "Z6091", "Z6091K1": "Q571" }, "Z32982K3": { "Z1K1": "Z6091", "Z6091K1": "Q24925" }, "Z32982K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } g5j5h9m0g8p5vzvgp97vbjgpcsqiden 14 5169 14373 2026-08-10T19:13:14Z EatingCarBatteries 1378 Created page with "[[Category:Abstract Wikipedia administration| ]]" 14373 wikitext text/x-wiki [[Category:Abstract Wikipedia administration| ]] 1it13z9wcbth1h9awcflwox9ixwkwdc 14 5170 14379 2026-08-10T19:48:27Z EatingCarBatteries 1378 Created page with "[[Category:Abstract Wikipedia policies and guidelines| ]]" 14379 wikitext text/x-wiki [[Category:Abstract Wikipedia policies and guidelines| ]] c8o2bbxa5zw92bod8mcqae1ozzbnb8a 14 5171 14381 2026-08-10T19:58:47Z EatingCarBatteries 1378 Created page with "[[Category:Abstract Wikipedia administration| ]]" 14381 wikitext text/x-wiki [[Category:Abstract Wikipedia administration| ]] 1it13z9wcbth1h9awcflwox9ixwkwdc 0 5172 14385 2026-08-10T22:11:06Z B.Zsolt 1598 Created page with "{ "qid": "Q982364", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z18", "Z18K1": "Z8..." 14385 abstractwiki text/plain { "qid": "Q982364", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32962", "Z32962K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32962K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 2q3t69yd8ipbwdn6i3xkn69bnl4ljla 0 5173 14386 2026-08-10T22:32:30Z Back ache 7101 Created page with "{ "qid": "Q124354356", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M194269038" }, "Z38053K2": { "Z1K1": "Z18", "Z1..." 14386 abstractwiki text/plain { "qid": "Q124354356", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z38053", "Z38053K1": { "Z1K1": "Z310", "Z310K1": "M194269038" }, "Z38053K2": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z38053K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } cdqkimhopr6l4xs26js59ibjmajwo94 4 5174 14405 2026-08-11T04:07:03Z EatingCarBatteries 1378 EatingCarBatteries moved page [[Abstract Wikipedia:Tools]] to [[Help:Tools]] 14405 wikitext text/x-wiki #REDIRECT [[Help:Tools]] h0upv31qhlvxxeoex2cf7xkeb2y8o7u 1198 5175 14415 2026-08-11T07:53:07Z Ameisenigel 31 Created page with "Suche nach dem Thema, zu dem du einen Artikel erstellen möchtest." 14415 wikitext text/x-wiki Suche nach dem Thema, zu dem du einen Artikel erstellen möchtest. mpps9xrri1aj4wmg6ca7nki2kci9tu1 1198 5176 14417 2026-08-11T07:53:26Z Ameisenigel 31 Created page with "Einen neuen Artikel erstellen" 14417 wikitext text/x-wiki Einen neuen Artikel erstellen 4f604ppz76dcv2lxlezjl1zicpgkkmz