<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
It sounds to me like you are suggesting that there should be some sort
of confirmation in the GUI. So for your example, when you add 94025 as
the founder of the NPR radio station it would prompt you and ask if you
wanted to add the Founder type to 94025. I think this would be a good
idea. Not only would it help prevent the types of mistakes that you've
experienced but it would also encourage people to add new types to
existing topics.<br>
<br>
Shawn<br>
<br>
Arthur van Hoff wrote:
<blockquote
cite="mid:A6F816F1BC86CC46A10618006196729602F09508@zsi-sbs01.ZSI.local"
type="cite">
<pre wrap="">Just for kicks I added the postal code 94025 as founder of the NPR radio
station. I don't understand why a postal code is allowed to also be a
company founder and a person. Maybe you need to explain more clearly why
this is a good thing...
My concern is that if we want the public to contribute freely to the
data base, then there needs to be a type system that is actually
enforced. Otherwise it will end up in a mess that will be very difficult
to untangle.
I would have expected that adding a new type to a topic would require an
explicit action, one that is only allowed in certain cases. But instead
it appears that it is an implicit (and often undesired) side effect of
accidentally selecting the wrong item from a list when editing an
unrelated type.
By the way, undoing this is much harder than it would first appear. If
you do it in the wrong order you end up with a property pointing to an
object of the wrong type, which appears in the database, but not in the
UI. This will break my application, which expects the property to only
refer to objects of the correct type.
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:developers-bounces@freebase.com">developers-bounces@freebase.com</a>
[<a class="moz-txt-link-freetext" href="mailto:developers-bounces@freebase.com">mailto:developers-bounces@freebase.com</a>] On Behalf Of Kirrily Robert
Sent: Saturday, December 01, 2007 11:37 PM
To: For discussions about MQL,Freebase API and apps built on Freebase
Subject: Re: [Developers] type checking?
On Dec 2, 2007 12:03 PM, Arthur van Hoff <a class="moz-txt-link-rfc2396E" href="mailto:AVH@zing.net"><AVH@zing.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">When adding a genre to an podcast I accidentally picked National
</pre>
</blockquote>
<pre wrap=""><!---->Public
</pre>
<blockquote type="cite">
<pre wrap="">Radio from the popup list. The expected type for the was
/user/cotton/default_domain/broadcast_genre, and NPR was not of that
</pre>
</blockquote>
<pre wrap=""><!---->type.
</pre>
<blockquote type="cite">
<pre wrap="">Why does the site allow me to pick a topics that is not of the correct
</pre>
</blockquote>
<pre wrap=""><!---->type?
</pre>
<blockquote type="cite">
<pre wrap="">Can't it restrict the list to just the valid type for that property?
</pre>
</blockquote>
<pre wrap=""><!---->
As they say in the classics: "That's a feature, not a bug!"
John's described the reasoning behind it, but I'll just add that if
you want to revert your mistake properly, you have to do it in two
places:
1) remove the genre from the list on the podcast's page
2) remove the type "podcast genre" from the NPR page
Annoying I know, but the ability to add types to topics really is one
of freebase's strongest features!
K.
</pre>
</blockquote>
<br>
</body>
</html>