View source for User:Waldyrious

{{#babel:kea-n|pt-5|en-4|pt-br-3|es-2|gl-2|quickpresets}}

About me: [[m:user:waldir|Waldir@meta.wikimedia]]

== Work in progress ==

* We need a way to explain the reason for constraints.
** I've proposed this [[Template talk:Constraint#Explanation parameter|here]].
* There should be a "TED event ID" property, to complement {{P|P2611}}, {{P|P2612}} and {{P|P2613}}.
** I've proposed it [[Wikidata:Property proposal/TEDx event ID|here]].
* There should be a "source code archives" property to complement {{P|1324}} (which should only contain links to repositories using version control systems).
** See for example the entries at {{Q|3756198}}.
** {{P|953}} is meant for the full text of a written work. It could be expanded to include this case, but I think it's better to keep things explicit.

== To do ==

=== Recurring tasks ===

* Clean up Repology's [https://repology.org/repository/wikidata/problems Problems in Wikidata] report
* Clean up the tricky items in Mix'n'match Exoplanets list

=== Assorted todo ===

* Descriptions (semi-automated?)
** TODO: Add "{{P|27}}→{{P|1549}} {{P|106}}" as description for {{q|5}} items that have both properties and no English description
*** <s>WIP query, for Portuguese people only: https://w.wiki/4K6h</s>
**** Update: this doesn't correctly filter for <code>count(?occupation) = 1</code>; Lukas Werkmeister explained why in Telegram: ''"you’re grouping by <code>?occupationLabel</code> as well, so unless two occupations have the same label, <code>COUNT(?occupation) = 1</code> will always be true"'', and offered an improved version: https://w.wiki/4K75
**** [https://tabernacle.toolforge.org/?#/tab/sparql/SELECT%20%3Fperson%20WHERE%20%7B%0A%20%20%7B%0A%20%20%20%20SELECT%20%3Fperson%20(SAMPLE(%3Foccupation_)%20AS%20%3Foccupation)%20WHERE%20%7B%0A%20%20%20%20%20%20%3Fperson%20wdt%3AP31%20wd%3AQ5.%0A%20%20%20%20%20%20%3Fperson%20wdt%3AP27%20wd%3AQ45.%20%23%20Portuguese%0A%20%20%20%20%20%20%3Fperson%20wdt%3AP106%20%3Foccupation_.%0A%20%20%20%20%20%20MINUS%20%7B%20%3Fperson%20schema%3Adescription%20%5B%5D%20%7D.%0A%20%20%20%20%7D%0A%20%20%20%20GROUP%20BY%20%3Fperson%0A%20%20%20%20HAVING(COUNT(%3Foccupation_)%20%3D%201)%0A%20%20%7D%0A%20%7D/P21%3BP106%3BDen%2Cpt TABernacle version]
*** Sample of the QuickStatements v2 (CSV) commands to add the missing descriptions (based on the data outputted by the query):
**** qid,Den
**** Q10261736,Portuguese Catholic priest
**** Q10262996,Portuguese banker
**** Q10277601,Portuguese sailor
** Some bots that add descriptions (their code could be useful for inspiration): [[User:Mr.Ibrahembot]], [[User:Edoderoobot]], [[User:MatSuBot]].
* Is there a way to generate a list of Wikidata items that should have a {{P|P1190}}, but don't?
** Is it perhaps [[Template:Book properties|specific]] to [[Wikidata:WikiProject Books#Work item properties|books]]?
** Should it not be extended to other domains (in which case, where to get authoritative mappings?)
** See also: [[Wikidata:WikiProject Ontology]]
* Change [[MediaWiki:Wikibase-entitytermsforlanguagelistview-more]] from "{{int:Wikibase-entitytermsforlanguagelistview-more}}" to "Show all entered languages" (and the same for [[MediaWiki:Wikibase-entitytermsforlanguagelistview-less]] ("{{int:Wikibase-entitytermsforlanguagelistview-less}}" → "Show fewer languages")
* Suggest a new property accepting values of the [[Help:Data type#math|math datatype]] ([[Special:ListProperties/math|list of current ones]]), for multilevel formulas such as [[Q861364#P2534|this one]].
** Something like "has part", but equivalent to the mathematical "where".
** See also discussion [[Property talk:P2534#Symbol definitions|here]].
** TODO: split first and last names; group by count; check for existence of the top ones; create when needed.
* Colors: {{Q|5148617}}, {{Q|2357944}}... colormap? viridis?

=== Geography ===

(Moved to [https://workflowy.com/s/mapsgeography-data/fUUKRXgtOSI28V3v Workflowy].)

=== Cape Verde ===

* [[Wikidata:WikiProject Cape Verde]]
* [https://tabernacle.toolforge.org/?#/tab/sparql/SELECT%20%3Fq%20WHERE%20%7B%3Fq%20wdt%3AP27%20wd%3AQ1011.%7D/P18%3BP21%3BP106%3BDen%2Cpt%3BP735%3BP734%3BP1449%3BP742%3BP1477%3BLpt TABernacle dashboard of Cape Verdean people]
*** TODO: Ensure items whose labels are pseudonyms have a full name statement with the actual birth name
*** TODO: Add {{statement||P1412|Q35963}} and {{statement||P66|Q1011}} (or any location within it)
** TODO: build a version in the Profiling Wikidata tool, like this one: https://prowd-prototype.herokuapp.com/profile/33

==== Lexemes (kea dictionary) ====

* Books I own
** Dicionário Caboverdiano—Português (Manuel Veiga)
** Léxico do dialecto crioulo do Arquipélago de Cabo Verde (Armando Napoleão Rodrigues Fernandes)
* [https://docs.google.com/spreadsheets/d/1lsHvLlB5_wmDL4kbf8sJ_qaAGli4KNZ1hg6iYqCWXEg/edit#gid=1566994564 Google Sheets file]
* [https://ordia.toolforge.org/language/Q35963 Stats in the Ordia tool]
* Tools to work with lexemes (To experiment with)
** Apparently [https://github.com/Elhuyar/Wikidata-Toolkit-9.0- Wikidata-Toolkit-9.0] (written in Java) was used to convert Basque Wiktionary entries into Wikidata entries
** Here's another one that aims to convert Wiktionary data to Lexemes: https://github.com/nyurik/lexicator (written in Python)
* TODO: Create [[Wikidata:Lexicographical data/Documentation/Languages/kea]], documenting the intended structure for kea lexemes, showing examples of lexemes for various word classes, etc.
** Examples
*** [[Wikidata:Lexicographical data/Documentation/Languages/de|German (de)]]
*** [[Wikidata:Lexicographical data/Documentation/Languages/bn|Bengali (bn)]]
** Contents
*** Guidelines: what language to use for "spelling variant"; how to model dialect variations; which properties to set in the senses, which grammatical features to set in the forms, etc.
*** Instructions for how to create lexemes, add pronunciation, etc.
* TODO: set up completion dashboards for lexemes
** Senses: translations, glosses in en/pt/kea, item for this sense, etc.
** Forms: badiu & sampadjudu, IPA transcription, pronunciation audio
** Perhaps a simplified interface (as a toolforge tool?), similar to how [http://ninjawords.com/ ninjawords.com] did for Wiktionary. Example image:<br/>[[File:Supercompact view of Wikidata for Wiktionary.png|border]]
*** Hauki (listed [[Wikidata:Tools/Lexicographical data|here]], source code [https://github.com/Vesihiisi/Hauki here]) appears to be one such attempt ([https://hauki.toolforge.org/lex/pt/autocarro example])
*** Maybe {{u|Jon Harald Søby}} could work his magic like he did for the [[MediaWiki:Gadget-compact items.css|Compact items]] gadget? 😁
* [https://w.wiki/93o8 Automatic list of kea lexemes]: {{SPARQL
|query=SELECT ?item ?lexemeLabel WHERE {
    ?item a ontolex:LexicalEntry ;
            dct:language wd:Q35963 ; 
            wikibase:lemma ?lexemeLabel .
  }
}}

==== TEDxPraia ====

Goal: Add items for the TEDxPraia event ([http://www.tedxpraia.com tedxpraia.com], [https://www.ted.com/tedx/events/19377 TED event ID 19377]) and talks

* [https://www.youtube.com/playlist?list=PLsRNoUx8w3rNW-stxwwifZ-FkVfpba5qx video playlist]
** [https://www.youtube.com/watch?v=9Thv4mUBvAo 3rd edition live stream]
* Existing instances of {{LinkedLabel|Q23058953}}: https://w.wiki/LJ6
** Rendered version, updated regularly: [[Wikidata:TED/TEDx Talks]]
** Note: at the moment not all of these (https://w.wiki/LJ7) have a {{property|P2613}}. I believe that ID is only available for those that have been featured on the main TED.com site.
** That said, they should all have {{P|50}}, {{P|1476}} and {{P|1651}}. At the moment most of them (https://w.wiki/LJ9) only have the author (but the title can be easily extracted from the label)
* Existing subclasses of {{LinkedLabel|Q23058942}}: https://w.wiki/LJA
** Lists that should be synced with the result of the query above:
*** [[w:List of TEDx conferences]]
*** [[w:Category:TEDx conferences]]
*** [[w:Template:TEDx]]
*** [[c:Category:TEDx]]

=== Scripts / gadgets ===

* Auto-fill item titles (labels) with corresponding language's article title (using the same algorithm as [[mw:pipe trick|link piping]] to cut out parentheticals, etc.)
** [[User:Waldir/autoFill.js]]
** Use button to auto-save (dialog asking to confirm)
** Support fallback languages
* Suggest content for unfilled descriptions, with:
** First sentence of corresponding language's article
** Automatic translation of description in other languages, in the order defined by translatewiki's fallback chain (should be accessible through API), ultimately falling back to English
* Highlight (bolden) the label for the current interface language, or move it to the top
** [[Wikidata:Tools#Main language first]]

=== Musical chords ===

Goal: model [https://docs.google.com/spreadsheets/d/13tYbx-kR9hKMssnMTIaOVnHTwMrQmKKhhxqAacT7Zx8/ musical chords] [https://tools.wmflabs.org/reasonator/?q=Q911604&lang=en in Wikidata].

* Currently there are various {{Statement|*|P279|Q170439}}but they should be separated into two families: relative chords (i.e. chords comprised of a specific relationship between the component notes, like {{Q|Q5358758}}), and "absolute" chords (i.e. chords built around a specific root note, like {{Q|Q24076679}}). Then there should be items for the individual chords at each intersection of those two categories. There are other categories as well, e.g. chords by number of notes (e.g. {{Q|Q944899}})
* TODO: Synthesize and record audio samples of all chords, upload the files to Commons, and add them to the Wikidata items
** Should showcase the individual notes and the full chord – [[:File:F-A-C-E-F chords.ogg|example]]
** Possibly in MIDI format – [[:File:D chord in all fourths tuning.mid|example]]
* TODO: Generate standardized diagrams for all main chords and add them to the items
** sheet music diagrams
*** [[:File:Chord D.svg|Example for D major]]
** [[c:Category:Pitch constellations|pitch constellation]] images 
** [[c:Category:Guitar fretboard diagrams|guitar fretboard diagrams]] (in standard tuning). Possibly using [http://vexflow.com/vexchords/ vexchords]
** [[c:Category:Piano chord diagrams|piano chord diagrams]] (see also the parent categories [[c:Category:Chords on musical keyboards|Category:Chords on musical keyboards]] and [[c:Category:Musical keyboard diagrams|Category:Musical keyboard diagrams]])
*** [[:File:Re maggiore.png|Example for D major]]
** [[c:Category:3D Lissajous curves|Lissajous knots]] (preferably [[c:Category:Blue knots rendered; animated|animated]], or even in [[c:Category:STL mathematics|actual 3D]])
* Besides chords, notes should also be represented — both the generic ones (aka pitch classes) like {{Q|Q843813}}, and the specific ones belonging to a given octave, like {{Q|Q96254632}}.
* [[Wikidata:List of properties/work#Wikidata property for items about musical works]]
* Dynamic list (query): [https://w.wiki/C4C Music-related (non ID) properties]
** Plus {{P|1236}}
** TODO: request creation of properties for instances/subclasses of {{Q|20202269}} that aren't tied to specific musical works.
*** Perhaps as instances of a new [https://w.wiki/C4D direct subclass] of {{Q|27525351}}
**** currently there's only {{Q|22965078}}
*** Should include:
**** melody-related properties: {{P|2279}}, {{P|826}}, {{P|870}}, ...
**** timing-related properties: {{P|3440}}, {{P|1558}}, {{P|1725}}, {{Q|21655334}}, ...
* [[Wikidata:WikiProject Music]]
** Specifically the sections [[Wikidata:WikiProject Music#Musical scales|Musical scales]] and [[Wikidata:WikiProject Music#Chords|Chords]]
** Relevant properties: {{P|P826}}, {{P|P3030}}, {{P|P6116}}, and others.
* Properties:
** Some notes from the top of my head:
*** Open vs. barre chords
*** [[w:Guitar chord#Alternate tunings|tuning]]
*** [[w:Guitar chord#Playing chords: Open strings, inversion, and note doubling|playing method]]
*** Positioning of each finger (tab notation? Perhaps something similar to {{P|1236}}?)
** Possibly useful:
*** [[Help:Modelling/arts/music]] (empty ATM)
*** Subcategories of [[commons:Category:Guitar chords]] (currently: Guitar chords by tuning‎; Hendrix chord‎; Open chords‎; Power chords‎)
**** The cleanest style can be found at [[commons:Category:SVG guitar fretboard diagrams (LilyPond style)]]
*** ChordPro provides a custom format for encoding a chord, including fingering data:
**** [https://www.chordpro.org/chordpro/Directives-chord.html Chord directive] ([https://github.com/ChordPro/chordpro/wiki/Directives-chord source])
**** [https://www.chordpro.org/chordpro/ChordPro-Configuration-Generic.html#user-defined-chords User-defined chords] ([https://github.com/ChordPro/chordpro/wiki/ChordPro-Configuration-Generic#user-defined-chords source])
*** [http://acousticguitar.com/acoustic-guitar-notation-guide/ Acoustic Guitar Notation Guide]: Overview of the various methods
*** [https://www.guitarhabits.com/how-to-read-a-chord-diagram-and-other-chord-notation/ How to Read a Chord Diagram and Other Chord Notation] (section "Numeric Chord Notation")
**** The gist of it is: <code>x32010</code> represents [[:File:C major chord for guitar (open).svg|this diagram]] (the {{Q|55706505}} chord)
* [https://lists.wikimedia.org/pipermail/wikidata/2019-March/012843.html New data type: musical notation]

=== Software data ===

* [[:File:Pathways-discovery-free.pdf|Pathways for Discovery of Free Software (slide deck from LibrePlanet 2018)]]
** [https://www.softwareheritage.org SoftwareHeritage.org]
** Libraries.io
** Repology (not mentioned)
** Release-monitoring.org
** Several others mentioned

* Clean up license data
** license = {{Q|12948581}}
*** and more generally, any item that has a license set to an item that is not a subclass of {{Q|79719}}
*** or any instance of {{Q|7397}} that has a license set to an item that is not a subclass of {{Q|Q207621}}
** {{Q|218616}} vs. {{Q|3238057}} vs. {{Q|31202214}} vs. {{Q|1340793}}

* Example query: free software that can read the OBJ file format → https://w.wiki/LJ3

* See info at [[User:MichaelSchoenitzer/FLOSS]]
* Maybe use [[toolforge:integraality]] to produce a dashboard of properties coverage
* [https://tools.wmflabs.org/mix-n-match/#/group/Software Mix'n'match catalogs under the "Software" group]

* [[Wikidata:WikiProject Informatics/Software/Properties]]
** TODO: cross-check (merge?) with list of properties
** TODO: propose a "development status" or "lifecycle" property that can complement {{P|582}}, with values like "active", "dormant", "abandoned", "archived", etc. Check for existing ontologies, such as http://repostatus.org or something more formal

* Repology
** See [[Wikidata:Project chat/Archive/2018/01#Using data on software versions from Wikidata in Repology project|Comment by Repology's maintainer]]
** See [[Property talk:P6931#Discussion|discussion]] in the property talk page
** [https://repology.org/projects/?inrepo=wikidata&outdated=1 Automated report] of outdated software versions in Wikidata
*** TODO: to connect this with one of the software version updater tools
** Automated reports of packages missing in Wikidata that are in other repos: [https://repology.org/projects/?search=&maintainer=&category=&inrepo=arch&notinrepo=wikidata&repos=&families=&repos_newest=&families_newest= Arch], [https://repology.org/projects/?search=&maintainer=&category=&inrepo=distrowatch&notinrepo=wikidata&repos=&families=&repos_newest=&families_newest= DistroWatch], etc.
*** TODO: convert these into a Mix'n'match catalog. Ideally weighted/filtered by number of (unrelated) repos?

* [[Wikidata:WikiProject Informatics/FLOSS#Identifiers|Identifiers]] (see also programming-language-specific package managers/repositiories, aka {{Q|98400282}}, such as PyPI, NPM, etc.; non-exhaustive list [https://docs.google.com/document/d/185BkzAVbBjf9C1m9aaOw-KzeSb2Go0uPGwc0sLXMyAw/edit here])
** {{P|P6931}}
** {{P|P8443}}
** {{P|P1972}}
** {{P|P2209}}
** {{P|P2537}}
** {{P|P3597}}
** [https://github.com/gobolinux/Recipes GoboLinux recipe]?
** [[Wikidata:Property proposal/Reposcope ID|Reposcope]]?
** [https://github.com/JuliaPackaging/Yggdrasil Yggdrasil]?
** [https://github.com/NixOS/nixpkgs NixPkgs]?
** [https://packages.guix.gnu.org Guix packages]?
** [https://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/ pkgsrc]?
** [https://pkgs.org/about/ pkgs.org]?
** Other [https://repology.org/repositories/statistics/total large repositories] according to Repology?
*

* Software versions
** {{P|348}}
*** How does one point to the URLs of the release? The URL property seems to be disallowed...
** In table form: {{P|4669}}
*** Should the existing data be converted?
*** Can the tables have a common schema?
**** The [[commons:Data:Sandbox/mediawiki-versions.tab|MediaWiki example]] seems to define its own schema inline...
**** In particular, I'm wondering about the addition of support periods.
** TODO: Import all versions of Julia (and maybe additional metadata) from https://github.com/jlenv/julia-versions.
*** Also add support periods. For instance, minor versions don't have LTS, so newer releases supersede previous ones, as described [https://discourse.julialang.org/t/julia-v1-3-0-has-been-released/31549 here].
** [[User:Github-wiki-bot]] ([https://github.com/konstin/github-wikidata-bot#setup-and-usage usage]) can import releases data from GitHub

==== Unix distro manifests ====

I.e. the set of packages that come pre-installed with (specific versions of) Unix-like operating systems (distros)

* Not in scope for Repology: https://github.com/repology/repology/issues/494
* Early, very incomplete attempt: https://github.com/waldyrious/unix-manifests
* Instances of Linux distros: https://w.wiki/LJD

=== Listeria ===

Try replacing the table at [[:pt:Prémio Camões#Premiados]] with Listeria, based on a query like this: https://w.wiki/LJB

=== Lexemes ===

''See also [[#Lexemes 2|Useful stuff § Lexemes]] below, for general information about these.''

* Add list of [https://docs.google.com/spreadsheets/d/1yehbWFfcfHfICfhmN1suWVoRGxyLneKVuO9a3Z-RTgM/edit EN-PT false friends] ({{Q|202961}}), and link them using {{P|5976}}
* Add lexemes at the top of [[Wikidata:Lexicographical coverage/pt/Missing]]

=== Fonts and characters ===
* {{Q|17451}} ← {{P|2739}}
** {{Q|424598}}
** {{Q|864011}}
** {{Q|58480509}}
* {{Q|4868296}}
* {{Q|377688}} ← {{P|4586}}
* {{P|4099}}
* {{P|5467}}
* [https://docs.google.com/spreadsheets/d/175zOmbW60dWzSFQchk8bWNd4UhHxNB-iY0M3lgdocio/edit#gid=0 Compilation of serif fonts] and their inclusion in various repositories
** TODO: Complete missing information on Wikidata based on that
* TODO: propose a property for [https://www.fileformat.info/info/unicode/char/search.htm fileformat.info character pages], like [https://www.fileformat.info/info/unicode/char/1f782/index.htm this] (and also their file format pages, while we're at it; they are already linked to from various items as "described at URL").
* Individual letters should be modeled by an abstract grapheme item with additional items for specific characters linked as representations thereof.
** For example:
*** {{statement|Q87497006|P1269|Q14667}}
*** {{statement|Q87544199|P1269|Q10714}}
*** Maybe also use for symbols variants like text/emoji representations, gender variations or skin tones?
** {{P|487}} should only be used in the individual characters, not the abstract grapheme (I've seen it modeled as {{statement|Q14662|P487|Č|P518|Q98912}}, but that's redundant and [[w:Database normalization|unnormalized]].
** The link could be {{P|1557}} too, not sure which one is more appropriate.
** What would be the appropriate reverse property?
** The abstract grapheme should have {{P|898}} and {{P|443}} properties, possibly qualified with {{P|407}} if needed.
*** For the audio files, see [[c:Category:Audio files of phonetic samples]], [[w:Help:IPA]], [[w:Template:IPA charts and audio]]
**** Besides the templates listed at [[w:Template:IPA charts and audio]], there appear to be three duplicates: [[w:Template:IPA affricates/audiotable]], [[w:Template:IPA co-articulated consonants/audiotable]] and [[w:Template:IPA non-pulmonic consonants/audiotable]] — I've asked about the duplication [[w:Template talk:IPA affricates#Difference from Template:IPA chart affricate consonants with audio?|here]].

== Useful stuff ==

=== Assorted useful stuff ===

* [[Wikidata:Tools]]
** [https://github.com/maxlath/wikidata-edit wikidata-edit]: Edit Wikidata from NodeJS
** [https://github.com/maxlath/wikidata-cli wikidata-cli]: A command-line interface for Wikidata

* [[Wikidata:List of properties]] and the pages linked from it
** For example, see the tables at [[Wikidata:List of properties/number of entities]] (populated by entries that are instances of {{Q|52513243}})
*** Note: these pages updated by a bot, based on the "instance of" statements in the properties. So it's a good idea to add those statements to properties (similar to categories), and link properties via "related property" statements (similar to "see also" links). This allows navigating the existing properties and discovering potentially useful properties. It's also useful to add aliases (similar to redirects) and even create more specific Wikidata items to categorize properties more accurately in case the existing/available "instance of" entities are too broad or apply to many properties that could be grouped further. I did this, for example, by creating {{Q|111974592}} as a subclass of {{Q|52513243}} and of {{Q|64830420}}
** Tools for browsing/searching properties
*** [https://hay.toolforge.org/propbrowse/ '''Wikidata Propbrowse''']
*** [https://prop-explorer.toolforge.org/ Wikidata Property Explorer] ([https://github.com/stevenliuyi/wikidata-prop-explorer source code repository]) — essentially an interactive representation of the pages under [[Wikidata:List of properties]]?
*** [https://sqid.toolforge.org/#/browse?type=properties SQID's property browser]
** [[Wikidata:Property proposal]]

* languages to skip on wikidata game: <code>zh,ja,ru,uk,hu,ko,pl,tr,et,el,ar,bg,vi</code>

* languages to prefer on wikidata game: <code>pt,gl,es,it,ro,fr</code>

* Useful templates
** link to an item given one of its sitelinks: {{tl|item}} (there's no option for "item by label", since multiple items with the same label can't be [[Special:ItemDisambiguation|automatically disambiguated]])
** link to an item given its ID: {{tlx|LinkedLabel|Q1}} → {{LinkedLabel|Q1}}
** statement (full or partial semantic triple): {{tlx|statement|{{!}}P31|Q5}} → {{statement||P31|Q5}}
** graphical statement display, emulating Wikidata's interface: {{tlx|Statement+| <nowiki>P={{P-|27}} |V={{Q-|145}} </nowiki>}}
*** Use qp/qv to add a qualifier property and value, and rp/rv to add a reference property and value, as demonstrated [[Template:Statement+#Basic|here]].
** block query: {{tlx|SPARQL|query {{=}} ... }}
** inline query: {{tlx|SPARQL Inline|label {{=}} foobar |query {{=}} ... }} → {{SPARQL Inline|label = foobar |query = ... }}

* [[Wikidata:Wiktionary]]

* [http://tools.dicare.org/wikidata-diff/ Wikidata Diff]: compare two entries (example: [http://tools.dicare.org/wikidata-diff/?qids=Q45+Q1011&language=en Portugal vs. Cape Verde])
** Doesn't work with more than two entries :(
** Perhaps there should be a way to filter out external identifiers (which by definition are going to be all different anyway)

* Graph relationship between items / shortest path between two items
** [https://angryloki.github.io/wikidata-graph-builder/ Wikidata Graph Builder]
** [https://wikioverdata.toolforge.org/wikitree/public/ Wikitree] (mostly for family trees, but not just that)
** [https://www.entitree.com/ EntiTree] (defaults to family tree, but has many —hardcoded— properties to build graphs from)
** All of these require the user to provide the property. None of them discovers the best connection. I'd like one that would find the shortest path between two items (sort of playing the [[w:Wikipedia:Getting to Philosophy|Getting to Philosophy]] game, but on Wikidata).
*** [https://www.xefer.com/wikipedia Xefer's tool] and [https://www.sixdegreesofwikipedia.com Six Degrees of Wikipedia] sort of do this, but using links in the text of the Wikipedia articles, rather than explicit relationships in Wikidata.
*** I've suggested this feature to EntiTree in [https://twitter.com/waldyrious/status/1584280815462395904 this tweet].
** More entries may be added to [[Wikidata:Tools/Visualize data]] or [[Wikidata:Tools/Query data]] later

* Narrowing down search results: {{int:search-summary}}

* [https://www.wikidata.org/w/index.php?title=Special%3AAllMessages&prefix=&filter=modified&lang=en&limit=5000 List of Wikidata-tailored MediaWiki system messages]

* [https://tools.wmflabs.org/wikidata-todo/cradle/ Cradle]
** Forms to create Wikidata items by filling all the relevant properties given the type of entity
** Presets are listed at [[Wikidata:Cradle]] (like the [[Wikidata:SPARQL query service/queries/examples|query examples]], this is a shared list that everyone uses)
** Similar to QuickSettings, but has two major differences
*** It is used to create new items, rather than edit existing items
*** There's no way to create custom presets, so the full shared list is a little noisy, with e.g. multiple forms for the same kind of entity depending on what properties one wants to fill in
** Feedback
*** It should be possible to create multiple items at once, e.g. a book as a work, its edition(s), and its author(s)
*** It should be possible to load custom presets, not just those from [[Wikidata:Cradle]]
*** The presets should allow a description field besides just the name
*** The presents should allow usage of the <code><nowiki>{{P}}</nowiki></code> template to make the page more readable
*** Optional fields should be collapsed under a "more" section, to make the forms less overwhelming
*** The <code>+</code> icons should stay in place, rather than be to the left of the <code>-</code> icon when multiple items are added
*** The form should not be fillable if one's not logged in, since logging in loses all input 😱

* [[Wikidata:Wikidata front ends]] and [https://wikibase-registry-query.wmflabs.org/#SELECT%20%3Fitem%20%3FitemLabel%20WHERE%20%7B%0A%20%20%3Fitem%20wdt%3AP11%20wd%3AQ20%20.%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22%20%7D%0A%7D Wikibase instances]

* [[MediaWiki:Gadget-statementSort.js]]

* {{P|4896}}

* Infoboxes: {{Q|Q20702632}}, {{Q|Q42054995}}...

* {{tl|Instances of}}

* According to [[Special:MyLanguageFallbackChain]], the languages that appear in item pages are determined by the contents of the <code><nowiki>{{#babel}}</nowiki></code> box in the userpage.

* TODO: Figure out how to use [https://quarry.wmcloud.org Quarry]
** [[Wikidata:Quarry]]
** [[mw:Wikibase/Schema]] (database schema)
** [https://doc.wikimedia.org/Wikibase/master/php/md_docs_storage_terms.html Wikibase: Item & Property Terms]

* Alternatives to {{P|642}}: [[Wikidata:WikiProject Data Quality/Issues/P642#Use cases by property being qualified]]

=== Data model ===

* [[Wikidata:Glossary]]
* [[Help:Basic membership properties]] — mentions {{P|31}}, {{P|279}} and {{P|361}} (and the latter's inverses, {{P|527}} and {{P|2670}})
** Perhaps it should include {{P|1269}} as well. Proposed [[Help talk:Basic membership properties#Include facet of (P1269) and has parts of the class (P2670)  ?|here]].
** Shouldn't {{P|463}} have an inverse, similar to {{P|361}} <--> {{P|527}}?
* [[mw:Wikibase/DataModel/Primer|Wikibase/DataModel/Primer]]
* [[Help:Modelling/General]]
* [[Help:About data#Modeling data|Help:About data § Modeling data]]
* [[Wikidata:Data model]]
* {{Q|115569934}} — item containing sample statements to demontrate all supported data types

==== Modeling specific topics ====

===== EntitySchemas =====
* Can be used to define the expected statements (and their values) of an item of a given type (e.g. humans should have a given name, a gender with specific values, etc.). This is done using uses the Shape Expressions (ShEx) syntax.  
* Reference links
** [[Wikidata:Schemas]]  
** [[Wikidata:WikiProject Schemas]]  
** [[Wikidata:Database reports/EntitySchema directory]]
** [[phab:project/view/3789|Shape Expressions]] workboard on Phabricator
** [https://docs.google.com/presentation/d/1xbqaJHZEotZuq1GGKYlTJYoAzRKBOoLGKtdSX-R8cQQ/edit#slide=id.g2a0d0270497_0_404 Let's write a schema together]: slides from [[Wikidata:Events/Data Modelling Days 2023|Data Modelling Days 2023]] — lots of useful info (for future reference) but a bit overwhelming to consume standalone.
* [[Wikidata:WikiProject Schemas#Tools|Tools to work with schemas]]
** [https://gitlab.inria.fr/jdusart/shexjapp Shape Designer] — GUI to create schemas (similar to the [[User:Waldyrious#Query building interfaces|visual query builder]])
** [https://wd-shex-infer.toolforge.org/ Wikidata Shape Expressions Inference] — infer schemas from a set of items
** [[User:Teester/CheckShex.js]] — allows selecting an EntitySchema and validating the current item against the schema directly from the Wikidata interface
** Idea: tool to locate similar schemas and merge/consolidate them

===== Model items =====
* [[Wikidata:Model items]]
* [https://query.wikidata.org/embed.html#SELECT%20%3Fsubject%20%3FsubjectLabel%20%3FmodelItem%20%3FmodelItemLabel%20WHERE%20%7B%0A%20%20%0A%20%20%3Fsubject%20wdt%3AP5869%20%3FmodelItem%20.%0A%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%7D List of items] with {{P|5869}} property

===== Property constraints =====
* Property constraints are scoped to a property, so they have to be broad/generic, and can't offer nuanced recommendations depending the type of item (e.g. a different constraint for a human and a country)
* Entity Schemas and model items, on the other hand, pertain to items as a whole, so they provide restrictions/recommendations as cohesive sets, and are more and won't apply to items that don't match that schema).
* Both property constraints and EntitySchemas are amenable to mechanical application/validation, whereas Model items require manual lookup and application.
* Property constraints are much easier to edit and are well integrated with the Wikidata interface than EntitySchemas, though that could change in the future

===== WikiProjects =====
* Many Wikiprojects have lists of properties that can be applies to items in the subject areas they cover. They can also have explicit recommendations about which properties are mandatory, recommended or ancillary.
* TODO: Add some examples

===== Recoin =====

=== OpenRefine ===
* [[Wikidata:Tools/OpenRefine]]
* Now accessible via the browser (since [[Wikidata talk:Tools/OpenRefine#OpenRefine now available on PAWS!|may 2021]]), without installing anything!
** The URL is user-specific; this dynamic link will point to it: https://hub-paws.wmcloud.org/hub/user-redirect/openrefine
* Watch the [[Wikidata:Tools/OpenRefine/Editing/Tutorials/Video|tutorial videos]] and take notes on ideas for using it

=== TABernacle ===

* [[toolforge:wikidata-todo/tabernacle.html|TABernacle]]: provide a list of items for the rows, and a list of properties for the columns; the tool fills up the matrix and helps identify missing data, and add it directly.
* There are short descriptions at [[Wikidata:Tools/Query data]] and the [https://tools.wmflabs.org/admin/tools#!/search/tabernacle Tools directory]
* The help page at [[Help:TABernacle]] is very sparse, but [[Wikidata:TABernacle]] has more detail
* Issues / needed improvements:
** No way to sort the table columns (e.g. to locate empty cells)
*** Tracked as [https://bitbucket.org/magnusmanske/wikidata-todo/issues/15/add-table-sorting-to-tabernacle issue #15]

=== SPARQL queries ===

==== Query building interfaces ====

* [https://query.wikidata.org/ Wikidata Query Service]
* [https://query.wikidata.org/querybuilder/ Wikidata Query Builder]
** Based on [https://wd-query-builder.toolforge.org Wikidata Query Builder] (2017 prototype, no longer updated)
** Previously called "Simple Query Builder", in relation to the 2017 prototype
* [https://hay.toolforge.org/vizquery VizQuery] less visually polished; no options for sorting the results or which properties to show

Notes:
* Neither VizQuery nor Wikidata Query Builder allow combining conditions with <code>OR</code>
* Neither VizQuery nor Wikidata Query Builder allow specifying non-property conditions (number of sitelinks, label/description, ...)

See also [[User:SpinachBot]] (more info [[#Question-answering|below]])

==== REST endpoint ====

* [[mw:Wikibase/DataModel/JSON|DataModel/JSON]]
* GitHub: [https://github.com/wikimedia/wikidata-query-rdf/blob/master/docs/exploring-linked-data.md wikimedia/wikidata-query-rdf: docs/exploring-linked-data.md]
* [[mw:Wikidata query service/User Manual#SPARQL endpoint|SPARQL REST endpoint]]
* [[mw:Wikibase/EntityData|Special:EntityData]]
** Example: https://www.wikidata.org/wiki/Special:EntityData/Q42.json
* [[mw:Wikibase/API|API]]
** Example (get only the claims): https://www.wikidata.org/w/api.php?action=wbgetentities&props=claims&ids=Q42&languages=en&format=json
** Supported values for the <code>props</code> parameter: <code>info</code>, <code>labels</code>, <code>descriptions</code>, <code>aliases</code>, <code>sitelinks</code>, <code>claims</code>, <code>datatype</code>. Multiple values can be provided, separated with <code>|</code>.

==== Documentation ====

===== Introduction / general reference =====
* Visual demonstration of how to build queries using the autocompletion feature: [[Wikidata:SPARQL query service/A gentle introduction to the Wikidata Query Service#Text to SPARQL walkthrough]]
** [[c:File:Wikidata write SPARQL query for dummies.gif]]
** [[c:File:Sparql for dummies - Poet spouses.gif]]
* [[toolforge:wdqs-tutorial|Wikidata Query Service Tutorial]]
* [[Wikidata:SPARQL tutorial]] (see below for extracts)
* Complete syntax reference: [https://www.w3.org/TR/2013/REC-sparql11-query-20130321/#contents SPARQL 1.1 Query Language]
* Wikibook: [[b:SPARQL|SPARQL]]
* Optimization tips: [[Wikidata:SPARQL query service/query optimization]]
** Example of query that was optimized to split out the label service calls: https://w.wiki/6dfX → https://w.wiki/6dfb

===== Prefixes =====
* General reference
** Prefixes (<code>wd:</code>, <code>wdt:</code>, etc.) are used to qualify elements of a query (operators and operands) depending on their type (e.g. item, property, value, etc.)
** [[mw:Wikidata query service/User Manual#Basics - Understanding Prefixes|About prefixes]]
** [[mw:Wikibase/Indexing/RDF Dump Format#Full list of prefixes|Full list]]
* List of prefixes
** <code>wd</code> = Wikidata entity (e.g. ___)
*** <code>wds</code> = Wikidata statement (e.g. ___)
*** <code>wdv</code> = Wikidata value (e.g. ___)
*** <code>wdt</code> = Wikidata property (equivalent to <code>p</code> + <code>ps</code> as shown below)
**** "p: links to a statement node which has various things (the main value, rank, qualifiers, etc), you'll need to use p:P123/ps:P123 to get the value. wdt: is simpler to use if it does what you want (return just the main value of preferred rank statements if they exist, otherwise of normal rank ones), but for anything else it has to be p: and ps:" (Nikki in the Wikidata group on Telegram, [https://t.me/c/1224298920/109391 21 June 2023])
** <code>p</code> = a property statement (e.g. <code>?item p:P123 ?prop.</code>)
*** <code>ps</code> = prop/statement/ — the value of a property statement (e.g. <code>?item p:P123 ?prop. ?prop ps:P123 ?propValue.</code>)
**** <code>psv</code> = prop/statement/value/ — the numeric value of a property as written in the statement (i.e. disregarding the unit)
**** <code>psn</code> = prop/statement/value-normalized/ — the numeric value of a property, normalized to the base unit of the measured quantity.
*** <code>pq</code> = prop/qualifier/ — a qualifier for a property statement (e.g. <code>?item p:P123 ?prop. ?prop pq:P456 ?propQualifier.</code>)
**** <code>pqv</code> = prop/qualifier/value/ — ?
*** <code>pr</code> = prop/reference/ — ?
**** <code>prv</code> = prop/reference/value/ — ?
** '''TODO''': add examples above where missing

===== Query syntax cheatsheet =====

''Condensed/edited from the excellent —but awfully verbose— [[Wikidata:SPARQL tutorial]])''

* The core structure of any query is a [[w:Semantic triple|semantic triple]] (subject, predicate, object).<br/> The "predicate" represents the relationship between subject and object, so I'll call it "relation" to make this clearer:
** <code>?subject wdt:relation wd:object.</code>
* The object of one triple can be the subject of another triple, which allows building more complex queries:
** <code>?nephew wdt:child ?father. ?father wdt:brother wd:uncle.</code>
** There are also two shorthands for this:
*** <code>?nephew wdt:child/wdt:brother wd:uncle.</code> — using the path separator character <code>/</code> to chain predicates together, creating a "property path" from the subject to the object.
*** <code>?nephew wdt:child [ wdt:brother wd:uncle ].</code> — using <code>[]</code> to nest a partial triple, where the omitted part is the missing piece in the outer triple.
* Use <code>,</code> to append another object to the previous triple, reusing both the subject and the predicate:
** <code>?subject wdt:relation wd:object1, wd:object2.</code>
* Use <code>;</code> to append a predicate-object to the previous triple's subject:
** <code>?subject wdt:relation1 wd:object1;</code><br/><code>wdt:relation2 wd:object2.</code>
* Predicates can be combined using regex-like syntax:
** Use the regex-like quantifiers <code>*</code>, <code>+</code> and <code>?</code> to represent how many times a predicate appears in the query:
*** <code>?descendant wdt:child+ ?ancestor.</code>
** The two constructs above are commonly used to specify the notion "instance of X or of any subclass of X":
*** <code>?subject wdt:P31/wdt:P279* ?object.</code>
** As in regex, <code>()</code> groups expressions.
** As in regex, <code>|</code> means OR:
*** <code>?itemA wdt:relation1|wdt:relation2 wd:itemB.</code>
*** Note that this is not an OR for entire triples, but for parts thereof!
*** Parenthesis may be needed to mark the limits of the OR expression: <code>?itemA (wdt:prop1|wdt:prop2)/wdt:prop3 wd:itemB.</code>
**** Note: for OR-ing entire "sentences", wrap them in curly brackets and use the <code>UNION</code> operator between the two blocks.
* Sorting results
** Add <code>ORDER BY ?fooBar</code> after the closing <code>}</code> of the <code>SELECT</code> statement
* Negative assertions
** <code>MINUS { ?item wdt:P3999 ?closure_date }</code>
** <code>FILTER NOT EXISTS { ?item wdt:P3999 ?closure_date }</code>
** Both of the above work... not sure if one is preferable over the other.
** Remove specific items
*** <code>FILTER(?item != wd:Q12345)</code> for a single item
*** <code>FILTER(?item NOT IN (wd:Q123,wd:Q456,wd:Q789))</code> for multiple items
* Optional assertions
** <code>OPTIONAL { ?city wdt:P1082 ?population. }</code>
* More useful info: https://www.slideshare.net/LeeFeigenbaum/sparql-cheat-sheet
** <code>UNION</code> / <code>MINUS</code> (slide 8)
** literal values (strings, numbers, ...)
** comparison operators (<code>!</code>, <code>&&</code>, <code>||</code>, <code>&lt;</code>, <code>=</code>, <code>!=</code>, ...)
** more predicate path operators (<code>^</code>, <code>!</code>, ...)
** underspecified triples (e.g. two or even 3 variables)
* Wikidata-specific helpers
** label and description
*** Include <code>SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }</code>
*** For a variable <code>?foo</code> representing an item, that automatically binds its label to <code>?fooLabel</code>, and its description to <code>?fooDescription</code>
*** To add custom names for the label variables (other than ?fooLabel), use <code>rdfs:label</code>:
***:<code>SERVICE wikibase:label { <br/><!--
-->&nbsp; bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". <br/><!--
-->&nbsp; ?variableName rdfs:label ?customLabel . <br/><!--
-->}</code>
** Associated Wikipedia article ("sitelink")
*** <code>?sitelink schema:isPartOf <https://pt.wikipedia.org/>; schema:about ?item.</code>
** lexeme representations (lemmas)
*** <code>?item wikibase:lemma ?lemma.</code>
*** Filter lemmas by plain string matching: <code>FILTER (str(?lemma) = "foobar")</code>
*** Filter lemmas by regex matching: <code>FILTER (regex(?lemma, '^foobar$'))</code>

==== Example queries ====

* Using the UNION operator: https://w.wiki/3Txr (organizations and communities of which {{Q|1011}} is part)
* Using the FILTER operator and custom names for the label variables: https://w.wiki/44h ([[Wikidata:SPARQL query service/queries/examples#Fathers with non-existent or unusual gender statements|items that are the object in a "father" triplet, but have gender != male]])
* Items whose label (in the language(s) specified in the <code>wikibase:label</code> service command) match a given pattern: TODO
** [[Wikidata:SPARQL query service/queries/examples#Given names with most variations]]
** [[Wikidata:SPARQL query service/queries/examples#Actors whose Spanish label ends with “ (actor)”]]
** [[Wikidata:SPARQL query service/queries/examples#Person labels containing parentheses]]
* Instances of X sorted by number of statements and sitelinks (https://w.wiki/44e)
** Useful to find good representatives as a showcase
** Something like https://w.wiki/44c ought to work for the statement count query, but the number of statements seems quite off, not sure why. Maybe I'd need a nested query for that to work.
* Items with a given qualifier in a given property: https://w.wiki/X6s
* Chain of {{P|131}}, all the way to a {{P|17}}: <code>?item wdt:P131*/wdt:P17 ?country</code>
* Remove duplicates (show only unique items): <code>SELECT DISTINCT ...</code>
* Filtering by number of values in a given property (e.g. persons with double nationality, articles with a single author, etc.)
** https://w.wiki/4K6M
** https://w.wiki/4KB$
** https://w.wiki/4KC2
* List of all statements (property/value pair, including qualifiers) of an item (thanks to {{u|Santhosh.thottingal}}): https://w.wiki/9XTp

=== Written works ===

''books, scholarly/academic/scientific publications (papers, reports, theses/dissertations), etc.''

* [[Wikidata:WikiProject Source MetaData#Projects]]
** [[Wikidata:WikiProject Source MetaData/Bibliographic metadata for scholarly articles in Wikidata]]
* [https://tools.wmflabs.org/scholia/ Scholia], for '''searching''' data already on Wikidata
* [https://sourcemd.toolforge.org/index_old.php Source Metadata], for '''creating'''/importing individual scholarly articles (e.g. by DOI)
** Get DOIs from title at [https://search.crossref.org/ Crossref Metadata Search]
** Wikipage with more info: [[Wikidata:SourceMD]]
** See also [https://sourcemd.toolforge.org/orcidator_old.php ORCIDator]
* Search Google Scholar author profiles: [https://www.google.com/search?q=site%3Ascholar.google.com/citations &lt;search terms&gt; site:scholar.google.com/citations]
* [https://tools.wmflabs.org/mix-n-match/#/group/ig_authority_control_for_works Mix'n'match], for '''linking''' Wikidata items with identifiers in external catalogs
* [https://tools.wmflabs.org/sourcemd/new_resolve_authors.php Resolve authors] (search by name, with fuzzy match option; can create Wikidata item from ORCID)
* [https://tools.wmflabs.org/wikidata-game/distributed/#game=9 Distributed game #9]: identify authors in publications
* [[meta:WikiCite/Shared Citations]] is a proposal for a new Wikimedia project that hosts metadata for reference works in a structured, reusable and machine-readable way.
* Standard format for descriptions of {{statement||P31|Q13442814}} with {{P|50}} or {{P|2093}} 
** One author: <code>scholarly article by <First Last> published in [<month>] <year></code>
** Two authors: <code>scholarly article by <F. Last1> and <F. Last2> published in [<month>] <year></code> 
** Three authors: <code>scholarly article by <F. Last1>, <F. Last2> and <F. Last3> published in [<month>] <year></code>
** Four or more authors: <code>scholarly article by <First1 Last1> et al. published in [<month>] <year></code>
** With journal name: <code>[<month>] <year> scientific article by <author(s)> published in <publication></code>
** TODO: generate a query to get instances of {{Q|13442814}} with no description, or description = "scholarly article", but with author and year of publication, and use it to build a QuickStatements batch to fill the English description using the appropriate format above. 
*** Start by those with a single author (based on [[Wikidata:SPARQL query service/queries/examples#Buildings in more than one country|this]] perhaps?) and no {{P|P2093}} property
*** [https://query.wikidata.org/#SELECT%20DISTINCT%20%3Farticle%20%3FauthorLabel%20%3FarticleLabel%20%3FarticleDescription%20WHERE%0A%7B%0A%20%20%3Farticle%20wdt%3AP31%20wd%3AQ13442814.%20%20%20%23%20scientific%20articles%0A%20%20%3Farticle%20wdt%3AP50%20%3Fauthor.%20%20%20%20%20%20%20%20%23%20with%20at%20least%20one%20author%0A%20%20%3Fauthor%20wdt%3AP31%20wd%3AQ5.%20%20%20%20%20%20%20%20%20%20%20%20%20%23%20...who%20is%20a%20human%0A%20%20%3Fauthor%20wdt%3AP27%20wd%3AQ45.%20%20%20%20%20%20%20%20%20%20%20%20%23%20...from%20the%3A%20USA%20%28Q30%29%2C%20Portugal%20%28Q45%29%2C%20...%20%28this%20is%20just%20to%20make%20the%20results%20list%20shorter%20and%20avoid%20a%20timeout%29%0A%20%20%23%3Farticle%20wdt%3AP577%20%3Fpubdate.%20%20%20%20%20%20%23%20with%20a%20publication%20date%0A%20%20MINUS%20%7B%20%3Farticle%20wdt%3AP2093%20%5B%5D%20%7D.%20%23%20with%20no%20%22author%20name%20string%22%20property%0A%20%20%23FILTER%20NOT%20EXISTS%20%7B%20%3Farticle%20wdt%3AP2093%20%3Fauthor_name_string%20%7D%20%23%20%28alternative%20to%20the%20MINUS%20statement%20above%29%0A%20%20%0A%20%20%23%3Farticle%20rdfs%3Alabel%20%22Generalized%20Lorentz%20invariance%20with%20an%20invariant%20energy%20scale%22%40en.%0A%20%20%23%3Farticle%20rdfs%3Alabel%20%3FarticleLabel.%0A%20%20%23FILTER%20LANG%28%3FarticleLabel%20%3D%20%22en%22%29.%20%23%20doesn%27t%20work%3F%3F%0A%20%20%23FILTER%20REGEX%28%3FarticleLabel%2C%20%22%5EGeneralized.%2Bscale%24%22%29.%0A%20%20%23FILTER%20CONTAINS%28%3FarticleLabel%2C%20%22Lorentz%22%29.%0A%20%20%23FILTER%20STRSTARTS%28%3FarticleLabel%2C%20%22Generalized%22%29.%0A%20%20%20%20%20%20%20%20%20%20%0A%20%20%23%3Farticle%20schema%3Adescription%20%22scientific%20article%22%40en.%0A%20%20%3Farticle%20schema%3Adescription%20%3FarticleDescription.%0A%20%20%23FILTER%20LANG%28%3FarticleDescription%20%3D%20%22en%22%29.%20%23%20doesn%27t%20work%3F%0A%20%20FILTER%20REGEX%28%3FarticleDescription%2C%20%22%5E%28scientific%20%29%3Farticle%24%22%29.%0A%20%20%23FILTER%20CONTAINS%28%3FarticleDescription%2C%20%22scientific%22%29.%0A%20%20%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22%20%7D%0A%7D%0ALIMIT%2020 WIP query]

==== Items of personal interest ====

===== Authors =====
* {{Q|Q43411442}}
* {{Q|Q48192056}}
* {{Q|Q50810545}}
* {{Q|52407619}}
* {{Q|109325951}}
** Author of the {{Q|109328432}}
** The telescope might warrant its own item, and should eventually be mentioned in [[:w:Schmidt–Cassegrain telescope#Derivative designs]] and [[:w:List of telescope types]], and possibly [[:w:History of the telescope]] too.
** [https://www.youtube.com/watch?v=HxwhCmO90UQ Why is this Space Telescope so Tiny?] (YouTube video)
** [https://www.reddit.com/r/telescopes/comments/q90ki5/the_monolithic_telescope_concept_from_rik_ter/ The monolithic telescope concept from Rik ter Horst presented by Huygens Optics] (Reddit thread in r/telescopes about the video above)
** [https://www.cloudynights.com/topic/406276-a-solid-30-mm-f10-schmidt-cassegrain/ A SOLID 30 mm F/10 Schmidt Cassegrain] (original forum post about the concept by the author, in 2013)
*** Author says the first inception was made in 1998
*** One of the commenters said: «This is a variation of the [https://luminous-landscape.com/solid-cat/ "Solid Cat"] [http://www.ayton.id.au/wiki/doku.php?id=photo:vivitar800mmf11 Vivitar 800mm f/11] which used the same principle, except a larger scale», to which the author responded: «the optical configuration of the Vivitar consists of several (bonded) components with different refractive indices and with some air gaps. For comparison [my] Solid SCT [...] is made from just one piece of BK7, no bonding whatsoever...»

===== Publications =====
* {{Q|Q50292399}}
* {{Q|Q50810415}}

==== Books ====

===== Useful links =====
* [[Wikidata:WikiProject Books#Bibliographic properties|Wikidata:WikiProject Books § Bibliographic properties]]
* [[Template:Book properties]] (exhaustive list, no editing guidance)
* [[Wikidata:WikiProject Periodicals]]
* [[User:Marianika/Historical Bibliographic Data#Documentation]]

===== Creating new books =====

* Check the [[#Wikidata (Q2013)|Wikidata]] section below for properties
* Ideally there should be an interface to create, at once, all items related to a book (the work, edition and author items), all with the appropriate connections, with a good autocomplete system, and able to import public data given e.g. an ISBN.
* For now, we can use the Cradle forms for [https://cradle.toolforge.org/#/subject/book_(work) book (work)], [https://cradle.toolforge.org/#/subject/book_edition_2 book (edition)] and [https://cradle.toolforge.org/#/subject/author author]
** There's a [https://cradle.toolforge.org/#/subject/book_edition_1 strict book edition] preset, but requires authors to exist first (it doesn't accept {{P|P2093}}, nor empty author fields); the flexible preset, linked above, accepts both, and also has a field for Google Books ID.

===== Data models =====

====== {{Q|1201876}} ======
* [https://blog.openlibrary.org/2020/07/08/re-thinking-open-librarys-book-pages/ Re-thinking Open Library’s Book Pages]
** Explains very well the intricacies of distinguishing between a book as a work with multiple representations, a specific edition of a book, physical instances of books, etc.
** Slightly edited quote: ''To simplify the experience for readers, we released a new type of Book Page which combines the affordances of the Work and Edition Pages into a single view. Two pages become one: By default, the Book Page attempts to automatically feature the “best” (previewable, available) edition of a book and places an editions table front-and-center to enable readers to quickly switch which edition is selected.''

====== {{Q|16388}} (FRBR) ======
* Wikidata's model is based on this
* From [https://www.tandfonline.com/doi/abs/10.1080/00049670.2005.10721710 What is FRBR? A conceptual model for the bibliographic universe], quoted in [[b:Introduction to Library and Information Science/Information Organization#Cataloging]]:
** ''When we say the word book in everyday language, we may actually mean several things.''
** ''For example, when we say book to describe a physical object that has paper pages and a binding and can sometimes be used to prop open a door or hold up a table leg, FRBR calls this an "'''item'''."''
** ''When we say book we also may mean a "publication" as when we go to a bookstore to purchase a book. We may know its ISBN but the particular copy does not matter as long as it's in good condition and not missing pages. FRBR calls this a "'''manifestation'''."''
** ''When we say book as in "who translated that book," we may have a particular text in mind and a specific language. FRBR calls this an "'''expression'''."''
*** This is the most confusing aspect to me. It may help to think of different versions of a work by the same author as it evolves in time (draft/manuscript, first edition, revised edition, etc.) as different expressions of the work; and similarly, a translation is a separate expression, authored by the translator. But, as hinted in [[v:pt:Transcrição digital#Definição formal]], a transcription (e.g. from a manuscript to a printed book) transforms one manifestation in another, but preserves the expression.
** ''When we say book as in "who wrote that book," we could mean a higher level of abstraction, the conceptual content that underlies all of the linguistic versions, the story being told in the book, the ideas in a person's head for the book. FRBR calls this a "'''work'''."''
* Diagram:<br/>[[File:FRBR-Group-1-entities-and-basic-relations.svg|300px]]

====== {{Q|17050075}} ======
* Meant to replace MARC
* Diagram:<br/>[[File:Bibframe2-model.jpg|350px]]

====== {{Q|722609}} ======
* (MARC,  UNIMARC, MARC 21...

====== {{Q|54410458}} (IFLA-LRM) ======
* Diagram:<br/>[[File:IFLA-LRM Overview of Relationships.png|300px]]<br/>(Probably a simplified diagram would be helpful, containing just the work/expression/manifestation/item chain, plus the agent box (with an indication that this could be a single person or a collective.)

====== {{Q|32193244}} ======
* They seem to focus on three main levels of the "book" concept:
** works, i.e. {{Q|Q47461344}} ([https://inventaire.io/items/401d62d554fff436cbaaeabefe57a2a9 example])
** instances/manifestations, i.e. {{Q|3331189}} ([https://inventaire.io/entity/isbn:9781449388393 example])
*** They actually store this information separately from Wikidata, due to the inconsistency in how books are modeled in Wikidata (as of Nov 2022, [https://query.wikidata.org/#SELECT%20%28COUNT%28%3Fedition%29%20AS%20%3Fcount%29%20WHERE%20%7B%0A%20%20%3Fedition%20wdt%3AP31%20wd%3AQ3331189%20.%0A%20%20FILTER%20NOT%20EXISTS%20%7B%20%3Fedition%20wdt%3AP629%20%3Fwork%20.%20%7D%0A%7D there are +100K] instances of {{Q|3331189}} without a {{P|629}} property)
** items, i.e. {{Q|53731850}} ([https://inventaire.io/items/401d62d554fff436cbaaeabefe57a2a9 example])
*** They don't actually encode this in Wikidata, because the individual copies of books owned by users of the platform are almost certainly not notable enough to have their individual item on Wikidata.
* [https://wiki.inventaire.io/wiki/Glossary#Concepts Glossary § Concepts]
* [https://wiki.inventaire.io/wiki/Guides#Entities Guides § Entities]
* Diagram (old):<br/>[[File:Wikidata-Inventaire entities overlap map.png|400px]]
* Diagram (new - [https://inventaire.github.io/entities-map/ source]):<br/>[[File:Inventaire.io-entities-map-2022.png|400px]]
* Railroad diagram:<br/>[[File:Inventaire entities railroad diagram.svg|400px]]

====== {{Q|56100780}} ======
* [https://bookbrainz-user-guide.readthedocs.io/en/latest/glossary/ Glossary]
* [https://bookbrainz-user-guide.readthedocs.io/en/latest/getting-started/ Getting started] — describes the data model composed of the following elements:
** Author
** Work
** Edition
** Edition group (e.g. paperback, hardcover, e-book)
** Publisher
** Series (sequential grouping of works)
* Allows creating private or public collections
** In this sense, it's similar to Inventaire, although the latter tries to rely more on Wikidata

====== {{Q|2013}} ======
* {{statement||P31|Q47461344}} (not {{statement||P31|Q571}}? How does that play with {{Q|53731850}}?)
** {{P|50}}
*** For compilation works: {{P|767}} and {{P|98}}
**** No {{P|50}}?
**** How does one note contributors that don't have dedicated items, i.e. equivalent of {{P|P2093}}?
** {{P|1476}}
** {{P|1680}}
** {{P|407}}
** {{P|571}}
** {{P|747}}
** {{P|921}}
** {{P|7937}} (novel, poem, comic book, etc.)
** {{P|136}} (mostly for fiction? science fiction, fantasy, romance, adventure, drama...)
** Identifiers
*** {{P|648}}
*** {{P|7823}}
*** {{P|1085}}
*** {{P|8383}}
*** {{P|5331}}
*** {{P|2671}}
** [[Wikidata:WikiProject Books#Work item properties|...more]]
* {{statement||P31|Q3331189}}
** {{P|629}}
** {{P|655}}
** {{P|393}}
** {{P|123}}
** {{P|577}}
** {{P|2048}}
** {{P|2049}}
** {{P|1104}}
** {{P|110}}<!-- Illustrator -->
** {{P|736}}<!-- Cover designer -->
** {{P|437}} (paperback, hardcover, ...)<!-- Distribution format -->
** Identifiers
*** {{P|212}}
*** {{P|675}}
*** {{P|1957}}
*** {{P|648}}
*** {{P|243}}
*** {{P|5749}} (TODO: check if this indeed is meant for editions only)
** [[Wikidata:WikiProject Books#Edition item properties|...more]]
* {{statement||P31|Q53731850}}
** {{P|1574}} (target should be {{Q|3331189}}, but the constraints on the property are much laxer ☹️)
** {{P|276}} (sometimes {{P|629}} is used instead)
** {{P|127}}
** condition / preservation status? (intact, missing pages, water damage, annotated...)
** {{P|793}} ({{Q|17781833}}, {{Q|22340494}}, {{Q|14903979}}, {{Q|107036510}}...)
** {{P|195}}
** {{P|1028}}
** [[Wikidata:WikiProject Books#Exemplar properties|...more]]
** [https://tabernacle.toolforge.org/?#/tab/sparql/SELECT%20%3Fitem%20WHERE%20%7B%20%3Fitem%20wdt%3AP31%20wd%3AQ53731850.%20%7D/P1574%3BP629%3BP276%3BP407%3BP127 TABernacle list of such items]
* From [[Wikidata talk:WikiProject Books/2013#First of all, a definition for Book entity]]: ''the relationship between works and book is (unluckily) many-to-many. Having a list of works, they are collected into many kind of books: single work books, collections of many works into a single book, or a single work can be published in different books.''

=== QuickStatements reference ===

* [[Help:QuickStatements]]
* [https://tools.wmflabs.org/wikidata-todo/quick_statements.php QuickStatements v1] (deprecated)
* [https://quickstatements.toolforge.org QuickStatements v2] (recommended)
** Can import commands in the v1 format
** The CSV format is pretty straightforward (and actually easier to author than v1):
*** cells are comma-separated instead of tab-separated
*** there's a header row, which allows avoiding the repetition of the same prefixes in every row (thus halving the number of fields per row)
*** Queries in the query service can be tweaked to produce near-ready QuickStatement commands; see e.g. [https://gist.github.com/waldyrious/d0e57926f6a2d1904795c928eb6a0e5e these steps] to remove the "NAME" prefix from the label of exoplanets).
** The batch mode ("run in background") doesn't seem too reliable; I got some errors, but then wasn't able to see what they were
*** Update Nov 2021: still getting some "no API success flag set" errors. Better just stick to the sequential mode. 

==== Examples ====

'''Example 1''' → {{Q|Q34637733}}: {{P|P348}} = "2.12.5.1503"; {{P|P577}} = +2017-06-09T00:00:00Z/11; {{P|P400}} = {{Q|Q1406}}; {{P|P548}} = {{Q|Q2804309}} ([https://tools.wmflabs.org/reasonator/?q=Q28530564 others listed here]); {{P|P854}} = "https://www.rescuetime.com/updates/win_release_notes.html"; {{P|1476}} = "RescueTime for Windows Release Notes" (English).

<pre>
Q34637733	P348	"2.12.5.1503"	P577	+2017-06-09T00:00:00Z/11	P400	Q1406	P548	Q2804309	S854	"https://www.rescuetime.com/updates/win_release_notes.html"	S1476	en:"RescueTime for Windows Release Notes"
</pre>

Simplified template:
<pre>
<item>	P348	"<version number>"	P577	+<date>T00:00:00Z/11	S854	"<url>"	S1476	en:"<title>"
</pre>

Observations:
* Note how source (reference) properties must be provided using the nonstandard "S" prefix — so "S854" instead of "P854".
* Note that the whitespace characters are tabs, not spaces
* Note that timestamps must have zero time
* Note that the reference title requires a language specifier, here indicated by the <code>en:</code> prefix.

'''Example 2''' → (TODO: human-readable translation)

<pre>
CREATE
LAST	Len	"Buying Lumber"
LAST	Den	"song from the sountrack of the 2000 game The Sims"
LAST	P361	Q7764364	P1545	"4"	P2047	306U11574
LAST	P31	Q217199
LAST	P86	Q943225
CREATE
LAST	Len	"Mall Rat"
LAST	Den	"song from the sountrack of the 2000 game The Sims"
LAST	P361	Q7764364	P1545	"5"	P2047	164U11574
LAST	P31	Q217199
LAST	P86	Q943225
</pre>

Observations:
* Note the usage of CREATE and LAST directives, since we're creating new items, rather than adding statements to an existing item
* Note the Len and Den, for the English label and description
* Note now '''each line can only contain a single statement triplet''', but a given statement (e.g. {{P|P361}}) can have any number of '''properties/qualifiers'''.
* Note now the {{P|P2047}} is provided as seconds which are marked U11574, when in reality the item is {{Q|Q11574}}.
* Note how the number for {{P|P1545}} is provided as a string, even though a plain number should work as a quantity, according to the docs ("unit is optional")

'''Example 3''' → (TODO: human-readable translation)

<pre>
Q2986828	P348	"CLDR 30.0.1"	S854	"http://cldr.unicode.org/index/downloads/cldr-30#TOC-CLDR-30.0.1-Maintenance-Release"	S1476	en:"CLDR 30 Release Note"	S958	"CLDR 30.0.1 Maintenance Release"
</pre>

'''Example 4''' → (TODO: human-readable translation)
<pre>
Q839063	P1324	"http://git.savannah.gnu.org/cgit/oddmuse.git/"	P8423	Q186055
</pre>

'''Example 4''' → Add software versions, release dates and reference URLs
<pre>
qid,P348,qal577,S854
Q109462071,"""v0.0.3""",+2020-05-17T00:00:00Z/11,"""https://github.com/bigskysoftware/htmx/releases/tag/v0.0.3"""
Q109462071,"""v0.0.4""",+2020-05-26T00:00:00Z/11,"""https://github.com/bigskysoftware/htmx/releases/tag/v0.0.4"""
Q109462071,"""v0.0.5""",+2020-06-19T00:00:00Z/11,"""https://github.com/bigskysoftware/htmx/releases/tag/v0.0.5"""
</pre>

Observations:
* Note the usage of triple quotes for string values
* Note the same clunky v1 syntax for dates
* Other than that, this is actually quite an improvement: less repetition, and no reliance on tabs

=== Lexemes ===

''See also [[#Lexemes|To do § Lexemes]] above, for tasks related to lexemes.''

* [[Template:Lexicographical properties]]
** [[Wikidata:Tools/Lexicographical data]]
* [[Wikidata:Lexicographical data/Documentation#Data Model]]
* [[commons:Category:Lexeme presentations in English]]
* [[Wikidata:Wiktionary/Data model examples|Lexeme examples]]
* [[Wikidata:Lexicographical data/Best practices]]
* [[Wikidata:Lexicographical data/Documentation/Languages]] ([[Wikidata:Lexicographical data/Documentation/Languages/en|en]], [[Wikidata:Lexicographical data/Documentation/Languages/fr|fr]], [[Wikidata:Lexicographical data/Documentation/Languages/es|es]], [[Wikidata:Lexicographical data/Documentation/Languages/pt|pt]], [[Wikidata:Lexicographical data/Documentation/Languages/gl|gl]], [[Wikidata:Lexicographical data/Documentation/Languages/kea|kea]])
* List of lexemes
** [https://www.wikidata.org/w/index.php?title=Special%3AWhatLinksHere&target=Q5146&namespace=146 Links to "Portuguese" (Q5146) in the Lexeme namespace] (hack to get an approximation of all lexemes in Portuguese)
** {{SPARQL Inline
|label = All lexemes in {{Q|5146}} 
|query = SELECT ?lexeme ?lemma WHERE {
   ?lexeme dct:language wd:Q5146 ;
   wikibase:lemma ?lemma .
}
}}

==== FAQ ====

''TODO: Create a quickstart / FAQ / examples page in [[Wikidata:Lexicographical data]]. See also [[Wikidata:Lexicographical data/Glossary]] (which isn't linked from the main page, for some reason)''

* What are lexemes?
** words, phrases/expressions, prefixes, acronyms, etc.
* Wikidata vs. Wiktionary
** [[User:Rua/Wikidata for Wiktionarians]]
** In '''Wiktionary''' each page contains <u>''all homographs of a word''</u>, with sections for each language, and subsections for each lexical category (verb, noun, etc.)
*** Wiktionary uses separate pages for different forms of the same word, e.g. [[wikt:house|house]] vs. [[wikt:houses|houses]], [[wikt:pequeno|pequeno]] vs. [[wikt:pequena|pequena]], etc.
** In '''Wikidata''', each Lexeme page contains the <u>''homographs that share the same spelling+language+grammatical class''</u> (verb, noun, etc.)
*** The same Wikidata Lexeme page groups the different forms in the same word — e.g. "[[Lexeme:L512#F2|houses]]" is represented as a form in the [[Lexeme:L512|house]] (noun) lexeme
*** Words that are spelled the same but belong to different languages are placed in different Lexeme pages. These homographs in other languages can be connected via {{P|5402}}
*** Additionally, there can be the same word spelled in alternative ways (e.g. loiça/louça). These can be connected via {{P|8530}} (or probably {{P|5973}}, for those that aren't similar, e.g. cruzeta/cabide)
* Lexemes (L...) vs. items (Q...)
** A '''lexeme''' has statements that describe the <u>''word''</u>
** An '''item''' has statements that describe the <u>''concept''</u>
** noun-type lexemes link to items via the {{P|5137}} property; verb-type lexemes link to items via the {{P|9970}} property
* Senses and forms
** Each '''sense''' represents a <u>''meaning''</u> of the word — e.g. "screen" (noun) as a display, and "screen" (noun) as a net
*** A sense can therefore be linked to an item, via {{P|5137}}
*** Senses can also be linked to the same sense in other languages, via {{P|5972}}
** Each '''form''' represents <u>''variations''</u> (inflections and declensions) of the same word — e.g. house/houses, go/going/gone, pequeno/pequena/pequenos/pequenas, etc.
** Both senses and forms can have statements assigned to them, describing their properties
*** e.g. statements for a form: the gender, number, tense, pronunciation, etc.
*** e.g. statenents for a sense: {{P|5137}}, {{P|5972}}, {{P|5973}}, {{P|5974}}, {{P|18}}, {{P|5831}}, {{P|6084}} etc.
* Spelling variations
** A lexeme can have different representations in different spelling variants (e.g. color vs. colour in en-us and en-gb).
** These spelling variants need to have an official language code assigned, so thinks like {{Q|2217638}} and {{Q|18707467}} can't be used.
** A poor man's spelling variant can be done with separate lexemes connected via {{P|8530}} (in the Forms section of the lexeme)

==== Tools ====
* [[Wikidata:Tools/Lexicographical data|Tools]]
** https://tools.wmflabs.org/lexeme-forms — Create new lexemes from scratch, using templates specific to a language-lexical category combination
*** Templates can be created like this: https://tools.wmflabs.org/lexeme-forms/template/spanish-noun-masculine/
* [[Wikidata:Lexicographical data/Ideas of tools]]
** How can Wiktionary be converted?
** There could be a Mix'n'match-like tool that imports and converts data but waits for human confirmation

==== Data model ====

* [[mw:Extension:WikibaseLexeme/Data Model|Lexeme]]
*# Top level
*## [[mw:Extension:WikibaseLexeme/Data Model#Lemma|Lemma]]
*##* e.g. "run"
*## [[mw:Extension:WikibaseLexeme/Data Model#|Language]]
*##* e.g. {{Q|1860}}
*## [[mw:Extension:WikibaseLexeme/Data Model#|Lexical category]]
*##* e.g. {{Q|34698}}
*## Statements (properties of the lexeme that are not specific to a Form or Sense). E.g. derived from, region, period, homonym, etc.
*# [[mw:Extension:WikibaseLexeme/Data Model#Form|Forms]] (i.e. [[w:Inflection|inflections]])
*#* string representations of variants per gender, number, conjugation, etc.
*#* one for each combination, tagged with the relevant qualifiers/properties (e.g. 2nd person, singular, past tense...)
*#* [[mw:Extension:WikibaseLexeme/Data Model#Representation|Representation]]
*#* [[mw:Extension:WikibaseLexeme/Data Model#Grammatical Feature|Grammatical features]]
*#* e.g. (TODO)
*# [[mw:Extension:WikibaseLexeme/Data Model#Sense|Senses]]
*#* string representations different meanings
*#* link to items for the actual concepts (see "lexemes vs. items" above) 
*#* e.g. the lexeme "bank" (English noun) would have the senses "financial institution" and "edge of a body of water"
*#* [[mw:Extension:WikibaseLexeme/Data Model#Gloss|Gloss]]

Diagrams:

[[File:Lexeme data model.svg]]

[[File:Wikidata lexemes diagram.svg|600px]]

Also:
* Etymology ({{P|P5191}}, {{P|P5238}}...)
* Translations
* Pronunciation ({{P|P898}}, {{P|P443}})

==== Problems ====

* The creation form shows a "language variant" field when the entered language is not recognized.
** See [[Help:Monolingual text languages]] and the tracking ticket [[phab:T144272]].
** For some reason the list of languages is restricted to the one approved by the Language committee for new Wikipedias, rather than e.g. the full list of languages from CLDR
** To request a language to be supported, a new Phabricator task needs to be created in the same model as one of the child tasks of the one linked above
** As a workaround, new lexemes can still be created by using the <code>mis</code> as described in the help page linked above.
** For Kabuverdianu, the code is actually already available/linked (since [[phab:T127435]]), but the extra field was appearing nonetheless in the creation form; possibly that was due to a "no value" value for the language code, which was just removed in [[Special:Diff/1052835986|this edit]].
*** TODO: if the problem persists, maybe a new Phabricator issue needs to be created.
*** Update Jun 2021: the problem still occurs — may be related to [[phab:T284870]]?

== Question-answering ==

Tools:
* {{Q|Q42365752}}: [http://qanswer-frontend.univ-st-etienne.fr/ website] / [https://github.com/WDAqua source] / [http://wdaqua.eu/ overview]
* {{Q|Q47525695}}: [https://tools.wmflabs.org/magnus-toolserver/thetalkpage/ website] / [https://bitbucket.org/magnusmanske/magnus-toolserver/src/master/public_html/thetalkpage/ source] / [https://github.com/waldyrious/wiri my fork]
* {{Q|Q47525820}}: [http://tools.wmflabs.org/bene/ask/ website] / [https://github.com/Benestar/ask-wikidata source] / [https://github.com/Benestar/ask-wikidata/issues/9 overview?]
* {{Q|Q20726406}}: [http://askplatyp.us/ website] / [https://github.com/ProjetPP/PPP-Wikidata source] / [https://github.com/ProjetPP/PPP-QuestionParsing-Grammatical/issues/144#issuecomment-80558485 overview?]
* {{Q|Q28381936}} (formerly "Sirius"): [http://sirius.clarity-lab.org/ website] / [https://github.com/jhauswald/sirius source] ([http://web.archive.org/web/20151030182104/https://github.com/jhauswald/sirius archived])
** From http://sirius.clarity-lab.org/downloads/: "Sirius uses a Wikipedia knowledge database, download the database (compressed 11GB): [http://web.eecs.umich.edu/~jahausw/download/wiki_indri_index.tar.gz wiki_indri_index.tar.gz]
* [[User:SpinachBot]] — an LLM-based natural-language interface for SPARQL queries via exchanging messages on-wiki.
** There's also an interactive UI at at https://spinach.genie.stanford.edu/.

See also:
* [[w:Template:Computable knowledge]]
* [[Wikidata:WikiProject Reasoning]]
* [https://mycroft.ai/ Mycroft] (an open source voice assistant) has a [https://github.com/MycroftAI/skill-wiki "wiki" skill]

Benchmarks:
* [https://www.youtube.com/watch?v=BkpAro4zIwU The Voice Assistant Battle! (2017)]
* [https://www.youtube.com/watch?v=JFiu5rfnhzo&feature=youtu.be Google Assistant vs Siri! (2016)]
* [https://www.wolframalpha.com/examples/ Wolfram|Alpha: Examples by Topic]
* [https://iswc2017.ai.wu.ac.at/wp-content/uploads/papers/PostersDemos/paper555.pdf Question Answering Benchmarks for Wikidata]
** [https://research.fb.com/downloads/babi/ SimpleQuestions] ([https://github.com/askplatypus/wikidata-simplequestions adaptation to Wikidata])

Maybe there should be a completeness/coverage/parity dashboard, similar to [[w:Wikipedia:WikiProject Missing encyclopedic articles]], that maps how much of the [https://zverok.github.io/blog/2021-10-19-wikipedia.html#how-they-do-it Wolfram Language] can be modeled in terms of properties/qualifiers.

== Mini-bios ==

Thanks to the [[WD:Wikidata Game|Wikidata Game]], it will be possible to move quickly to a state where we Wikidata will have all the information needed to build automated mini-bios in the form

:'' '''&lt;[[Template:LinkedLabel|label]]&gt;''' (&lt;{{P|19|show_p=no}}, &lt;{{P|569|show_p=no}}&gt; — &lt;{{P|20|show_p=no}}&gt;, &lt;{{P|570|show_p=no}}&gt;) was a &lt;{{P|27|show_p=no}}&gt; &lt;{{P|106|show_p=no}}&gt; who &lt;[[Template:autodescription|description]]&gt;.''

In fact, the description field for people in Wikidata should probably forgo occupation and nationality, and go straight to their claim to notability, since the former are redundant with the corresponding fields.

This proposal was originally posted [https://bitbucket.org/magnusmanske/wikidata-game/issue/125/proposal-game-with-occupation-profession#comment-11049697 here].

=== Related resources ===

* [[toollabs:reasonator|Tool:Reasonator]] generates automated stubs based on Wikidata info

* [[mw:Extension:ArticlePlaceholder|Extension:ArticlePlaceholder]] embeds data boxes for a Wikidata item directly within a wiki, under Special:AboutTopic
** [https://wikitech.wikimedia.org/w/index.php?title=Special:Search&search=%22articleplaceholder%22+prefix%3Adeployments Deployments on Wikimedia sites]
** [https://phabricator.wikimedia.org/maniphest/query/5HlyNet7NU3K/#R deployment requests]

* [[toollabs:autodesc|Tool:AutoDesc]] provides auto-generated descriptions for Wikidata items; I believe it is used by Reasonator, and the user script version provides in-place content in search result pages on the wikis themselves
** [https://bitbucket.org/magnusmanske/autodesc/src/master/www/js/ source]
** [https://github.com/dbrant/wikidata-autodesc fork]
** [[:en:MediaWiki:Wdsearch-autodesc.js|user script]]
** [http://magnusmanske.de/wordpress/?p=64 blog post 1]
** [http://magnusmanske.de/wordpress/?p=265 blog post 2]

* [[MediaWiki:Gadget-autoEdit.js]] allows users to automatically add descriptions to Wikidata items, from [[User talk:Jitrixis/autoEdit.js/lists|a list]] of commonly used descriptions.

* [[Wikidata:Automating descriptions]]
* [[Wikidata:Article placeholder input]]
* [[meta:Wikidata/Notes/Article generation]]
* [[meta:Abstract Wikipedia/Updates/2022-06-07]]