Re: [Wikidata] No links, wrong data: Scotland's orphans need help

of maintaining data, since one would have a way to filter statements by how long ago they had last been checked. Best wishes, Markus On 03.06.2015 15:56, Markus Krötzsch wrote: On 03.06.2015 13:57, Magnus Manske wrote: Maybe there is a case to separate import and verification here? There are many

Re: [Wikidata] [Spam] Re: No links, wrong data: Scotland's orphans need help

On 03.06.2015 13:57, Magnus Manske wrote: Maybe there is a case to separate import and verification here? There are many statements in Wikidata nowadays, but they get really trustworthy through references (other than imported from Wikipedia). But for external IDs, references are superfluous;

Re: [Wikidata] [Spam] Re: No links, wrong data: Scotland's orphans need help

see the same thing there, with it having identifiers from both sides. Andrew. On 2 June 2015 at 12:12, Markus Krötzsch mar...@semantic-mediawiki.org wrote: Another interesting type of Scottish historic orphans are those that are duplicates of items that do have site links. Even very prominent

Re: [Wikidata] People who died in 2015 who were Dutch

for almost arbitrary data imports. It was just my first thought for turning your complaint into something that could work as a solution -- if you have a better idea which tool to use, feel free to post it. Regards, Markus Thanks, GerardM On 4 June 2015 at 10:31, Markus Krötzsch mar

Re: [Wikidata] New Wikidata maps

Update: I added a link to a high-resolution (17280x8640 pixels) monochrome image of all Wikidata items to the article [1]. Maybe best viewed after download (the file is only 2MB, but my browser got a bit slow on this). Markus [1]

Re: [Wikidata] Update frequency on the Wikidata Query API

On 18.06.2015 21:40, Thomas Steiner wrote: Sorry, realizing only now that this is for the Query API, not the Linked Data interface. My bad, please ignore my previous reply. Maybe it would still be a good idea for bots to do a check against the live json data right before the edit. Checking

Re: [Wikidata] accessing data from a wikidata concept page

On 11.06.2015 15:06, Lydia Pintscher wrote: On Thu, Jun 11, 2015 at 9:08 AM, Markus Krötzsch mar...@semantic-mediawiki.org wrote: Hi Ben, That's a very good point. We should really have direct links to JSON and RDF for each item (e.g., at the top-right, which seems to be the custom now on many

Re: [Wikidata] Mexico / Building up Wikidata, country by country

Hi Yaroslav, On 10.06.2015 22:01, Yaroslav M. Blanter wrote: On 2015-06-10 17:46, Markus Krötzsch wrote: On 10.06.2015 17:05, Magnus Manske wrote: Some country-specific things to do on Wikidata: https://tools.wmflabs.org/wikidata-todo/?country=96 Wikidata by country stats: http

Re: [Wikidata] Wikidata Visualization Challenge

Dear Jan, I just wondered about the timeline you have for this event. Is it true that the submission deadline is 1 June 2015, and that the ten finalists are then expected to present their work in Sweden on 4 June 2015? Or is this a typo? Three days seem to be a very short time to select

Re: [Wikidata] calendar model screwup

On 01.07.2015 16:00, Pierpaolo Bernardi wrote: On Wed, Jul 1, 2015 at 8:17 AM, Markus Krötzsch mar...@semantic-mediawiki.org wrote: Dear Pierpaolo, This thread was only about Julian and Gregorian calendar dates. If and how other calendar models should be supported in some future is another

Re: [Wikidata] Donostia-San Sebastián Wikidata Editathon

Hi Cristina, I found maps to be very helpful when doing Wikidata editing for a certain place or area. Here is the map of all 556 things Wikidata currently has in and around Donostia-San Sebastián:

Re: [Wikidata] calendar model screwup

On 01.07.2015 18:14, Peter F. Patel-Schneider wrote: On 07/01/2015 07:00 AM, Pierpaolo Bernardi wrote: On Wed, Jul 1, 2015 at 8:17 AM, Markus Krötzsch mar...@semantic-mediawiki.org wrote: Dear Pierpaolo, This thread was only about Julian and Gregorian calendar dates. If and how other calendar

Re: [Wikidata] New Wikidata maps

