Jump to content

User talk:Xain36

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Xain36 (talk | contribs) at 14:45, 16 February 2020 (→‎February 2020: Replying to GSS (using reply-link)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.



Welcome!

Hello, Xain36, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are a few links to pages you might find helpful:

You may also want to complete the Wikipedia Adventure, an interactive tour that will help you learn the basics of editing Wikipedia. You can visit the Teahouse to ask questions or seek help.

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or ask for help on your talk page, and a volunteer should respond shortly. Again, welcome! --John Maynard Friedman (talk) 14:39, 3 February 2019 (UTC)[reply]

@John Maynard Friedman: Thanks Xain36 (talk) 06:23, 4 February 2019 (UTC)[reply]

February 2019

Information icon Hello, I'm Shellwood. I wanted to let you know that I reverted one of your recent contributions —specifically this edit to Mulberry Violence— because it did not appear constructive. If you would like to experiment, please use the sandbox. If you have any questions, you can ask for assistance at the Help Desk. Thanks. Shellwood (talk) 09:40, 6 February 2019 (UTC)[reply]

@Shellwood: Do you mean this: [1]? Xain36 (talk) 09:42, 6 February 2019 (UTC)[reply]
@Shellwood: I think there is a misunderstanding between this massage. I was reverting vandalism. Xain36 (talk) 09:48, 6 February 2019 (UTC)[reply]

Zawiślak

Hi Xain36, I have reverted your edit to Zawiślak because it was created (and is tagged as) a surname page. I don't think that there are enough articles with names similar to Zawiślak to warrant a disambiguation page, and pages shouldn't be tagged with both {{surname}} and {{disambiguation}}. Leschnei (talk) 13:54, 15 February 2019 (UTC)[reply]

@Leschnei: Thanks for appraising me. Xain36 (talk) 14:13, 15 February 2019 (UTC)[reply]

Articles you might like to edit, from SuggestBot

SuggestBot predicts that you will enjoy editing some of these articles. Have fun!

Views/Day Quality Title Tagged with…
1,387 Quality: Medium, Assessed class: Stub, Predicted class: C Karan Kundra (talk) Add sources
8 Quality: Low, Assessed class: Stub, Predicted class: Start Audit Commission (Hong Kong) (talk) Add sources
1,008 Quality: High, Assessed class: Start, Predicted class: FA 2000s (decade) (talk) Add sources
27 Quality: Low, Assessed class: NA, Predicted class: Start Lunar pareidolia (talk) Add sources
73 Quality: Low, Assessed class: NA, Predicted class: Start Earthlight (astronomy) (talk) Add sources
42 Quality: Medium, Assessed class: C, Predicted class: B Customs and Excise Department (Hong Kong) (talk) Add sources
176 Quality: High, Assessed class: Start, Predicted class: FA Construction of electronic cigarettes (talk) Cleanup
6 Quality: Low, Assessed class: NA, Predicted class: Start My Destiny (Malaysian TV series) (talk) Cleanup
21 Quality: Low, Assessed class: Stub, Predicted class: Stub Uyil (talk) Cleanup
66 Quality: High, Assessed class: Start, Predicted class: GA Lunar lava tube (talk) Expand
66 Quality: High, Assessed class: Start, Predicted class: GA Military of Burkina Faso (talk) Expand
13 Quality: Low, Assessed class: Start, Predicted class: Start Honey in the Horn (talk) Expand
447 Quality: High, Assessed class: Start, Predicted class: GA Texarkana, Texas (talk) Unencyclopaedic
2,062 Quality: High, Assessed class: Start, Predicted class: GA MTV Roadies (talk) Unencyclopaedic
1,265 Quality: Medium, Assessed class: Start, Predicted class: B Think tank (talk) Unencyclopaedic
86 Quality: High, Assessed class: C, Predicted class: GA Human germline engineering (talk) Merge
464 Quality: High, Assessed class: C, Predicted class: GA Designer baby (talk) Merge
41 Quality: High, Assessed class: C, Predicted class: GA Lavender (Nightfall Remix) (talk) Merge
314 Quality: High, Assessed class: C, Predicted class: GA Mushfiqur Rahim (talk) Wikify
5 Quality: Low, Assessed class: NA, Predicted class: Start Crossings (TV series) (talk) Wikify
1,107 Quality: High, Assessed class: C, Predicted class: GA Atkins diet (talk) Wikify
8 Quality: Low, Assessed class: C, Predicted class: Start Kathy Niakan (talk) Orphan
14 Quality: Low, Assessed class: Stub, Predicted class: Stub Eenu Shree (talk) Orphan
6 Quality: Low, Assessed class: Start, Predicted class: Start Er Sanjeev Singh (talk) Orphan
194 Quality: Low, Assessed class: Stub, Predicted class: Start SNAC (talk) Stub
9 Quality: Low, Assessed class: Stub, Predicted class: Start Beibut Atamkulov (talk) Stub
40 Quality: Low, Assessed class: Stub, Predicted class: Stub Lunar magma ocean (talk) Stub
1,020 Quality: Low, Assessed class: NA, Predicted class: Start My Special Tatay (talk) Stub
52 Quality: Low, Assessed class: Stub, Predicted class: Start Lunar precession (talk) Stub
7 Quality: Low, Assessed class: Stub, Predicted class: Stub KKYR-FM (talk) Stub

Note: All columns in this table are sortable, allowing you to rearrange the table so the articles most interesting to you are shown at the top. All images have mouse-over popups with more information. For more information about the columns and categories, please consult the documentation and please get in touch on SuggestBot's talk page with any questions you might have.

SuggestBot picks articles in a number of ways based on other articles you've edited, including straight text similarity, following wikilinks, and matching your editing patterns against those of other Wikipedians. It tries to recommend only articles that other Wikipedians have marked as needing work. Your contributions make Wikipedia better — thanks for helping.

If you have feedback on how to make SuggestBot better, please tell me on SuggestBot's talk page. Thanks from Nettrom (talk), SuggestBot's caretaker. -- SuggestBot (talk) 05:53, 16 February 2019 (UTC)[reply]

Twinkle preferences

Hi, if you'd like to create CSD and PROD logs automatically for the dashboard, see Wikipedia:Twinkle/Preferences to enable them. A log full of red links can be very useful to prove your experience, for example when applying as a new page reviewer. ~ ToBeFree (talk) 05:31, 19 February 2019 (UTC)[reply]

1993 Aurora shooting

FYI, you moved 1993 Aurora shooting before one week of discussion. Usually, one week should elapse before closing a discussion without WP:SNOW. --Jax 0677 (talk) 15:34, 24 February 2019 (UTC)[reply]

@Jax 0677: I thought 7 days are over (24 Feb-17 Feb = 7 Days). Is there any way to find out the exact time? Regards, Xain36 (talk) 15:56, 24 February 2019 (UTC)[reply]
@Jax 0677: Oh! I got it. Currently I am using my native's time zone, that's why I couldn't notice. Xain36 (talk) 00:11, 25 February 2019 (UTC)[reply]

Yes, it's still very much being discussed. The other Aurora RM discussion was just relisted; so should this one. Please revert your close and relist. Thanks. --В²C 19:11, 24 February 2019 (UTC)[reply]

@Born2cycle: Sorry, but I couldn't get the point about "other RM". Did you mean these "Talk: Aurora, Illinois shooting" and "Talk: 2012 Aurora shooting"? Also the "1993 Aurora" discussion's result is totally clear crystal case as 5 Support and 3 Oppose. Xain36 (talk) 00:34, 25 February 2019 (UTC)[reply]
Um, 5 to 3 is not “crystal clear” especially when you closed it early and when the discussion was still recent. I’m just requesting a relist so others can weigh in. Why the reluctance? —В²C 05:51, 25 February 2019 (UTC)[reply]
@Born2cycle: Sorry, I can't reopen the discussion because I already moved the article. I'm afraid because I am a new user and I don't know what is the fact of "reopen". Also, this discussion little discouraged me from editing. :( Xain36 (talk) 06:11, 25 February 2019 (UTC)[reply]
As a new user you should not be closing RM discussions. Anyway, the move can be reverted. If you can’t move it, file a technical request after you revert your close explaining you’ve re-opened the RM per request and need the corresponding move reverted. —В²C 06:52, 25 February 2019 (UTC)[reply]

@Dekimasu: As a new editor, I need your help. Xain36 (talk) 06:19, 25 February 2019 (UTC)[reply]

Hello Xain36, please don't be discouraged. In this case I would suggest reverting by going into the history of the talk page and re-saving the last edit before your closure. Then you can relist the discussion using {{subst:relisting}}. The move back to 1993 Aurora shooting does not appear to be blocked so you should be able to undo it, but let me know if you need help. It is true that not all move discussions need to be reopened upon request, but I generally agree with В²C that the outcome is still unclear in this case, since the outcomes of move discussions are based upon the strength of the arguments, not by the number of editors supporting or opposing a move alone. Dekimasuよ! 06:59, 25 February 2019 (UTC)[reply]
 Done ;-) Dekimasu. Regards, Xain36 (talk) 08:27, 25 February 2019 (UTC)[reply]
