Alphos added a comment.
The debate is long over.
Links MUST point to articles specifically about the entity described. Not sections, not redirects, not articles about generic entities, not articles about something unrelated. There can be no exceptions. This is especially useful to machines, which
Alphos added a comment.
It doesn't matter that Wikipedias chose to handle things that way. Wikipedia chose to fill any gap by pointing to a related article. Wikidata chose to fill any gap by actually filling said gap.
Wikidata chose to point to articles specifically about the entity described
Alphos added a comment.
In T145522#2999881, @2015.ww wrote:
Could someone kindly show a case -- or two :) -- of how such links cause a problem?
For example... looking at flautist / flûtist / fløjtenist (Q12902372) with an article e.g. at Fløjtenist but some other links, such as in enwiki
Alphos added a comment.
For what it's worth, I've built WRCR with the intent of finding items that link to pages that redirect to other pages that have items linking to them too.
I must warn there are some false positives, due to a tradeoff between specificity and speed ; and even though I'd like
Alphos created this task.Alphos added a project: Wikidata-Query-Service.Herald added a subscriber: Aklapper.Herald added projects: Wikidata, Discovery.
TASK DESCRIPTIONAfter finding an odd result while testing an ASK query, I stumbled upon this obvious example case :
ASK {
wd:Q618123 wdt:P279
Alphos added a comment.
Or, to handle the string literals too :
# People who died in the last 7 days
SELECT ?person ?deathDate {
?person wdt:P31 wd:Q5 .
?person wdt:P570 ?deathDate .
FILTER( IF ( sameTerm(dataType(?deathDate), xsd:dateTime), ?deathDate >= ( NOW() - "P7D"^
Alphos added a comment.
It's weirder than you think :
SELECT ?now WHERE {
BIND( ( NOW() - "P7D"^^xsd:duration ) AS ?now ) .
}
returns "Sep 1, 2016", which is 6 days from today (we're 2016-08-25T23:55:00.000+02:00, give or take a few minutes)
SELECT ?now WHERE {
BIND(
Alphos added a comment.
Temporary workaround :
# People who died in the last week
# Well, more accurately, people whose death + 7 days is after the current day and time, but still !
SELECT ?human ?humanLabel ?date
WHERE
{
?human wdt:P31 wd:Q5;
wdt:P570 ?date.
FILTER(?date + &quo
Alphos added a comment.
Way ahead of ya ;-)
Current implementation (JS on test.wikidata
https://test.wikidata.org/wiki/User:Alphos/ytreporp.js) performs the
##action=wbgetclaimsprops=claims|info## call at window.onload time on items
that are targetted by properties of interest.
Still wrapping
Alphos created this task.
Alphos added a subscriber: Alphos.
Alphos added a project: MediaWiki-extensions-WikibaseRepository.
Restricted Application added a subscriber: Aklapper.
TASK DESCRIPTION
When viewing an entity, wbUsedEntities currently contains JSON (a string, not
an actual javascript
Alphos added a comment.
I did find wgCurRevisionId ;-)
Too bad about wbUsedEntities being dropped, it means we're either :
- facing race conditions (and potential edit conflicts) : the lastrevid of the
used entities may have changed since the loading of the current page
- or not caring
Alphos added a comment.
I'm working on a gadget that will allow you to insert by hand only one side of
a relationship, and click for an automated insertion of the other side.
Let me clarifiy with a real world example :
- La Villette https://www.wikidata.org/wiki/Q532352 was a subdivision
12 matches
Mail list logo