On 28.06.2015 13:51, Emilio J. Rodríguez-Posada wrote: Very cool. Now try the same with other bodies of Solar System.[1] Specially moon craters. Right ... here you go: https://korrekt.org/page/Note:Wikidata_on_the_Moon With the density that low, other visualisations (Google Maps like) would

Re: [Wikidata] calendar model screwup

, as converting between calendars may be extremely difficult, or impossible. P. On Tue, Jun 30, 2015 at 11:32 PM, Markus Krötzsch mar...@semantic-mediawiki.org wrote: Hi everyone, Thanks to Lydia and the team for containing this issue and providing the necessary documentation for fixing it. For all

Re: [Wikidata] Wikidata needs your votes

On 18.08.2015 12:39, Lydia Pintscher wrote: On Tue, Aug 18, 2015 at 12:53 AM, Chris Caceres Alhambra krsal...@gmail.com wrote: Hi Scott, I just voted, and I did receive the email to confirm my vote. It was, however, in my spam folder, rather than my inbox. Yeah it seems to be landing in

Re: [Wikidata] Wikidata needs your votes

On 21.08.2015 16:55, Jane Darnell wrote: it would help if you included the link in these reminders! Here you go: https://www.land-der-ideen.de/ausgezeichnete-orte/preistraeger/wikida - yellow vote button upper right, enter email (the terms and conditions in German ensure that it will only

Re: [Wikidata] Wikidata needs your votes

Of course I meant https://www.land-der-ideen.de/ausgezeichnete-orte/preistraeger/wikidata Markus On 22.08.2015 14:03, Markus Krötzsch wrote: On 21.08.2015 16:55, Jane Darnell wrote: it would help if you included the link in these reminders! Here you go: https://www.land-der-ideen.de

Re: [Wikidata] Properties for family relationships in Wikidata

On 20.08.2015 14:51, Andrew Gray wrote: As someone with an extensive collection of Hindi-speaking relatives, I agree entirely with the complexity here. Never did a language have such specialised ways of identifying your relations :-) This is in fact exactly where inferred relations can make

Re: [Wikidata] Naming Conventions for URIs

For the benefit of those of you reading only the Wikidata list: this question has been answered on the semantic web list now. The conclusion is that the problem does not affect SPARQL and RDF 1.1 Turtle syntax: you can start local names with numbers in both cases. XML, RDF and SPARQL all have

Re: [Wikidata] Properties for family relationships in Wikidata

Hi all, There have been some discussions here already on what to do with the inferences (add them to Wikidata, just display them, add them only to the query service, etc.). That's great, but this is already the second step from where we are now. Right now, we don't have any way yet for

Re: [Wikidata] Properties for family relationships in Wikidata

On 19.08.2015 08:38, Stas Malyshev wrote: ... Also, there's another thing. Suppose we have Q345 - spouse - Q123, but not Q123 - spouse - Q345, and we process entities, without loss of generality, in order of ascending IDs. When we generate data for Q123, we don't know yet that Q345 is linked to

Re: [Wikidata] calendar model screwup

Hi everyone, Thanks to Lydia and the team for containing this issue and providing the necessary documentation for fixing it. For all of you who wonder what the scale of the issue is (a.k.a. How bad is it?), here are some numbers. The most important years for better understanding: 1582:

Re: [Wikidata] Critical JSON bugs back in production; all dumps broken now

by writing some more integration tests for our json dumps to spot this kind of thing! That's great news! Many thanks. Markus On 4 August 2015 at 11:26, Lydia Pintscher lydia.pintsc...@wikimedia.de mailto:lydia.pintsc...@wikimedia.de wrote: On Tue, Aug 4, 2015 at 12:20 PM, Markus Krötzsch

[Wikidata] Critical JSON bugs back in production; all dumps broken now

Hi, The recent Wikidata JSON dumps again contain huge amounts of broken JSON where empty maps are serialized as [] instead of using {}. Just grep for claims:[] or aliases:[] or any other key that requires a map to find many examples. The scope of the problem is massive. Basically all entity

Re: [Wikidata] Merging items creates redirect now

On 30.07.2015 09:12, Lydia Pintscher wrote: On Thu, Jul 30, 2015 at 5:39 AM, Markus Krötzsch mar...@semantic-mediawiki.org wrote: Hi, Thanks for the update. With redirect now becoming common as a meaningful part of the data, could we also have information about them in the JSON dumps