Thank you --В²C 18:00, 25 February 2019 (UTC)[reply]

Info this da person from jojo siwa btw

It is true that her brother is a volgger if you haven’t seen his channel and the episode where he says to jojo that he is a vlogger. Ilikehorses123457 (talk) 22:04, 28 February 2019 (UTC)[reply]

@Ilikehorses123457:Why are you telling me again? I already claimed on the talk page that the edit was a false positive and I have fixed that. I strongly recommend you to provide a verifiable/reliable source for your edits. Regards, Xain36 {talk} 04:35, 1 March 2019 (UTC)[reply]

Zara

Hello Xain36,

This image was shot in NYC protesting company's treatment of workers. Thank you. — Preceding unsigned comment added by 174.202.25.98 (talk) 16:35, 2 March 2019 (UTC)[reply]

Thanks for apprising to me. I have a little issue about your edit, where you provided a photo - "Shame on you Zara!", that's why I reverted your edits. Glad to see you reverted my edit [2]. If need any help then send me a message. Regards, Xain36 {talk} 16:43, 2 March 2019 (UTC)[reply]

Thank you! This image was in SoHo, Manhattan wikicommons category. And is new pic as it was shot in early Feb. Regards, — Preceding unsigned comment added by 174.202.25.98 (talk) 16:50, 2 March 2019 (UTC)[reply]

