Jump to content

User talk:Xain36/Archive 2

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 1Archive 2Archive 3Archive 4Archive 5

Wikidata weekly summary #357

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Stanglavine
    • An open discussion on how to model one-way train routes is now taking place, and everyone is welcome to pitch in
  • Development
    • Update property suggester data (phab:T216270)
    • Add a link to the shex-simple tool to make it easier to check entities against a Schema (phab:T217331)
    • Make the placeholders on Special:NewSchema now match the ones on Special:NewItem (phab:T215386)
    • Check for edit conflicts when editing schemas (phab:T217338, phab:T218300)
    • Enable the parser cache for Schema pages (phab:T218459, phab:T218769)
    • Use the FormatAutocomments hook for Schemas to implement translatable edit summaries (phab:T218889)
    • Implement a proper Wikibase-Termbox-Integration according to the ADR (phab:T214679)
    • Fix the emoji breaking the termbox column layout (phab:T217244)
    • Correctly showing revisions with the new termbox (phab:T210615)
    • Correctly handle user-specific language settings in the new termbox (phab:T218111)
    • Fix an issue for score extension (phab:T218535)
    • Turn off RDF support for entity types that doesn't support it (phab:T213483)
    • Respect nofollow config on wikidata identifier links (phab:T175230)
    • Allow accessing Wikibase entities from multiple (Wikibase) databases (phab:T214557)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


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)

Scripts++ Newsletter – Issue 4

News and updates associated with user scripts from the past month (March 2019).

Hello everyone and welcome to the fourth issue of the new Wikipedia Scripts++ Newsletter:

Miscellaneous


Enjoy your April Fool's, --DannyS712 (talk) 18:43, 30 March 2019 (UTC)

The Signpost: 31 March 2019

News, reports and features from the English Wikipedia's weekly journal about Wikipedia and Wikimedia

Wikidata weekly summary #358

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Work on a dashboard for external identifiers (phab:T204440)
    • Add baserevid to WikibaseLexeme API modules (phab:T217243)
    • Add tests for embed.html (phab:T212649)
    • Improve features for wikibase vandalism detection model (phab:T194737)
    • Improve Property Info cache performance (phab:T218115, phab:T218197)
    • Adding nofollow to external identifiers links (phab:T175230)
    • Hide query helper by default in Query Service (phab:T217886)
    • More work on wb_terms normalization (Phab board)
    • Enable trimming whitespace around Label/Description/Aliases and Schema text (phab:T215761)
    • Prevent moving Schemas between namespaces (and generally) (phab:T219313)
    • Limit the length of Schema labels, descriptions, aliases, and schema text in the frontend (phab:T218867)
    • Add tracking for clicks on the “check entities against this Schema” link (phab:T218899)
    • Disallow importing of Schemas from another wiki or XML files to avoid ID conflicts (phab:T218181)
    • Make sure RTL text is being handled correctly in the Schema labels, descriptions and aliases table (phab:T219136)
    • Add a publish button on mobile termbox: (phab:T218573)
    • Building the wbeditentity request to be fired on save request: (phab:T218577)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #359

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • More work on documenting and preparing the announcement for the Wikidata External Landscape dashboard (phab:T204440)
    • Improved the documentation of WMDE analytic documents (phab:T219844)
    • Set up translatable schema edit summaries using the FormatAutocomments hook (phab:T218893)
    • Improved right-to-left support on schema pages (phab:T219298)
    • Protected schemas against imports (phab:T218181) and page moves (phab:T219313) and disabled the useless “move” and “create” protections for them (phab:T219980)
    • Improved schema edit conflict detection to allow merging of non-conflicting edits (phab:T218300, phab:T219173)
    • Improved the Extension:WikibaseSchema documentation on mediawiki.org (phab:T219979)
    • Fixed a bug on Lexicographical Data when editing existing grammatical features (phab:T219318)
    • Increased musical notation datatype string length limit to 1500 characters (phab:T218767)
    • Got ready for the last steps of new constraint level for suggestions (phab:T204439)
    • More work on allowing editing of mobile termbox fields (phab:T216987)
    • Let term value fields grow with their content (phab:T220185)
    • More work on migrating away from wb_terms

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #360

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Added Sámi monolingual language codes sia (Akkala), sjk (Kemi) and sjt (Ter), thanks to Jon Harald Søby (phab:T217521)
    • Moving forward with enabling constraints suggestions for everyone and remove beta feature (phab:T220609)
    • Fixing an issue with displaying mapframes for geocoordinate on client (phab:T220122)
    • Make it impossible to set the same content in the same language for label and description (phab:T212869)
    • Catch Exceptions where the entity can not be serialized due to being too big (phab:T217741)
    • Fix the order of value suggestions based on constraint (phab:T220587)
    • Add links on entity suggestions from constraint definitions (phab:T207363)
    • Increase musical notation datatype string length limit to 1500 characters (phab:T218767)
    • More work on making the new mobile termbox editable (phab:T216987)
    • More work on migrating away from wb_terms

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #361

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Improved the external identifiers landscape (phab:T204440)
    • Prepare process and announcement for the wb_terms migration to come
    • Allow configuring WDQS UI without changes to files under version control (phab:T194179)
    • Configure suggestion constraint level on Beta (phab:T221107)
    • Graduate suggestions based on constraints beta feature out of beta features (phab:T209879)
    • Editing of labels and descriptions on mobile (phab:T216987)
    • Editing aliases on mobile (phab:T218690)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #362

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: BRPever
  • Development
    • Displaying mapframes for geocoordinate on client requires preprocessing by the user (phab:T220122)
    • Fixing cursor jumping to next field and overlapping of menus (phab:T172937)
    • Wikidata a focus issue on grammatical features field (phab:T218229)
    • Add language codes rm-rumgr, rm-sursilv, rm-surmiran, rm-sutsilv, rm-vallader, rm-puter for Lexemes (phab:T210293)
    • Align RTL languages in glosses to right (phab:T203081)
    • Add new monolingual codes: qya + sjn, el-cy, syc, abq, hbo) (phab:)
    • Fix a bug with NewLexeme suggester menu (phab:T199409)
    • Created a dedicated Phab board to help tool builders with the changes on wb_terms
    • More internal work to get the first version of mobile termbox ready for deployment

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Scripts++ Newsletter – Issue 5

News and updates associated with user scripts from the past month (April 2019). Hello everyone and welcome to the 5th issue of the Wikipedia Scripts++ Newsletter:

Until next month, --DannyS712 (talk) 00:22, 30 April 2019 (UTC)

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)

The Signpost: 30 April 2019

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 17:38, 30 April 2019 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Xain36/Archive_2&oldid=1197267014"