Re: [Wikidata] wikidata workflow in Wikipedia

On 23.07.2015 01:06, Federico Leva (Nemo) wrote: Benjamin Good, 22/07/2015 23:15: I'm particularly concerned about the edit button. When a Wikipedia user hits edit on an article built using wikidata content, how are they supposed to edit the wikidata content? On the consuming templates, you

Re: [Wikidata] property label/alias uniqueness

On 13.07.2015 16:01, John Erling Blad wrote: No we should not make the aliases unique, the reason aliases are useful is because they are _not_ unique. Add versioning to labels, that is the only real solution. Following this thread for a while, I still have no idea what this solution is. Could

Re: [Wikidata] Announcing Wikidata Taxonomy Browser (beta)

On 24.10.2015 12:29, Martynas Jusevičius wrote: I don't see how cycle queries can be a requirement for SPARQL engines if they are not part of SPARQL spec? The closest thing you have is property paths. We were talking about *cyclic data* not cyclic queries (which you can also create easily

Re: [Wikidata] Announcing Wikidata Taxonomy Browser (beta)

On 23.10.2015 11:16, Gerard Meijssen wrote: Hoi, The problem with tools like this is that they get a moment attention. Particularly when they are stand alone, not integrated, they will lose interest. Problems, problems, ... Would it be an option to host this tool on Labs? Yes, this is

Re: [Wikidata] Announcing Wikidata Taxonomy Browser (beta)

On 25.10.2015 02:18, Kingsley Idehen wrote: On 10/24/15 10:51 AM, Markus Krötzsch wrote: On 24.10.2015 12:29, Martynas Jusevičius wrote: I don't see how cycle queries can be a requirement for SPARQL engines if they are not part of SPARQL spec? The closest thing you have is property paths. We

Re: [Wikidata] Announcing Wikidata Taxonomy Browser (beta)

On 24.10.2015 09:36, James Heald wrote: On 24/10/2015 00:50, Stas Malyshev wrote: Hi! least one Wikipedia) are considered to refer to equivalent classes on Wikidata, which could be expressed by a small subclass-of cycle. For We can do it, but I'd rather we didn't. The reason is that it

Re: [Wikidata] Blazegraph

On 27.10.2015 15:34, Paul Houle wrote: One thing I really liked about Kasabi was that it had a simple interface for people to enter queries and share them with people. The "Information Workbench" from fluidOps does something similar although I never seen it open to the public. A database of

Re: [Wikidata] Data model explanation and protection

On 11.11.2015 11:33, Thomas Douillard wrote: There is a proposal for some kind of class disjointness : https://www.wikidata.org/wiki/Wikidata:Property_proposal/Generic#subclass this is here for a while now, maybe a few more supporters would speed up the process :) Interesting. This looks like

Re: [Wikidata] "Implementing" OWL RL in SPARQL (Was: qwery.me - simpler queries for wikidata)

On 12.11.2015 22:09, Peter F. Patel-Schneider wrote: On 11/12/2015 09:10 AM, Markus Krötzsch wrote: [...] On the other hand, it is entirely possible to implement correct OWL QL (note: *QL* not *RL*) reasoning in SPARQL without even using "rules" that need any recursive eva

Re: [Wikidata] Data model explanation and protection

On 29.10.2015 05:41, Benjamin Good wrote: For what its worth, I tend to agree with Peter here. It makes sense to me to add constraints akin to 'disjoint with' at the class level. +1 for having this. This does not preclude to have an additional mechanism on the instance level if needed to

Re: [Wikidata] Announcing wdq command line client

