GreenReaper added a comment.
The latest patch set seems to resolve the above issue.
The fixed version should presumably be used externally only with MW 1.43+,
once it is released. Which probably isn't too much of a problem, as many stick
to LTS anyway.
TASK DETAIL
GreenReaper added a comment.
The proposed change restores the examples, but not the section headers. I've
marked the section in question in Gerrit, but here's screenshots to illustrate.
With the patched code as submitted as an override to wdqs.js:
F55027951: Screenshot
GreenReaper added a comment.
I believe this may have broken due to T365736
<https://phabricator.wikimedia.org/T365736>, in relation to the code to find
the previous header
<https://github.com/wikimedia/wikidata-query-gui/blob/da379757474aa5044aa64106095b618d1c9b5e45/wikibase/que
GreenReaper created this task.
GreenReaper added a project: Wikidata Query UI.
Restricted Application added a subscriber: Aklapper.
TASK DESCRIPTION
**Steps to replicate the issue** (include links if applicable):
- Go to https://query.wikidata.org/ or https://commons-query.wikimedia.org
GreenReaper updated the task description.
TASK DETAIL
https://phabricator.wikimedia.org/T366866
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: GreenReaper
Cc: Aklapper, GreenReaper, Danny_Benjafield_WMDE, S8321414, Astuthiodit_1,
AWesterinen
GreenReaper created this task.
GreenReaper added a project: Wikidata Query UI.
Restricted Application added a subscriber: Aklapper.
TASK DESCRIPTION
**Steps to replicate the issue** (include links if applicable):
- Load https://query.wikidata.org on Edge Dev 127 (or probably Chrome Dev
GreenReaper added a comment.
WikiScholar <https://meta.wikimedia.org/wiki/WikiScholar> Query Service
(WSQS)? 🐙
WikiCite <https://meta.wikimedia.org/wiki/WikiCite> Query Service (WCQS)? 📖
Scholarly Query Service (SQS)? 📘
TASK DETAIL
https://phabricator.wikimedia.org/T3
GreenReaper added a comment.
Wikibase Community UG proposed something rather like this for the recent Open
Call: Integrating form-based entity creation using Shape Expressions into the
Wikibase UI
<https://drive.google.com/file/d/10dymKaXA3g5Bm6jk730OvNERsJMFNPjp/view>.
TASK DETAIL
GreenReaper edited projects, added Wikibase (3rd party installations); removed
MediaWiki-extensions-WikibaseRepository.
TASK DETAIL
https://phabricator.wikimedia.org/T344246
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: GreenReaper
Cc: Aklapper
GreenReaper added a comment.
We've been getting reports of Wikibase community WDQS end-users having
trouble using whitelist.txt - might the changes above have broken use of this
file if they had it incorporated into a Wikibase docker/suite setup? It looks
like wmde.16 version of wik
GreenReaper added a comment.
The desire to create lexemes via QuickStatements was raised by a FactGrid
user in the Wikibase Community User Group mailing list
<https://lists.wikimedia.org/hyperkitty/list/wikibas...@lists.wikimedia.org/thread/NV3Z3K2L73TMIRJID5SR2TINCQM6S4NN/>.
It
GreenReaper edited projects, added Wikibase (3rd party installations); removed
Wikidata.
GreenReaper added a comment.
This doesn't seem to be anything to do with Wikidata now, but rather
third-party installations not using a suite install including Cirrus (which
just came up in Telegra
GreenReaper added subscribers: Lucas_Werkmeister_WMDE, GreenReaper.
GreenReaper added a comment.
Perhaps related to T301249
<https://phabricator.wikimedia.org/T301249>/T305785
<https://phabricator.wikimedia.org/T305785> and stuff like DataModel\Entity:
Add __serialize/__uns
GreenReaper added a comment.
My own view: it's a bad idea to use wd:, wdt: etc. for things that are not
Wikidata. Yes, they are stated to be "internal to Wikidata"
<https://mediawiki.org/wiki/Wikidata_Query_Service/User_Manual#Basics_-_Understanding_Prefixes>,
a
GreenReaper renamed this task from "add wikibase.cloud to the SPARQL whitelist
" to "Add OpenDataSweden to the SPARQL whitelist ".
TASK DETAIL
https://phabricator.wikimedia.org/T315124
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
GreenReaper added a comment.
Adding the whole of wikibase.cloud (as this task's title suggests) would be
cool, and was discussed in the Telegram chat for Wikibase.cloud, but will
require a wildcard, which I'm not sure is possible yet - there are none in the
current list. But p
GreenReaper added a comment.
In T207705#8091791 <https://phabricator.wikimedia.org/T207705#8091791>,
@Jheald wrote:
> I believe an exception should be made for a pair of functions to return as
an `xsd:dateTime` the minimum and the maximum date that a given `edtf:EDTF`
va
GreenReaper added a comment.
sharedCacheKey* [seem to be documented
here](https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_options.html],
although there might be other appropriate locations, e.g. a hint on the
MediaWiki wiki.
TASK DETAIL
https://phabricator.wikimedia.org
GreenReaper added a comment.
From what I can see with a cursory search, the IETF seem happy to declare
extensions to the standard
<https://datatracker.ietf.org/doc/draft-ietf-sedate-datetime-extended/02/>
rather than seeking to replace it. Time in a general sense is not their
GreenReaper added a comment.
Of course, the trouble is what's useful may change. But it is true that most
specific items mentioned have been added.
One thing that struck me was that - where used on wiki, e.g. on Wikipedia -
Lua tends to be a big part of the solution, in concert
GreenReaper added a comment.
In some cases that feature could be useful, though I suspect many would be
surprised to get results from an ordered query that might not be correct with
respect to the entire data set.
I tried the mentioned query, setting a timeout of 0 which disables this
GreenReaper added a comment.
Regarding the ranking discussion, I would've thought you're more likely to
want a Lexeme if you're on a page about a Lexeme already, and so it should be
prioritized in the results list (but not to the extent of excluding other
results).
That
GreenReaper added a comment.
MediaWiki:Randompage-url
<https://wikibase-registry.wmflabs.org/wiki/MediaWiki:Randompage-url> could be
changed to
`[Special:Random/Item](https://wikibase-registry.wmflabs.org/wiki/Special:Random/Item)`,
or alternatively $wgContentNamespaces
GreenReaper added a comment.
WBStack would be a convenient solution. Is there anything custom about the
registry? Is anything unique to the current hosting relevant, like losing
access to the WMF tile server for Kartographer
<https://github.com/wbstack/mediawiki/issues/69> - would t
GreenReaper added a comment.
Restricted Application added a project: wdwb-tech.
Having got Cradle working with a shape
<https://furry.wiki.opencura.com/tools/cradle/?#/shex/E2> on WBStack after a
bit of fuss
<https://github.com/wbstack/cradle/issues/2#issuecomment-818352157>
GreenReaper added a comment.
A largely complete PHP library <https://github.com/ProfessionalWiki/EDTF>
(limitations as specified) and Wikibase data type
<https://github.com/ProfessionalWiki/WikibaseEdtf> (MediaWiki extension
<https://www.mediawiki.org/wiki/Extensio
GreenReaper added a comment.
In T206560#6864268 <https://phabricator.wikimedia.org/T206560#6864268>,
@Krabina wrote:
> I don't understand the "I don't like Java" argument. Blazegraph - which is
in discussion here - is also written in Java als are most (all?)
GreenReaper added a comment.
Within Wikimedia I'd really expect it to be directly editable; on a
third-party wiki, a plain display of elements with an edit icon linking to
Wikidata might be more suitable.
For very tight integrations, some implementation of Wikidata Bridge would b
GreenReaper added a comment.
This came up when I was looking over the Wikibase suite installation guide
<https://www.mediawiki.org/wiki/Wikibase/Suite#Wikidata_Query_Service>. I know
a lot of what's been done recently is more for Wikimedia's specific
requirements, but it
GreenReaper added a comment.
The registry now runs 1.32.5
<https://wikibase-registry.wmflabs.org/wiki/Special:Version> (not .6), but
should probably be running 1.35, or even 1.36 (but with the risk of going
unsupported again). PHP 7.2.26 may need an upgrade to PHP 7.3 (or possib
GreenReaper added a comment.
#mediawiki-extensions-page_forms
<https://phabricator.wikimedia.org/tag/mediawiki-extensions-page_forms/>
already works with SMW and Cargo
<https://www.mediawiki.org/wiki/Extension:Page_Forms>. Could it be enhanced to
support Wikibase, even i
GreenReaper added a comment.
In T261102#6405480 <https://phabricator.wikimedia.org/T261102#6405480>,
@Lucas_Werkmeister_WMDE wrote:
>> is it technically possible that someone would use the Bridge feature for
other purposes (eg create a new item or add a message on
GreenReaper added a comment.
I'm curious about this, too. MediaWiki 1.35.0 was released almost a month ago
now. Is there anything technically blocking Wikibase 1.35 from being built? I
see T192006 <https://phabricator.wikimedia.org/T192006> and T192792
<https://phabricator
GreenReaper added a comment.
Probably not an issue for Wikimedia, but perhaps for embedded usage: as of
Virtuoso 7, only 64-bit platforms are supported
<https://github.com/openlink/virtuoso-opensource/issues/439> (enforced by
configure, maybe to avoid spurious segmentation faul
GreenReaper added a comment.
Perhaps @Smalyshev could confirm this? As I understand it T206561
<https://phabricator.wikimedia.org/T206561> is stalled on this issue (and has
been for almost a year).
TASK DETAIL
https://phabricator.wikimedia.org/T221631
EMAIL PREFERENCES
GreenReaper added a subscriber: WMDE-leszek.
GreenReaper added a comment.
Right, it was the intention to move to WMF hosting. But it seems (as
@WMDE-leszek recognised in the other thread), that it will *not* be hosted by
WMF, because WMDE won't transfer the domain. I'm pres
GreenReaper added a comment.
Looks to me like it has the same IP address it did last year
<https://phabricator.wikimedia.org/T99531#4573965>, which is in "United Domains
via IP Exchange GmbH
<https://apps.db.ripe.net/db-web-ui/#/query?searchtext=89.31.143.100>" space.
GreenReaper added a comment.
I ran into this trying to link to https://wikiba.se when explaining Wikibase
to someone on Twitter <https://twitter.com/WikiNorn/status/1158991278375415809>
(in the context of use on WikiFur <https://wikifur.com/>, tracking conventions
<https:/
38 matches
Mail list logo
