Talk:Q80096233

From Wikidata
Jump to navigation Jump to search
description: list of Wikimedia articles belonging to one topic
Useful links:
Classification of the class Wikimedia information list (Q80096233)  View with Reasonator View with SQID
For help about classification, see Wikidata:Classification.
Parent classes (classes of items which contain this one item)
Subclasses (classes which contain special kinds of items of this class)
Wikimedia information list⟩ on wikidata tree visualisation (external tool)(depth=1)
Generic queries for classes
See also


Consequences of the split

[edit]

@Infovarius: I don't understand how this differs from its superclass, but the split is going to cause a lot of issues for the ~100 properties that reference Wikimedia list article (Q13406463) from constraints. --Yair rand (talk) 04:54, 2 January 2020 (UTC)[reply]

Actually it is intended to avoid violations caused by using Wikimedia list article (Q13406463)... --Infovarius (talk) 19:13, 3 January 2020 (UTC)[reply]
@Infovarius: Why is that positive? Presumably instances of Q80096233 should also not have such attributes (inconsistent with being such a list) applied to them? --Yair rand (talk) 16:44, 5 January 2020 (UTC)[reply]
As it is said in ru:Википедия:Списки#Информационные_списки: "Информационный список фактически является энциклопедической статьёй специфичного вида" i.e. "Information list is a type of encyclopedic articles". So probably superclass should be different from usual list. --Infovarius (talk) 18:39, 7 January 2020 (UTC)[reply]
@Infovarius: So, if I'm understanding correctly, instances of Q80096233 are Wikimedia list articles of a different type than Wikimedia list article (Q13406463)? If so, Q80096233 should be added to all ~100 constraints that use Q13406463, to avoid misuse of the properties. An entity can't be both an article and work as a real-world (non-internal) entity. --Yair rand (talk) 17:53, 8 January 2020 (UTC)[reply]

@Infovarius: I don't get the difference between this class and Wikimedia list article (Q13406463). list of subcamps of Buchenwald (Q321360) instance of (P31) Wikimedia information list (Q80096233) and therefore category related to list (P1754). Throws a warning. What needs to be fixed? Can we please merge this item and Wikimedia list article (Q13406463)? -- Dr.üsenfieber (talk) 19:17, 19 April 2020 (UTC)[reply]

@Infovarius: +1. I don’t understand the supposed difference between the two entities. What difference is there between e.g. list of chemical elements (Q6102450), list of chemical element naming controversies (Q428800), and list of misidentified chemical elements (Q21068667)? The only explanation above, that “information list is a type of encyclopedic article” explains editing standards on one project, but does not really concern this class hierarchy. As far as I understand it, these “information lists” are still “Wikimedia list articles”, only on some projects, list articles are split into “non-encyclopedic articles” and “encyclopedic articles”? Fine, if that is an interesting distinction, let’s make Wikimedia information list (Q80096233) subclass of Wikimedia list article (Q13406463) and if some of the properties are relevant only for “encyclopedic articles”, move it there. But having a completely separate superclass? Why? Are “information lists” not “Wikimedia list articles”?? I don’t think so. (And if this would be indeed what we wanted, we need to decide whether we want to use e.g. is a list of (P360) for this new class as well as for the original one, as User:Yair rand said above.) --Mormegil (talk) 15:31, 25 February 2021 (UTC)[reply]
You almost convinced me... Probably the solution is to introduce a new badge specifically for ru-wiki (and for other languages who wants this distinction). Infovarius (talk) 20:48, 18 June 2023 (UTC)[reply]

Is the problem that Wikimedia list article (Q13406463) is currently used both for the concept "Wikimedia list article" and for the project pages about that concept with interwiki links to Project namespace pages? This has somehow made Wikimedia list article (Q13406463) subclass of both Wikimedia project page (Q14204246) and MediaWiki main namespace page (Q15633587), but a page can only belong to one namespace. 90.227.175.218 21:42, 17 June 2023 (UTC)[reply]

Actually not, but this could be another problem. What to do with es-pages belonging to another namespace? --Infovarius (talk) 20:48, 18 June 2023 (UTC)[reply]
> but a page can only belong to one namespace
I can't find anything in the WD rules that restricts from linking different namespaces between interwikis in a single Qitem. I suppose we should be guided by a common sense in this case. Making the separation of identical lists (often translations) into two separate Qitems: mainspace list and project space list seems irrational to me. I suppose this should be resolved with "nature of statement: sometimes" of something like that. Solidest (talk) 23:54, 4 July 2024 (UTC)[reply]
  • These items need to be merged. In the Russian Wikipedia, the whole difference between the two is that the informational ones are full-fledged finalized lists, which the ruwiki rules allow to stay in the main namespace. And the rest are coordinating lists or whatever, which are actually stub-like and cannot stay in the main space because there is no "generalizing source for list entries" as required by the ruwwiki rules. And so the list will not (or not yet) be finalized into a full-fledged list. Such a division is completely unnatural and makes no sense for Wikidata. And I don't see the need for a separate badge either. Even from a Ruwiki user's perspective, it seems like an artificial separation to limit the number of lists in the main space. Such local policies should not affect Wikidata in any way and I also insist on merging. Solidest (talk) 00:04, 5 July 2024 (UTC)[reply]