Hi Jakob, Very handy, thanks. Markus On 07.10.2015 14:04, Jakob Voß wrote: Hi, Based on a script by Marius Hoch (https://github.com/mariushoch/asparagus) I created a command line client to access Wikidata Query Service. The current release 0.2.0 includes the following features: * adding of

Re: [Wikidata] need help in running Wikidata-Toolkit-0.5.0 examples

[Maybe let's move this to wikidata-tech -- including the Wikidata discussion list here for the last time; please remove it in your reply] Dear Satya, Both issues you encountered seem to be caused by how you run the examples. It seems that the project is not configured/compiled properly yet.

Re: [Wikidata] First version for units is ready for testing!

Hi, Great news, but I have some questions ;-) It seems that the unit can be any IRI that starts with http or https, even if not referring to an entity of the wiki. Then what happens with the "unit":"1" that currently we have in JSON? It seems that one cannot enter this string in the field,

Re: [Wikidata] First version for units is ready for testing!

On 01.09.2015 05:11, Stas Malyshev wrote: ... That's a very interesting point, I think this can be handled by establishing: 1. Types/classes of units, such as "measure of length" 2. Designated standard unit - e.g. "meter" is a "standard measure of length". 3. Conversion properties - e.g. "foot"

Re: [Wikidata] First version for units is ready for testing!

On 01.09.2015 09:56, Stas Malyshev wrote: Hi! Also, I don't see a reason why the JSON encoding should use an IRI It probably doesn't have to, just Q-id would be enough. "1" is OK too, but a bit confusing - if the rest would be Q-ids, then it makes sense to make all of the Q-ids. Other option

Re: [Wikidata] Wikidata Toolkit 0.5.0 released

On 02.09.2015 08:11, Gerard Meijssen wrote: Hoi, It reads like a lot of work went in there.. Congratulations. I understand that it uses the live data and that it can be using dumps of other installations :) Now how do I use it from Labs ? Labs has Java installed. You can just copy any Java

Re: [Wikidata] Source statistics

I put into the existing method writeFinalResults() that is called at the end. As I said, this runs in about 30min on my laptop, but downloading the dump file first time takes a bit longer. [1] https://github.com/Wikidata/Wikidata-Toolkit/blob/v0.5.0/wdtk-examples/src/main/java/org/wikidata/wdtk/examp

Re: [Wikidata] Source statistics

On 07.09.2015 14:25, Edgard Marx wrote: Is not an updated version, but dbtrends.aksw.org I am getting an error there. Is the server down maybe? Markus best, Edgard On Mon, Sep 7, 2015 at 1:25 PM, André Costa

Re: [Wikidata] Announcing the release of the Wikidata Query Service

On 08.09.2015 23:56, Denny Vrandečić wrote: Anyone an idea why this query has a trouble when I add the OPTIONAL keyword? *http://tinyurl.com/pgsujp2* Doesn't look much harder than the queries in the examples. Looking at the bottom of the exceptions, you can see that the system simply

Re: [Wikidata] Announcing the release of the Wikidata Query Service

On 09.09.2015 00:07, Markus Krötzsch wrote: On 08.09.2015 23:56, Denny Vrandečić wrote: Anyone an idea why this query has a trouble when I add the OPTIONAL keyword? *http://tinyurl.com/pgsujp2* Doesn't look much harder than the queries in the examples. Looking at the bottom

Re: [Wikidata] Announcing the release of the Wikidata Query Service

On 09.09.2015 00:13, Stas Malyshev wrote: Hi! Anyone an idea why this query has a trouble when I add the OPTIONAL keyword? *http://tinyurl.com/pgsujp2* Doesn't look much harder than the queries in the examples. It's not because it's harder. It's because ?head can be unbound, and you can

[Wikidata] Wikidata Live RDF?

Hi, Now that the SPARQL endpoint is "official", will the life RDF data (which you get, e.g, via Special:EntityData) also be switched to show the content using in SPARQL? Since this is already implemented, I guess this would be a minor switch. It could be very useful for users who want to

Re: [Wikidata] Announcing the release of the Wikidata Query Service

Good morning :-) On 09.09.2015 00:45, Stas Malyshev wrote: Hi! P.S. I am not convinced yet of this non-standard extension of SPARQL to fetch labels. Its behaviour based on the variables given in SELECT seems You don't have to use variables in SELECT, it's just a shortcut. What I meant

Re: [Wikidata] Wikidata Live RDF?

On 09.09.2015 08:30, Stas Malyshev wrote: Hi! Now that the SPARQL endpoint is "official", will the life RDF data (which you get, e.g, via Special:EntityData) also be switched to show the content using in SPARQL? Since this is already implemented, I guess I think it might be a good idea. We

Re: [Wikidata] Importing Freebase (Was: next Wikidata office hour)

