User:SM5POR
| Babel user information | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
| Users by language |
Real name: Anders Andersson
Subject areas[edit]
Alphabetical any easily in information is most order sorted understood when.
Current work[edit]
Class logic[edit]
The distinction between class and instance is not always clear. Here is a rule of thumb that may work (not sure if it applies in every language):
- Nurse is a profession (an instance of profession).
- Health worker is also an instance of profession.
- A nurse is a health worker (a subclass of health worker).
Try moving the indefinite article around and see what happens. "A nurse" refers to a member of the nurse group, while "nurse" refers to the group as a whole. A few more examples:
- Road is an infrastructure (an instance of infrastructure).
- Transport route is also an instance of infrastructure.
- A road is a transport route (a subclass of transport route).
- Square is a shape (an instance of shape).
- Rectangle is also an instance of shape.
- A square is a rectangle (a subclass of rectangle).
Cleaning up the root[edit]
Computing history[edit]
Vintage computers[edit]
Recreate old hardware in virtual reality.
Data representation[edit]
Apple computers and orange revolutions.
Future applications[edit]
Enable Wikipedia[edit]
Allow Wikipedia to benefit from the full potential of Wikidata without depending on inverse properties.
Library development[edit]
Prototyping in Lua.
Geometric shapes[edit]
Information theory[edit]
Dimensions of data[edit]
Spherical vectors and non-linear vector field arrays are potential new data types.
Linguistic modelling[edit]
Clarifying lexemes[edit]
What is a lexeme, and what isn't?
Semantic grammar[edit]
We want to translate semantics, not merely cache translations.
Contextual relations[edit]
How many different senses can a preposition really have? Phasing out of (P642) is a good start.
Wikidata Work strategy[edit]
The number of Q items is in the range of hundreds of millions. The number ofproperties in the tens of thousands. To improve the expressivenessof Wikidata statements. It's better to comeup with new items than to invent new properties seldom to be used. Besides, item creation doesn'trequire discusion and consensus like property proposalsdo, so using items leaves more options available for independent development. It's like modern pictorial art. To create newworks of art and establish new genres, a good artis doesn'tneed new colours of paint, but will make do with whatalready exists. New and unexpected combinations of existing things is innovative too. such as rock opera.
Lexodus[edit]
The word is not the thing.
Mongolian writing systems[edit]
Alphabet[edit]
Property value inheritance[edit]
Transitivity[edit]
Consider some new transitivity paths, such as corporate membership and ownership.
Statistics[edit]
Unfinished work[edit]
Nematode infections[edit]
Quite an interesting case of confusion:
| Item | History | Wikipedia | Wikipedia quotes | |
|---|---|---|---|---|
| Subclass of | Selected properties | |||
| ancylostomiasis (Q14623417) | ||||
| (no subclass) | ||||
| ancylostomiasis (Q11679861) |
|
| ||
| necatoriasis (Q4118581) |
|
| ||
| ancylostoma duodenale ancylostomiasis (Q137597) |
| |||
| hookworm disease (Q5898175) | ||||
| nematode infection (Q2072680) | ||||
| parasitic helminthiasis infectious disease (Q578994) | ||||
Legend for the Wikipedia column:
| Tag | Explanation |
|---|---|
A+N
|
Article is about the generic hookworm disease, including both parasites |
A__
|
Article is about the ancylostomiasis disease |
__N
|
Article is about the necatoriasis disease |
_?_
|
Article is too brief, unclear, or difficult for me to translate even with Google Translate to reliably determine its subject |
The only languages with articles for all three interrelated items are Arabic, English, and Russian (plus Kirghiz for the two mutually confused articles only), where the Russian article disagrees with the English one on its subject and (I think) also the Arabic one, but this is not a simple majority point of view issue, and there may have been many changes and "corrections" done to the items by editors who have been unaware of the disputable linking of either language edition. Let's not disappoint those editors who were correct in the first place by unnecessarily redefining the items according to what topics may have been inferred later.
So this is apparently why there was a subclass loop between ancylostomiasis (Q11679861) and ancylostoma duodenale ancylostomiasis (Q137597) in the first place. After my initial attempt to resolve the loop by removing one of the subclass links was reverted, I found myself creating this table simply to figure out why we had different opinions on which subclass link should be removed. Thanks to User:Infovarius for drawing my attention to the confusion!
For additional reference, here are the associated nematode species
| Item | History | Wikipedia | Wikipedia quotes |
|---|---|---|---|
| Subclass of | Selected properties | ||
| Ancylostoma duodenale (Q2520810) | |||
| (not a subclass) | |||
| Necator americanus (Q2433913) | |||
| (not a subclass) | |||
| Ancylostomatidae (Q3093248) | |||
| (no subclass) |
And I need to work on my table design skills as well...
Lexical reference[edit]
| Shorthand | Description | Latin term or grammatical feature | English | Russian |
|---|---|---|---|---|
| ancylostomatidae | = Latin | = Latin | ||
| AD | ||||
| ADA | ||||
| NA | necator americanus |
Planned resolution[edit]
When the above analysis is finished, here is what should be done (plan to be further refined as potential issues emerge):
- Spell out which item should serve what purpose, where unclear
- Move away those interwiki links and other item properties that don't belong with either of the items being revised
- Delete or rectify properties (including labels and descriptions) that are in error, or will be in error after the revision
- Move
Statistics[edit]
Wikidata contents[edit]
Progress[edit]
| Date and time | Highest numbered item | Number of items | Highest numbered property | Number of properties |
|---|---|---|---|---|
| 2020-05-24 12:23 UTC | TO THE EDITOR (Q95375079) | 86577965 | field of training (P8258) | 7580 |
| 2020-10-06 05:04 UTC | Franklin School (Q100000001) | social media followers (P8687) | ||
| 2021-10-17 00:24 UTC | Mirnawati (Q108911746) | Research Vocabularies Australia ID (P10000) |
| Date and time | P279 | Subclasses | Classes | Metaclasses |
|---|---|---|---|---|
| 2020-06-01 18:30 UTC | 2994218 | 2428462 | 117174 | 4951 |
Count item labels[edit]
SELECT ?item ?itemLabel (COUNT(?value) AS ?values)
WHERE
{
?item wdt:P31 wd:Q6256.
OPTIONAL{?item rdfs:label ?value}
SERVICE wikibase:label { bd:serviceParam wikibase:language "en". }
}
GROUP BY ?item ?itemLabel
ORDER BY DESC(?values)
Count properties[edit]
SELECT (COUNT(?property) AS ?properties) WHERE {
SELECT DISTINCT ?property WHERE {
?property wdt:P31/wdt:P279* wd:Q18616576.
}
}
SELECT ?class ?classLabel (COUNT(?property) AS ?properties) WHERE {
SELECT DISTINCT ?class ?classLabel ?property WHERE {
?property wdt:P31/wdt:P279* wd:Q18616576.
?property wdt:P31 ?class.
SERVICE wikibase:label { bd:serviceParam wikibase:language "en". }
}
}
GROUP BY ?class ?classLabel
ORDER BY DESC(?properties)
Non-instance items[edit]
I'm not quite sure what I'm looking for here; just exploring...
SELECT ?item ?itemLabel (COUNT(?property) AS ?statements)
WHERE
{
?item rdf:type wdno:P31.
OPTIONAL{?item ?property ?value}
SERVICE wikibase:label { bd:serviceParam wikibase:language "en". }
}
GROUP BY ?item ?itemLabel
ORDER BY DESC(?statements)
LIMIT 50