Child pages
  • info-eu-repo

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 33

...

Namespace

 

Type

 

Term

 

Description

 

Used by project

info:eu-repo

/

classification

/

ddc

 

Dewey Decimal Classification (DDC)
http://www.oclc.org/dewey/

 

 

info:eu-repo

/

classification

/

udc

 

Universal Decimal Classification
http://www.udcc.org/http://www.udcc.org/

 

 

info:eu-repo

/

classification

/

lcc

 

Library of Congress Classification
http://www.loc.gov/catdir/cpso/lcco/http://www.loc.gov/catdir/cpso/lcco/

 

 

info:eu-repo

/

classification

/

lcsh

 

Library of Congress Subject Headings (LCSH)

 

 

info:eu-repo

/

classification

/

swd

 

Schlagwortnormdatei (SWD)

 

 

info:eu-repo

/

classification

/

bicssc

 

Book Industry Communication - Standard Subject Categories
http://www.bic.org.uk/7/BIC-Standard-Subject-Categories/

 

Open Access Publishing in European Networks (OAPEN)
http://www.oapen.org/

Anchor
publicationtypes
publicationtypes

...

conferenceObject of Driver includes all other conference-related publications. This can be used if none of the more specific publicationtypes comply.
Within conferenceObject are two types: conferenceProceedings as proposed by NEOO and ConferenceItem from the vocabulary of UKOLN. The type conferenceProceedings is used for authors who want to include the conference proceedings of which they are the editor. It is helpful if conference proceedings are contained in the repositories as compound objects. ConferenceItem is not really necessary, because there are more specific types who cover all sorts of ConferenceItems: ConferencePaper and conferenceContribution. The distinction between these two subtypes is the whether or not it's included in conference proceedings.
conferenceContribution has a subtype: conferencePoster. Not published readings for a conference are a conferenceObject, a ConferenceItem and a ConferenceContribution.
The class-subclass relations can be represented with the following hierarchy.

Code Block
 conferenceObject
    conferenceProceedings
    ConferenceItem
        conferencePaper = ConferenceItem in conferenceProceedings
        conferenceContribution = ConferenceItem not in conferenceProceedings
            conferencePoster

The term conferenceContribution is confusing. A more clear term is concerenteItemNotInProceedings. The proposal is to adopt conferenceObject, conferenceProceedings, conferencePaper, conferenceItemNotInProceedings, conferenceContribution (owl:sameAs conferenceNotInProceedings; the latter is the preferred term) and conferencePoster in the info:eu-repo/semantics namespace. If we specify in a more formal way the semantic relations, we can use ConferenceItem from the UKOLN vocabulary.

The new situation can be visualised as follows:

...

| CODE_OUTPUT | Resulttype | Publicatietype (info:eu-repo/semantics) |

10

annotatie

annotation

11

artikel in bundel - proceedings

conferencePaper

01

artikel in tijdschrift

article

02

boek / monografie

book

05

boekbespreking

bookReview

03

boekdeel - hoofdstuk

bookPart

04

boekredactie

 

20

dissertatie

doctoralThesis

70

erkenning

 

08

extern rapport

report

12

inaugurele rede

lecture

13

krantenartikel

contributionToPeriodical

30

octrooi

patent

50

overige resultaten

 

60

relevante functies

 

06

tijdschriftredactie - refereeschap

 

40

voordracht - lezing (ongepubl)

 

 

 

bachelorThesis

 

 

researchProposal

 

 

masterThesis

 

 

preprint

 

 

studenThesis

 

 

technicalDocumentation

 

 

workingPaper

 

 

conferencePoster

...