...
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.
...