Re: [Wikidata-tech] Missing documentation of Wikibase Lexeme data model

t to have documentation that defines the contract - that is, the intended semantics and guarantees. -- Daniel Kinzler Principal Software Engineer, Core Platform Wikimedia Foundation ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.

Re: [Wikidata-tech] Missing documentation of Wikibase Lexeme data model

Senses. The abstract model for Lexemes is here: https://www.mediawiki.org/wiki/Extension:WikibaseLexeme/Data_Model The RDF binding his here: https://www.mediawiki.org/wiki/Extension:WikibaseLexeme/RDF_mapping Looks like documentation for the JSON bindinng is indeed missing. -- Daniel Kinzler

Re: [Wikidata-tech] lexeme fulltext search display

Am 18.06.2018 um 19:25 schrieb Stas Malyshev: > 1. What the link will be pointing to? I haven't found the code to > generate the link to specific Form. You can use an EntityTitleLookup to get the Title object for an EntityId. In case of a Form, it will point to the appropriate section. You can

Re: [Wikidata-tech] lexeme fulltext search display

the match itself, so I am not sure whether it should be or not. Again, I don't think any highlighting is needed. But, as you know, it's all up to Lydia to decide :) -- daniel -- Daniel Kinzler Principal Platform Engineer Wikimedia Deutschland Gesellschaft zur Förderung Freien W

Re: [Wikidata-tech] Fastest way (API or whatever) to verify a QID

You can do this via the API, e.g.: https://www.wikidata.org/w/api.php?action=query==json=Q1|Qx|Q1003|Q66=1 Note that this uses QIDs directy as page titles. This works on wikidata, but may not work on all wikibase instances. It also does not work for PIDs: for these, you have to

Re: [Wikidata-tech] Search on Wikibase/Wikidata sans CirrusSearch?

Yes, it's supposed to work, see FingerprintSearchTextGenerator and EntityContent::getTextForSearchIndex Am 30.12.2017 um 06:47 schrieb Stas Malyshev: > Hi! > > I wonder if anybody have run/is running Wikibase without CirrusSearch > installed and whether the fulltext search is supposed to work in

Re: [Wikidata-tech] Does a rollback also roll back revision history?

e page's history (but it is instead visible in the template's history). However, no transclusion mechanism exists for Wikidata entities. -- Daniel Kinzler Principal Platform Engineer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V.

Re: [Wikidata-tech] Wikibase and PostgreSQL

information to Wikibase docs? > // -- Daniel Kinzler Principal Platform Engineer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

Re: [Wikidata-tech] [Wikidata] Significant change: new data type for geoshapes

UTC (2pm PDT, 23:00 CEST) #wikimedia-office. -- Daniel Kinzler Principal Platform Engineer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

Re: [Wikidata-tech] Two questions about Lexeme Modeling

gy. Further investigation is needed. I have filed a Phabricator task for investiagting this. I suggest to take the discussion about how to represent languages/variants/dialects/etc there: https://phabricator.wikimedia.org/T151626 -- Daniel

Re: [Wikidata-tech] Two questions about Lexeme Modeling

le overhead. We'll want the lemma to be represented in a more compact way in the UI than we currently use for labels, though. Thank you all for your help! -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. _

Re: [Wikidata-tech] Two questions about Lexeme Modeling

a look and comment: https://docs.google.com/spreadsheets/d/1PtGkt6E8EadCoNvZLClwUNhCxC-cjTy5TY8seFVGZMY/edit?ts=5834219d#gid=0 -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech m

Re: [Wikidata-tech] Two questions about Lexeme Modeling

being imprecise. And yes, if we have a multi-variant lemma, we should also have multi-variant Forms. Our lemma corresponds to the canonical form in Lemon, if I understand correctly. > The preference for showing e.g. the American or English variant should be > stated by the application that use

Re: [Wikidata-tech] Linking RDF resources for external IDs

transition. Please let me know which approach you prefer. Have a look at the files attached to my original message. Thanks, Daniel Am 09.11.2016 um 17:46 schrieb Daniel Kinzler: > Hi Stas, Markus, Denny! > > For a long time now, we have been wanting to generate proper resource > refere

[Wikidata-tech] Two questions about Lexeme Modeling

o the variants of a single language. For display, we would apply a similar language fallback mechanism we now apply when showing labels. 2b) if we treat lemmas as multi-variant, should Forms also be multi-variant, or should they be per-variant? Should the glosse of a Sense be multi-variant? I c