You're welcome! Xain36 {talk} 16:54, 2 March 2019 (UTC)[reply]

Wikidata weekly summary #354

Result of move request for Sinhalese language

Hi Xain36! Could you please explain why for Sinhala language "The result of the move request was: Not Moved per consensus"?

Wikipedia:Deletion_guidelines_for_administrators#Rough_consensus says "Consensus is not determined by counting heads, but by looking at strength of argument, and underlying policy (if any). Arguments that contradict policy, are based on opinion rather than fact, or are logically fallacious, are frequently discounted."

I provided many mostly strong or medium pieces of evidence in favour of the move, one user provided evidence against that was "based on opinion rather than fact, or ... logically fallacious", one user provided anecdotal evidence in favour, another user provided anecdotal evidence against, and one user provided medium evidence in favour of the move. Here is my rough breakdown on the strength of the evidence presented:

Strong For Medium For Weak For Anecdotal For Inconclusive Anecdotal Against Weak Against Medium Against Strong Against
Consensus reached three times before
Google Trends
Google Ngrams
Seven instances of consensus, attempted moves, and discussions
The New York Times
BBC
Encylopaedia Britannica
Media Wiki (Wikipedia)
Google Books
not yet in reliable published sources
WP:CRYSTAL
the correct term is Sinhala
Sinhalese is still the clear common name in English-language sources
The 'ese' ending is usually used for something that has relation to some proper noun
There is no such thing for Sinhala, the language name stands in itself
"Sinhala" is also the internationally accepted standard name, for e.g. by Unicode Consortium
Majority of the references to "Sinhalese" must come from old texts
5 3 2 2 2 3 0 0 0

