<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16705" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=312511617-03092008><FONT face=Arial
color=#0000ff size=2>Thanks for the pointer; I hadn't looked at this one before.
There are roughly a zillion different ontologies out there for modeling
bibliographic data, and rather than trying to base a model off of one of them, I
think the goal is to make Freebase's model compatible with as many of them
as possible. (This is broadly true for all schemas in Freebase, not just
publishing.) At a glance, it looks like the NLM's model is broadly
compatible, with the understanding that there are a bunch of things they capture
that don't apply to Freebase (like markup for article content). The major issues
I see are that they have "issue title" and "volume title" tags. I'm in the midst
of proposing that we do away with the "journal issue" type entirely, which would
lose that distinction, and we don't model volumes at all, except as a plain-text
property. But we could also decide to simply omit this data in imports as
well.</FONT></SPAN></DIV>
<DIV><SPAN class=312511617-03092008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=312511617-03092008><FONT face=Arial color=#0000ff
size=2>Jeff</FONT></SPAN></DIV>
<DIV dir=ltr align=left><BR></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> data-modeling-bounces@freebase.com
[mailto:data-modeling-bounces@freebase.com] <B>On Behalf Of </B>Mohammad
Al-Ubaydli<BR><B>Sent:</B> Wednesday, September 03, 2008 2:07 AM<BR><B>To:</B>
Freebase data modeling mailing list<BR><B>Subject:</B> Re: [Data-modeling]
Possible revision to the way journal articlesare modeled<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr>Hi Jeff,<BR>my apologies that I am new and so have not seen your
previous discussion thread but I just wanted to make sure that you had already
seen and considered the National Library of Medicine's journal archiving DTD.
This website has very good documentation about the tags and
hierarchy:<BR><BR><A
href="http://dtd.nlm.nih.gov/archiving/tag-library/2.3/index.html">http://dtd.nlm.nih.gov/archiving/tag-library/2.3/index.html</A><BR><BR>The
DTD has been adopted by most major publishing houses for use across all their
Science, Technology and Medicine journals. I would recommend using it as the
standard on which to model, except where data entry presents a difficulty,
because it would allow mass imports from PubMed and from journals much more
easily in the future.<BR><BR>(I used to work at NLM so would be happy to
answer more questions if you wanted to pursue this
further.)<BR><BR>Best,<BR>mohammad<BR><BR>Mohammad Al-Ubaydli, MD<BR>e <A
href="mailto:me@mo.md">me@mo.md</A><BR>w <A
href="http://www.mo.md">www.mo.md</A><BR><BR>
<DIV class=gmail_quote>On Wed, Sep 3, 2008 at 1:13 AM, Jeff Prucher <SPAN
dir=ltr><<A href="mailto:jeff@metaweb.com">jeff@metaweb.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">I'm
reposting this because I've gotten some feedback at the
related<BR>discussion thread (<url:<BR><A
href="http://www.freebase.com/discuss/threads/book#/guid/9202a8c04000641f8000000008cdbc2f"
target=_blank>http://www.freebase.com/discuss/threads/book#/guid/9202a8c04000641f800000000<BR>8cdbc2f</A>>)
and I'd like to see if anyone else has other thoughts before we<BR>make a
decision on this.<BR><BR>Original message:<BR><BR>Spurred on by an aside
that spatialed made in some discussion post awhile<BR>back (I can't locate
the post), I'm considering revising the way that we<BR>model journal issues.
Currently, each issue has its own topic, which links<BR>to both the
journal and the articles contained in that issue. (See<BR><A
href="http://www.freebase.com/type/schema/book/journal_issue"
target=_blank>http://www.freebase.com/type/schema/book/journal_issue</A>)
The main problems<BR>with this format are that it is cumbersome to
enter data, and also that most<BR>bibliographic sources are concerned
primarily with the article and the<BR>journal, relegating the issue to a
series of strings (volume, issue, date).<BR>This latter issue might make
integration with standard bibliographic schemas<BR>a bit cumbersome,
although it wouldn't be insurmountable.<BR><BR>As an experiment, though, I
thought I'd try to see what a model that<BR>eliminated the issue entirely
looked like. Here are the results (this links<BR>to the filter view of
the new CVT):<BR><A
href="https://sandbox.freebase.com/type/view/book/journal_publication"
target=_blank>https://sandbox.freebase.com/type/view/book/journal_publication</A>.<BR><BR>I've
replaced the issue type with a CVT that connects the article and
the<BR>journal, and includes the standard bibliographic data of Volume,
issue,<BR>date, date extra, and pages ("date extra" is something I had to
make up for<BR>journals that aren't published on a schedule that translates
into<BR>mm/dd/yyyy). Journal articles have both Scholarly Work and
Written Work as<BR>included types, although a journal article can also be a
review, editorial,<BR>letter or other type of writing.<BR><BR>The only real
disadvantage that I see to this is that constructing the<BR>contents of a
given issue will be harder -- users will have to query on a<BR>combination
of several fields (volume, issue, etc.) to find what they're<BR>looking
for.<BR><BR>I'd love to hear what people think about
this.<BR><BR>Thanks,<BR><BR>Jeff Prucher<BR>Type Librarian &
Ontologist<BR>Metaweb Technologies,
Inc.<BR><BR>_______________________________________________<BR>Data-modeling
mailing list<BR><A
href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</A><BR><A
href="http://lists.freebase.com/mailman/listinfo/data-modeling"
target=_blank>http://lists.freebase.com/mailman/listinfo/data-modeling</A><BR></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>