Re: [Wikidata-tech] Why term for lemma?

l reasons. One viable approach for code sharing would be to have MonolingualText contain a Term object. But that would introduce more coupling between our components. I don't think the little bit of code that could be shared is worth the effort. -- Daniel Kinzler Senior Software Developer Wikimedi

[Wikidata-tech] Linking RDF resources for external IDs

look at the two options for the new mapping and let me know which you like best. You can use a plain old diff between the files for a first impression. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. @prefix rdf: <http://www.w3.o

[Wikidata-tech] BREAKING CHANGE: Quantity Bounds Become Optional

F_Dump_Format#Quantity Relevant tickets: * <https://phabricator.wikimedia.org/T115269> Relevant patches: * <https://gerrit.wikimedia.org/r/#/c/302248> * <https://github.com/DataValues/Number/commit/2e126eee1c0067c6c0f35b4fae0388ff11725307> -- Daniel Kinzler Senior Software

Re: [Wikidata-tech] Why term for lemma?

And it's always *in* a language. The only question is whether we only have one, or multiple (for variants/scripts). But one will do for now. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. __

[Wikidata-tech] Proposed update to the stable interfaces policy

Tomorrow I plan to apply the following update to the Stable Interface Policy: https://www.wikidata.org/wiki/Wikidata_talk:Stable_Interface_Policy#Proposed_change_to_to_the_.22Extensibility.22_section Please comment there if you have any objections. Thanks! -- Daniel Kinzler Senior Software

[Wikidata-tech] Announcing the Wikidata Stable Interface Policy

munity. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

[Wikidata-tech] Policy on Interface Stability: final feedback wanted

tended as a reference for bot authors, data consumers, and other users of our APIs. We plan to announce this as the development team's official policy on Monday, August 22. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wisse

Re: [Wikidata-tech] URL strategy

"full" or "deep" mapping, where the statement is a resource in it's own right, and we use several triples to describe its type, value, rank, qualifiers, references, etc. -- Daniel Kinzler Senior Software Developer Wikimedia Deuts

Re: [Wikidata-tech] MathML is dead, long live MathML

Am 07.04.2016 um 20:00 schrieb Moritz Schubotz: > Hi Daniel, > > Ok. Let's discuss! Great! But let's keep the discussion in one place. I made a mess by cross-posting this to two lists, now it's three, it seems. Can we agree on as the venue of discussion? At least

[Wikidata-tech] MathML is dead, long live MathML

Peter Krautzberger, maintainer of MathJax, apparently thinks that MathML has failed as a web standard (even though it succeeded as an XML standard), and should be removed from HTML5. Here's the link: https://www.peterkrautzberger.org/0186/ It's quite a rant. Here's a quick TL;DR: > It doesn’t

Re: [Wikidata-tech] Caches for Special:EntityData json

s this > the > desired behaviour? When will the cache be cleared? > > Thanks, > > Markus > > ___ > Wikidata-tech mailing list > Wikidata-tech@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikidata-te

[Wikidata-tech] Wikibase CI is broken because auf Scribunto issue

yLibraryTest::testRegister 11:39:14 Failed asserting that LuaSandboxFunction Object () is an instance of class "Scribunto_LuaStandaloneInterpreterFunction". I guess some change to Scribunto broke compatibility... -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gese

[Wikidata-tech] Technical information about the new "math" and "external-id" data types