If "Strong" is 4, "Medium" is 3, "Weak" is 2, "Anecdotal" is 1, "Inconclusive" is 0, "For" is positive, and "Against" is negative, the total is 20 + 9 + 4 + 2 + 0 - 3 - 0 - 0 - 0 = 32 on a scale from -68 to 68, or re-scaled from 0 to 100: 73.5. On just this evidence, it is almost 3:1 in favour of the move. Maybe these weights should be more like [10, 6, 3, 1, 0, -1, -3, -6, -10], but that doesn't change the final figures by enough to make a significant difference. If more evidence is needed, Microsoft, Apple, Google, Mozilla, Unicode, etc. only call the language "Sinhala". The International Standards Organisation (ISO) says "Sinhala" is the primary name, "Sinhalese" is the secondary name. The language organisations Glottolog (a main article reference), Linguasphere (another main article reference), WALS, Ethnologue, and Omniglot all call it "Sinhala", sometimes recognising "Sinhalese" as an alternate name. Of course, you could disagree with the strengths of some of the evidence, but I don't think it's possible to reasonably reclassify enough evidence to support "Sinhalese" over "Sinhala", or even decide that it's inconclusive overall.

It seems pretty clear to me that the consensus was For, not Against. If my reasoning is wrong, I'd like to have it explained to me. Danielklein (talk) 04:39, 6 March 2019 (UTC)[reply]

@Danielklein:, Well, per consensus: Sinhalese is still the clear WP:COMMONNAME in English-language sources. Also, please see this: 2 and 2. As you pointed Google Trends, shows the ratio of "Sinhala": "Sinhalese" in searches was 4:1 in 2004, increasing to greater than 80:1 since October 2015. No country had fewer searches for "Sinhala" than "Sinhalese", with ratios varying from 8:1 (Canada and the US) to 99:1 or greater (Saudi Arabia, Jordan, Israel, Oman, Italy, Japan). But please see this example: Bengali has known natively/endonym as Bangla. In Google trends, Bangla is most searched on Google. But it doesn't mean we need to change the name of the Article. Bangla and Sinhala are known for native languages and Bengali and Sinhalese is known or written as English-language. Simple. Xain36 {talk} 06:35, 6 March 2019 (UTC)[reply]
Bangla is an interesting case! According to the Unicode Consortium, "Bangla" is the name used in the US, but "Bengali" is the name used in Australia. As an Australian, I didn't even realise there was another name until I saw this on Unicode's website! The trend for "Bengali/Bangla" is quite different, since it shows a consistent 2:1 preference for Bangla:Bengali, i.e. both terms are growing at the same rate. I will continue to call the language "Bengali" because that is the preferred term in my country, despite "Bangla" being preferred world-wide, and also being the name in its own language. If "Bangla" becomes more widely used in Australia, I will change to using that name.
I already addressed the two Google Books links you provided. They include all books including ones published in the 19th century and early 20th century, and those same books republished recently with a new date. Therefore, "Sinhalese" is over-represented in the data, unless you limit it to recent years. "sinhalese language" (23 books),"sinhala language" (27 books).
Out of the 23 "Sinhalese language" books, 3 were published before 1940: two in 1938 and one in 1891. One recent book had no preview to verify the ratio of "Sinhalese language" to "Sinhala language". Seven books surprisingly actually used "Sinhala language" more times than "Sinhalese language". Some books contrast "Sinhalese language" with "Sinhala language", some contrast "Sinhalese language" with "Sinhala" (without the word "language"), decreasing the data set, i.e. "The name of the Sinhalese language is Sinhala." It is necessary to count the occurrences along with their meanings, which is hard to do. However, it is important to be aware of the biases in the data. Some occurrences of "Sinhalese language" only appear in titles in bibliographies, because the older books exclusively use "Sinhalese", never "Sinhala". Long story short, you can't just do two basic searches on Google, compare the number of hits and make a decision. You need to look carefully at the data first, discounting old data and duplicated data. The initial data I've seen so far seems to indicate that authors are more likely to add "language" to "Sinhalese" than "Sinhala", further skewing the data. Just on the surface, of the 19 "Sinhalese" books published after 1986 the ratio of "Sinhalese language":"Sinhala language" is only 12:7, with a further two preferring "Sinhala" to "Sinhalese". A search in the text of these two books shows that "Sinhala" is being used as the name of the language. The final ratio is therefore 10:9, almost even. Of those 4 use "Sinhalese language" 2 to 5 times as much as "Sinhala language", 11 use both terms about the same amount, and 4 use "Sinhala language" 2 to 14 times more than "Sinhalese language".
I rate the statement "Sinhalese is still the clear common name in English-language sources" as anecdotal, because I provided verifiable contrary evidence, and no evidence was provided to back that statement. The evidence that news organisations seem to only use "Sinhala" seems to have been ignored in the final decision. News organisations don't call Ivory Coast "Côte d'Ivoire" despite that country saying that the French name is the only name allowed in any other language. So, since the BBC and the New York Times, etc. call the language "Sinhala", they must have a good, English language reason for doing so. Danielklein (talk) 10:16, 6 March 2019 (UTC)[reply]
@Danielklein:, As a Bangladeshi citizen, we used "Bengali", when we wrote something or spoke in English. For your clarification, "Bangla" is an incorrect spell, you can use Spell Checker, and check which is a correct spell in US and UK. Regards, Xain36 {talk} 12:04, 6 March 2019 (UTC)[reply]
Thank you for your comment, however, I fear this discussion has got off-topic because what Bengali is called in English has nothing to do with what Sinhala/Sinhalese is called in English. Both names are correct, but I can see no strong evidence that Sinhalese is still the preferred term, and lots of strong evidence that Sinhala is now the preferred term. E.g. over a dozen of the largest: technology companies and news organisations that provide services in Sinhala, and language organisations all using Sinhala exclusively, or in the case of some language organisations making it clear that "Sinhalese" is an alternative or secondary name. Why would so many top institutions fly against convention and choose the lesser used name as the only name or main name? I see no reason why they would. If "Sinhala" is good enough for them, including Media Wiki (the software that runs Wikipedia!), then I see no reason why the articles should not go with the established convention and use "Sinhala" as well.
Please let me know if you are reconsidering your close decision, or if your decision is final. I don't want to keep writing you messages if they're doing no good. Danielklein (talk) 00:12, 7 March 2019 (UTC)[reply]

