Wikidata-tech

wikidata-tech@lists.wikimedia.org

1 participants
622 discussions

Deprecation & Removal of the ungroupedlist API parameter
by Addshore 27 Jul '15

27 Jul '15

The ungroupedlist api parameter will be deprecated from the wbgetentities and wbgetclaims modules on Wikidata as of the next deployment on Wednesday 29th July. The parameter has very low usage and removing it removes code complexity in the API. Phabricatior - https://phabricator.wikimedia.org/T106863 Deprecation change - https://gerrit.wikimedia.org/r/225903 Removal change - https://gerrit.wikimedia.org/r/226643 To adjust for this change users of the API simply have to use the default format, which is grouped by property ID. Addshore

2 2

Obtaining the RDF description of a Wikidata item via the Linked Data interface
by csarasua 09 Jul '15

09 Jul '15

Hi, I would like to get the RDF description of Wikidata items by using the Linked Data interface. After executing an HTTP GET of "https://www.wikidata.org/entity/Q10313" with header "Accept, application/rdf+xml" I get RDF data, but I don't see all the statements that I am able to see via the wiki (at https://www.wikidata.org/wiki/Q10313). For example, I don´t see the statement indicating that "Q10313 is instanceOf city". Should I query the RDF dump for this, or is it possible to query such RDF data via the Linked Data interface? I included below the kind of statements I do get in the response. Thanks in advance. Cristina --- # <rdf:Descriptionrdf:about="https://www.wikidata.org/wiki/Special:EntityData/Q10313"> # <schema:versionrdf:datatype="http://www.w3.org/2001/XMLSchema#integer">226415944</schema:version> # <schema:dateModifiedrdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2015-07-05T08:34:43Z</schema:dateModified> # <rdf:typerdf:resource="http://schema.org/Dataset"/> # <schema:aboutrdf:resource="http://www.wikidata.org/entity/Q10313"/> # </rdf:Description> # <rdf:Descriptionrdf:about="http://www.wikidata.org/entity/Q10313"> # <rdf:typerdf:resource="http://wikiba.se/ontology-beta#Item"/> # <rdfs:labelxml:lang="it">San Sebastián</rdfs:label> # <skos:prefLabelxml:lang="it">San Sebastián</skos:prefLabel> # <schema:namexml:lang="it">San Sebastián</schema:name> # ... # </rdf:Description> # <rdf:Descriptionrdf:about="https://it.wikipedia.org/wiki/San%20Sebasti%C3%A1n"> # <rdf:typerdf:resource="http://schema.org/Article"/> # <schema:aboutrdf:resource="http://www.wikidata.org/entity/Q10313"/> # <schema:inLanguage>it</schema:inLanguage> # </rdf:Description> # <rdf:Descriptionrdf:about="https://an.wikipedia.org/wiki/Sant%20Sabasti%C3%A1n"> # <rdf:typerdf:resource="http://schema.org/Article"/> # <schema:aboutrdf:resource="http://www.wikidata.org/entity/Q10313"/> # <schema:inLanguage>an</schema:inLanguage> # </rdf:Description> # ... # # <rdf:Descriptionrdf:about="https://vi.wikivoyage.org/wiki/San%20Sebastian"> # <rdf:typerdf:resource="http://schema.org/Article"/> # <schema:aboutrdf:resource="http://www.wikidata.org/entity/Q10313"/> # <schema:inLanguage>vi</schema:inLanguage> # </rdf:Description> # </rdf:RDF> -- Cristina Sarasua Institute for Web Science and Technologies (WeST) Universität Koblenz-Landau Universitätsstraße 1 56070 Koblenz Germany e: csarasua(a)uni-koblenz.de p: +49 261 287 2772 f: +49 261 287 100 2772 w: http://west.uni-koblenz.de

2 3

Need to support PHP 5.3?
by Jeroen De Dauw 30 Jun '15

30 Jun '15

Hey, I'm wondering if we still need to support PHP 5.3. http://blog.ircmaxell.com/2014/12/on-php-version-requirements.html I'd rather bump the minimum version up to PHP 5.5, and know people have been talking about doing the same for MediaWiki itself. My question is if this can already be done without making Wikibase undeployable on WMF servers. Is everything running HHVM yet, or is there some stuff relevant to Wikibase that still runs an unsupported version of PHP? Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3

4 8

Dump requirements
by Daniel Kinzler 29 Jun '15

29 Jun '15

There's an ongoing discussion in ops about improving the dump process, see https://phabricator.wikimedia.org/T88728 https://phabricator.wikimedia.org/T93396 https://phabricator.wikimedia.org/T17017 https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team/Backlog/Improv… I would like to join in and add our requirements and thoughts to the list, and would like some input on that. So far I have: Make it easier to register a new type of dump via a config change. A dump should define: * a script(s) to run * output file(s) * the dump schedule * a short name * brief description (wikitext or HTML? translatable?) * required input files (maybe) Make clear timelines of consistent dumps. * drop the misleading "one dir with one timestamp for all dumps" appraoch * have one timeline per dump instead * for dumps that are guaranteed to be consistent (one generated from the other), generate a timeline of directories with symlinks to the actual files. Make dumps discoverable: * There should be a machine readable overview of which dumps exist in which versions for each project. * This overview should be a JSON document (may even be static) * Perhaps we also want a DCAT-AP 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 Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V.

1 0

pywikibot: how to add claims to a property page?
by Marco Fossati 17 Jun '15

