the results directly.
3. API at http://queryr.wmflabs.org/about/docs has /properties which
will provide you with the list of properties.
HTH,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://
nce
> UUID like this:
I'm not sure I understand - what would doing this earn us? This looks
like just adding one more join to the lookups.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://l
SPARQL_query_service/queries#Working_with_co-ordinates
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
an allowed runtime (30 seconds
currently). The best way in general to deal with it is to rewrite query
to be faster or to use a different service, as per above, that is more
efficient in this specific case.
--
Stas Malyshev
smalys...@wikimedia.org
___
net
There is a good platform to discuss performance/optimization questions.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
the problem
> might be to adopt the Blazegraph multi-GPU architecture
> (https://www.blazegraph.com/product/gpu-accelerated/).
>
> Could anyone provide guidance as to how much pain would be involved in
> making such a transition?
I'd ask on Blazegraph list: bigdata-develop...@list
not use a variable in BIND that was
previously used, and I guess OpenRDF parser chooses to be more strict
than Blazegraph.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
/entity/
>
> When I substitute the https://example.com for http://example.com in my
> RDF, the munge works.
Hmm, it may be not accounting for https URLs.. I'll check that, thanks.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailin
u think it means, use
limit, it'll save you time and frustration and CPU resources :)
> Could Blazegraph prevent this query from even starting?
There's no reason to prevent this query from starting, it's a completely
legitimate query, just most likely not doing what you thought it's do
ide,
not sure why - I can access that URL just fine. Updater can't do much if
Wikidata refuses to talk to it, so if this keeps happening I'd ask on
Ops channel why it may be happening.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailin
:)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
%20%0A%3FxRefNode%20pq%3AP2937%20wd%3AQ30579723%3B%0A%20%20%20ps%3AP39%20wd%3AQ1939555.%0A%7D
Or change "preferred" status on Q17905:P39.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wik
i/Wikibase/Indexing/RDF_Dump_Format#Statement_representation).
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
information about anything you think would
be useful for us to know.
What was that page again?
https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Usage
Thanks in advance,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata
to go back to the common format?
>
> Not sure if we had a reason tbh.
OK then, I'll feel free to shuffle things around then :) Having more
freedom in the title line is good because we can then display both label
& aliases.
Thanks!
--
Stas Malyshev
smalys...@wikimedia.org
_
to add them one by
one but want to collect a set and then do it in one hit.
We also do not have syntax for searching (as in match, instead of boost)
by statement values, but it should not be hard - we just need to design
proper syntax and implement it (syntaxes are now pluggable, so should
not be
://phabricator.wikimedia.org/T178851
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
d getEntityIdForTitle
uses content model to get from Title to ID. So, I could duplicate all
this code but I don't particularly like it. Could we fix
HtmlPageLinkRendererBeginHookHandler instead maybe?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikid
past, conjunctive", derived from multiple Q-ids.
Yes, of course.
> Again, I don't think any highlighting is needed.
Not strictly speaking needed, but might be nice.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikid
ormat links to Forms? Leszek, do you have any information on this?
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
So, does this display look as what we want to produce for Lexemes? Is
there something that needs to be changed or improved? Would like to hear
some feedback.
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wik
/disabled by default.
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
go by default for Special:Search:
1. Search in Items only
2. Search in Items + Properties
3. Search in Items + Properties + Lexemes
4. Search in Items + Lexemes
5. Any of the above plus some of the article spaces (i.e. Wikidata or Help)
This requires mixed search working (except for 1 and 2) but is a
s
omment in the task) if you have any questions or
concerns.
[1] https://www.mediawiki.org/wiki/Wikibase/Indexing/RDF_Dump_Format#Header
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wiki
w, and RDF data is generated without
the beta prefix. Please tell me if you notice any problems or have any
questions.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
gain I am not sure what's the best way to treat this situation,
since I am not sure how federation model in SDC is working - the code
suggests there should be some kinds of prefixes for entity IDs, but SDC
does not seem to use any.
Any suggestions about the above are welcome.
Thanks,
--
Stas Malyshe
301 - 326 of 326 matches
Mail list logo