Please review WP:RMNAC

Hi Xain36. Multiple people are complaining about some of your RM closes. As an editor with limited experience I advise you to stick to closing RM discussions where consensus of the participants is nearly unanimous. —В²C 15:35, 11 March 2019 (UTC)[reply]

@Born2cycle:, Oh! I am not aware of this. Where is the source of my reports? Xain36 {talk} 17:14, 11 March 2019 (UTC)[reply]
See User_talk:Born2cycle#New_editor_making_poor_choices and Wikipedia:Move_review#Sinhalese_language. Agan, I advise you to participate in RMs rather than close them. You need to develop a better understanding of the system. If you don’t pay heed to my advice, I’m concerned the community will take formal action. In fact, the MRV and this friendly advice I’m providing now may serve as evidence against you if you don’t stop. —В²C 18:00, 11 March 2019 (UTC)[reply]
@Born2cycle:, Ok, I got it. Xain36 {talk} 18:29, 11 March 2019 (UTC)[reply]

Wikidata weekly summary #355

Wikidata weekly summary #356

Wikidata weekly summary #357

Facto Post – Issue 22 – 28 March 2019

Facto Post – Issue 22 – 28 March 2019

The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.
Back numbers are here.

When in the cloud, do as the APIs do

Half a century ago, it was the era of the mainframe computer, with its air-conditioned room, twitching tape-drives, and appearance in the title of a spy novel Billion-Dollar Brain then made into a Hollywood film. Now we have the cloud, with server farms and the client–server model as quotidian: this text is being typed on a Chromebook.