Hi Thad, thanks for your support. I think this can be really useful. Now just to clarify: I am not developing or maintaining the Primary Sources tool, I just want to see more Freebase data being migrated :-) I think making the mapping more complete is clearly necessary and valuable, but maybe

Re: [Wikidata] Duplicate identifiers (redirects & non-redirects)

On 01.10.2015 00:58, Ricordisamoa wrote: I think Tom is referring to external identifiers such as MusicBrainz artist ID etc. and whether Wikidata items should show all of them or 'preferred' ones only as we did for VIAF redirects

Re: [Wikidata] Italian Wikipedia imports gone haywire ?

On 28.09.2015 13:31, Luca Martinelli wrote: 2015-09-28 11:16 GMT+02:00 Markus Krötzsch <mar...@semantic-mediawiki.org>: If this is the case, then maybe it should just be kept as an intentionally broad property that captures what we now find in the Wikipedias. +1, the more

Re: [Wikidata] Italian Wikipedia imports gone haywire ?

Hi, Important discussion (but please don't get angry over such things -- some emails sounded a bit rough to my taste if I may say so :-). Property definitions are an important issue, and ours are too vague in general. However, some properties need to be quite broad to be useful: they need

Re: [Wikidata] next Wikidata office hour

On 24.09.2015 23:48, James Heald wrote: Has anybody actually done an assessment on Freebase and its reliability? Is it *really* too unreliable to import wholesale? From experience with the Primary Sources tool proposals, the quality is mixed. Some things it proposes are really very valuable,

Re: [Wikidata] Wikidata Analyst, a tool to comprehensively analyze quality of Wikidata

Hi Amir, Very nice, thanks! I like the general approach of having a stand-alone tool for analysing the data, and maybe pointing you to issues. Like a dashboard for Wikidata editors. What backend technology are you using to produce these results? Is this live data or dumped data? One could

Re: [Wikidata] Preferred rank -- choices for infoboxes, versus SPARQL

On 28.11.2015 16:51, Federico Leva (Nemo) wrote: Gerard Meijssen, 28/11/2015 07:05: A big city is what? A city with more than a given number of inhabitants? If so it is redundant because it can be inferred. Criteria might be defined by local law and/or require some administrative act. That's

Re: [Wikidata] [Wikimedia-l] Quality issues

On 08.12.2015 00:02, Andreas Kolbe wrote: Hi Markus, ... Apologies for the late reply. While you indicated that you had crossposted this reply to Wikimedia-l, it didn't turn up in my inbox. I only saw it today, after Atlasowa pointed it out on the Signpost op-ed's talk page.[1] Yes, we

Re: [Wikidata] [Wikimedia-l] Quality issues

P.S. Meanwhile, your efforts in other channels are already leading some people to vandalise Wikidata just to make a point [1]. Markus [1] http://forums.theregister.co.uk/forum/1/2015/12/08/wikidata_special_report/ On 09.12.2015 11:32, Markus Krötzsch wrote: On 08.12.2015 00:02, Andreas

Re: [Wikidata] REST API for Wikidata

On 02.12.2015 23:17, Martynas Jusevičius wrote: JSON-LD does add complexity over plain JSON -- because it also can be interpreted as RDF. And that makes all the difference. The importance of this distinction cannot be overstated. If one views some custom JSON and JSON-LD (and by extension, RDF)

Re: [Wikidata] Query Service Examples

Thanks, nice. Two comments: * Activating the tag cloud in the UI was not very intuitive to me. I thought this was the search button or something. * The tag cloud pop-up is half off-screen for me, and I cannot move it to be fully visible (Firefox, Linux). Cheers, Markus On 10.12.2015 17:12,

Re: [Wikidata] Miga Classes and Properties Browser

Hi, Something to be noted here is that initial loading is quite a bit slower than it used to be, since there are a lot more classes now. We are looking into options of making this faster, but this might need a full rewrite to become really fast. The good thing is that loading only has to

Re: [Wikidata] Miga Classes and Properties Browser

On 16.12.2015 11:10, Gerard Meijssen wrote: Hoi, In the WDQ database all the data on P and Q values exist. It is stable and it has proven itself over the last years as flexible and very fast. Why build another database that is specific to one goal when another database already exists that

Re: [Wikidata] Miga Classes and Properties Browser

the Web API) Thanks, Markus On 15 December 2015 at 22:54, Markus Krötzsch <mar...@semantic-mediawiki.org <mailto:mar...@semantic-mediawiki.org>> wrote: Hi, Something to be noted here is that initial loading is quite a bit slower than it used to be, since there ar

