Okkn

Welcome to Wikidata, Okkn!

Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike and you can go to any item page now and add to this ever-growing database!

Need some help getting started? Here are some pages you can familiarize yourself with:

• Introduction – An introduction to the project.
• Wikidata tours – Interactive tutorials to show you how Wikidata works.
• Community portal – The portal for community members.
• User options – including the 'Babel' extension, to set your language preferences.
• Contents – The main help page for editing and using the site.
• Project chat – Discussions about the project.
• Tools – A collection of user-developed tools to allow for easier completion of some tasks.

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date.

If you have any questions, don't hesitate to ask on Project chat. If you want to try out editing, you can use the sandbox to try. Once again, welcome, and I hope you quickly feel comfortable here, and become an active editor for Wikidata.

Best regards! --Tobias1984 (talk) 12:53, 15 August 2016 (UTC)

Babel

Babel lets you view and edit more than one language on Wikidata. Just add e.g. {{#babel:de-N|en-3|es-1|fr-2|nl-3|it-4|da-0}} to your user page. With the same language codes you can add links to your userpage on Wikipedia e.g. ja:User:Okkn. --Tobias1984 (talk) 12:53, 15 August 2016 (UTC)

Hi Tobias. Thank you for informing me. I'll try it. --Okkn (talk) 15:04, 15 August 2016 (UTC)

I saw that everything worked. Perfect. If you have any questions you can ask here Wikidata:井戸端 --Tobias1984 (talk) 15:36, 15 August 2016 (UTC)

And if you are interested in Medicine you are more than welcome to join our WikiProject: Wikidata:WikiProject Medicine --Tobias1984 (talk) 15:49, 15 August 2016 (UTC)

Sounds interesting! How can I join the project? --Okkn (talk) 15:54, 15 August 2016 (UTC)

You just sign your name here: Wikidata:WikiProject_Medicine#Participants. Then you can also add {{ .... |Medicine}} at the end of your Babel box to indicate that you are part of the project. --Tobias1984 (talk) 16:02, 15 August 2016 (UTC)

I've got it. Thank you very much! --Okkn (talk) 16:07, 15 August 2016 (UTC)

Wikidata Graph Builder

Did you see the Wikidata Graph Builder yet (warning needs a good CPU, might crash browser): https://angryloki.github.io/wikidata-graph-builder/?property=P279&item=Q12140&limit=10&mode=reverse ? The ontology shown traverses the subclass of (P279) property down from medication (Q12140). It shows that we do have some problems in certain areas, where we are not specific enough (i.e. linking directly to the drug without any subclasses) or large grouping, which might also need further subdivision. By the way you can do the same in SPARQL by writing ?item wdt:P279* wd:Q12140. The * will traverse subclass of (P279) (367 results) instead of just going to the first level (41 results). --Tobias1984 (talk) 17:50, 16 August 2016 (UTC)

@Tobias1984: Wow, it's a nice tool and some problems around pharmaceutical drug are visualized... And I didn't know * in SPARQL. Thank you.

Well, I don't really understand the rule for using subclass (and subclass of (P279) property). Should we only use suitable specific subclasses? Superclasses have not to be used with their subclass? For example, linking to both medication (Q12140) and antibiotic (Q12187) is valid or not? --Okkn (talk) 20:16, 16 August 2016 (UTC)

The decision to link is actually more dependent, if there is a source that suggests this link. Multiple p279 statements might seem redundant, but that might change according to how the query is written. I think in general it is a complicated topic and we still have a lot of work to do in Medicine and Pharmacology. --Tobias1984 (talk) 20:57, 16 August 2016 (UTC)

anatomical branch of (P3261)

Are you planning to add dat for anatomical branch of (P3261)? ChristianKl (talk) 15:36, 10 October 2016 (UTC)

@ChristianKl: No, not yet. Do you have any idea? --Okkn (talk) 03:34, 11 October 2016 (UTC)

Share your experience and feedback as a Wikimedian in this global survey

Hello! The Wikimedia Foundation is asking for your feedback in a survey. We want to know how well we are supporting your work on and off wiki, and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation. You have been randomly selected to take this survey as we would like to hear from your Wikimedia community. To say thank you for your time, we are giving away 20 Wikimedia T-shirts to randomly selected people who take the survey. The survey is available in various languages and will take between 20 and 40 minutes.

Take the survey now!

You can find more information about this project. This survey is hosted by a third-party service and governed by this privacy statement. Please visit our frequently asked questions page to find more information about this survey. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email to surveys@wikimedia.org.

Thank you! --EGalvez (WMF) (talk) 20:36, 13 January 2017 (UTC)

Your feedback matters: Final reminder to take the global Wikimedia survey

(Sorry to write in Engilsh)

Hello! This is a final reminder that the Wikimedia Foundation survey will close on 28 February, 2017 (23:59 UTC). The survey is available in various languages and will take between 20 and 40 minutes. Take the survey now.

If you already took the survey - thank you! We won't bother you again.

About this survey: You can find more information about this project here or you can read the frequently asked questions. This survey is hosted by a third-party service and governed by this privacy statement. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email through EmailUser function to User:EGalvez (WMF) or surveys@wikimedia.org. About the Wikimedia Foundation: The Wikimedia Foundation supports you by working on the software and technology to keep the sites fast, secure, and accessible, as well as supports Wikimedia programs and initiatives to expand access and support free knowledge globally. Thank you! --EGalvez (WMF) (talk) 08:19, 24 February 2017 (UTC)

東雲寺 (名古屋市)

東雲寺 (名古屋市)の編集をしていただき、ありがとうございました。--duck775 (talk) 03:00, 27 November 2017 (UTC)

@Duck775: いえいえ、どういたしまして。Wikidataに日本の項目を増やしていきましょう！わからないことがあればいつでも聞いてください。 --Okkn (talk) 13:05, 27 November 2017 (UTC)

Henri-Frédéric Iselin

Bonjour, pouvez-vous supprimer cette image ? Elle n'est pas une image de l'artiste, mais d'un de ses productions, présente au sein de son article. --Lyokoï (talk) 15:41, 24 February 2018 (UTC)

@Lyokoï: I got it. Because IP address users remove that image, I misunderstood as the acts of vandalism. --Okkn (talk) 15:51, 24 February 2018 (UTC)

Note: this is about Henri-Frédéric Iselin (Q2083652) --Okkn (talk) 15:54, 24 February 2018 (UTC)

Sorry, it's because the contributor is learning during an workshop. I'm sorry for this misunderstand. And thank for the link. --Lyokoï (talk) 17:43, 24 February 2018 (UTC)

Dog is not Taxon, but Cat (among others) is

I noticed that cat (Q146) is also instance of common name (Q502895) but is also instance of taxon. is therefore this list also all not considered taxon and need to be corrected? Also the examples Wikidata:SPARQL_query_service/queries/examples#Animals_that_were_executed, Wikidata:SPARQL_query_service/queries/examples#Animals_owned_by_people_holding_any_position do not cover dogs in the query. Thanks! --Sphericon

@Sphericon: You are a man of vision. I think house cat (Q146) should also be fixed. The model case is the relation of human (Q5) and Homo sapiens (Q15978631). Taxon of house cat (Q146) is Felis catus (Q20980826), and that of dog (Q144) is Canis familiaris (Q20717272). It is true that not all taxons have the corresponding items for common name (Q502895), but if common name item exists, common name (Q502895) and taxon (Q16521) should be separated. By the way, examples can be fixed to cover common names (Fixed query for the latter example). --Okkn (talk) 04:40, 18 March 2018 (UTC)

@Okkn: Thank you! I agree with your example to remove human, I guess in some definitions human is considered an animal. I also saw that many animals use the subclass of (P279) of animal (Q729) is this maybe a viable option additionally to common name (Q502895)? There are also a three animals with both instance of (P31) taxon (Q16521) and subclass of (P279) animal (Q729) as in this list It seems there are many holes in the animal ontology, is there a central discussion dedicated to this?

@Sphericon: You can join Wikidata:WikiProject Taxonomy or disscuss this problem on Wikidata:Project chat. --Okkn (talk) 13:06, 22 March 2018 (UTC)

@Okkn: Thank you, I will have a look! --Sphericon

Congratulations, Dear Administrator!

English | español | français | Nederlands | русский | +/−

An offering for our new administrator from your comrades... (our gift is better than the one at Commons or Meta)

You have your gun; now here's your badge: {{User admin}}/{{#babel:admin}} and {{Admin topicon}}. Enjoy!

Congratulations! You now have the rights of administrator on Wikidata. Please take a moment to read the Wikidata:Administrators page and watchlist related pages (in particular Wikidata:Project chat, Wikidata:Requests for comment, and Wikidata:Administrators' noticeboard), before launching yourself into page deletions, page protections, account blockings, or modifications of protected pages.

Please feel free to join us on IRC: #wikidata-admin @ irc.freenode.net. If you need access, you can flag someone down at @ irc.freenode.net. You may find Wikidata:Guide to Adminship to be useful reading. You may also want to consider adding yourself to meta:Template:Wikidata/Ambassadors, and to any similar page on your home wiki if one exists. (Check Wikipedia:Wikidata/Wikidatans (Q14964498).)

Please also add/update the languages you speak to your listing at Wikidata:List of administrators. You may also like to add your username to this list if you would not like that items you delete at RfD get marked as deleted automatically. Again, welcome to the admin corps!

Lymantria (talk) 09:54, 25 March 2018 (UTC)

Backlinked items

Hey Okkn, I think you should have a look at this page. When you delete an item, please make sure that it is no longer in use by any other item. If you still think that the item should be deleted (e.g. empty category item), please also remove all other statements that use the deleted item. You can easily find them via Special:WhatLinksHere in the left menu within each item. Good luck! —MisterSynergy (talk) 16:48, 28 March 2018 (UTC)

@MisterSynergy: Thank you for informing me. I will take care of it. --Okkn (talk) 22:31, 28 March 2018 (UTC)

Share your experience and feedback as a Wikimedian in this global survey

Hello! The Wikimedia Foundation is asking for your feedback in a survey. We want to know how well we are supporting your work on and off wiki, and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation. You have been randomly selected to take this survey as we would like to hear from your Wikimedia community. The survey is available in various languages and will take between 20 and 40 minutes.

Take the survey now!

You can find more information about this survey on the project page and see how your feedback helps the Wikimedia Foundation support editors like you. This survey is hosted by a third-party service and governed by this privacy statement (in English). Please visit our frequently asked questions page to find more information about this survey. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email through the EmailUser feature to WMF Surveys to remove you from the list.

Thank you!

WMF Surveys, 18:57, 29 March 2018 (UTC)

Reminder: Share your feedback in this Wikimedia survey

Every response for this survey can help the Wikimedia Foundation improve your experience on the Wikimedia projects. So far, we have heard from just 29% of Wikimedia contributors. The survey is available in various languages and will take between 20 and 40 minutes to be completed. Take the survey now.

If you have already taken the survey, we are sorry you've received this reminder. We have design the survey to make it impossible to identify which users have taken the survey, so we have to send reminders to everyone. If you wish to opt-out of the next reminder or any other survey, send an email through EmailUser feature to WMF Surveys. You can also send any questions you have to this user email. Learn more about this survey on the project page. This survey is hosted by a third-party service and governed by this Wikimedia Foundation privacy statement. Thanks!

WMF Surveys, 01:40, 13 April 2018 (UTC)

Edits to "Year"

Your edits to year (Q577) are being discussed at Wikidata: Project chat#Will "applies to part" work well with conversion factors?. Also, I removed one conversion factor because it was too precise to apply to all the kinds of years that the item reasonably applies to. This aspect is discussed further on the item talk page. Jc3s5h (talk) 13:51, 23 April 2018 (UTC)

I mentioned in Talk:Q577. --Okkn (talk) 14:46, 23 April 2018 (UTC)

Possible WikiProject for year discussion

I have inquired at Wikidata talk:WikiProject Calendar Dates#Expand to cover year items? to see if that project would like to be a more enduring place to discuss and document the year-related discussions currently going on at Wikidata:Project chat. Since you have participated, I wanted to invite you to the discussion. Perhaps we shouldn't advertise the WikiProject in Project chat until a consensus emerges about whether the WikiProject wants to take on years or not. Jc3s5h (talk) 21:04, 30 April 2018 (UTC)

SuccuBot must be blocked

WD:SOCK clearly and explicitly states that a block placed on his main account applies to all accounts they use, so their bot may not edit. I also strongly dislike that you reverted my action without consulting me.--Jasper Deng (talk) 20:38, 5 May 2018 (UTC)

@Jasper Deng: Operating the SuccuBot is not "circumventing sanctions or blocks", because the bot had only continued the approved tasks since before you blocked Succu. Do you really think Succu operated his bot account "for an improper purpose"? I believed this is an obvious and uncontroversial case, so I didn't consult you before unblocking it. --Okkn (talk) 05:01, 6 May 2018 (UTC)

This is the policy the community made. I personally want an exemption for bots in the policy, but the policy makes no such exemption, and we are not at liberty to make one because bot operators are responsible for their bots' edits. If you want to change this, make an RfC. But this is what it is at the time. It is generally frowned upon to revert any admin's actions of any sort except for very obvious mistakes (i.e. things like blocking you by mistake).--Jasper Deng (talk) 05:30, 6 May 2018 (UTC)

Okay, if that is the official interpretation of the policy, my action was wrong. --Okkn (talk) 05:49, 6 May 2018 (UTC)

Request for help

I was referred to you by Mr. @Mahir256:. Can you please add the following to this page in Japanese:

1. Label: ニセコイ
2. Description: 河合隼人による映画 (I doubt if this description is correct!)
3. Aliases: Use the full name as seen in the poster on en wiki.

Harsh Rathod Poke me! 18:56, 6 May 2018 (UTC)

 Done Thanks! Harsh Rathod Poke me! 19:13, 6 May x2018 (UTC)

@Harshrathod50: Not at all, but what's wrong with you? --Okkn (talk) 19:16, 6 May 2018 (UTC)

No, nothing, what happened? Harsh Rathod Poke me! 19:20, 6 May 2018 (UTC)

Lexeme entity use on Items and Properties phab:T195611

Hi! An abuse filter that I made last night stopped one of your edits to Property:P5186. This is currently in place due to a bug which you can read about @ https://phabricator.wikimedia.org/T195611 Adam Shorland (WMDE) (talk) 10:12, 26 May 2018 (UTC)

@Adam Shorland (WMDE): Thank you for informing me. I had noticed the filter and read the ticket. But isn't it enough to apply this filter only to Items, not to Properties? --Okkn (talk) 10:32, 26 May 2018 (UTC)

To be honest I am not 100% sure, but to avoid things being broken over the weekend we decided to apply it to both properties and items for now. We will reassess the situation on Monday. If we switch it to just Items I'll go through and undo my undos. Adam Shorland (WMDE) (talk) 13:11, 26 May 2018 (UTC)

Due to a US holiday today (Monday) this will be pushed back to Tuesday. Adam Shorland (WMDE) (talk) 18:00, 28 May 2018 (UTC)

John Lennon

Could you please protect this? - Bossanoven (talk) 06:07, 29 May 2018 (UTC)

@Bossanoven: Thank you for reporting the vandalism. I semi-protected John Lennon (Q1203) for three months, but next time please request at Administrators' noticeboard, if there isn't any special reason. Regards, --Okkn (talk) 06:52, 29 May 2018 (UTC)

Lexeme:L821

• [1]

I'm surprised by your decision here. When I learnt Japanese, my teacher taught me that the stem for 見る is み! --Deryck Chan (talk) 16:32, 8 June 2018 (UTC)

@Deryck Chan: Japanese grammar which native Japanese speakers learn in Japan is sometimes different from the grammar non-native speakers learn. You can see w:ja:上一段活用 and find that 「語幹」 of 「見る」 is put in parentheses. --Okkn (talk) 16:44, 8 June 2018 (UTC)

Actually you're right. When I read w:ja:上一段活用 it came back to me that the prevalent definition of "stem" in Japanese textbooks for 上一 and 下一 is that the last two syllables of the dictionary form both get cut off. Considering み as the stem because it doesn't change with conjugation generally comes from European linguisticians who take a functional definition of "stem". Deryck Chan (talk) 16:59, 8 June 2018 (UTC)

@Deryck Chan: Definition of "word stem" in the Japanese grammar (studied in school in Japan) may not be linguistic, but it is reasonable to regard the last two syllables of 上一 verbs as their word stem, because some 上一 verbs are derived from w:ja:上二段活用 verbs of Old Japanese language (文語文法). For example, 「落[お]ちる (上一)」 is derived from Old Japanese 「落[お]つ (上二)」, and the word stem of 「落[お]つ」 must be 「落[お]」 (See the table in w:ja:上二段活用). However, if we regard the word stem of 「見る」 as 「み」, the word stem of 「落ちる」 will be 「落ち」. This discordance seems to be strange to native Japanese speakers. --Okkn (talk) 17:42, 8 June 2018 (UTC)

そですね。そして、文語上一は、「見る」の「語幹」が何ですか。でもありませんか。Deryck Chan (talk) 20:38, 9 June 2018 (UTC)

@Deryck Chan: 文語文法でも「見る」には語幹がありません。マ行上一段活用の活用語尾は「み-み-みる-みる-みれ-みよ」で、上二段活用の活用語尾は「み-み-む-むる-むれ-みよ」です。上一段活用についても「み」を語幹に入れないことにより、活用パターンに一貫性があり、学習しやすいのだと思います。 --Okkn (talk) 04:44, 10 June 2018 (UTC)

P1889 and P461

[2] [3]

Do you think the constraint is a bad idea? Swpb (talk) 18:18, 9 July 2018 (UTC)

@Swpb: Yes. These properties have already been used many times without that qualifier. --Okkn (talk) 18:21, 9 July 2018 (UTC)

Items about library only in Japanese

Hi,

Could you take a look at this item library in Japan (Q11632449). I put a subclass of (P279) a bit more specific but beyond that, I'm not sure what this item is about. Is it similar (sbuclass) or identical (merge) to parliamentary library (Q2052886) ?

Cdlt, VIGNERON (talk) 11:02, 23 July 2018 (UTC)

@VIGNERON: It is a common noun for the library of parliament (Q35749). National Diet Library (Q477675) and Library of Congress (Q131454) can be the instance of it. So it may be identical to parliamentary library (Q2052886). --Okkn (talk) 15:56, 23 July 2018 (UTC)

Help us improving the user experience of Lexicographical Data

Hello,

I’m Jan, doing research on user experience in the Wikidata team. I’m currently discussing with people who are editing Lexemes, in order to understand their needs better, and improve their experience with the interface.

We noticed that you have been actively editing Lexemes recently (thank you for that!) and we would love to have a discussion with you about what you’re doing, how you work, what motivates you to create Lexemes, and how you imagine reusing the data later.

This discussion would take place as an individual interview with one of our designers. Via the communication platform of your choice, you’ll be able to share your screen, show how you’re currently editing the data and chat with us. The discussion would take between 30 and 60 min, we will set up the appointment depending on when you are available. Depending on your preferred language, the discussion can happen in English, German or French.

If you’re interested, feel free to reply to this message or send me an email: jan.dittrich@wikimedia.de.

If you don’t want to be contacted by us on this topic anymore, please let me know.

Thanks a lot for your help Jan Dittrich (WMDE) (talk) 11:41, 16 August 2018 (UTC)

koaza

I have a strong feeling that this list of items is using P279 improperly, in part because they show up on Wikidata:List_of_classes_of_administrative_territorial_entities. Should that statement in fact be removed (or moved to a P31 claim)? Mahir256 (talk) 23:22, 2 September 2018 (UTC)

@Mahir256: You are right. They should be moved to P31 claims. Could you please replace in that way? --Okkn (talk) 01:59, 3 September 2018 (UTC)

Okay, doing this right now. Thank you for letting me know! Mahir256 (talk) 02:03, 3 September 2018 (UTC)

Not at all! Thank you for improving Japan-related items. --Okkn (talk) 02:06, 3 September 2018 (UTC)

Japanese lexemes

Hi, could you look into https://www.wikidata.org/wiki/Special:Contributions/Egalles ? I feel uncomfortable seeing Internet slang as lexical category. KaMan (talk) 16:49, 18 September 2018 (UTC)

@KaMan: Thank you for informing me. Some of them are inappropriate (just disparaging terms), so I have deleted them. --Okkn (talk) 17:47, 18 September 2018 (UTC)

Please don't vandalize

[4] Thank you! 77.179.13.21 20:38, 26 September 2018 (UTC)

Ernst Johann Alexander Medem (Q16350920) has had a sitelink of w:lv:Aleksandrs fon Mēdems. Is "Ernst Johann Alexander Medem" really a right name? Do you havn any source for that? If so, sorry for reverting the edit. Anyway, please create an account not to be misunderstand as vandals. Best regards, --Okkn (talk) 23:02, 26 September 2018 (UTC)

You have an account, but you are the vandal! What does it help to create an account? You support the vandalism of Jura1 on Property:P2580. Please stop it. Do you want that Wikidata stores correct informationi? Look all the changes done in the edit that YOU protected [5] are insertion of FALSE information. 2.243.96.129 15:46, 11 October 2018 (UTC)

The case of Ernst Johann Alexander Medem (Q16350920) are completely different from your case. I reverted the edit because the label was changed by a new IP user, and the new label was different from the title of sitelink. It is really difficult to distinguish such edits from a real vandals.

When it comes to your case, an edit war was actually happened. That's why I terminate it. I just semi-protected the pages, so every auto-confirmed users can edit those pages. --Okkn (talk) 16:47, 11 October 2018 (UTC)

But you protected a vandalized version, you HELPED a vandal. You say "every auto-confirmed user" - I am not auto-confirmed. It is like saying: Every White-Male can edit, but Black-Woman are out. Even if the Black-Woman gave the correct information, but the White-Male was vandalizing. Look at the content, Jura1 was vandalizing. He removed a lot of content from the talk page. The IPs made dozens of correct edits. You can see in Russian and German and Latvian Wikipedia: IPs made hundreds of correct edits. Jura1 is vandalizing. Look all the edits in the property, he is editing against half a dozen of users and intimidates them, threatening with blocks. And you help Jura1. YOU support a vandal. 2.243.96.129 19:12, 11 October 2018 (UTC)

Talk pages are not your personal notebook or clipboard. I think Jura's edits are appropriate. If you believe you are right, please ask other (auto-confirmed) users to support you. I haven't prohibited you from doing so. Also, the reason you are not "auto-confirmed" just depends on your own choice; i.e. deciding not to create an account. Be careful at your language. --Okkn (talk) 19:41, 11 October 2018 (UTC)

You helped and still help a vandal. Editing via IP is allowed, but you disallowed it for some pages. - "I think Jura's edits are appropriate." - see, from the very beginning your intention was to help Jura1. You are co-working with Jura1 in vandalism. Jura1 inserted the nonsense en:label:Aleksandrs fon Mēdems and you support it. Jura1 vandalises BBLD ID - and you support it. 77.0.225.254 15:58, 13 October 2018 (UTC)

Answered in "You are a liar" section below. --Okkn (talk) 07:11, 17 October 2018 (UTC)

"Try it!" translation link

Hi! do you know where the link to translate this term (from Template:SPARQL label)? I need to translate it to Bahasa Indonesia --Pebaryan (talk) 10:37, 3 October 2018 (UTC)

@Pebaryan: You can translate it in Template:Int try it. Thank you for your contribution! --Okkn (talk) 11:32, 3 October 2018 (UTC)

super! many thanks! --Pebaryan (talk) 13:39, 3 October 2018 (UTC)

The composer of Sikken voldsom trængsel og alarm

We had an editing session with some university students in Aarhus friday. Among the information added or revised was that the composer of that christmas song is Adolf Müller, not as normally stated Emil Horneman (check Danish article). In any case it is not Peter Faber, he wrote the text.Ditlev Petersen (talk) 05:24, 8 October 2018 (UTC)

Okay, I see that you have the correct data now. Ditlev Petersen (talk) 05:25, 8 October 2018 (UTC)

(Sikken voldsom trængsel og alarm (Q12335279)) I'm sorry for upsetting you. I noticed that and undid my edit, just after I mistakenly reverted your edit. --Okkn (talk) 08:22, 8 October 2018 (UTC)

from User:Okkn/common.js to User:Okkn/jsonLexeme.js

Hi! I have noticed that you modified and extended functionality from oryginal User:GZWDer/newentity.js. Could you please move your code to separate place outside your common.js so others could include it and benefit from your extensions? From what I understood you have added 'edit' to existing lexemes and I'm very interested in such functionality myself. :) Do I need to modify my Module:Lexeme-pl to be able to edit lexemes? KaMan (talk) 11:30, 8 October 2018 (UTC)

@KaMan: I have created User:Okkn/jsonLexeme.js (and changed the section title). You will be able to use Module:Lexeme-pl just as it is, but please note that this script will create duplicate claims if the Lexeme had already had the same claims. Regards, --Okkn (talk) 13:16, 8 October 2018 (UTC)

If you open "Edit Lexeme" dialog on a Lexeme page, the Lexeme ID will be autofilled. --Okkn (talk) 13:36, 8 October 2018 (UTC)

Thank You, it works great! I have added your script and module to tools list: https://www.wikidata.org/w/index.php?title=Wikidata%3ATools%2FLexicographical_data&type=revision&diff=759937693&oldid=748252248 KaMan (talk) 15:12, 8 October 2018 (UTC)

I'm glad to hear that. And thank you for adding them to the list! --Okkn (talk) 15:18, 8 October 2018 (UTC)

I'm trying to use this script to edit lexemes, but I didn't get how to put original JSON, I copied from https://www.wikidata.org/w/api.php?action=wbgetentities&ids=L63832&format=json ant tried to remove encapsulating stuff but the edit button on the script popup won't respond. It will be helpful to add a few words on how to get acceptable JSON of current article, and even better if you can automatically load it like you load ID. Uziel302 (talk) 06:06, 12 December 2019 (UTC)

@Uziel302: When you edit Lexemes, you don't need to get the current contents of the Lexeme. You can just input what you want to add to the Lexeme. Actually, inputted json is sent via Wikibase API wbeditentity. Examples of valid json for Lexeme can be seen by expanding {{#invoke:Lexeme-ja|verbForms|足りる|たりる|ra-kami}} or {{#invoke:Lexeme-ja|adjectivalNoun|雅|みやび|Q55814931}}. If you need more help, please tell me how you want to edit Lexemes. --Okkn (talk) 02:19, 13 December 2019 (UTC)

The thing is, I don't want to add any forms. I uploaded forms using LexData and I later noticed that some have issue, forms like L67149-F22 have both plural and singular, and it should be singular, possessive plural, the form is of a single object that belongs to many people. I tried using the API myself but failed to pass JSON as required, that's why I need to know how to get JSON of a lexeme.Uziel302 (talk) 05:07, 13 December 2019 (UTC)

@Uziel302: Here is an example to update grammatical features of F67149-F22 https://www.wikidata.org/w/index.php?title=Lexeme:L67149&diff=1075143836&oldid=1075093987. I just inputted {"forms":[{"id":"L67149-F22","grammaticalFeatures":["Q1084","Q110786","Q1775415","Q69761633","Q71470909"],"update":""}],"lexicalCategory":"Q1084"}. --Okkn (talk) 07:59, 13 December 2019 (UTC)

Thanks a lot for this useful tool. Is there a limit to the json length? The tool failed to make this edit so I made it with python script and the same json. Your tool didn't give any error, just didn't respond. JSON in note here. Thanks, Uziel302 (talk) 13:27, 17 December 2019 (UTC)

You are a liar

"Excessive vandalism"

(cur | prev) 15:35, 11 October 2018‎ Okkn (talk | contribs)‎ m . . (17,595 bytes) (0)‎ . . (Protected "Property talk:P2580": Excessive vandalism ([Edit=Allow only autoconfirmed users] (expires 15:35, 11 January 2019 (UTC)) [Move=Allow only autoconfirmed users] (expires 15:35, 11 January 2019 (UTC))))

But you protected the vandalised version! 2.243.96.129 15:48, 11 October 2018 (UTC)

@Jura1: Any thoughts? --Okkn (talk) 15:56, 11 October 2018 (UTC)

Look what he removed [6] 2.243.96.129 16:04, 11 October 2018 (UTC)

As an admin, I must terminate an edit war. Also, Jura1 is a trusted user, and I cannot understand your intention at those pages. Thanks, --Okkn (talk) 16:19, 11 October 2018 (UTC)

Trusted by whom? Look at the edits. He inserts nonsense. His edits have been changed several times by other users. Look at the talk page what he removed. YOU support Jura1 a vandal if you protect the page. He started the edit war. Everything was fine. Look at the changes by jura1 to the property : every single change is wrong. It is "BBLD" not "BBLd" not "BBL digital" - even you as a Japanese can understand that. You are NOT honest if you say you don't understand. It is very easy to understand. See https://bbld.de . Jura1 is a vandal. 2.243.96.129 19:17, 11 October 2018 (UTC)

I protected the pages not because of the contents of the page, but because of the nonesense edit warring.

Hmm, the property was originally created as "Baltisches Biographisches Lexikon digital ID"(https://www.wikidata.org/w/index.php?title=Property:P2580&oldid=310075486), but "BBLd" and "Baltisches Biographisches Lexikon digital" seems an old name (de:Baltisches Biographisches Lexikon Digital). However, my talk page is not the place to discuss what is the right name for the property. Please open a dicussion in other place. I have no idea about BBLD or BBLd at all. --Okkn (talk) 20:46, 11 October 2018 (UTC)

YOU protected the page in a vandalised state. Jura1 vandalised hundreds of items, altering labels, removing links, removing other claims e.g. removing instanceOf [7]. You wrote "Excessive vandalism", you didn't write "nonesense edit warring". Look who started the edit warring and content removal on the talk page: Was it Jura1? Why do you help this vandal? 77.0.225.254 15:53, 13 October 2018 (UTC)

Jura's and my edits on Ernst Johann Alexander Medem (Q16350920) is not vandalism because "Aleksandrs fon Mēdems" is actually the page title of the sitelink (lv:Aleksandrs_fon_Mēdems).

You can make edit requests for the semi-protected pages in Wikidata:Project chat or Wikidata:Administrators' noticeboard, if the current contents should be modified. You can also request to unprotect those pages in Wikidata:Administrators' noticeboard, if the current protection is inappropriate. --Okkn (talk) 07:09, 17 October 2018 (UTC)

• Why do you keep evading your block instead of asking WMF for a deblock? --- Jura 17:49, 11 October 2018 (UTC)

Japanese lexeme in latin alphabet

Hi! Could you please look into 女神/めがみ (L39628) if it is created correctly and support User:Mr. Guye if needed? Thanks in advance. KaMan (talk) 06:31, 10 December 2018 (UTC)

@KaMan: Thank you for reporting it! I have modified the lexeme. --Okkn (talk) 04:21, 11 December 2018 (UTC)

Tedi Aleksandrova

Hello I see you've taken off my edits because it has no source but to be fair her claimed d.o.b of 11/12/1990 has no source other than her claiming. Everyone in Bulgaria knows she's lying about her age I mean it's obvious she looks a lot older than 28  – The preceding unsigned comment was added by 86.20.236.251 (talk • contribs) at 14:57, 19 January 2019‎ (UTC).

We cannot allow data which remain no more than speculation. Regards, --Okkn (talk) 11:25, 20 January 2019 (UTC)

Hello well technically like I said before her being born in 1990 is just a speculation I haven't seen any official documents that prove that's when she's born. Like I'm 23 and I look 15-20 years younger than her.

Is there any source which shows that many people in Bulgaria know she is lying about her age? In that case, we can assign "deprecated rank" to the statement, rather than removing current value. For detail, please see Help:Ranking. --Okkn (talk) 10:01, 1 February 2019 (UTC)

Species items

Vanessalozano (talk) 09:00, 4 February 2019 (UTC)Hi Okkn, nice suggestion! instead of country of origin (P495) I can use "indigenous to" (P2341).

• @Vanessalozano: I'm glad to help! Thank you for your contribution. --Okkn (talk) 13:01, 4 February 2019 (UTC)

Japanese lexeme

Is this invalid ID (L42253) candidate for deletion or it can be fixed? I don't know japanese. KaMan (talk) 07:15, 6 February 2019 (UTC)

@KaMan: Deleted. It may be a test edit. --Okkn (talk) 13:47, 6 February 2019 (UTC)

Green color blindness

Hi! Is deuteranopia (Q1201709) = green color blindness (Q26738900), should one merge it? Wikisaurus (talk) 22:30, 19 September 2019 (UTC)

@Wikisaurus: They seem to refer to the same concept, but do we have a common parent item of deuteranomaly (Q9206592) (anomalous trichromatism) and "deuteranopia" (dichromatism)? Currently, deuteranopia (Q1201709) is a superclass of both deuteranomaly (Q9206592) and green color blindness (Q26738900). --Okkn (talk) 04:41, 21 September 2019 (UTC)

• I can not find any name for it in Google Books, maybe just red–green color blindness (Q2167988), which also includes protanopia (Q1300720) and colour vision deficiency (Q11827902)? One can connect -anopia's and -anomaly's with different from (P1889). It is a bit weird, but a subclass of trichromatism should not also be a subclass of dichromatism, no? Wikisaurus (talk) 09:55, 21 September 2019 (UTC)
  • @Wikisaurus: Probably, "deutan defect" (2型色覚; 'type 2 color vision' in Japanese) includes both "deuteranomaly" (2型3色覚; 'type 2 (anomalous) trichromatism' in Japanese) and "deuteranopia" (2型2色覚; 'type 2 dichromatism' in Japanese). Also, "protan defect" (1型色覚; 'type 1 color vision' in Japanese) includes "protanomaly" and "protanopia", and "tritan defect" (3型色覚; 'type 3 color vision' in Japanese) includes "tritanomaly" and "tritanopia". (ref. http://jams.med.or.jp/dic/colorvision.html https://enchroma.com/pages/types-of-color-blindness) --Okkn (talk) 08:28, 23 September 2019 (UTC)

Deleted item Julien Cadieux (Q76833295)

Hi, You have deleted this item Julien Cadieux (Q76833295), but I have information to fill in to get it to it's notability status. Can you undelete it? Antoine2711 (talk) 22:26, 1 December 2019 (UTC)

@Antoine2711: I have undeleted it. Make good use of it. By the way, English label of it should not be "Director". --Okkn (talk) 03:24, 3 December 2019 (UTC)

@Okkn: Well, I did a new one meanwhile, and I now just merged the 2 together (New Julien Cadieux (Q77017121)). So good for now. Thanks and have a good day. Oh, and the Director in the name, well, the student didn't quite understand that part… ;-) --Antoine2711 (talk) 01:39, 4 December 2019 (UTC)

Comments about a possible ID from Japan

Hi, as an active user who speaks Japanese and has interested in natural science, I hope you can help me.

I have discovered this database months ago and I would like to suggest an ID... they also have link to this other ID and also profile for the institution.

Maybe you can double check with me and tell me your opinion. We need less euro-centric ID for bibliometric profiles and this looks interesting, IMHO.--Alexmar983 (talk) 16:53, 31 March 2020 (UTC)

• @Alexmar983: Hi. I find that Researchmap ID (P5029) and J-GLOBAL ID (P7783) have been created. Institution code in researchmap may be worth proposing for new property. --Okkn (talk) 09:30, 3 April 2020 (UTC)

Q4936952 as metaclass

Hi. In response to Special:Diff/1275559200, I now notice that it is used as a kind of metaclass indeed. It currently has 44940 direct and indirect instances. It is currently even more widely used as a superclass for concrete objects as it has 72200 direct and indirect subclasses. Among its instances there are probably many items that are at the same time also its subclasses (at the moment I failed to get exact count without query timing out), which in any case is a contradiction. Among these instances, in addition to metaclass instances (i.e. classes of concrete objects) are also instances of concrete objects like Steinheim skull (Q550393).

In this way classification system is largely useless, and as people still use anatomical structure (Q4936952) for classification, without actually being able to know whether it's supposed to be a metaclass or a superclass for concrete objects (based on statements added to this item), this inevitably causes further confusion. So for a start this item should be corrected to be either not a metaclass or a true metaclass. Based on counts given above it still seems that removing the statement about metaclass eliminates much larger part of the mess. As for creating an additional item for "anatomical structure" as metaclass, I suppose it's an option, but would it be useful really? It doesn't seem like ranks of related metaclasses are involved here and so querying instances of this metaclass would be just as good as querying subclasses of existing "anatomical structure" item (superclass for concrete objects).

I now also noticed item cell type (Q189118) that is more close to being a true metaclass by its use. It's set as an (indirect) subclass of abstract entity (Q7184903)), as a metaclass should be, but contradictingly it's also set as a subclass of anatomical structure (Q4936952) (item talk page has an unanswered question about the latter relation). 2001:7D0:81F7:B580:8506:97F0:B19D:27A8 11:04, 11 September 2020 (UTC)

I agree with the need for correction. However, I think it would be better to create "anatomical structure" as superclass because direct subclasses of anatomical structure (Q4936952) are few. The main advantage for using P31 is human readability, and you can easily see which ontological level of concept it is. And actually, running queries using recursive P279 for such deep trees is very costly. --Okkn (talk) 03:46, 13 September 2020 (UTC)

Concerning direct relations, anatomical structure (Q4936952) currently has 724 instances and 100 subclasses. So overall there may be somewhat less items that need cleanup indeed if current "anatomical structure" item is kept as a metaclass. Then again, 724 instances is rather little part of 72200 direct and indirect subclasses mentioned above. This raises a question if at least 71500 classes more should get P31=Q4936952 statement then? Or is there some not so evident criteria based on which these 724 instances are selected?

I don't quite get what you mean by "ontological level of concept". If this level for all anatomical structures is the same "anatomical structure", then this is to state that other levels of class tree are kind of unimportant? To me it seems that this justifys duplicating other levels of class tree as separate metaclasses and P31 values as well. Not to mention that the difference between anatomical structure as superclass and anatomical structure as metaclass is probably a considerable brain-teaser for large part of users who don't even get the the difference between P31 and P279. I'd consider it more comprehensible to rely on subclasses in regular manner. 2001:7D0:81F7:B580:F022:FE02:A3F3:78EE 15:08, 13 September 2020 (UTC)

I now noticed your reply to Talk:Q189118. It seems you suggest that anatomical structure (Q4936952) should be used as both second-order class (Q24017414) and third-order class (Q24017465). I don't think this works really. 2001:7D0:81F7:B580:F022:FE02:A3F3:78EE 15:24, 13 September 2020 (UTC)

The 724 items are not specially selected, but most of them are prominent anatomical structures (and that is because they are manually added P31 statements).

I used "ontological level of concept" to mean something like "instance level", "class level", "first-order metaclass level", "second-order metaclass level" ...

One of the disadvantages of subclass trees is that they can be susceptible to changes in superclasses, particulary when the trees are deep. Also, using P31 with a metaclass is equivalent to explicitly indicating a semantic type of the item, and makes it easier for humans to understand it at a glance.

I think both third-order class (Q24017465) and cell type (Q189118) should be just second-order class (Q24017414).

By the way, you seem to have deep insights into this topic, so I hope you'll create an account and join us. --Okkn (talk) 10:09, 16 September 2020 (UTC)

Distinction between prominent and not so promnient anatomical structures isn't straightforward. If data user can't really know why e.g. blood cell (Q211709) (along with its subclasses in turn) isn't a (prominent) anatomical structure, then this P31 scheme seems to have little meaning. Also, while subclass relations and subclass trees in their (deeper) parts are prone to disruption, doesn't the same apply do instance relations?

Item pages don't provide good overview of subclass tree and its perhaps more interesting parts ("ontological level", "semantic type") indeed, but I'd consider it as a limitation of current user interface on Wikidata, rather than a limitation of data model.

Do you mean anatomical structure (Q4936952) (not Q24017465) should be kept as first-order metaclass? If so, then it shouldn't be a parent class to other metaclasses, they way it currently is set for cell type (Q189118).

As for metaclasses in general, I think metaclass is more useful when it can be naturally described as type of things (cf. ship type (Q2235308)) or when there are well-defined ranks of metaclasses (e.g. mineral group (Q1936581), mineral supergroup (Q3977918)). In case of anatomical structure we might label metaclass more explicitly as "type of anatomical structure", but this still feels kind of artificial.

Now that I've looked around in this area in relation to this discussion, I've noticed that use of P31/P279 is problematic in some other aspects as well. I may dig a little deeper into this rabbit hole and comment on it later in some other venue. :) Regretfully I don't have capacity to work on anatomical items systematically myself. 2001:7D0:81F7:B580:61DA:A1C2:3F7B:44CF 09:49, 17 September 2020 (UTC)

How we will see unregistered users

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:20, 4 January 2022 (UTC)

Reminder to participate in the Ratification vote of UCoC Enforcement guideline

This message has been sent because you are administrator in this project. If you voted, Thank you and please ignore this message 🙂

Hello Okkn,

The Ratification vote of Universal Code of Conduct Enforcement Guidelinein currently taking place until March 21. If you didn't vote yet, please take a few minutes to participate the ratification vote! Your voice is important.

Best, —YKo (WMF) via MediaWiki message delivery (talk) 04:44, 15 March 2022 (UTC)

P31 on CJK characters

Hello, since I started adding instance of (P31)CJKV character (Q53764732) to the items on Unicode characters in CJK ideograph blocks and noticed you had already applied instance of (P31)ideograph (Q53764738) and/or instance of (P31)kanji character (Q53764782) for characters in the CJK Unified Ideographs (Q994386) block multiple years ago, I stopped toolforge:quickstatements/#/batch/78585 to avoid redundancy (but continued the other batches since the relevant items did not contain any similar statements yet). However, I wonder whether you applied the statements based on Unihan data or added them to all characters in the block. I'm not fully sure yet whether to revert the ~400 edits the batch performed before I stopped it. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 11:58, 15 March 2022 (UTC)

UPD: There are about 700 potentially redundant claims; see https://w.wiki/4xHy. Courtesy ping @Theknightwho. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 23:19, 15 March 2022 (UTC)

I don't think there's a problem in having redundancy on this. Having them all specifically entered as CJK characters ensures full coverage, and then details of which languages they're used in can be filled out over time as it's a much more complex job. Theknightwho (talk) 23:54, 15 March 2022 (UTC)

@1234qwer1234qwer4: I did not refer to Unihan or any other database, but semi-manually maintained commonly used Japanese kanji character (Q53764782) instances such as Jōyō kanji (Q875368). In other words, it does not cover all characters in CJK Unified Ideographs (Q994386), or even Japanese kanji characters. I think all characters in CJK Unified Ideographs (Q994386) are ideograph (Q53764738) (subclass of CJKV character (Q53764732)). By the way, whether or not the definition of CJKV character (Q53764732) includes そ (Q74807470) and Hangul syllable (Q55809450) as well as ideograph (Q53764738) needs to be debated. --Okkn (talk) 11:49, 16 March 2022 (UTC)

I think for the last part, it's best to follow the Unicode standard, which has CJK, Hangul, Hiragana and Katakana separated as different writing systems (https://www.unicode.org/versions/Unicode14.0.0/UnicodeStandard-14.0.pdf, table 6-1, page 262); this also makes sense since Hangul, Hiragana and Katakana are not shared between the three CJK languages. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 19:02, 16 March 2022 (UTC)

The term "CJK" does not appear in Table 6-1, but instead "Han" appears; the Han character certainly does not include hiragana or hangul, but the CJK character is ambiguously defined. Of course, the CJK unified ideographs refer to Han characters. The definition of ideograph (Q53764738) is also ambiguous in Wikidata: there appears to be no uniformity as to whether ideograph (Q53764738) refers (1) only to Han characters used in China or (2) to all Han characters used in CJK(V). If the latter, CJKV character (Q53764732) and ideograph (Q53764738) refer to the same thing. --Okkn (talk) 07:50, 17 March 2022 (UTC)

@Theknightwho Feel free to add the remaining statements as desired. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 15:14, 28 May 2022 (UTC)

Japanese Numbers

I tried to complete japanese numbers 0-9. Since you have proposed reading pattern of Han character (P5244) I ask you to review them 😬🙏.

I have a feeling that the list is both incomplete and erroneous. 一つ/ひとつ (L686295) looks suspicously like its a number+counter but jmdictdb lists it as meaning one 🤷. What would you propose to do with counter words? What Lexical category are they? – Shisma (talk) 07:34, 23 July 2022 (UTC)

@Shisma: Although 「つ (L625739)」 can also be interpreted as a Japanese counter word (Q2116774), the entire word 「一つ」or「ひとつ」 can be regarded as an old (before Chinese words introduced) Japanese word for counting (numeral (Q63116)). 「つ」 is a special Japanese counter word (Q2116774). Perhaps originally, 「つ」 was not an independent Japanese counter word (Q2116774), but a part of a word, and actually 「つ」 can only be used for the numbers 1 thorough 9 in Japanese. Similar to 一つ/ひとつ (L686295) (jmdictdb), the numbers less than or equal to 10 have the following words of old Japanese origin: 「二つ/ふたつ」(2; jmdictdb), 「三つ/みっつ」(3; jmdictdb), 「四つ/よっつ」(4; jmdictdb), 「五つ/いつつ」(5; jmdictdb), 「六つ/むっつ」(6; jmdictdb), 「七つ/ななつ」(7; jmdictdb), 「八つ/やっつ」(8; jmdictdb), 「九つ/ここのつ」(9; jmdictdb), and 「十/とお」(10; jmdictdb). These are good to exist as special numeral (Q63116) lexemes. Is this the answer to your question? Feel free to ask me anytime if you have any questions. --Okkn (talk) 10:01, 23 July 2022 (UTC)

This is helpful. thank you. I'll make sure lexemes exist for the ten つ-numbers you listet. But please review the 32 lexemes so far created – Shisma (talk) 10:19, 23 July 2022 (UTC)

• 一/いつ (L686293) exists as a Kanji reading (kan-on (Q6360011)), but this reading is not usually used as a numeral in Japanese.
• 三/さ (L685724) is not read this way as a numeral. (It may be read this way only in personal names, etc.).
• 七/な (L686408) is not read this way as a numeral. (It may be read this way only in personal names, etc.).
• 八/は (L686409) is not read this way as a numeral. (It may be read this way only in personal names, etc.).

--Okkn (talk) 14:16, 23 July 2022 (UTC)

• kan-on (Q6360011):
  • 0: 零/れい 零/れい (L625710)
  • 1: 一/いち 一/いち (L47983)
  • 2: 二/に 二/に (L625227)
  • 3: 三/さん 三/さん (L641828)
  • 4: 四/し 四/し (L641752)
  • 5: 五/ご 五/ご (L625705)
  • 6: 六/ろく 六/ろく (L625255)
  • 7: 七/しち 七/しち (L686406)
  • 8: 八/はち 八/はち (L625708)
  • 9: 九/く 九/く (L293662) or 九/きゅう 九/きゅう (L625285)
• kun'yomi (Q1147749) (usual):
  • 1: 一つ/ひとつ 一つ/ひとつ (L686295)、一/ひと 一/ひと (L686294)
  • 2: 二つ/ふたつ×、二/ふた 二/ふた (L686343)
  • 3: 三つ/みっつ×、三/み 三/み (L686402)
  • 4: 四つ/よっつ×、四/よ 四/よ (L686404)、四/よん 四/よん (L625228)
  • 5: 五つ/いつつ×、五/いつ×
  • 6: 六つ/むっつ×、六/む 六/む (L686405)
  • 7: 七つ/ななつ×、七/なな 七/なな (L625229)
  • 8: 八つ/やっつ×、八/や 八/や (L685723)
  • 9: 九つ/ここのつ 九つ/ここのつ (L679423)、九/ここの 九/ここの (L679425)
• kun'yomi (Q1147749) (old-fashioned spoken language?):
  • 1: 一/ひい
  • 2: 二/ふう 二/ふう (L686347)
  • 3: 三/みい
  • 4: 四/よお
  • 5: 五/いつ
  • 6: 六/むう
  • 7: 七/なな 七/なな (L625229)
  • 8: 八/やあ
  • 9: 九/ここ 九/ここ (L680105) or 九/ここの 九/ここの (L679425)
• English-derived words:
  • 0: ゼロ (zero) 〇/ゼロ (L625706)
  • 1: ワン (one) ワン (L686346)
  • 2: ツー (two) ツー (L686348)
  • 3: スリー (three)×
  • 4: フォー× or フォア (four) フォア (L679225)
  • 5: ファイブ (five)×
  • 6: シックス (six)×
  • 7: セブン (seven)×
  • 8: エイト (eight)×
  • 9: ナイン (nine)×

--Okkn (talk) 14:27, 23 July 2022 (UTC)

wow, thank you. I'm gonna work on it 👌 – Shisma (talk) 15:07, 23 July 2022 (UTC)

Representations…

could you please translate label & description of kanji representation (Q112898118) and kana representation (Q112898119) to japanese?

I'm using it to qualify homograph lexeme (P5402) statements in japanese lexemes like in 歯/は (L688579) or 歯/し (L688580) or 四/し (L641752). Do you have an opinion about this modelling? Thank you 🙏 – Shisma (talk) 16:32, 29 July 2022 (UTC)

I have translated them (although specialists may use different translations).

I think this is a very appropriate and consistent modeling, although the concept of homographs is not often used in Japanese language. By the way, homographs with respect to kana expressions are also homophone (Q221079). In Japanese, the concept of homophone (Q221079) is widely known. I also found homophone form (P10822). --Okkn (talk) 06:50, 30 July 2022 (UTC)

True, it‘s gonna be a long list for single syllable words 😅 Shisma (talk) 09:16, 30 July 2022 (UTC)

Counts instances of

in response to your comment:

 Support. However, some Japanese numerals (such as 個/こ (L625738), 本/ほん (L679421), and 枚/まい (L626242)) are too broadly adaptable, so it is difficult to determine how to limit them.

don't you think we can manage with classes? For the proposal I created long, thin object (Q113519195) which has the subclass scissors (Q40847). My assumption was, that every subclass of scissors (Q40847) (like nail scissors (Q1963547)) would also be counted with 丁/ちょう (L689194). Does it? Are there exceptions where you would count subclasses of something with a different counter? – Loominade (talk) 10:31, 15 August 2022 (UTC)

It may not be a good idea to incorporate ad hoc items like long and narrow object (Q113383399), which rely on Japanese grammar, into the Wikidata ontology.

By the way 丁/ちょう (L689194) -> scissors (Q40847) is not a good example. Most Japanese use 本/ほん (L679421) instead of 丁/ちょう (L689194) to count scissors. So, when looking at nail scissors, most Japanese would not use 丁/ちょう (L689194). Examples where 丁/ちょう (L689194) is often used include tofu (Q177378) and handgun (Q1574963). I can't think of a good example, but I think we often use more generic numerals like 個/こ (L625738) when counting special objects. --Okkn (talk) 11:13, 15 August 2022 (UTC)

It may not be a good idea to incorporate ad hoc items like long and narrow object (Q113383399), which rely on Japanese grammar, into the Wikidata ontology.

I was sure this would be possible but I wasn't sure if it was a good idea. Nobody in the proposal discussion seemed concerned about it. Maybe I didn't make it clear enough? Well, we don't have to create classes like this just because the property proposal included it. Is there an expert on ontology in wikidata somewhere? –Loominade (talk) 11:50, 15 August 2022 (UTC)

Japansese adjective forms and their grammatical features

hi,

I'm writing to you because you created a lot of japanese lexemes. I'd like to programmatically demonstrate the negative form of a given japanese adjective. In my understanding, in these case of 暑い/あつい (L21412) that should be あつくない. So I would have queried for the one form that is あつく in this lexeme by filtering only those forms that have the grammatical feature conjunctive form (Q2888577). Unfortunaly that also gives me あつかっ since it is also a conjunctive form (Q2888577). In my understanding this form allows me to form the past form あつかった. So I see why they are both conjunctive. But how can I discriminate between the two? shouldn't they have another grammatical feature that allows me to figure out if they can form the past or negative form? I wouldn't want to query for a conjunctive form (Q2888577) that ends on く 😅 – Shisma (talk) 13:51, 11 April 2023 (UTC)

@Shisma: Unfortunately, in Japanese grammar, both are just said to be "conjunctive forms". It always takes the 「-かっ」 form when followed by た (L629) and the 「-く」 form when followed by ない (L621) or 成る/なる (L727140). However, the Japanese grammar that Japanese people learn in compulsory education may differ from the one that non-native speakers learn. I am not familiar with the latter. --Okkn (talk) 14:17, 11 April 2023 (UTC)

so you are suggesting that, for my purpose, filtering the ending 「-く」or 「-かっ」should suffice? – Shisma (talk) 14:28, 11 April 2023 (UTC)

Yes, you are right. That rule is always true for い-adjective (Q34698). --Okkn (talk) 14:33, 11 April 2023 (UTC)

great. thank you! – Shisma (talk) 14:34, 11 April 2023 (UTC)

Centrair

Centrair means Chubu International Airport. 問答 (talk) 04:30, 29 April 2023 (UTC)

@問答: I know that 'Centrair' is a common name for Chubu Centrair International Airport (Q679345). However, Centrair (Q5060186) is not the place to explain the meaning of 'Centrair', but a corresponding item to the instance of Wikimedia disambiguation page (Q4167410) that exists in the English (en:Centrair) and Japanese (ja:Centrair) Wikipedia. Wikidata items are managed in units of 'concepts' rather than in units of 'names'. For Wikidata, name labels such as 'Centrair' are not important, all that is needed is a QID (eg. Q5060186) to identify the item representing the concept. The item representing the concept equivalent to your 'Centrair' is Chubu Centrair International Airport (Q679345). In Wikipedia, when there are several things with the same name, it may be debatable which one takes precedence or whether it should be on the disambiguation page, but in Wikidata this is not necessary and different concepts are represented by different items (QIDs). If you want to know more about Wikidata items, see Help:Items. --Okkn (talk) 05:01, 29 April 2023 (UTC)

Sysop rights and inactivity

Hi Okkn, I have requested removal of your sysop rights at meta due to inactivity. You have made 4 sysop actions in the last six months (see User:MisterSynergy/activity/Administrator). --Lymantria (talk) 17:41, 1 February 2024 (UTC)

Thank you for your time. I hope that one day I will be able to be active again. --Okkn (talk) 22:22, 1 February 2024 (UTC)

Thank you for the good work you have done and indeed I hope to see you back being active again one day. --Lymantria (talk) 12:55, 2 February 2024 (UTC)