File:Cloud-API-Logo.svg
Logo of Cloud API on Google Cloud Platform

The term Applications Programming Interface or API is 50 years old, and refers to a type of software library as well as the interface to its use. While a compiler is what you need to get high-level code executed by a mainframe, an API out in the cloud somewhere offers a chance to perform operations on a remote server. For example, the multifarious bots active on Wikipedia have owners who exploit the MediaWiki API.

APIs (called RESTful) that allow for the GET HTTP request are fundamental for what could colloquially be called "moving data around the Web"; from which Wikidata benefits 24/7. So the fact that the Wikidata SPARQL endpoint at query.wikidata.org has a RESTful API means that, in lay terms, Wikidata content can be GOT from it. The programming involved, besides the SPARQL language, could be in Python, younger by a few months than the Web.

Magic words, such as occur in fantasy stories, are wishful (rather than RESTful) solutions to gaining access. You may need to be a linguist to enter Ali Baba's cave or the western door of Moria (French in the case of "Open Sesame", in fact, and Sindarin being the respective languages). Talking to an API requires a bigger toolkit, which first means you have to recognise the tools in terms of what they can do. On the way to the wikt:impactful or polymathic modern handling of facts, one must perhaps take only tactful notice of tech's endemic problem with documentation, and absorb the insightful point that the code in APIs does articulate the customary procedures now in place on the cloud for getting information. As Owl explained to Winnie-the-Pooh, it tells you The Thing to Do.

Links

If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 11:46, 28 March 2019 (UTC)[reply]

Scripts++ Newsletter – Issue 4

The Signpost: 31 March 2019

Wikidata weekly summary #358

Wikidata weekly summary #359

Wikidata weekly summary #360

Wikidata weekly summary #361

Wikidata weekly summary #362

Scripts++ Newsletter – Issue 5

Facto Post – Issue 23 – 30 April 2019

Facto Post – Issue 23 – 30 April 2019

The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.
Back numbers are here.

Completely clouded?
Cloud computing logo

Talk of cloud computing draws a veil over hardware, but also, less obviously but more importantly, obscures such intellectual distinction as matters most in its use. Wikidata begins to allow tasks to be undertaken that were out of easy reach. The facility should not be taken as the real point.

Coming in from another angle, the "executive decision" is more glamorous; but the "administrative decision" should be admired for its command of facts. Think of the attitudes ad fontes, so prevalent here on Wikipedia as "can you give me a source for that?", and being prepared to deal with complicated analyses into specified subcases. Impatience expressed as a disdain for such pedantry is quite understandable, but neither dirty data nor false dichotomies are at all good to have around.

Issue 13 and Issue 21, respectively on WP:MEDRS and systematic reviews, talk about biomedical literature and computing tasks that would be of higher quality if they could be made more "administrative". For example, it is desirable that the decisions involved be consistent, explicable, and reproducible by non-experts from specified inputs.

What gets clouded out is not impossibly hard to understand. You do need to put together the insights of functional programming, which is a doctrinaire and purist but clearcut approach, with the practicality of office software. Loopless computation can be conceived of as a seamless forward march of spreadsheet columns, each determined by the content of previous ones. Very well: to do a backward audit, when now we are talking about Wikidata, we rely on integrity of data and its scrupulous sourcing: and clearcut case analyses. The MEDRS example forces attention on purge attempts such as Beall's list.

Links

If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 11:27, 30 April 2019 (UTC)[reply]

The Signpost: 30 April 2019

Wikidata weekly summary #363

Wikidata weekly summary #364

Facto Post – Issue 24 – 17 May 2019

Facto Post – Issue 24 – 17 May 2019
Text mining display of noun phrases from the US Presidential Election 2012

The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.
Back numbers are here.
Semantic Web and TDM – a ContentMine view

Two dozen issues, and this may be the last, a valediction at least for a while.

It's time for a two-year summation of ContentMine projects involving TDM (text and data mining).