Re: [Wikidata] Odd results from wdqs

need some extra memory, but the data you get in the end should not be much bigger than the original string, or should it? Markus On Fri, Nov 27, 2015 at 2:12 PM Markus Krötzsch <mar...@semantic-mediawiki.org <mailto:mar...@semantic-mediawiki.org>> wrote: On 25.11.2015 16:05,

Re: [Wikidata] Preferred rank -- choices for infoboxes, versus SPARQL

Hi James, I would immediately agree to the following measures to alleviate your problem: (1) If some instance-of statements are historic (i.e., no longer valid), then one should make the current ones "preferred" and leave the historic ones "normal", just like for, e.g., population numbers.

Re: [Wikidata] WDQS updates have stopped

On 19.11.2015 10:40, Gerard Meijssen wrote: Hoi, Because once it is a requirement and not a recommendation, it will be impossible to reverse this. The insidious creep of more rules and requirements will make Wikidata increasingly less of a wiki. Arguably most of the edits done by bot are of a

Re: [Wikidata] [Wiki-research-l] Quality issues

On 21.11.2015 12:21, Jane Darnell wrote: +1 I think many Wikipedians are control freaks who like to think their articles are the endpoint in any internet search on their article subjects. We really need to suppress the idea that the data they have curated so painstakingly over the years is less

Re: [Wikidata] [Wiki-research-l] Quality issues

On 20.11.2015 09:18, Federico Leva (Nemo) wrote: Gerard Meijssen, 20/11/2015 08:18: At this moment there are already those at Wikidata that argue not to bother about Wikipedia quality because in their view, Wikipedians do not care about its own quality. And some wikipedians say the same of

Re: [Wikidata] Browsing concepts and entities

On 08.06.2016 13:34, Satya Gadepalli wrote: I want to look up concepts and entities by their name even if it contains typos or omissions in wiki data. Can I do this using Wikidata-Toolkit? No, there is no error-tolerant string matching function in there. If no other tool can help you,

Re: [Wikidata] SPARQL CONSTRUCT results truncated

On 12.02.2016 00:04, Stas Malyshev wrote: Hi! We basically have two choices: either we offer a limited interface that only allows for a narrow range of queries to be run at all. Or we offer a very general interface that can run arbitrary queries, but we impose limits on time and memory

Re: [Wikidata] SPARQL CONSTRUCT results truncated

Hi Joachim, I think the problem is not to answer your query in 5min or so (Wikidata Toolkit on my laptop takes 27min without a database, by simply parsing the whole data file, so any database that already has the data should be much faster). The bigger issue is that you would have to

Re: [Wikidata] SPARQL CONSTRUCT results truncated

On 12.02.2016 10:01, Osma Suominen wrote: 12.02.2016, 10:43, Markus Krötzsch wrote: Restricting queries syntactically to be "simpler" is what we did in Semantic MediaWiki (because MySQL did not support time/memory limits per query). It is a workaround, but it will not prevent lo

[Wikidata] Wikidata Toolkit 0.6.0 released