"datatype": "external-id" } In some cases, such as ISBNs, we would want a URL as well as a URI: { "snaktype": "value", "property": "P708", "datavalue": { "value": "3827370

[Wikidata-tech] On interface stability and forward compatibility

MUST either ignore the respective Snak, or fail with a fatal error. A warning SHOULD be issued to alert the user that some part of the data could not be processed. Do you think these guidelines are reasonable? It seems to me that adopting them should save everyone some trouble. -- Daniel Kinzler

Re: [Wikidata-tech] On interface stability and forward compatibility

Am 05.02.2016 um 14:55 schrieb Tom Morris: > Sounds a lot like a restatement of Postel's Law > > https://en.wikipedia.org/wiki/Robustness_principle Yes indeed: "Be conservative in what you send, be liberal in what you accept" -- Daniel Kinzler Senior Software Developer Wi

Re: [Wikidata-tech] On interface stability and forward compatibility

o. But this kind of thing is clearly distinct from actual "breaking changes" in my mind. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

[Wikidata-tech] Last call for objections against DataModel changes.

lementation details can still change later, but after nearly 3 months, we finally need a decision on the conceptual level. If there are no substantial objections, this will become definite on Tuesday, December 8. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellsch

[Wikidata-tech] Using the Role Object Pattern to represent derived information in the data model

amous names when during my research. Looks like we are not first in having this need... -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wik

Re: [Wikidata-tech] [Wikidata] how to map other identifiers to Wikidata entity IDs

ll have search-by-property soonish, too. I certrainly hope so. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://li

Re: [Wikidata-tech] how is the datetime value with precision of one year stored

=", "type": "string" }, "datatype": "url" } ] }, "snaks-order": [ "P854" ] } ] } ] Am 31.08.2015 um 19:19 schrieb Ra

[Wikidata-tech] Dump requirements

description of our dumps Promote stable URLs: * The latest dump of any type should be available under a stable, predictable URL. * TBD: latest URL could point to a symlink, get rewritten to the actual file, or trigger an HTTP redirect. Thoughts? Comments? Additions? -- Daniel Kinzler Senior Software

Re: [Wikidata-tech] Thoughts on (not) exposing a SPARQL endpoint

, especially Gabriel's. -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo

Re: [Wikidata-tech] Thoughts on (not) exposing a SPARQL endpoint

my mail to this list. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo

Re: [Wikidata-tech] Thoughts on (not) exposing a SPARQL endpoint

. Or, if it is not possible, an improved version of WDQ that would break its current limitations. Absolutely. I'd like to avoid any commitment to keeping the SPARQL interface stable, though. That's why I'd limit it to labs-based usage. -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia

[Wikidata-tech] Thoughts on (not) exposing a SPARQL endpoint

that this is not a decision or recommendation by the Wikidata team, just my personal take. -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech

Re: [Wikidata-tech] Thoughts on (not) exposing a SPARQL endpoint

Am 10.03.2015 um 21:09 schrieb Stas Malyshev: People would ask us for full SPARQL as soon as they'd know we're running SPARQL db. Sure. And I'D tell them you can use SPARQL on labs, but beware that it may change or go away. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland

Re: [Wikidata-tech] Globe coordinates precision question (technical)

, and we can't really guess the precision based on the float values. Looking at GeoCoordinateFormatter, I see this: if ( $precision = 0 ) { $precision = 1 / 3600; } I.e. it assumes 1 arc sec if no percision is given. Not great, but not much else we can do at this point. -- Daniel Kinzler

[Wikidata-tech] Things to get merged before the branch next week

. Are there any other performance improvements that we should get in? I imagine that this will be the last time we branch until the third week of January. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V

Re: [Wikidata-tech] Parsing Entity IDs

). -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

Re: [Wikidata-tech] Wikibase changesAsJson

-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech

Re: [Wikidata-tech] alternatives to memcached for caching entity objects across projects

nicely. I forget why exactly. I don't care much either way. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https

Re: [Wikidata-tech] alternatives to memcached for caching entity objects across projects

? Wikibase/docs/caching.md or some such? -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org

Re: [Wikidata-tech] [Multimedia] From the MW Core Backlog....

-- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

Re: [Wikidata-tech] Removing 3rd party dependencies from WikibaseQueryEngine

Am 09.09.2014 19:20, schrieb Daniel Kinzler: Hi Rob, thanks for clarifying! I guess I just oversimplified what was said in our discussion. I'll try to summarize what you now wrote: If there is a package for dbal/symfony/whatever in Ubuntu LTS, we have a good chance, but no guarantee

Re: [Wikidata-tech] Removing 3rd party dependencies from WikibaseQueryEngine

package is ok. Don't know about PEAR... -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https

[Wikidata-tech] How to record redirects in the database

query. Could be acceptable if these cases are rare. Needs trivial schema change deployment (new table). -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing

Re: [Wikidata-tech] reviews needed for pubsubhubbub extension

Am 09.07.2014 19:39, schrieb Dimitris Kontokostas: On Wed, Jul 9, 2014 at 6:13 PM, Daniel Kinzler daniel.kinz...@wikimedia.de mailto:daniel.kinz...@wikimedia.de wrote: Am 09.07.2014 08:14, schrieb Dimitris Kontokostas: Maybe I am biased with DBpedia but by doing some experiments

Re: [Wikidata-tech] reviews needed for pubsubhubbub extension

creation and deletion (I don't know about moves/renames). -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https

Re: [Wikidata-tech] PubSubHubbub what is it all about ? - Re: Wikidata-tech Digest, Vol 15, Issue 3

it for wikidata.org. The code is at https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FPubSubHubbub -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing

[Wikidata-tech] Resolving Redirects

() is the most practical, even though it's not the most elegant from an OO design perspective. What's your take on this? Got any better ideas? -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V

Re: [Wikidata-tech] Constructing Entities from their serialization

that's why this was introduced. I'm moving tests away from that, though. -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech

[Wikidata-tech] Using the canonical JSON model in dumps.

-- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

Re: [Wikidata-tech] Managing dependencies when extending Wikibase

:03, schrieb Daniel Kinzler: The folks of the Wikidata.lib project at the Hasso Plattner Institut have developed an extension to Wikibase that allows us to suggest properties to add to items, based on the properties already present (a very cool project, btw). This is, conceptually

[Wikidata-tech] Managing dependencies when extending Wikibase

: Original-Nachricht Betreff: PropertySuggester Dependencies Datum: Thu, 6 Mar 2014 11:07:56 + Von: Finke, Moritz moritz.fi...@student.hpi.uni-potsdam.de An: Daniel Kinzler daniel.kinz...@wikimedia.de Hi, unten sind die Abhängigkeiten des PropertySuggesters nach Klassen sortiert

Re: [Wikidata-tech] wbsetclaim

went wrong somewhere. I have filed https://bugzilla.wikimedia.org/show_bug.cgi?id=61950 now. -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list

Re: [Wikidata-tech] Badges

have to be fetched for every page view on wikipedia... not good. -- daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech

[Wikidata-tech] Report from the Architecture Summit

by pp_propname+pp_sortkey. That should cover most use cases nicely, without big schema changes. So, lots to follow up on! Cheers Daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V

Re: [Wikidata-tech] Adding configuration to WikibaseLib

sure they are consistent, which is especially important when running both repo and client on the same wiki. Do you have a suggestion how to solve this? We have had different saettigns for the same thing in repo and client before, I would like to avoid this in the future. -- daniel -- Daniel

Re: [Wikidata-tech] Wikibase data exchange format

. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

Re: [Wikidata-tech] Wikibase data exchange format

on how PuSH works - if this is not the case, I see no good way to support multiple content formates. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata

Re: [Wikidata-tech] Wikibase data exchange format

Am 17.01.2014 08:39, schrieb Daniel Kinzler: I suggest to use format-agnostic canonical *description* URI for PuSH notifications. I just realized that this will not work well, since the hub will retrieve that data, and all clients would then receive the data in the format the hub

Re: [Wikidata-tech] locally run lua scripts

http://wikipediafs.sourceforge.net/ There's also the (inactive) levitation project: https://github.com/scy/levitation - a project to convert Wikipedia database dumps into Git repositories. It doesn't scale for Wikipedia, but should work fine for smaller dumps. -- daniel -- Daniel Kinzler

[Wikidata-tech] Improving leaky test cases

to inject real ids for placeholders in the data the providers return. Cheers! Daniel -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. ___ Wikidata-tech mailing list Wikidata-tech

Re: [Wikidata-tech] [Wikitech-l] Help needed with ParserCache::getKey() and ParserCache::getOptionsKey()

Am 10.12.2013 22:38, schrieb Brad Jorsch (Anomie): Looking at the code, ParserCache::getOptionsKey() is used to get the memc key which has a list of parser option names actually used when parsing the page. So for example, if a page uses only math and thumbsize while being parsed, the value

[Wikidata-tech] Help needed with ParserCache::getKey() and ParserCache::getOptionsKey()

? Possible fix: ParserCache::getOptionsKey could delegate to ContentHandler::getOptionsKey, which could then be used to override the default behavior. Would that be a sensible approach? And if so, would it be feasible to push out such a change before the holidays? Thanks, Daniel -- Daniel Kinzler

Re: [Wikidata-tech] future of the entity suggester

Hello Nilesh! Good to hear from you. I was off for a couple of days, and asked Lydia to make introductions. Thanks Lydia! A quick heads up: The architecture we have discussed with the team at the HPI is a bit different from what we designed for the GSoC project. The idea is to have a MediaWiki

[Wikidata-tech] RFC: TitleValue

Hi all! As discussed at the MediaWiki Architecture session at Wikimania, I have created an RFC for the TitleValue class, which could be used to replace the heavy-weight Title class in many places. The idea is to show case the advantages (and difficulties) of using true value objects as opposed to

Re: [Wikidata-tech] [Wikidata-l] [Pywikipedia-l] wbsearchentities()

Hi all! We have to impose a fixed limit on search result, since search results can not be ordered by a unique ID, so paging is expensive. The default for this limit is 50, but it SHOULD be 500 for bots. But the higher limit for bots is currently not applied by the wbsearchentities module -

Re: [Wikidata-tech] IRI, URL, sameAs and the identifier mess

Am 03.09.2013 21:43, schrieb David Cuenca: A couple of months ago there was a conversation about what to do with the identifiers that should be owl:sameAs [1] It's unclear to me where owl:sameAs would be used... it should definitely NOT be used to point to descriptions of the same thing in

Re: [Wikidata-tech] [Wikidata-l] [Pywikipedia-l] wbsearchentities()

Am 13.09.2013 18:24, schrieb Benjamin Good: Daniel, Even 500 seems like a very low limit for this system unless I'm misunderstanding something. Unless there is another way to execute queries that return more rows than that, this would negate the possibility of a huge number of applications

[Wikidata-tech] BREAKING CHANGE: Wikidata API changing top upper-case IDs.

Hi all. With today's deployment, the Wikibase API modules used on wikidata.org will change from using lower-case IDs (q12345) to upper-case IDs (Q12345). This is done for consistency with the way IDs are shown in the UI and used in URLs. The API will continue to accept entity IDs in lower-case

Re: [Wikidata-tech] IRI-value or string-value for URLs?

Am 03.09.2013 11:50, schrieb Lydia Pintscher: On Mon, Sep 2, 2013 at 11:56 AM, Denny Vrandečić denny.vrande...@wikimedia.de wrote: OK, based on the discussion so far, we will add the data type to the snak in the external export, and keep the string data value for the URL data type. That should

Re: [Wikidata-tech] IRI-value or string-value for URLs?

Am 30.08.2013 17:21, schrieb Denny Vrandečić: I do see an advantage of stating the property datatype in a snak in the external JSON representation, and am trying to understand what prevents us from doing so. Not much, the SnakSerializer would need access to the PropertyDataTypeLookup service,

Re: [Wikidata-tech] Is assert() allowed?

Am 31.07.2013 13:42, schrieb Tim Starling: We could have a library of PHPUnit-style assertion functions which throw exceptions and don't act like eval(), I would be fine with that. Maybe MWAssert::greaterThan( $foo, $bar ) or something. I like that! Should support an error message as an

[Wikidata-tech] Jenkins failing for no good reason.

There seems to be an issue with Jenkins. It appears to use an old version of other extensions under some circumstances. It's like this: If you submit change 33 for extension A, which needs change 44 in extension B (which isn't merged yet), jenkins will fail correctly fail. BUT: When change 44

Re: [Wikidata-tech] WikiVOYAGE deployment plan

Am 28.06.2013 11:45, schrieb Denny Vrandečić: * Wikipedia will not automatically and suddenly display links to Wikivoyage. The behavior on Wikipedia actually remains completely unchanged by this deployment. Let's make sure we have thorough tests for this, I'm not 100% sure how

Re: [Wikidata-tech] Representing invalid Snaks

A quick follow up to this morning's mail: I discussed this issue with Denny for a while, and we came up with this: * I'll explore the possibility of using a BadValue object instead of a BadSnak, that is, model the error on the DataValue level. My initial impression was that this would be more

Re: [Wikidata-tech] Getting the property (data) type of a PropertyValueSnak.

Am 13.06.2013 06:38, schrieb Jeroen De Dauw: Hey, Putting the DataType id in PropertyValueSnaks at this point seems like a bad idea for several reasons. Doing so would cost us quite some work end end up with a more complicated system as foundation. Changing it now would be hard. But I

Re: [Wikidata-tech] Getting the property (data) type of a PropertyValueSnak.

Am 13.06.2013 03:22, schrieb Daniel Werner: -1 Had to deal with this in the frontend as well and don't think this is inconvenient. It seems like the cleanest approach. Polluting the Snaks with information like this for performance or convenience reasons will probably cause more trouble in