I think an abstract type should be fairly simple. The primary properties are:
1. A name or title (the same as the article being abstracted).
2. One to two paragraphs for text.
Of course, we also need to be able to move back and forth between the abstract and the article that it is abstracting.
The abstract structure from DocBook is probably the best example to use for properties in an abstract. That structure is documented at http://www.docbook.org/tdg/en/html/abstract.html.
Some more descriptive information about what abstracts should be is at:
http://www.rpi.edu/web/writingcenter/abstracts.html
http://leo.stcloudstate.edu/bizwrite/abstracts.html
Let me know if you have any additional questions.
Abstract Content
-
-
-
That looks pretty straightforward. The big question is, what type should it connect to? "Published Work" is the most general type for publishing, but since it includes books (of any type), stories, poems, essays, etc., as well as articles and non-fiction books, it seems a bit odd to put it there. On the other hand, I'm reluctant to add another type called "abstracted publication" (or something) that could be added as a co-type to any work that needed to have an abstract attached. Any thoughts?
-
I'm trying to think through how these various types are related to each other.
My thinking is that there is an Article type (perhaps your Published Work type). An article would be a type related to Periodical/Magazine, and an Abstract would be part of an Article. The relationships would be something like:
Magazine > Article > Abstract
Of course, there would be other types included within these.
There clearly needs to be a linkage back and forth between these various types so that a user is able move from magazine to abstract to article. Unfortunately, I'm not familiar enough with Freebase to say how this should be implemented.
-