Hi all, I am happy to announce the release of Wikidata Toolkit 0.6.0 [1], the Java library for programming with Wikidata and Wikibase. The most prominent new feature of this release is improved support for writing bots (full support for maxlag and edit throttling, simpler code through

Re: [Wikidata] SPARQL CONSTRUCT results truncated

Hi Joachim, Here is a short program that solves your problem: https://github.com/Wikidata/Wikidata-Toolkit-Examples/blob/master/src/examples/DataExtractionProcessor.java It is in Java, so, you need that (and Maven) to run it, but that's the only technical challenge ;-). You can run the

Re: [Wikidata] SPARQL CONSTRUCT results truncated

On 11.02.2016 15:01, Gerard Meijssen wrote: Hoi, What I hear is that the intentions were wrong in that you did not anticipate people to get actual meaningful requests out of it. When you state "we have two choices", you imply that it is my choice as well. It is not. The answer that I am looking

Re: [Wikidata] SPARQL CONSTRUCT results truncated

Hi Joachim, Stas would be the right person to discuss service parameters and the possible setup of more servers with other parameters. He is part of the team at WMF who is in charge of the SPARQL ops. You note that "it isn’t always obvious what is right and what the limitations of a tool

Re: [Wikidata] How to reach the wikipedia abstract propert?

Hi, For the record, I have heard a similar question recently. Maybe we could actually offer the abstracts as a service or otherwise "virtual" property that is simply added to the query result at the end. With the API Finn mentions (I did not know this, thanks!), it seems that this is not so

Re: [Wikidata] upcoming deployments/features

of developers, and yet ...). Markus On Wed, Feb 3, 2016 at 12:06 PM, Markus Krötzsch <mar...@semantic-mediawiki.org <mailto:mar...@semantic-mediawiki.org>> wrote: For a consumer, the main practical questions would be: (1) What subset of LaTeX exactly do you need to suppor

Re: [Wikidata] upcoming deployments/features

EN7 Raum E-N 741 Einsteinufer 17 D-10587 Berlin Germany Tel.: +49 30 314 22784 Mobil:+49 1578 047 1397 E-Mail: schub...@tu-berlin.de Skype: Schubi87 ICQ: 200302764 Msn: mor...@schubotz.de -Ursprüngliche Nachricht- Von: Markus Krötzsch [mailto:mar...@semantic-mediawiki.org] G

Re: [Wikidata] upcoming deployments/features

On 01.02.2016 17:14, Lydia Pintscher wrote: Hey folks :) I just sat down with Katie to plan the next important feature deployments that are coming up this month. Here is the plan: * new datatype for mathematical expressions: We'll get it live on test.wikidata.org

[Wikidata] SPARQL service slow?

Hi, is it me or is the SPARQL service very slow right now? Thanks, Markus ___ Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] upcoming deployments/features

+49 30 314 22784 Mobil:+49 1578 047 1397 E-Mail: schub...@tu-berlin.de Skype: Schubi87 ICQ: 200302764 Msn: mor...@schubotz.de -Ursprüngliche Nachricht- Von: Markus Krötzsch [mailto:mar...@semantic-mediawiki.org] Gesendet: Mittwoch, 3. Februar 2016 12:06 An: Discussion list for the Wikida

Re: [Wikidata] upcoming deployments/features

On 03.02.2016 14:38, Daniel Kinzler wrote: Am 03.02.2016 um 14:31 schrieb Markus Krötzsch: Hi Moritz, I must say that this is not very reassuring. So basically what we have in this datatype now is a "LaTeX-like" markup language that is only supported by one implementation that w

Re: [Wikidata] upcoming deployments/features

le's hands. Cheers, Markus Am 03.02.2016 um 14:31 schrieb Markus Krötzsch: Hi Moritz, I must say that this is not very reassuring. So basically what we have in this datatype now is a "LaTeX-like" markup language that is only supported by one implementation that was create

Re: [Wikidata] weekly summary #194

On 02.02.2016 02:07, Michael Karpeles wrote: Well, https://angryloki.github.io/wikidata-graph-builder will change my life, this is amazing. Thank you AngryLoki and all the hundreds of layers of contributors which lead to a tool like this. Also Lydia et al, thanks for the hard work in keeping

Re: [Wikidata] from Freebase to Wikidata: the great migration

On 23.02.2016 16:30, Tom Morris wrote: ... Or the paper might be off. Addressing the flaws in the paper would require a full paper in its own right. Criticising papers is good academic practice. Doing so without factual support, however, is not. You may be right, but you should try to

Re: [Wikidata] SPARQL returns bnodes for some items

On 26.02.2016 13:32, James Heald wrote: These are used as placeholders for the meta-values "unknown value" and "no value" aren't they ? Oh, right! I had not considered it to be possible that any subclass of statement would use "unknown value". All classes could at least be subclasses of

Re: [Wikidata] Wikidata Propbrowse

On 15.02.2016 11:52, Hay (Husky) wrote: On Mon, Feb 15, 2016 at 10:56 AM, André Costa wrote: Would it be possible to set the language used to search with? Whilst I most often use English on Wikidata I'm sure a lot of people don't. Not yet. The query takes quite a