17 Jun '15

Hi everyone, I am the maintainer of the DBpedia mapper bot [1]. Currently, I'm trying to add claims to property pages. There seems to be no implementation in pywikibot to add a claim to a property page. For an 'ItemPage' [2], I proceed as per the following (dummy) example: site = pywikibot.Site("wikidata", "wikidata") repo = site.data_repository() item = pywikibot.ItemPage(repo, item_id) claim = pywikibot.Claim(repo, 'P1709') claim.setTarget('http://dbpedia.org/ontology/Espresso') item.addClaim(claim) As property pages should be instances of 'PropertyPage' [3], I would expect an 'addClaim' method implemented there, but that's not the case. I tried with the 'DataSite.addClaim' method [4] (used by ItemPage [5] BTW), but it cries at [6] since the PropertyPage object has no 'claims' attribute. The edit from the Wikidata Web UI is indeed possible, so my question is: how can I add a claim to a property page with pywikibot? Thanks for your time, cheers! [1] https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Bot/DBpedia… [2] http://pywikibot.readthedocs.org/en/latest/pywikibot/#pywikibot.__init__.It… [3] http://pywikibot.readthedocs.org/en/latest/pywikibot/#pywikibot.__init__.Pr… [4] http://pywikibot.readthedocs.org/en/latest/pywikibot/#pywikibot.site.DataSi… [5] https://github.com/wikimedia/pywikibot-core/blob/master/pywikibot/page.py#L… [6] https://github.com/wikimedia/pywikibot-core/blob/master/pywikibot/site.py#L… -- Marco Fossati http://about.me/marco.fossati Twitter: @hjfocs Skype: hell_j

1 0

Change: including entrypoint now required for Wikibase
by Jan Zerebecki 17 Jun '15

17 Jun '15

Your Wikibase installation will now require you to include its entrypoint. (No change needed for production.) If you didn't already have something like this in your LocalSettings.php you now need to: require_once "$IP/extensions/Wikibase/Wikibase.php"; Or alternatively: require_once "$IP/extensions/Wikibase/repo/Wikibase.php"; require_once "$IP/extensions/Wikibase/client/Wikibase.php"; Change that caused this: https://gerrit.wikimedia.org/r/#/c/217947/ There might be future changes in this area, for switching to https://www.mediawiki.org/wiki/Manual:Extension_registration but those should hopefully be backwards compatible to the above. -- Regards, Jan Zerebecki

3 2

Tiny possibly breaking API change (wbeditentity & wbgetclaims)
by Addshore 15 Jun '15

15 Jun '15

Please see the lower portion of the commit message of this change which has now been merged: https://gerrit.wikimedia.org/r/#/c/217885 I don't image this will break anything really, unless scripts are written expecting 'claim' as the type here. Addshore

1 0

Composer.lock
by Matthew Flaschen 05 Jun '15

05 Jun '15

I could use some feedback related to https://gerrit.wikimedia.org/r/#/c/215815/1 ("Use composer install, not composer update"). Composer strongly recommends committing both composer.json and composer.lock to the repository (https://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file). This means the user can install the exact dependencies tested by the last developer who updated composer.lock (the goal is that you will only commit composer.lock if the dependency set works). Can you comment at https://gerrit.wikimedia.org/r/#/c/215815/1 on why Wikibase does not commit it? Thanks, Matt Flaschen

1 0

Freebase Migration
by Laura DOMINIQUE 27 May '15

27 May '15

Hi Team, I'm working at Dailymotion and we are currently using Freebase to gather information about Topic mentioned in our video catalogue: * It is used upon upload where user can enter tags on video (list of tag is based on Freebase's topic list) * It is also used to create pages around a topic and thus classifies videos (example: http://www.dailymotion.com/us/topic/01mpq7s-beyonce-knowles) Note that this project is only on Beta version on our side. However, we have closely followed the announcement around the migration to Wikidata and have some questions: * Can you confirm what is the new planning as it is said Freebase would still exists after the 30th of June 2015? * I suppose API calls would not remain the same. Would there be a mapping provided to ease the switch? * Would the entire set of topics included in Freebase be migrated to Wikidata? If not, how the selection would be done? * For a given topic, is there some information that would not be integrated in Wikidata (for example: alias, official_website,...) Many thanks in advance for your feedback on that. [cid:image001.gif@01D06194.71FFD4B0] Laura Dominique | Head of Relevant Content 140, boulevard Malesherbes, 75017 Paris, France | Mobile : +33 (0)6 29 45 24 22 dailymotion.com<http://www.dailymotion.com/> | Find us on Facebook<https://www.facebook.com/dailymotionFrance> | Follow us on Twitter<https://twitter.com/dailymotion>

3 3

Alternative to wbformatvalue
by Almer Bolatov 06 May '15

06 May '15

Hello all, is there an alternative to MediaWiki Api wbformatvalue <http://www.wikidata.org/w/api.php?action=help&modules=wbformatvalue> function in Wikidata Toolkit? Currently I search for items with the help of MediaWiki Api <http://www.wikidata.org/w/api.php> and parse them as a list of JacksonItemDocuments. Actually, at this point I already have the required information. But now I have to do another query to format the value by calling wbformatvalue. What I could do (if WikidataToolkit supports it) is extract and format the value from JacksonItemDocument already. Thanks in advance Cheers, Almer

4 3

← Newer
1
...
35
36
37
38
39
40
41
...
63
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Wikidata-tech