Copyright © 2004-2007 by Sebastian Ryszard Kruk with contributions from (under the Corrib.org project):
Digital Enterprise Research Institute, National University of Ireland, Galway, Ireland
Faculty of Electronics, Telecommunication and Informatics and Main Library Gdansk University of Technology, Poland
This work is licensed under a Creative Commons
License. This copyright applies to the JeromeDL Ontology Specification
and accompanying documentation and does not apply to JeromeDL data formats,
ontology terms, or technology.
The structure ontology is used at the bottom layer in JeromeDL. It is used to handle typical tasks required from a digital objects repository, that is, it keeps track of physical representation of resources, their structure and provenance. The structure ontology provides means for a flexible and extendable electronic representation of objects. Such flexibility is especially significant in expressing relations to other resources.
NOTE: This section describes the status of this document at the time of its publication. Other documents may supersede this document.
Authors welcome suggestions on the JeromeDL ontology and this document. Please send comments to the JeromeDL developers list; public archives are available. This document may be updated or added to based on implementation experience, but no commitment is made by the authors regarding future updates.
Modern digital library systems not only store bibliographic metadata but also an electronic representation of the content itself. Depending on its type, content typically follows some structure, e.g. we can decompose a book into chapters and provide individual descriptions for each chapter with information about re- lations between them. Including structural concepts in ontologies and using these concepts in metadata descriptions provides a universal layer for metadata and content retrieval. It allows to extend the structure description with new concepts, without violating the integrity of existing data. The application of ontologies for structural descriptions enables uniform access to structural and bibliographical information, and delivers new search and discovery possibilities, as described in Kruk et al.
For more information about JeromeDL, see the project website
The XML Namespace URI that MUST be used by implementations of this specification is:
An alphabetical index of JeromeDL terms, by class (categories or types) and by property. All the terms are hyperlinked to their detailed description for quick reference.
Classes: BinaryResource, Chapter, ComputedResource, Context, DynamicCollection, DynamicCollectionType, ImageResource, InformationObject, MediaPart, MediaResource, Page, Part, Resource, ResourceType, ResourcesAggregationService, SubmissionStatusType,
Properties: actsOn, hasAttachment, hasBookType, hasCollectionOrder, hasCollectionSpecification, hasContext, hasCopyrightsOwner, hasCover, hasCurrentVersion, hasDescription, hasFileSize, hasInvocationParam, hasMimeType, hasNumberOfPages, hasPages, hasPart, hasParts, hasPosition, hasPreviousVersion, hasRepresentation, hasSimplerRepresentation, hasSpecification, hasSubmissionStatus, hasUploadDate, hasVersionComment, hasVersionCreator, hasVersionDate, hasVersionNumber, http://www.w3.org/2004/02/skos/core#narrow, invokesService, isPeerReviewed, isPreprintVersion, isPublished, isReviewed, isScaledToFit, isSizeWithSubCollections, isUnion, isUploadedBy, isVisible,
It is important to understand that the JeromeDL ontology as specified in this document is not a standard in the sense of ISO Standardisation, or that associated with W3C Process.
JeromeDL ontology depends heavily on W3C's standards work, specifically on XML, XML Namespaces, RDF, and OWL.
This specification contributes an ontology, "JeromeDL structure ontology", to the Semantic Web, specifying it using W3C's Resource Description Framework (RDF). As such, JeromeDL adopts by reference both a syntax (using XML), a data model (RDF graphs) and a mathematically grounded definition for the rules that underpin the RDF design.
JeromeDL structure ontology introduces the following classes and properties.
URI: http://www.jeromedl.org/ontology/2.0/BinaryResource
- This is an infomration object which has a binary representation, such as JPG, PDF, etc. NOTE: metainformation extracted from the resource (e.g., EXIF) should be directly bound to this resource, not through some additional properties (e.g., hasExif), unless the ontology related to this binary resource does not support such direct binding
URI: http://www.jeromedl.org/ontology/2.0/Chapter
- Is a special type of Part information object for expressing chapter information
URI: http://www.jeromedl.org/ontology/2.0/ComputedResource
- This is a virtual information object which is computed out of other resources (dessiminator)
URI: http://www.jeromedl.org/ontology/2.0/Context
- this concept will allow to bind any kind of annotatiosn to the information object
URI: http://www.jeromedl.org/ontology/2.0/DynamicCollection
- Collection created dynamically based on provided specification
URI: http://www.jeromedl.org/ontology/2.0/DynamicCollectionType
-
URI: http://www.jeromedl.org/ontology/2.0/ImageResource
- Special type of media resource - all image resources (JPG, PNG)
URI: http://www.jeromedl.org/ontology/2.0/InformationObject
- The most abstract type of resource in the library (NOTE: this concept supersedes jdl1:Book)
URI: http://www.jeromedl.org/ontology/2.0/MediaPart
- Special type of Part - which allows to reference multimedia content
URI: http://www.jeromedl.org/ontology/2.0/MediaResource
- it is a generic binary type, the distintive feature is the its physical size and scalling ability
URI: http://www.jeromedl.org/ontology/2.0/Page
-
URI: http://www.jeromedl.org/ontology/2.0/Part
- This is a information object which is a part of another information object
URI: http://www.jeromedl.org/ontology/2.0/Resource
-
URI: http://www.jeromedl.org/ontology/2.0/ResourceType
- Types of special Information Objects - Resources (these are the most highlevel information objects presented to the user)
URI: http://www.jeromedl.org/ontology/2.0/ResourcesAggregationService
- aggregation service which can deliver a bunch of information objects in one go
URI: http://www.jeromedl.org/ontology/2.0/SubmissionStatusType
- Defines a list of individuals which cover the submission workflow status
URI: http://www.jeromedl.org/ontology/2.0/actsOn
- allows to specify number of resources that are used as a source for computing the new resource
URI: http://www.jeromedl.org/ontology/2.0/hasAttachment
- indicates the attachment of the information object
URI: http://www.jeromedl.org/ontology/2.0/hasBookType
- defines type of the book - is used to the main classification scheme in JeromeDL
URI: http://www.jeromedl.org/ontology/2.0/hasCollectionOrder
- The ordering number of the collection in the tree of collections [http://www.jeromedl.org/structure#collectionOrder]
URI: http://www.jeromedl.org/ontology/2.0/hasCollectionSpecification
- literal/string representation of the specification of the collection [http://www.jeromedl.org/structure#collectionSpecification]
URI: http://www.jeromedl.org/ontology/2.0/hasContext
- used to bind multipurpose context to an information object
URI: http://www.jeromedl.org/ontology/2.0/hasCopyrightsOwner
- indicates who own copyrights for given information object
URI: http://www.jeromedl.org/ontology/2.0/hasCover
- Defines a binary resource (an image) that represents the cover of the information object; also used as a thumbnail of media resource
URI: http://www.jeromedl.org/ontology/2.0/hasCurrentVersion
- Points to the most current version of the information object (IMPORTANT: I would suggest that either all information objects points to their current versions - even the current ones, or only the non-current ones)
URI: http://www.jeromedl.org/ontology/2.0/hasDescription
- a textual description on the information object
URI: http://www.jeromedl.org/ontology/2.0/hasFileSize
- Size of the binary file related to this resource
URI: http://www.jeromedl.org/ontology/2.0/hasInvocationParam
- Defines parameter for invocation
URI: http://www.jeromedl.org/ontology/2.0/hasMimeType
- MIME type of the binary resource
URI: http://www.jeromedl.org/ontology/2.0/hasNumberOfPages
- Some resources (antique book chapter, PDF, ...) can have information about number of pages (physical size of the resource, compare to marcont:hasNumberOfPages representing the actual size of the content of the resource)
URI: http://www.jeromedl.org/ontology/2.0/hasPages
- Indicates the logical page in the resource (it can have binary resources like PNG, JPG and computed resources [disseminators] like deJa Vu)
URI: http://www.jeromedl.org/ontology/2.0/hasPart
- An abstract property to indicate that one information object indicates another as its part
URI: http://www.jeromedl.org/ontology/2.0/hasParts
- allows to point from an information object to aggregation service - e.g., we can point from chapter to a set of pages in one go
URI: http://www.jeromedl.org/ontology/2.0/hasPosition
- used to indicate the position of the statement on the list
URI: http://www.jeromedl.org/ontology/2.0/hasPreviousVersion
- Points to the previous version (IMPORTANT: in case a version is removed, we will not be changing numbers, but we should change the linking)
URI: http://www.jeromedl.org/ontology/2.0/hasRepresentation
- allows to bind binary resource or computed resource to the part resource
URI: http://www.jeromedl.org/ontology/2.0/hasSimplerRepresentation
- smaller representation of the file
URI: http://www.jeromedl.org/ontology/2.0/hasSpecification
-
URI: http://www.jeromedl.org/ontology/2.0/hasSubmissionStatus
- Indicates the current submission status of the information object. NOTE: The submission status can refer to the submission process of an article, or to the internal submission workflow in the digital library
URI: http://www.jeromedl.org/ontology/2.0/hasUploadDate
- When the infomration object was uploaded
URI: http://www.jeromedl.org/ontology/2.0/hasVersionComment
- Comment explaining what has changes in this version
URI: http://www.jeromedl.org/ontology/2.0/hasVersionCreator
- A person who has created this version
URI: http://www.jeromedl.org/ontology/2.0/hasVersionDate
- defines date when this version of the information object was created
URI: http://www.jeromedl.org/ontology/2.0/hasVersionNumber
- indicates the unique number of the version of the information object
URI: http://www.jeromedl.org/ontology/2.0/invokesService
- indicates the REST service which should be invoked to compute the result
URI: http://www.jeromedl.org/ontology/2.0/isPeerReviewed
- Indicates whether the information object has been peer reviewed to check the correctness of the content
URI: http://www.jeromedl.org/ontology/2.0/isPreprintVersion
- defines if the information object is a preprint
URI: http://www.jeromedl.org/ontology/2.0/isPublished
- if resource is allowed for publishing
URI: http://www.jeromedl.org/ontology/2.0/isReviewed
- Indicates whether the information object has been reviewed (to check the correctness of the information object as whole)
URI: http://www.jeromedl.org/ontology/2.0/isScaledToFit
- should the media object be scalled to fit the content
URI: http://www.jeromedl.org/ontology/2.0/isSizeWithSubCollections
- if collection contains items from subcollection [http://www.jeromedl.org/structure#sizeWithSubCollections]
URI: http://www.jeromedl.org/ontology/2.0/isUnion
- if the collection is build as a union of specifications [http://www.jeromedl.org/structure#isUnion]
URI: http://www.jeromedl.org/ontology/2.0/isUploadedBy
- Who has uploaded the infomration object
URI: http://www.jeromedl.org/ontology/2.0/isVisible
- if the collection is visible to the end user [http://www.jeromedl.org/structure#isVisible]