The structure ontology (see http://www.jeromedl.org/ontology/2.1/ for more information) is used at the bottom layer (classic services and metadata) of JeromeDL architecture (see Sec. 7.2). It is used to handle typical tasks required from a digital objects repository, i.e., it keeps track of the 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.
Modern digital library systems not only store the bibliographic metadata but also the electronic representation of the content itself. Depending on its type, the content typically follows some structure, e.g. we can decompose a book into chapters and provide individual descriptions for each chapter with information about relations between them. Including structural concepts in ontologies and using these concepts in metadata descriptions provides a universal layer for metadata and content retrieval. It supports extending 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 (212,197).
An alphabetical index of JeromeDL terms, by class (categories or types) and by property.
Classes:
Properties:
JeromeDL structure ontology introduces the following classes and properties:
This is an information object which has a binary representation, such as JPG, PDF, etc. NOTE: meta-information 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.
Is a special type of jeromedl:Part information object for expressing chapter information.
This is a virtual information object, which is computed out of other resources (disseminator).
This concept binds any kind of annotations to the information object.
A collection created dynamically based on the provided specification.
The special type of media resources, i.e., all image resources (JPG, PNG).
The most abstract type of a resource in the library (NOTE: this concept supersedes jdl1:Book)
The special type of jeromedl:Part, which references the multimedia content.
It is a generic binary type, the distinctive feature is its physical size and the scaling ability.
Represents a single page in a chapter; usually used to capture a scanned page of an antique book.
This is an information object that is a part of another information object.
Represents the proper library resource (book, article, chapter, page).
Defines types of special Information Objects, i.e., Resources; these are the most high level information objects presented to the user.
The aggregation service that can deliver a bunch of information objects in one go.
Defines a list of individuals which cover the submission workflow status.
Specifies number of resources that are used as a source for computing the new resource.
Indicates the attachment of an information object.
Defines type of the resource; used in the main classification scheme in JeromeDL
The ordering number of the collection in the tree of collections (previously http://www.jeromedl.org/structure#collectionOrder)
Literal/string representation of the specification of the collection (previously http://www.jeromedl.org/structure#collectionSpecification)
binds predefined type of collection to dynamic collection.
Used to bind multipurpose context to an information object
Indicates who owns copyrights for given information object
Defines a binary resource (an image) that represents the cover of the information object; also used as a thumbnail of media resource
Points to the most current version of the information object (IMPORTANT: we suggest that either all information objects points to their current versions - even the current ones, or only the non-current ones)
A textual description on the information object
Size of the binary file related to this resource
Defines parameter for invocation
MIME type of the binary resource
Some resources (antique book chapter, PDF, ...) can have information about number of pages (physical size of the resource), compare to marcont:hasNumberOfPages (see Appendix G) representing the actual size of the content of the resource
Indicates the logical page in the resource (it can have binary resources like PNG, JPG and computed resources [disseminators] like DjVu)
An abstract property to indicate that one information object contains another as its part
Points from an information object to aggregation service - e.g., we can point from chapter to a set of pages in one go
Used to indicate the position of the statement on the list
Points to the previous version (IMPORTANT: in case a version is removed, we will not be changing numbers, but we should change the linking)
Binds binary resource or computed resource to the part resource
Smaller representation of the file (e.g., SWF optimized for mobile access)
Defines the specification of a collection; can be a string literal with a structure processable by the dynamic collections module.
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
When the information object was uploaded
Comment explaining what has changed in this version
A person who created this version
Defines date when this version of the information object was created
A unique number of the version of the information object
Defines the REST service which should be invoked to compute the result
Indicates whether the information object has been peer reviewed to check the correctness of the content
Defines if the information object is a preprint
Indicates should the media object be scaled to fit the content
Defines if collection contains items from sub-collection (previously
http://www.jeromedl.org/structure#sizeWithSubCollections)
Defines if the collection is build as a union of specifications (previously
http://www.jeromedl.org/structure#isUnion)
The person who uploaded the given information object.
Defines if the collection is visible to the end user (previously jdl1:isVisible)
Specifies where a library resource was originally published