Wikidata and now Structured Data on Commons represent the overlap of Wikimedia with the Semantic Web. This common ground is helping to convert an engineering concept into a movement. TDM generally has little enough connection with the Semantic Web, being instead in the orbit of machine learning which is no respecter of the semantic. Don't break a taboo by asking bots "and what do you mean by that?"

The ScienceSource project innovates in TDM, by storing its text mining results in a Wikibase site. It strives for compliance of its fact mining, on drug treatments of diseases, with an automated form of the relevant Wikipedia referencing guideline MEDRS. Where WikiFactMine set up an API for reuse of its results, ScienceSource has a SPARQL query service, with look-and-feel exactly that of Wikidata's at query.wikidata.org. It also now has a custom front end, and its content can be federated, in other words used in data mashups: it is one of over 50 sites that can federate with Wikidata.

The human factor comes to bear through the front end, which combines a link to the HTML version of a paper, text mining results organised in drug and disease columns, and a SPARQL display of nearby drug and disease terms. Much software to develop and explain, so little time! Rather than telling the tale, Facto Post brings you ScienceSource links, starting from the how-to video, lower right.

ScienceSourceReview, introductory video: but you need run it from the original upload file on Commons
Links for participation

The review tool requires a log in on sciencesource.wmflabs.org, and an OAuth permission (bottom of a review page) to operate. It can be used in simple and more advanced workflows. Examples of queries for the latter are at d:Wikidata_talk:ScienceSource project/Queries#SS_disease_list and d:Wikidata_talk:ScienceSource_project/Queries#NDF-RT issue.

Please be aware that this is a research project in development, and may have outages for planned maintenance. That will apply for the next few days, at least. The ScienceSource wiki main page carries information on practical matters. Email is not enabled on the wiki: use site mail here to Charles Matthews in case of difficulty, or if you need support. Further explanatory videos will be put into commons:Category:ContentMine videos.


If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 18:52, 17 May 2019 (UTC)[reply]

Wikidata weekly summary #365

Wikidata weekly summary #366

The Signpost: 31 May 2019

Scripts++ Newsletter – Issue 6

Wikidata weekly summary #367

Wikidata weekly summary #368

Wikidata weekly summary #369

Wikidata weekly summary #370

Scripts++ Newsletter – Issue 7

The June 2019 Signpost is out!

Wikidata weekly summary #371

Wikidata weekly summary #372

Wikidata weekly summary #373

Wikidata weekly summary #374

Wikidata weekly summary #375

The Signpost: 31 July 2019

Scripts++ Newsletter – Issue 8

Wikidata weekly summary #376

Wikidata weekly summary #377

Wikidata weekly summary #378

Wikidata weekly summary #379

The Signpost: 30 August 2019

Wikidata weekly summary #380

Wikidata weekly summary #381

Wikidata weekly summary #382

Wikidata weekly summary #383

A barnstar for you!!!!

The Anti-Vandalism Barnstar
This is for your valuable efforts for countering Vandalism and protecting Wikipedia from it's threats. I appreciate your effort. You are a defender of Wikipedia. Thank you. PATH SLOPU 10:54, 28 September 2019 (UTC)[reply]

The Signpost: 30 September 2019

Wikidata weekly summary #384

Hi

Xain, you should take a CVUA training. 2402:3A80:A6D:75D5:0:5B:A041:B601 (talk) 14:56, 5 October 2019 (UTC)[reply]

Scripts++ Newsletter – Issue 9

October 2019

Information icon Please do not add inappropriate external links to Wikipedia, as you did to Planting Fields Arboretum State Historic Park. Wikipedia is not a collection of links, nor should it be used for advertising or promotion. Inappropriate links include, but are not limited to, links to personal websites, links to websites with which you are affiliated (whether as a link in article text, or a citation in an article), and links that attract visitors to a website or promote a product. See the external links guideline and spam guideline for further explanations. Because Wikipedia uses the nofollow attribute value, its external links are disregarded by most search engines. If you feel the link should be added to the page, please discuss it on the associated talk page rather than re-adding it. [4] MrOllie (talk) 14:09, 7 October 2019 (UTC)[reply]

