Taxonomy

In our case we deal with publications. Generalizing a bit we introduce the 'document' as a top level concept:

document          subclasses opus

From this class we derive all sub-classes which we want to allow in our literature maps:

standard          subclasses document

specification     subclasses document

article           subclasses document

book              subclasses document

journal           subclasses book

proceedings       subclasses journal

essay             subclasses article

tutorial          subclasses article

online-article    subclasses article

white-paper       subclasses document

paper             subclasses article

journal-paper     subclasses paper

conference-paper  subclasses paper

report            subclasses document

draft             subclasses document

internet-draft    subclasses draft

internet-rfc      subclasses specification

Additionally to the above we need quite a few concepts to capture authorship, publication and other document related information to be used inside topics or associations:

# authorship
is-author-of

author

# editorship
is-editor-of

editor

# affiliation
is-affiliated-with

affiliation

# publication
is-published-by

year

publisher

conference

country

# document centric information
pages
in: nr of pages

weight
in: weight in gramm

language
in: the language a document is written in

cite-code
in: the code to be used by authors as reference \
   (a reference to a reference)

abstract

comment

homepage

To connect the instances of these classes we certainly need associations. Their types (while not their structure) can be readily listed:

is-author-of

is-published-by

is-published-in

is-edited-by

is-affiliated-with

As such the taxonomy is a more or less loose collection of concepts. It is building a scaffold which serves two purposes: first the basic concepts should allow for a controlled merging, secondly structural and application specific constraint can be built for it to narrow down our application domain.