The goal of MarcOnt bibliographic ontology is to provide a uniform bibliographic description format. It should capture concepts from existing formats such as Bibtex, Dublin Core, MARC21. As the process of development of such an ontology is complicated it should involve a community of domain experts sharing their knowlegde and experience, together building community ontology with tools such as MarcOnt Portal
We would like to invite domain experts to collaboratively develop MarcOnt ontology with tool such as MarcOnt Portal.
When talking about ontologies, classes are often identified with ob jects in the real world. Their names often reflect this approach (e.g. Person
class in Foaf ontology represents a human being). Because of that creation of list of classes in the ontology and their hierarchy seems to be straightforward.
The main problem occurs when one should build a model of particular domain of interest on mulitple models existing in this domain. This is a case when
building a bibliographic ontology. Such an ontology should be built on the base of existing metadata standards (e.g. Bibtex, DC etc.). This implies
thecomplicated process of achieving consensus on the ontology. The following crucial classes were defined within MarcOnt Ontology:
This document is a release candidate of MarcOnt Bibliographic Ontology version 2.0. An appropriate stable version documentation will be presented after review of this document.
Should you have any comments please feel free to contact authors or post them to Marcont-users mailing list
MarcOnt ontology at a glance
An alphabetical index of MarcONt terms, by class (concepts) and by property
(relationships, attributes), and instances are given below. All the terms are hyperlinked
to their detailed description for quick reference.
Classes: AccessMedium, Article, Book, Booklet, Cluster, Collection, Conference, Coverage, DemoSession, Event, Faculty, Inbook, Incollection, Inproceedings, Institute, Journal, Lab, LightingTalk, Manual, Mastersthesis, Meeting, Misc, Organization, Phdthesis, PosterSession, Presentation, Proceedings, Resource, ShortTalk, Talk, Techreport, Tutorial, University, Unpublished, Workshop,
Properties: hasAbstract, hasAddress, hasAffiliation, hasAuthor, hasBeginDate, hasContents, hasContributor, hasCoverage, hasCreator, hasDCMIType, hasDOI, hasDate, hasDescription, hasDomain, hasEdition, hasEditor, hasEndDate, hasHumanCreator, hasISBN, hasISSN, hasIdentifier, hasJournal, hasKeyword, hasMonth, hasNote, hasNumber, hasOrder, hasOrganization, hasOriginalPublicationMedium, hasPages, hasPagesFrom, hasPagesTo, hasPublisher, hasRelatedEvent, hasSchool, hasSeries, hasSource, hasSponsor, hasTagging, hasTitle, hasTopic, hasURL, hasVolume, hasYear, howPublished, isPartOf, isPeerReviewed, presentedAt,
Instances: IElectronic, IInternational, IInternet, ILocal, INational, IPrinted,
Cross-reference for MarcOnt Bibliographic Ontology classes and properties
An alphabetical index of MarcOnt terms, by class (categories or types) and by
property. All the terms are hyperlinked to their detailed description for quick reference.
Class: marcont:PosterSession
URI: http://www.marcont.org/ontology/2.0/PosterSession
Poster Session - Representation of a poster session at a given event (eg. conference).
- sub-class-of:
- marcont:Presentation
[back to top]
Property: marcont:hasContents
URI: http://www.marcont.org/ontology/2.0/hasContents
has table of contents - Used to identify table of contents (TOC)
- OWL Type:
- ObjectProperty
- Domain:
- marcont:Resource
[back to top]
Property: marcont:hasDomain
URI: http://www.marcont.org/ontology/2.0/hasDomain
has domain of interest - Describes the domain of interest appropriate for the resource.
- OWL Type:
- ObjectProperty
- Domain:
- marcont:Resource
- Range:
- skos:Concept
[back to top]
Property: marcont:hasNumber
URI: http://www.marcont.org/ontology/2.0/hasNumber
has number - The number of a journal, magazine, technical report, or of a work in a series. An issue of a journal or magazine is usually identified by its volume and number; the organization that issues a technical report usually gives it a number; and sometimes books are given numbers in a named series.
- OWL Type:
- DatatypeProperty
- Domain:
- marcont:Journal
- Range:
- xsd:int
[back to top]
Property: marcont:hasPages
URI: http://www.marcont.org/ontology/2.0/hasPages
has pages - Nu,ber of pages of the resource or chapter.
- OWL Type:
- DatatypeProperty
- Domain:
- marcont:Resource
- Range:
- xsd:int
[back to top]
Property: marcont:hasPagesFrom
URI: http://www.marcont.org/ontology/2.0/hasPagesFrom
Pages From - The starting page of the given document (article) in the collection (inproceedings)
- OWL Type:
- DatatypeProperty
- Domain:
- marcont:Article
- Range:
- xsd:int
[back to top]
Property: marcont:hasPagesTo
URI: http://www.marcont.org/ontology/2.0/hasPagesTo
Pages To - The starting page of the given document (article) in the collection (inproceedings)
- OWL Type:
- DatatypeProperty
- Domain:
- marcont:Article
- Range:
- xsd:int
[back to top]
Property: marcont:hasSeries
URI: http://www.marcont.org/ontology/2.0/hasSeries
has series - The name of a series or set of books. When citing an entire book, the the title field gives its title and an optional series field gives the name of a series or multi-volume set in which the book is published.
- OWL Type:
- DatatypeProperty
- Domain:
- marcont:Resource
[back to top]
This work is licensed under a Creative Commons
License. This copyright applies to the MarcOnt Ontology Specification
and accompanying documentation and does not apply to JeromeDL data formats,
ontology terms, or technology.