MrOllie, Oh Sorry I didn't know about that. I am very sorry. Xain36 {talk} 14:14, 7 October 2019 (UTC)[reply]

Wikidata weekly summary #385

Wikidata weekly summary #386

Wikidata weekly summary #387

Wikidata weekly summary #388 & Wikidata Birthday

The Signpost: 31 October 2019

Wikidata weekly summary #389

Scripts++ Newsletter – Issue 10

Wikidata weekly summary #390

Wikidata weekly summary #391

ArbCom 2019 election voter message

Hello! Voting in the 2019 Arbitration Committee elections is now open until 23:59 on Monday, 2 December 2019. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2019 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:24, 19 November 2019 (UTC)[reply]

Google Code-In 2019 is coming - please mentor some documentation tasks!

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at the English Wikipedia.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 21:58, 23 November 2019 (UTC)[reply]

Wikidata weekly summary #392

Scripts++ Newsletter – Issue 11

The Signpost: 29 November 2019

Wikidata weekly summary #393

Wikidata weekly summary #394

Weekly Summary #395

The Signpost: 27 December 2019

Wikidata weekly summary #396

Wikidata weekly summary #397

Wikidata weekly summary #398

Wikidata weekly summary #399

The Signpost: 27 January 2020

Wikidata weekly summary #400

Wikidata weekly summary #401

Scripts++ Newsletter – Issue 12

February 2020

Information icon

Hello Xain36. The nature of your edits gives the impression you have an undisclosed financial stake in promoting a topic, but you have not complied with Wikipedia's mandatory paid editing disclosure requirements. Paid advocacy is a category of conflict of interest (COI) editing that involves being compensated by a person, group, company or organization to use Wikipedia to promote their interests. Undisclosed paid advocacy is prohibited by our policies on neutral point of view and what Wikipedia is not, and is an especially egregious type of COI; the Wikimedia Foundation regards it as a "black hat" practice akin to black-hat SEO.

Paid advocates are very strongly discouraged from direct article editing, and should instead propose changes on the talk page of the article in question if an article exists, and if it does not, from attempting to write an article at all. At best, any proposed article creation should be submitted through the articles for creation process, rather than directly.

Regardless, if you are receiving or expect to receive compensation for your edits, broadly construed, you are required by the Wikimedia Terms of Use to disclose your employer, client and affiliation. You can post such a mandatory disclosure to your user page at User:Xain36. The template {{Paid}} can be used for this purpose – e.g. in the form: {{paid|user=Xain36|employer=InsertName|client=InsertName}}. If I am mistaken – you are not being directly or indirectly compensated for your edits – please state that in response to this message. Otherwise, please provide the required disclosure. In either case, do not edit further until you answer this message. Template:Z159 GSS💬 12:02, 9 February 2020 (UTC)[reply]

@GSS: it appears to state it at the top of this page. MPS1992 (talk) 15:23, 9 February 2020 (UTC)[reply]

Wikidata weekly summary #402

February 2020

Information icon

As previously advised, your edits give the impression you have a financial stake in promoting a topic, but you have not complied with Wikipedia's mandatory paid editing disclosure requirements. You were asked to cease editing until you responded by either stating that you are not being directly or indirectly compensated for your edits, or by complying with the mandatory requirements under the Wikimedia Terms of Use that you disclose your employer, client and affiliation. Again, you can post such a disclosure on your user page at User:Xain36, and the template {{Paid}} can be used for this purpose – e.g. in the form: {{paid|user=Xain36|employer=InsertName|client=InsertName}}. Please respond before making any other edits to Wikipedia. Template:Z160 GSS💬 18:09, 13 February 2020 (UTC)[reply]

GSS How to do that? Please guide me. Xain36 {talk} 15:10, 14 February 2020 (UTC)[reply]
See WP:DISCLOSEPAY and don't forget add link(s) to all active accounts at websites where you advertise paid Wikipedia-editing services. GSS💬 15:34, 14 February 2020 (UTC)[reply]
GSS, Will you show me a perfect example like an article that has been properly disclosed. Xain36 {talk} 14:45, 16 February 2020 (UTC)[reply]