Libraries find form in all languages and countries, but WUaS's plans to move to
Wikidata will make this a database. MIT-centric WUaS students will eventually
add to, and develop, these libraries greatly I suspect.
Best regards, Scott
On Tue, Jul 9, 2013 at 10:19 AM, Michael Hale
at 9:08 PM, Michael Hale hale.michael...@live.com wrote:
I've had some discussions with people on the Mathematica Stack Exchange site
about the project. There is interest, but most people don't seem to have as
much free time as me. So I've decided just to start the project as a way to
organize
this a database. MIT-centric WUaS students will eventually
add to, and develop, these libraries greatly I suspect.
Best regards, Scott
On Tue, Jul 9, 2013 at 10:19 AM, Michael Hale hale.michael...@live.com wrote:
I completely agree that wiki-projects are exemplary organic growth models
!
Jane
2013/7/9, Michael Hale hale.michael...@live.com:
Well, you would run into many of the same decisions we already face about
how much to limit automated uploads of data if you wanted to turn it into a
live programming platform. You can certainly already use DBpedia and
Wikidata to get
, 8 Jul 2013 16:10:20 -0400
From: Michael Hale hale.michael...@live.com
To: Discussion list for the Wikidata project.
wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Accelerating software innovation with
Wikidata and improved Wikicode
Message-ID: bay173
.
But then I never felt the need for high-fidelity simulations of
virtual worlds either.
2013/7/6, Michael Hale hale.michael...@live.com:
I have been pondering this for some time, and I would like some feedback. I
figure there are many programmers on this list, but I think others might
find
On Mon, Jul 8, 2013 at 10:13 PM, Michael Hale hale.michael...@live.com
wrote:
There are lots of code snippets scattered around the internet, but most of
them can't be wired together in a simple flowchart manner. If you look at
object libraries that are designed specifically for that purpose
/blog/2012/04/the-downfall-of-imperative-programming
With PHP and JavaScript being the most widespread (and still misused)
languages we will not get there soon, however.
On Mon, Jul 8, 2013 at 10:57 PM, Michael Hale hale.michael...@live.com
wrote:
In the functional programming language family
I have been pondering this for some time, and I would like some feedback. I
figure there are many programmers on this list, but I think others might find
it interesting as well.
Are you satisfied with our progress in increasing software sophistication as
compared to, say, increasing the size of
and the success of the supporting
technologies.
Micru
On Sat, Jul 6, 2013 at 3:10 PM, Michael Hale hale.michael...@live.com wrote:
I have been pondering this for some time, and I would like some feedback. I
figure there are many programmers on this list, but I think others might find
If you are going to use a computer to automatically generate new facts using an
ontology then you have to do fairly sophisticated filtering of the results. If
you start with just a few axioms for logic and Euclidean geometry you could
have a computer automatically prove new theorems using them
I spoke too soon. That is the only loop at two steps. But if you go out three
steps (25000 categories) you find another 23 loops. Organizational studies -
organizations, housing - household behavior and family economics - home -
housing, religious pluralism - religious persecution, secularism -
I agree they are extremely useful for many scenarios already. Earlier today I
sorted the human proteins category by popularity, and by reading the articles
for the most popular ones that I didn't know I felt like I was browsing the
table of contents of a live molecular biology book that was
, Michael Hale hale.michael...@live.com wrote:
I agree they are extremely useful for many scenarios already. Earlier today
I sorted the human proteins category by popularity, and by reading the
articles for the most popular ones that I didn't know I felt like I was
browsing the table of contents
From:
wikidata-l-boun...@lists.wikimedia.org
[mailto:wikidata-l-boun...@lists.wikimedia.org] On Behalf Of Michael
Hale
Sent: Saturday, May 04, 2013 2:57 AM
To: Discussion list for the Wikidata project.
Subject: Re: [Wikidata-l] Question about wikipedia categories.
I
think it's
to be
inaccurate and naive. So I do hope others with more experience will
come and help sort it out.
Chris
On Sun, May 5, 2013 at 11:06 AM, Michael Hale hale.michael...@live.com wrote:
As far as checking the import progress of Wikidata, the category American
women writers has 1479 articles. 651
I think it's important to consider the distinction between a category system
and semantic queries. I think it's very likely that DBpedia and Wikidata will
converge over time and develop a simple enough query interface that causes
fewer people to use the category system because we will be able
://www.wikidata.org/wiki/Wikidata:Property_proposal/Pending then???
2013/3/29 Michael Hale hale.michael...@live.com
It would be nice to never have to do any additional validation on the client,
but in general I'm pretty sure it's impossible to specify server validation for
every type in advance. Let's
for number of floors,
but for plenty of other applications.
On Mon, Apr 22, 2013 at 11:21 AM, Michael Hale hale.michael...@live.com wrote:
Well, there is a trade-off. If we have too few types then it is harder for
clients to use the data and inconsistencies might slip in. But if we delay
? Other than passing arguments to {{GNF_ProteinBox}} in the wiki gene
article. This would increase the length of each wiki gene article.
Thanks in advance,
Chinmay
On Wed, Apr 17, 2013 at 12:48 AM, Michael Hale hale.michael...@live.com wrote:
If you are saying that the parser functions
increase the length of each wiki gene article.
Thanks in advance,
Chinmay
On Wed, Apr 17, 2013 at 12:48 AM, Michael Hale hale.michael...@live.com wrote:
If you are saying that the parser functions ({{#property:...}}) aren't being
evaluated after the template is transcluded then I guess
}}
2) {{GNF_proteinBox| specify property syntax here}}
case 2 is supported. what about case 1??
On Wed, Apr 17, 2013 at 11:57 AM, Michael Hale hale.michael...@live.com wrote:
Yes, it seems to be working. I did a preview of deleting the flag parameter on
the Italian article for Turin
Hey, that's a great project. The current situation with ProteinBoxBot is not
ideal. We don't want to create a separate template for every protein. I suppose
they do that now to make the articles slightly shorter, but Wikidata will allow
us to accomplish the same thing without the confusing
If you are saying that the parser functions ({{#property:...}}) aren't being
evaluated after the template is transcluded then I guess the feature isn't
fully implemented yet.
From: hale.michael...@live.com
To: wikidata-l@lists.wikimedia.org
Date: Tue, 16 Apr 2013 15:11:35 -0400
Subject: Re:
by popularity
How do you run the source code?
I know this is a silly question, but I have no programming background or
perhaps my knowledge is rather elementary.
Cheers,
From: Michael Hale hale.michael...@live.com
To: Discussion list for the Wikidata project. wikidata-l@lists.wikimedia.org
Sent
] Browsing Wikipedia categories by popularity
How do you run the source code?
I know this is a silly question, but I have no programming background or
perhaps my knowledge is rather elementary.
Cheers,
From: Michael Hale hale.michael...@live.com
To: Discussion list for the Wikidata project
-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Browsing Wikipedia categories by popularity
On 13.04.2013 01:56, Michael Hale wrote:
Thank you. Yeah, Mathematica doesn't seem to be very popular. They
have a very large, well-designed function library, so you can get
things done very quickly
, Michael Hale hale.michael...@live.com:
I made a quick demo of browsing Wikipedia categories by popularity.
The video is here (sorry about the audio quality):
http://www.youtube.com/watch?v=f3QXwY-XR28The source code is here:
http://en.wikipedia.org/wiki/User:Wakebrdkid
I made a quick demo of browsing Wikipedia categories by popularity.
The video is here (sorry about the audio quality):
http://www.youtube.com/watch?v=f3QXwY-XR28The source code is here:
http://en.wikipedia.org/wiki/User:Wakebrdkid/Popular_category_browsing
If other people like having an option
: Nicolas Maduro is now being
pulled from Wikidata.
Date: Wed, 10 Apr 2013 08:46:41 +0200
From: psychosl...@culture-libre.org
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Page history and properties
Le 2013-04-09 20:44, Michael Hale a écrit :
Venezuela is electing a new
Venezuela is electing a new president in about a week. I went ahead and
switched the Italian article to use the Wikidata property so we might be able
to capture a good example there.
Date: Mon, 8 Apr 2013 16:24:49 +0200
From: psychosl...@culture-libre.org
To: wikidata-l@lists.wikimedia.org;
and properties
Le 2013-04-05 23:19, Michael Hale a écrit :
I'm not saying it is easy to use #property to refer to a particular
article revision. I'm saying it is impossible and should stay that
way.
As far I understand, I totaly disagree. We have to provide a way to
obtain the page
No, it is not an example of a solution. If you wrote a property inclusion like
that, and then someone changed the value on Wikidata, and then someone made an
arbitrary edit somewhere else in the article, then when they save the page
again the parameter that you have provided makes no sense. We
The thing to remember is that the history of a page is the history of the wiki
markup for the page, not the history of the rendered HTML. It would be
misleading if edits were shown in the markup history for an article each time a
template or Wikidata item changed because reverting the markup to
Oh, nice.
From: lydia.pintsc...@wikimedia.de
Date: Fri, 5 Apr 2013 20:07:44 +0200
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Page history and properties
On Fri, Apr 5, 2013 at 8:05 PM, Michael Hale hale.michael...@live.com wrote:
The thing to remember
20:05, Michael Hale hale.michael...@live.com wrote:
The thing to remember is that the history of a page is the history of the
wiki markup for the page, not the history of the rendered HTML. It would be
misleading if edits were shown in the markup history for an article each
time a template
is that not enough people are asking for that feature to warrant giving it a
high priority.
From: g.m.haged...@gmail.com
Date: Fri, 5 Apr 2013 22:22:06 +0200
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Page history and properties
On 5 April 2013 21:41, Michael Hale
and properties
On 5 April 2013 23:19, Michael Hale hale.michael...@live.com wrote:
So you agree that it is more important to reduce clutter than to add
functionality that very few people use?
No, I strongly disagree with this. I think the functionality of being
able to curate the page
Are you saying every property should have a valid_from and valid_to date or
every claim? If you want that information for queries to be able to show
information about deprecated properties then I don't understand the example
because both queries use the same properties. If it is for claims,
I thought one of the main reasons we are making Wikidata is so that you can
update a value there, and then everywhere it is used will be automatically
updated. If we find a more precise measurement for the depth of an ocean
trench, then I just want to update it on Wikidata, and then every
history and properties
I don't think, that the most claims are
immutable.
Am Fr 05.04.2013 00:30, schrieb Michael Hale:
We will use qualifiers to tag values with dates for
which they are relevant if there isn't a better place
, Michael Hale hale.michael...@live.com wrote:
Oh, I thought bot approval was just for tasks that have an indefinite running
time like cleaning vandalism, etc. I added a user-agent string to identify my
IP address, but I hadn't run into problems on Wikipedia without one before. Am
I supposed
On Tue, Apr 2, 2013 at 12:58 AM, Michael Hale hale.michael...@live.com
wrote:
I've been practicing using the Wikidata and MediaWiki APIs today. Even
though the Wikidata API is still being developed, using it was more pleasant
than parsing the templates. The good news is I'll probably
/User:Wakebrdkid%27s_bot/code
Date: Tue, 2 Apr 2013 05:10:22 -0400
From: e...@pobox.com
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Running Infobox film import script
Hi Michael,
Is the code for your bot publicly available somewhere?
//Ed
On Tue, Apr 2, 2013 at 12:58 AM, Michael
Well you can still view the revision history of an item on Wikidata, as you'd
expect. I view the information as being more tied to a specific reference than
to a specific revision of the item. I don't think the notion of orphaned data
is as big of a deal in a database as it is in an
Subject: Re: [Wikidata-l] Running Infobox film import script
On Tue, Apr 2, 2013 at 12:58 AM, Michael Hale hale.michael...@live.com wrote:
It will definitely have some errors, but I scanned the results for the first
100 movies before I started importing them, and I think the value-add
I can't reproduce the error here (using Chrome too). Anyone else?
Date: Tue, 2 Apr 2013 14:44:24 -0400
From: e...@pobox.com
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Running Infobox film import script
On Tue, Apr 2, 2013 at 5:25 AM, Michael Hale hale.michael...@live.com
with
though).
Tom
On Tue, Apr 2, 2013 at 2:44 PM, Ed Summers e...@pobox.com wrote:
On Tue, Apr 2, 2013 at 5:25 AM, Michael Hale hale.michael...@live.com wrote:
http://www.wikidata.org/wiki/User:Wakebrdkid%27s_bot/code
I got a 400 when fetching this (in Chrome).
//Ed
for templates
2013/4/1 Michael Hale hale.michael...@live.com
In the next update you will just be able to write {{#property:film director}}
instead of {{#property:p57}}.And translated versions, too?
--
Bináris
___
Wikidata-l mailing list
Wikidata-l
=
{{{#property_name:p57}}}| data1= {{{#property:p57}}}
Date: Mon, 1 Apr 2013 07:34:44 +0200
From: wikipo...@gmail.com
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] A question about wikidata for templates
2013/4/1 Michael Hale hale.michael...@live.com
In the next
/you-can-have-all-the-data/
Date: Mon, 1 Apr 2013 15:04:53 +0800
From: zhjy...@gmail.com
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] A question about wikidata for templates
I think that I haven't got it completely:
On Mon, Apr 1, 2013 at 11:15 AM, Michael Hale hale.michael
Although you can create a new item that doesn't correspond to an article here:
http://www.wikidata.org/wiki/Special:NewItem
I'm going to practice some with the Wikidata API later today by trying to
import all of the Infobox film data. Then when we update the template after the
inclusion syntax
I've been practicing using the Wikidata and MediaWiki APIs today. Even though
the Wikidata API is still being developed, using it was more pleasant than
parsing the templates. The good news is I'll probably be able to reuse a lot of
that code for other infoboxes that still need to be imported.
Here's the contributions from my IP address if you want to monitor it:
http://www.wikidata.org/wiki/Special:Contributions/108.235.225.145
From: hale.michael...@live.com
To: wikidata-l@lists.wikimedia.org
Date: Tue, 2 Apr 2013 00:58:05 -0400
Subject: [Wikidata-l] Running Infobox film import
coders to get
approval before they can run their scripts (see
https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Bot).
Your script did look pretty cool though :)
-- Legoktm
http://enwp.org/d:User:Legoktm
On Tue, Apr 2, 2013 at 12:01 AM, Michael Hale hale.michael...@live.com
The basic idea is to update templates like Infobox film to prefer to pull data
from Wikidata. So for a film article whose corresponding item on Wikidata is
fairly complete you can just put {{Infobox film}} at the top of the article and
everything will work as expected. They can click the link
It doesn't hinder the expansion of Wikidata because the current types are
flexible. Added types will improve performance and simplify client access for
some scenarios, but every scenario I can think of is possible with the
currently available types. If you have data that you would like to
: [Wikidata-l] phase 2 live on the first 11 Wikipedias
parse it into a date on the client-side.
this is exactly why I do not want to do. we should validate inputs, not (try
to) parse outputs
2013/3/29 Michael Hale hale.michael...@live.com
It doesn't hinder the expansion of Wikidata because
I didn't know about the VisualEditor initiative, but I use the wikEd gadget
that you can enable under your preferences for the English Wikipedia. It makes
links to images clickable while editing, among other things. If we could get a
similar experience to link to a Wikidata item that could be a
I wrote on the wikEd developer's talk page and said I could help out if needed.
http://en.wikipedia.org/wiki/User_talk:Cacycle/wikEd#Inline_links_to_Wikidata_itemsThat
still wouldn't help first time editors that come across the syntax
unexpectedly though. We should make sure it is described on
Oops. As of yesterday a template does exist.
http://en.wikipedia.org/wiki/Template:Wikidata
From: hale.michael...@live.com
To: wikidata-l@lists.wikimedia.org
Date: Fri, 29 Mar 2013 15:49:11 -0400
Subject: Re: [Wikidata-l] The experience for (local project) editors,
post-Phase 2
We'll
be
used in other context, e.g. a sentence. A good example could be
The children of Charles Dickens - Q were younger
than
On 03/27/2013 04:53 PM, Michael Hale wrote:
Regarding the construction phases complex type
You can't integrate the XSD model precisely as it is defined because Wikidata
doesn't allow all of the constraints that XSD allows. Specifically, you'll
notice that you can't force an item to have a specific property (like the
document or epigraphic reference in your model) and enumerations
Date: Thu, 21 Mar 2013 17:34:05 +
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Expiration date for data
On 21 March 2013 15:39, Michael Hale hale.michael...@live.com wrote:
Great post. Regarding the suggestions feature, it seems the easiest way to
get that rolling would
in an item's revision history. The sooner we introduce basic support
for qualifiers, the sooner we can avoid removing valuable information from
wikidata entries just for the sake of keeping them up-to-date.
Dario
On Mar 15, 2013, at 10:09 AM, Michael Hale hale.michael...@live.com wrote:For
most
, the sooner we can avoid removing valuable information from
wikidata entries just for the sake of keeping them up-to-date.
Dario
On Mar 15, 2013, at 10:09 AM, Michael Hale hale.michael...@live.com wrote:
For most of the scenarios I can think of, parsing the dates out of strings that
are in a standard
basic support
for qualifiers, the sooner we can avoid removing valuable information from
wikidata entries just for the sake of keeping them up-to-date.
Dario
On Mar 15, 2013, at 10:09 AM, Michael Hale hale.michael...@live.com wrote:
For most of the scenarios I can think of, parsing the dates
of usage of every property. See also here:
http://blog.wikimedia.de/2013/02/22/restricting-the-world/
Cheers,denny
2013/3/21 Michael Hale hale.michael...@live.com
Yes, I just meant that items aren't forced to have a specific set of properties
by the software, so they are essentially weakly
I think you want it to be Popular print. I changed it for
you.http://www.wikidata.org/wiki/Q1306119http://en.wikipedia.org/wiki/Popular_print
From: rupert.thur...@gmail.com
Date: Fri, 15 Mar 2013 06:29:24 +0100
To: wikidata-l@lists.wikimedia.org
Subject: [Wikidata-l] is there a schema for
is a (P31), which can have any value.
c) To get collection (museum) as an option you'd need to create a
Wikidata entry for that - there hadn't been one made yet. It's now
created: http://www.wikidata.org/wiki/Q7328910
- Andrew.
On 15 March 2013 06:01, Michael Hale hale.michael...@live.com
for that - there hadn't been one made yet. It's now
created: http://www.wikidata.org/wiki/Q7328910
- Andrew.
On 15 March 2013 06:01, Michael Hale hale.michael...@live.com wrote:
I think you want it to be Popular print. I changed it for you.
http://www.wikidata.org/wiki/Q1306119
http://en.wikipedia.org/wiki
So is the question whether there should be strong types for qualifiers as
opposed to just a string with custom logic for each type of template box that
will be displayed in articles? My opinion is that it is too difficult to know
in advance how many and what types of qualifiers the data will
A topic I've been involved in recently regards statistics for gun violence in
the US. The government publishes a big report every year, but it takes them
most of the year to collect the information from all of the local police
agencies and compile the results. Several English Wikipedia articles
Yes, I think once qualifiers are enabled you would just have something
like:...Property(head of local government)...Value(Elizabeth I) -
Qualifier(1558-1603) - Sources()Value(James VI and I) -
Qualifier(1603-1625) - Sources()..
There was a discussion about whether
I think of Wikidata as the symbiotic version of Freebase. I won't say Freebase
is a parasite, but I think a core aspect of Wikidata is that edits to the
database will often feed back into the encyclopedia in various places. I
haven't looked too much at the technical implementation of Wikidata
Sorting by the number of articles in that language's Wikipedia might be a nice
option. The articles in the more popular Wikipedia's might be more likely to be
closer to featured status. I pursued a similar thing for categories. I have a
script that sorts the articles in a category by their
Hi Joan,
It seems that historical event is on the proposed property list:
http://www.wikidata.org/wiki/Wikidata:Property_proposal#Historical_Event_.2F_Historisches_Ereignis_.2FIt
has been more than three days, so my understanding is that it can be
officially created now so people can start
Q: entityP: propertyU: query
Date: Wed, 6 Mar 2013 15:58:47 +0100
From: denny.vrande...@wikimedia.de
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] One entity per page question
Y, IIRC
2013/3/6 Yuri Astrakhan yuriastrak...@gmail.com
Thank you! So its a 1-1 relationship. Someone
78 matches
Mail list logo
