As someone who's entered a few ISBN's by hand through the UI, I've been confused as to whether I should enter the 10, 13 or online version of the ISBN, often because the document doesn't say which one it's presenting and requiring the member to count the number of numbers is probably too much to ask to be honest. Also, there are 3 not 2 kinds of ISBN counting the online ISBN that I've found on some documents. If the Freebase help for the property was clear that the default was ISBN-13 but the 10 or online versions were acceptable, then I would have no problem with this proposed single ISBN property. <br>
<br>-Ed<br><br><div class="gmail_quote">On Thu, Feb 12, 2009 at 6:59 PM, Brian Karlak <span dir="ltr"><<a href="mailto:zenkat@metaweb.com">zenkat@metaweb.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
On Feb 11, 2009, at 1:52 PM, Richard Newman wrote:<br>
<br>
> If you regard the ISBN as being an attribute shared by instances of<br>
> the edition, then I'd suggest having separate ISBN-10 and ISBN-13<br>
> properties, because you want to preserve the value printed on the<br>
> book. A user searching by the number on the book won't know to<br>
> translate their ISBN-10 to ISBN-13; a book with both fields printed on<br>
> the dust jacket (despite a well-documented 1-1 mapping) should perhaps<br>
> have both properties.<br>
<br>
</div>We had discussed implementing both ISBN-10 and ISBN-13 links. Beyond<br>
the extra space requirements needed to store equivalent information<br>
(which is significant when you consider the number of editions in<br>
freebase), my personal feeling is that dual properties will make the<br>
schema more complicated to use. Applications will now have to search<br>
two fields instead of one. Users entering data would need to make<br>
sure they used the proper field.<br>
<br>
Since the code to do ISBN-10 to ISBN-13 conversion (and vice-versa) is<br>
relatively straightforward, doesn't it make more sense to have a<br>
single standardized field that we can rely on? For instance, it I<br>
could a very simple ACRE app that would do the necessary conversion to<br>
do the proper freebase lookup.<br>
<font color="#888888"><br>
Brian<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Developers mailing list<br>
<a href="mailto:Developers@freebase.com">Developers@freebase.com</a><br>
<a href="http://lists.freebase.com/mailman/listinfo/developers" target="_blank">http://lists.freebase.com/mailman/listinfo/developers</a><br>
</div></div></blockquote></div><br>