Re: [Wikidata] SPARQL CONSTRUCT results truncated

Hi Joachim, I think SERVICE queries should be working, but maybe Stas knows more about this. Even if they are disabled, this should not result in some message rather than in a NullPointerException. Looks like a bug. Markus On 16.02.2016 13:56, Neubert, Joachim wrote: Hi Markus, Great

Re: [Wikidata] SPARQL endpoint caching

On 17.02.2016 09:54, Katie Filbert wrote: ... I think it would be nice if having a graph with query on a page does not too much adversely affect the time it takes to save a page. (e.g. if running the query takes 20 seconds..., and instead reuse cached query results) And not have such usage

Re: [Wikidata] SPARQL endpoint caching

On 17.02.2016 10:34, Magnus Manske wrote: On Wed, Feb 17, 2016 at 7:16 AM Stas Malyshev > wrote: Well, again the problem is that one use case that I think absolutely needs caching - namely, exporting data to graphs, maps, etc.

[Wikidata] Undoing merges (bibliographic articles are not humans)

Hi all, What is the correct process to undo merges? There are three cases where a bibliographical article (in Wikisource) has been accidentally merged with the human the article is about: http://www.wikidata.org/entity/Q85393 http://www.wikidata.org/entity/Q312607

Re: [Wikidata] from Freebase to Wikidata: the great migration

On 21.02.2016 16:00, Gerard Meijssen wrote: Hoi, I add statements of the primary sources tool in preference to add them myself (Primary Sources takes more time). I am still of the strongest opinion that given the extremely disappointing number of added statements the Primary Sources tool is a

Re: [Wikidata] from Freebase to Wikidata: the great migration

On 18.02.2016 15:59, Lydia Pintscher wrote: Hey everyone :) Thomas, Denny, Sebastian, Thomas, and I have published a paper which was accepted for the industry track at WWW 2016. It covers the migration from Freebase to Wikidata. You can now read it here:

Re: [Wikidata] from Freebase to Wikidata: the great migration

On 21.02.2016 20:37, Tom Morris wrote: On Sun, Feb 21, 2016 at 11:41 AM, Markus Krötzsch <mar...@semantic-mediawiki.org <mailto:mar...@semantic-mediawiki.org>> wrote: On 18.02.2016 15:59, Lydia Pintscher wrote: Thomas, Denny, Sebastian, Thomas, and I have publi

Re: [Wikidata] Wikidata Propbrowse

On 14.02.2016 16:04, Hay (Husky) wrote: On Sun, Feb 14, 2016 at 3:53 PM, Jane Darnell wrote: Now I suddenly understand why we should have "properties for properties" so we can categorize these things. It would be nice to have a list of "authority control" properties and

Re: [Wikidata] Wikidata Propbrowse

Very nice. Showing the shortened property classifications under "use" is a very good idea! Markus On 14.02.2016 15:11, Jane Darnell wrote: Wow Hay, this is super useful On Sun, Feb 14, 2016 at 8:50 AM, Hay (Husky) > wrote: Awesome, thanks! :)

Re: [Wikidata] Status and ETA External ID conversion

rent usage in Wikidata. Markus On 05.03.2016 17:15, Markus Krötzsch wrote: Hi, I agree with Egon that the uniqueness requirement is rather weird. What it means is that a thing is only considered an "identifier" if it points to a database that uses a similar granularity for modelling t

[Wikidata] Status and ETA External ID conversion

Hi, I noticed that many id properties still use the string datatype (including extremely frequent ids like https://www.wikidata.org/wiki/Property:P213 and https://www.wikidata.org/wiki/Property:P227). Why is the conversion so slow, and when is it supposed to be completed? Cheers, Markus

Re: [Wikidata] Status and ETA External ID conversion

On 05.03.2016 14:45, Lydia Pintscher wrote: On Sat, Mar 5, 2016 at 1:28 PM Markus Krötzsch <mar...@semantic-mediawiki.org <mailto:mar...@semantic-mediawiki.org>> wrote: Thanks, Katie. I see that the external ID datatype does not work as planed. At least I thought the o

  1   2   3   4   >