Book

Extensible Access Control (EAC) Ontology Specification

The EAC ontology (see http://www.jeromedl.org/eac/1.1/ for more information) is used at the bottom layer in JeromeDL. It is used to describe access controls to a digital objects repository.

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 relations between them. Including structural concepts in ontologies and using these concepts in metadata descriptions provides a universal layer for metadata and content retrieval. The structure description can be extended 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 (221)

EAC Ontology Index

An alphabetical index of EAC terms, by class (categories or types) and by property:

Classes:

Properties:

EAC cross-reference: Classes and Properties

EAC ontology introduces the following classes and properties.

Class: eac:Action

The action concept defines basic actions identified within certain applications. In the case of REST services these would be the basic HTTP methods: access (GET), modification (POST), creation (PUT), and removal (DELETE). Each Action is computed as a conjunction or sum (depending on the value of the is conjunction property) of Condition s.

in-domain-of:
eac:hasCondition, eac:isConjunctive
in-range-of:
eac:allowsFor

Class: eac:ActionAccess

Defines rules for accessing resources or invoking GET services.

FORMER: http://www.jeromedl.org/structure#ActionAccess

sub-class-of:
eac:Action

Class: eac:ActionCreate

Defines rules for creating resources or invoking PUT services.

FORMER: http://www.jeromedl.org/structure#ActionCreate

sub-class-of:
eac:Action

Class: eac:ActionModify

Defines rules for modifying resources or invoking POST services.

FORMER: http://www.jeromedl.org/structure#ActionModify

sub-class-of:
eac:Action

Class: eac:ActionRemove

Defines rules for deleting resources or invoking DELETE services.

FORMER: http://www.jeromedl.org/structure#ActionRemove

sub-class-of:
eac:Action

Class: foaf:Agent

Defined in the FOAF ontology (http://xmlns.com/foaf/0.1/Agent)

Class: eac:Condition

The condition concept defines an atomic policy condition, which aggregates a number of Rule s. The result of computing the policy condition is a conjunction of results of atomic rules. EAC Condition can be organized in hierarchical structures. It allows users to define abstract policies which are conjunction of other policies.

in-domain-of:
eac:isActive, eac:hasConditionType, eac:atPosition,
eac:hasRule, eac:isConjunctive
in-range-of:
eac:hasCondition

Class: eac:ConditionType

Identifies type of a condition.

Class: eac:License

License is the most important concept in the EAC model. It aggregates positive (al lows for performing certain actions) and negative (denies for per- forming certain actions) conditions for each type of action. A single license can be assigned to many Licensed Entities. It is validated by the EAC engine (see Sec. 5) against conditions defined in the licenses for the actions to be performed on the given entity. The license can define whether the negative (deny first = true) or positive (deny first = false) constraints should be computed first.

in-domain-of:
eac:isDeniedFirst, eac:allowsFor
in-range-of:
eac:hasLicense

Class: eac:Licensee

Agent/person who obtained the license.

sub-class-of:
foaf:Agent, eac:TriggerListener
in-range-of:
eac:belongsTo

Class: eac:Licensor

Agent/person who provided the license.

sub-class-of:
foaf:Agent, eac:TriggerListener
in-range-of:
eac:issuedBy

Class: eac:LicensedEntity

Licensed Entity is an abstract concept of a resource (Licensed Resource) or a service (Licensed Service ) to which a license can be applied. The Licensed Resources, following the aggregation capabilities of semantic digital libraries, support passing the license down to the sub-components of the given resource. The way in which the license is applied to sub-components, and in which it is computed for the resources and its sub-components, is defined by the Propagation State of the license.

in-domain-of:
eac:hasPropagationState, eac:hasLicense

Class: eac:LicensedResource

Represents all resources which can have licenses attached to them

sub-class-of:
eac:LicensedEntity
in-domain-of:
eac:hasInheritedLicense, eac:sameAs

Class: eac:LicensedService

Represents services which can have a license attached to them. It is preferable that we use REST services for that matter.

sub-class-of:
eac:LicensedEntity

Class: eac:PropagationState

Propagation State Identify how the license is applied to the Licensed Resources, and how it propagates to sub-components of the given resource. Possible states include: applying to the give resource only (Resource Only), to the resource and only direct sub-components (With Children), or to the resource and any sub-components (With Descendants); it is also possible to apply the license to the direct (Only Children) or all (Only Descendants) sub-components, but not the the resource itself.

in-range-of:
eac:hasPropagationState

Class: eac:Rule

Rule defines an atomic rule, which computed against give resource and within certain context returns boolean value, e.g., IP network address range, a part of a social network, maximum usage count.

in-range-of:
eac:hasRule

Class: eac:TriggerEvent

An event that is passed from the Triggering Source (e.g. Licensed Entity) through Triggering Bus (communication channel) and affects the Triggering Listener (e.g., License).

Class: eac:TriggerListener

An object that can accept Triggering Event.

super-class-of:
eac:License, eac:Licensee, eac:Licensor

Class: eac:TriggerSource

Source that is capable of emitting Triggering Events.

super-class-of:
eac:Condition, eac:LicensedEntity

Property: eac:allowsFor

Binds positive rules for accessing, modifying, creating or removing resources (or services).

FORMER: http://www.jeromedl.org/structure#allowAction

OWL Type:
ObjectProperty
OWL Type:
InverseFunctionalProperty (uniquely identifying property)
Domain:
eac:License
Range:
eac:Action

Property: eac:belongsTo

To whom the license belongs (Licensee)

OWL Type:
ObjectProperty
OWL Type:
FunctionalProperty
Domain:
eac:License
Range:
eac:Licensee

Property: eac:deniesForAction

Binds negative rules for accessing, modifying, creating or removing resources (or services).

FORMER: http://www.jeromedl.org/structure#denyAction

OWL Type:
ObjectProperty

Property: eac:atPosition

Defines the position at which the EAC Condition is hold in the hierarchy of conditions tree (in fact it tells the ordering number between peer EAC conditions)

OWL Type:
DatatypeProperty
Domain:
eac:Condition
Range:
xsd:int

Property: eac:hasCondition

Binds atomic specifications of rules to action access control definitions.

FORMER: http://www.jeromedl.org/structure#hasProtectionDefinition

OWL Type:
ObjectProperty
Domain:
eac:Action
Range:
eac:Condition

Property: eac:hasConditionType

Identifies types of conditions (recognized and supported by plugins of EAC module)

FORMER: http://www.jeromedl.org/structure#drmType

OWL Type:
DatatypeProperty
Domain:
eac:Condition
Range:
xsd:string

Property: eac:hasInheritedLicense

Binds sub-resource in aggregation view to the license inherited from the upper resource

OWL Type:
ObjectProperty
sub-property-of:
eac:hasLicense
Domain:
eac:LicensedResource

Property: eac:hasLicense

Binds licensed entity to the license

OWL Type:
ObjectProperty
Domain:
eac:LicensedEntity
Range:
eac:License

Property: eac:hasPropagationState

Defines how the license specification is propagated through the aggregation of resources (book → chapters → pages)

FORMER: http://www.jeromedl.org/structure#licensePropagation

OWL Type:
ObjectProperty
Domain:
eac:LicensedEntity
Range:
eac:PropagationState

Property: eac:hasRule

Defines one of many rules that create a condition.

OWL Type:
ObjectProperty
OWL Type:
InverseFunctionalProperty (uniquely identifying property)
Domain:
eac:Condition
Range:
eac:Rule

Property: eac:isActive

Determines if the EAC condition is currently active or not

OWL Type:
DatatypeProperty
Domain:
eac:Condition
Range:
xsd:boolean

Property: eac:isConjunctive

Tells whether the Action specification should fulfill all conditions or just some

OWL Type:
DatatypeProperty
Domain:
eac:Action, eac:Condition
Range:
xsd:boolean

Property: eac:isDeniedFirst

Defines if the negative conditions should be evaluated before the positive conditions

FORMER: http://www.jeromedl.org/structure#isDenyFirst

OWL Type:
DatatypeProperty
Domain:
eac:License
Range:
xsd:boolean

Property: eac:issuedBy

By whom the licenses was issued (Licensor)

FORMER: http://www.jeromedl.org/structure#isDenyFirst

OWL Type:
ObjectProperty
OWL Type:
FunctionalProperty
Domain:
eac:License
Range:
eac:Licensor

Property: eac:sameAs

(deprecated property) Used to indicate relations between real chapters (as handled in JeromeDL prior-2.1) and license entities of chapters (as handled in JeromeDL 2.1+). It probably become absolute once we bNodes from the aggregation model in JeromeDL 3.0

OWL Type:
DatatypeProperty
Domain:
eac:LicensedResource
Range:
xsd:string

S3B Tagging Ontology Specification

S3B Tagging Ontology (see http://s3b.corrib.org/tagging/ for more information) extends the basic concepts introduces by the Tom Gruber's TagOntology (150) with support for annotating fragments of information items using typed tags (object, setting, agent, action).

S3B Tagging Ontology Index

An alphabetical index of S3B Tagging terms, by class (concepts) and by property (relationships, attributes):

Classes:

Properties:

Cross-reference for S3B Tagging Ontology Classes and Properties

An alphabetical index of S3B Tagging terms, by class (categories or types) and by property. All the terms are hyperlinked to their detailed description for quick reference.

Class: tagging:CircleROI

ROI of circular shape

sub-class-of:
tagging:ROI
in-domain-of:
tagging:hasRadius, tagging:hasXCoordinate, tagging:hasYCoordinate

Class: tagging:Clipping

Defines a range within the tagged document (pages, ROI, time-tag)

in-range-of:
tagging:hasClipping

Class: tagging:Coordinate

Group of numbers (tagging:hasXCoordinate, tagging:hasYCoordinate) used to indicate the position of a point.

in-domain-of:
tagging:hasXCoordinate, tagging:hasYCoordinate
in-range-of:
tagging:hasCoordinates

Class: tagging:Document

Represents documents which are being annotated

in-domain-of:
tagging:hasTagging
in-range-of:
sioc:related_to

Class: tagging:Excerpt

Indicates a range in the multimedia stream

sub-class-of:
tagging:Clipping
in-domain-of:
tagging:hasExcerptStart, tagging:hasExcerptLength

Class: tagging:ROI

Region/Range of interest on the photo, movie

sub-class-of:
tagging:Clipping

Class: tagging:PolygonalROI

ROI of polygonal shape

sub-class-of:
tagging:ROI
in-domain-of:
tagging:hasCoordinates

Class: tagging:RectangleROI

ROI of rectangle shape

sub-class-of:
tagging:ROI
in-domain-of:
tagging:hasWidth, tagging:hasHeight, tagging:hasXCoordinate,
tagging:hasYCoordinate

Class: tagging:Tagger

Represents an agent (person or service) that provided the particular tagging

sub-class-of:
foaf:Agent
in-range-of:
dc:creator

Class: tagging:Tagging

Represents the tagging action, i.e., binds annotations and their author to the tagged document

in-domain-of:
tagging:hasTerm, tagging:hasClipping, tagging:linksTo, tagging:hasTime, dc:title, dc:creator, dc:description, sioc: related_to, tagging:isShared
in-range-of:
tagging:hasCrossReference, tagging:hasTagging

Class: tagging:Term

An abstract concept defining the annotation concept (tag, keyword, topic, etc)

in-range-of:
tagging:hasTerm

Property: tagging:hasActionTerm

Specifies tag/term of the type action, e.g., eating

OWL Type:
ObjectProperty
sub-property-of:
tagging:hasTerm

Property: tagging:hasAgentTerm

Specifies tag/term of the type agent, e.g., man

OWL Type:
ObjectProperty
sub-property-of:
tagging:hasTerm

Property: tagging:hasCoordinates

Points to an ordered collection (rdf:Seq) with coordinates; each resource (of type tagging:Coordinate) in this collection will have tagging:hasXCoordinate and tagging:hasYCoordinate.

OWL Type:
ObjectProperty
Domain:
tagging:ROI
Range:
rdf:Seq (of tagging:Coordinate) or tagging:Coordinate

Property: tagging:hasClipping

Binds the tagging to the region (part of) the multimedia resource

OWL Type:
ObjectProperty
Domain:
tagging:Tagging
Range:
tagging:Clipping

Property: tagging:hasCrossReference

Indicates relation to an internal resource or its region

OWL Type:
ObjectProperty
sub-property-of:
tagging:linksTo
Range:
tagging:Tagging

Property: tagging:hasExcerptLength

Indicates when the range in the multimedia stream ends

OWL Type:
DatatypeProperty
Domain:
tagging:Excerpt
Range:
xsd:float

Property: tagging:hasExcerptStart

Indicates when the range in the multimedia stream starts

OWL Type:
DatatypeProperty
Domain:
tagging:Excerpt
Range:
xsd:float

Property: tagging:hasHeight

The height of the rectangle ROI (should be percentage value)

OWL Type:
DatatypeProperty
Domain:
tagging:RectangleROI
Range:
xsd:float

Property: tagging:hasObjectTerm

Specifies tag/term of the type object, e.g., banana

OWL Type:
ObjectProperty
sub-property-of:
tagging:hasTerm

Property: tagging:hasRadius

In the circle ROI this property specifies the radius of the circle indicating the ROI (should be used as a percentage value of the size of the photo, NOTE: since there two dimensions to specify percentage by - this ontology defines the radius as a percentage value of the width of the photo/object)

OWL Type:
DatatypeProperty
Domain:
tagging:CircleROI

Property: tagging:hasSettingTerm

Specifies tag/term of the type setting, e.g., beach

OWL Type:
ObjectProperty
sub-property-of:
tagging:hasTerm

Property: tagging:hasTagging

Indicates the tagging operation related to given document

Inverse:
sioc:related_to
OWL Type:
ObjectProperty
OWL Type:
InverseFunctionalProperty (uniquely identifying property)
Domain:
tagging:Document
Range:
tagging:Tagging

Property: tagging:hasTerm

See also: sioc:topic. Binds Terms to the tagging concept.

OWL Type:
ObjectProperty
Domain:
tagging:Tagging
Range:
tagging:Term

Property: tagging:hasTime

When the tagging was issued

OWL Type:
DatatypeProperty
sub-property-of:
dcterms:created
Domain:
tagging:Tagging

Property: tagging:hasWidth

The width of the rectangle ROI (should be percentage value)

OWL Type:
DatatypeProperty
Domain:
tagging:RectangleROI
Range:
xsd:float

Property: tagging:hasXCoordinate

The X coordinate of the rectangle ROI (should be percentage value); indicates horizontal coordinate the upper-left corner of the rectangle ROI or a center of the circle ROI

OWL Type:
DatatypeProperty
Domain:
tagging:RectangleROI, tagging:CircleROI, tagging:Coordinate
Range:
xsd:float

Property: tagging:hasYCoordinate

The Y coordinate of the rectangle ROI (should be percentage value); indicates vertical coordinate the upper-left corner of the rectangle ROI or a center of the circle ROI

OWL Type:
DatatypeProperty
Domain:
tagging:RectangleROI, tagging:CircleROI, tagging:Coordinate
Range:
xsd:float

Property: tagging:isShared

Indicates whether this tagging is publicly available (following the model in del.icio.us)

OWL Type:
DatatypeProperty
Domain:
tagging:Tagging
Range:
xsd:boolean

Property: tagging:linksTo

Reference to other document (might be just URI), usually from outside of the system

OWL Type:
ObjectProperty
Domain:
tagging:Tagging

Property: dc:creator

(from DC metadata) Indicates who has provided the tagging

Property: dc:description

(from DC metadata) longer description of the resource/tagging

Property: dc:title

(from DC metadata) the title of the element

Property: dcterms:created

(from DC Terms metadata) when the object was created

Property: sioc:has_creator

(from SIOC ontology) person who provided the annotation/post/etc

Property: sioc:related_to

(from SIOC ontology) what resource the annotation is related to

Property: sioc:topic

(from SIOC ontology) See also: hasTerm

Social Semantic Collaborative Filtering Ontology

SSCF Ontology (see http://s3b.corrib.org/sscf/0.2/ for more information) describes objects and properties that are used by Social Semantic Collaborative Filtering.
SSCF is a personal knowledge management system. User builds a personal hierarchy of directories (personal taxonomy) and fills it with a links to interesting resources (web bookmarks, MultiBeeBrowse bookmarks). Users can share the gathered knowledge with others by importing others' directories. System provides also an import feature - one can import resources stored in different bookmarking system (like del.icio.us)

SSCF Ontology Index

An alphabetical index of SSCF Ontology terms, by class (concepts) and by property (relationships, attributes):

Classes:

Properties:

Cross-reference for SSCF Ontology classes and properties

An alphabetical index of SSCF Ontology terms, by class (categories or types) and by property. All the terms are hyperlinked to their detailed description for quick reference.

Class: sscf:Directory

Special kind of Resource. Resource that holds other resources creates tree structure.

sub-class-of:
sscf:Resource
in-domain-of:
sscf:isInSuggested, sscf:inDomain, sscf:hasTag, sscf: importedFrom,
sscf:accesibleTo, sscf:follows
in-range-of:
sscf:isInSuggested, sscf:removedSuggested, sscf:isIn

Class: sscf:Evaluation

Holds the evaluation information

in-domain-of:
sscf:value
in-range-of:
sscf:isEvaluatedWith

Class: sscf:HexResource

Resource which is a link to the search in MultiBeeBrowse.

sub-class-of:
sscf:Resource

Class: sscf:ImportedResource

Special kind of WebResource. URL which is a link to bookmark and is imported from a bookmarking source.

sub-class-of:
sscf:WebResource

Class: sscf:Resource

SSCF resource. It is generic bookmark. All resources that does not have specified type and should be treated as a bookmark should be instance of this class.

in-domain-of:
sscf:issuedBy, sscf:isEvaluatedWithrdfs:label, sscf: resourceHits,
rdfs:comment, sscf:isIn
in-range-of:
sscf:follows

Class: sscf:Tagger

Special kind of Directory. Resource that holds the information about tagger account. This is also Directory that may contain other resources (with isIn property).

sub-class-of:
sscf:Directory

Class: sscf:Term

A word or phrase that is recognizable by people and computers

in-domain-of:
rdfs:label
in-range-of:
sscf:hasTag

Class: sioc:Post

SSCF ontology uses Post concept from SIOC ontology to capture community contributed textual annotations.

in-domain-of:
sscf:annotates

Class: sscf:WebResource

Special kind of Resource. Resource which is a link to the page in a Web, URL.

sub-class-of:
sscf:Resource
in-domain-of:
rdfs:seeAlso

Property: sscf:accesibleTo

Holds the resource access policy, e.g., a FOAFRealm realm rule:
F[mailto:foo@bar.com]1.4

OWL Type:
DatatypeProperty
Domain:
sscf:Directory
Range:
xsd:string

Property: sscf:annotates

Links resource with its annotation.

OWL Type:
ObjectProperty
Domain:
sioc:Post
Range:
sscf:Resource

Property: sscf:createdBy

Points to Person that create the Resource

OWL Type:
ObjectProperty
Domain:
sscf:Resource
Range:
foaf:Person

Property: sscf:follows

Indicates that resource follows other resource, opposite to isIn.

Inverse:
sscf:isIn
OWL Type:
ObjectProperty
Domain:
sscf:Directory
Range:
sscf:Resource

Property: sscf:hasTag

Informs if there is a tag (Term) assigned to the Directory

OWL Type:
ObjectProperty
Domain:
sscf:Directory
Range:
sscf:Term

Property: sioc:has_container

Used by Annotation module to export data. Represents the following properties: rdf:type, sscf:annotates, sscf:isEvaluatedWith.

Property: sioc:has_creator

  • Used by Annotation module to export data. Shows the creator/owner of sscf:Resource, sscf:Evaluation or sioc:Post
  • Used to keep Creator of the Evaluation (Domain - sscf:Evaluation, Range - foaf:Person)

The sioc:has_creator property links a Post to its author's User account. Thus, we can follow the link from the post to the creator and locate the other posts by the same User.

The community can be seen as a network of posts with users linked to each post, and there is also a network of other posts created by a given user stemming from there. We can use this information in community sites to locate more contributions by the given author.

Property: sioc:has_host

Used by Annotation module to export data. Represents jeromedl:publishedAt (in case the using with JeromeDL instance) or sscf:isIn (for relation between main and subdirectory)

Property: sioc:has_reply

Represents the connections between sioc:Posts (one annotation can be an answer to the other). Also used to export data.

Property: sioc:properties

Used by Annotation module to export data. Represents the properties of sscf:Resource, sscf:Evaluation or sioc:Post

Property: sscf:importedFrom

Shows if the Directory was imported. Shows the location from which the Directory was imported.

OWL Type:
ObjectProperty
Domain:
sscf:Directory, sscf:ImportedResource

Property: sscf:inDomain

Defines in which domain is the given directory. (Currently deprecated)

OWL Type:
ObjectProperty
Domain:
sscf:Directory
Range:
skos:Concept

Property: sscf:isEvaluatedWith

Shows by which object the given Resource was annotated.

OWL Type:
ObjectProperty
Domain:
sscf:Resource
Range:
sscf:Evaluation

Property: sscf:isIn

Points to the super directory. This is the mean to create tree structure.

Inverse:
sscf:follows
OWL Type:
ObjectProperty
Domain:
sscf:Resource
Range:
sscf:Directory

Property: sscf:isInSuggested

- Indicates that the Directory is suggested to be placed in another Directory.

OWL Type:
ObjectProperty
Domain:
sscf:Directory
Range:
sscf:Directory

Property: sscf:issueDate

Holds the date of creation of the Resource

OWL Type:
DatatypeProperty
sub-property-of:
dc:date
Range:
xsd:dateTime

Property: sscf:removedSuggested

Indicates if the Directory should no be placed again in some other Directory as a suggested Directory.

OWL Type:
ObjectProperty
Domain:
sscf:Directory
Range:
sscf:Directory

Property: sscf:resourceHits

Indicates how many times the Resource was opened or clicked.

OWL Type:
DatatypeProperty
Domain:
sscf:Resource
Range:
xsd:int

Property: sscf:value

Holds the value of the evaluation.

OWL Type:
DatatypeProperty
Domain:
sscf:Evaluation
Range:
xsd:float

FOAFRealm Ontology Specification

The FOAFRealm system takes advantage of social networks and FOAF profiles in user profile management systems. However, the FOAF standard must be enriched with new concepts and properties that are described in this document. The enriched version is called FOAFRealm.

FOAFRealm Ontology Index

An alphabetical index of FOAFRealm terms, by class (categories or types) and by property ( see http://www.foafrealm.org/xfoaf/0.1/ for more information):

Classes:

Properties:

FOAFRealm cross-reference: Classes and Properties

FOAFRealm introduces the following classes and properties.

Class: xfoaf:Domain

Represents a domain of interest linked to the SSCF Directory instances

sub-class-of:
xfoaf:Resource
in-range-of:
http://www.foafrealm.org/xfoaf-sscf/0.1/interestedIn

Class: xfoaf:Resource

Represents an resource within the web application

sub-class-of:
http://xmlns.com/foaf/0.1/Documentfoaf:Document
in-domain-of:
xfoaf:timestamp, xfoaf:isIn, xfoaf:isEvaluatedWith, xfoaf: accessibleTo
in-range-of:
xfoaf:annotates

Property: xfoaf:accessibleTo

Defines valid FOAFRealm ACL entry (*, ISAFRIENDOF, F[login@domain]distance {,|.}trust)

Domain:
xfoaf:Resource
Range:
xsd:normalizedString

Property: xfoaf:annotates

Defines which resources are being annotated by this one

Domain:
xfoaf:Annotation
Range:
xfoaf:Resource

Property: xfoaf:bio

Describes some biography, resume or credential of the person

OWL Type:
InverseFunctionalProperty (uniquely identifying property)
Domain:
foaf:Person
Range:
xsd:string

Property: xfoaf:distributed

Indicates if the user profile is stored locally or if is distributed

Domain:
foaf:Person
Range:
xsd:boolean

Property: xfoaf:follows

Defines the annotations that this annotations follows/responds to in the conversation

sub-property-of:
xfoaf:annotates
Domain:
xfoaf:Annotation
Range:
xfoaf:Annotation

Property: xfoaf:friendshipLevel

Reifies the foaf:knows statement to define the trust level between people

Domain:
xfoaf:KnowsStatement
Range:
xsd:float

Property: xfoaf:hideEmail

Indicates if the user required to hide his email address during the FOAF export

Domain:
foaf:Person
Range:
xsd:boolean

Property: xfoaf:knows_sig

Local signature (done with SHA1SUM and RSA keys) on the foaf:knows and foaf:knows reifications

Domain:
foaf:Person
Range:
xsd:normalizedString

Property: xfoaf:nationality

Describes person nationality

Domain:
foaf:Person
Range:
xsd:normalizedString

Property: xfoaf:password_sha1sum

The property stores SHA1 sum of the password that with the email address stands for credentials of the person login in with FOAFRealm enabled service

Domain:
foaf:Person
Range:
xsd:normalizedString

Property: xfoaf:relationshipLevel

Reifies the foaf:knows statement to define the trust level between people

Domain:
foaf:Person
Range:
xsd:normalizedString

Property: xfoaf:relationshipName

Name of the relationship between two Persons; it identifies more precisely the nature of the relationship

Domain:
foaf:Person
Range:
xsd:normalizedString

Property: xfoaf:rsa_key

private RSA key - not exportable from home server, pass-phrase locked

Domain:
foaf:Person
Range:
xsd:normalizedString

Property: xfoaf:rsa_key_pub

public RSA key - exportable to and stored by other servers, together with foaf:seeAlso information

Domain:
foaf:Person
Range:
xsd:normalizedString

Property: xfoaf:sessionId

Used to identify logged user

Domain:
foaf:Person
Range:
xsd:normalizedString

Property: xfoaf:timestamp

Applications can make use of it to handle
caching in distributed environments

Domain:
foaf:Person, xfoaf:Resource
Range:
xsd:long

Property: xfoaf:value

Defines the value given to in this evaluation

Domain:
xfoaf:Evaluation
Range:
xsd:float

External Classes and Properties

Classes and properties from other ontologies can be used together with FOAFRealm. During the FOAFRealm ontology design process some external classes and properties were identified that are suitable for reuse. Such concepts are not included inside FOAFRealm but are use directly together with terms from FOAFRealm to describe the information about on-line community.

This sections list the main external classes and properties that can be used with FOAFRealm in a meaningful way. This list is not and can not be exhaustive because many RDF ontologies can be used together.

MarcOnt Bibliographic Ontology 2.1 Specification

The goal of MarcOnt bibliographic ontology (see http://www.marcont.org/ontology/2.1/ for more information) 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 knowledge and experience, together building community ontology with tools such as MarcOnt Portal96.

The ontology It is to be used in JeromeDL (see Chapter 7) as a format capturing bibliographic descriptions of the resources. The ontology is also being used as a mediation format in MarcOnt Mediation Services97. With use of MarcOnt ontology one can transform bibliographic descriptions of the resources between supported formats (BibTEX, Dublin Core, MARC21) and MarcOnt.

When talking about ontologies, classes are often identified with objects in the real world. Their names often reflect this approach (e.g. Person class in the 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 multiple 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, DublinCore etc.). This implies the complicated process of achieving consensus on the ontology.

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:

Properties:

Instances:

Cross-reference for MarcOnt Bibliographic Ontology Classes and Properties

An alphabetical index of MarcOnt terms, by class (categories or types) and by property:

Class: marcont:AccessMedium

Types of media available to access a resource.

in-range-of:
marcont:hasOriginalPublicationMedium

Class: marcont:Article

Represents the concept of a scientific publication (usually in a journal).

sub-class-of:
marcont:Resource
in-domain-of:
marcont:hasJournal, marcont:hasPagesTo, marcont:hasPagesFrom

Class: marcont:Book

Represents the concept of a book.

sub-class-of:
marcont:Resource, marcont:PublicationMedium
in-domain-of:
marcont:hasCoverage

Class: marcont:Booklet

One of the types of resources - a small information book, a booklet.

sub-class-of:
marcont:Resource, marcont:PublicationMedium

Class: marcont:Cluster

Represent a concept of cluster - sub-unit of an institute.

sub-class-of:
marcont:Organization

Class: marcont:Collection

Represents collection of resources.

sub-class-of:
marcont:Resource

Class: marcont:Conference

Represents the concept of a scientific event - a conference.

sub-class-of:
marcont:Event

Class: marcont:Coverage

This class represents the range of the "coverage" annotation property from Dublin Core.

in-range-of:
marcont:hasCoverage

Class: marcont:DemoSession

Poster session at a workshop or a conference.

sub-class-of:
marcont:Presentation

Class: marcont:Event

Class represents all types of events related to publication process.

in-domain-of:
marcont:hasBeginDate, marcont:hasDate, marcont:hasDescription, marcont:hasEndDate, marcont:hasMonth, marcont: hasOrganization, marcont:hasRelatedEvent, marcont:hasTitle, marcont:hasURL, marcont:isPeerReviewed
in-range-of:
marcont:presentedAt, marcont:hasRelatedEvent

Class: marcont:Faculty

Represents a concept of a faculty - subunit of a university.

sub-class-of:
marcont:Organization

Class: marcont:Inbook

One of the types of resources - part of a Book (e.g., a chapter in the Manuscript)

sub-class-of:
marcont:Resource

Class: marcont:Incollection

One of the types of resources - part of larger collection

sub-class-of:
marcont:Resource

Class: marcont:Inproceedings

One of the types of resources - an article in conference, workshop or proceedings

sub-class-of:
marcont:Resource

Class: marcont:Institute

Represents the concept of Institute.

sub-class-of:
marcont:Organization

Class: marcont:Journal

Represent the journal concept.

sub-class-of:
marcont:Collection
in-domain-of:
marcont:hasNumber
in-range-of:
marcont:hasJournal

Class: marcont:Lab

Represents a concept of a Laboratory, a sub-unit of a cluster.

sub-class-of:
marcont:Organization

Class: marcont:LightingTalk

A very short talk. Usually lasts no longer than 5 minutes.

sub-class-of:
marcont:Talk

Class: marcont:Manual

One of the types of resources - a manual or a use guide.

sub-class-of:
marcont:Resource

Class: marcont:Mastersthesis

One of the types of resources - Master's thesis document.

sub-class-of:
marcont:Resource

Class: marcont:Meeting

This class should be used to represent a general type of a meeting involving a number of agents.

sub-class-of:
marcont:Event

Class: marcont:Misc

One of the types of resources which does not belong to any other category: Miscellaneous.

sub-class-of:
marcont:Resource

Class: marcont:Organization

Represent the concept of on organization.

in-range-of:
marcont:hasAffiliation, marcont:hasOrganization

Class: marcont:PhDthesis

One of the types of resources - PhD Thesis document.

sub-class-of:
marcont:Resource

Class: marcont:PosterSession

Representation of a poster session at a given event (e.g., conference).

sub-class-of:
marcont:Presentation

Class: marcont:Presentation

Class represents all types of presentations that can be given during an event.

sub-class-of:
marcont:Event

Class: marcont:Proceedings

One of the types of resources - proceedings of conference or workshop

sub-class-of:
marcont:Collection, marcont:PublicationMedium

Class: marcont:PublicationMedium

Represents an abstract concept of publication medium - can be conference proceedings, book, website/social medium, journal 

domain-of:
marcont:hasRelatedEvent, marcont:hasPublisher
range-of:
marcont:publishedIn

Class: marcont:Resource

Base class for all bibliographical resources.

in-domain-of:
marcont:hasSponsor, marcont:presentedAt, marcont:hasOriginalPublicationMedium, marcont: hasDomain, marcont:hasKeyword, marcont:hasSource, marcont:hasContents, marcont:hasHumanCreator, marcont: hasTopic, marcont:hasDCMIType, marcont: hasPublisher, marcont:hasSchool, marcont:hasTagging, marcont: hasContributor, marcont:hasISSN, marcont:hasAbstract,
marcont: hasEdition, marcont:hasOrder, marcont: hasYear, marcont:hasNote, marcont:hasSeries, marcont:hasISBN, marcont:hasPages, marcont:howPublished, marcont:hasIdentifier, marcont:isPartOf, marcont: hasMonth, marcont:hasOrganization, marcont: hasRelatedEvent, marcont:hasTitle,
marcont:hasURL, marcont:isPeerReviewed
in-range-of:
marcont:hasSource, marcont:isPartOf

Class: marcont:Review

Provides information related to the review process.

sub-class-of:
sioc:Post
in-domain-of:
hasReviewComment, hasReviewer, isPeerReview, hasReviewDate
in-range-of:
hasReview

Class: marcont:ShortTalk

Short talk refers to a talk that last approximately 15 minutes and is given during an event.

sub-class-of:
marcont:Talk

Class: marcont:SocialMedium

Represents an electronic publication medium with a community of users build around it, etc. Facebook

sub-class-of:
marcont:WebSite

Class: marcont:Talk

Talk represents all types of talks and presentations different from Demo session, Poster session and Tutorial, that can be given during an event.

sub-class-of:
marcont:Presentation

Class: marcont:Techreport

One of the types of resources - technical report.

sub-class-of:
marcont:Resource

Class: marcont:Tutorial

This class represents tutorial given at a conference (or in some cases in other circumstances).

sub-class-of:
marcont:Presentation

Class: marcont:University

This class represents the concept of a university.

sub-class-of:
marcont:Organization
in-range-of:
marcont:hasSchool

Class: marcont:Unpublished

One of the types of resources - a resource that has not been published.

sub-class-of:
marcont:Resource

Class: marcont:WebSite

Represents a generic Internet-based publication medium

sub-class-of:
marcont:PublicationMedium

Class: marcont:Workshop

Represents the scientific event, less prominent and more focused than a conference.

sub-class-of:
marcont:Event

Property: marcont:hasAbstract

Abstract of the resource. This property is equivalent to the bibtex:hasAbstract property.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource
Range:
xsd:string

Property: marcont:hasAddress

Usually the address of the publisher or other type of institution. For small publishers, on the other hand, you can help the reader by giving the complete address.

OWL Type:
ObjectProperty
Range:
http://gaia.fdi.ucm.es/ontologies/address.owl#Address

Property: marcont:hasAffiliation

Affiliation of a given person.

OWL Type:
ObjectProperty
Domain:
foaf:Person
Range:
marcont:Organization

Property: marcont:hasAuthor

Attaches information about human author of the resource or the collection of resources.

OWL Type:
ObjectProperty
sub-property-of:
marcont:hasHumanCreator

Property: marcont:hasBeginDate

Begin date of the copyright period.

OWL Type:
DatatypeProperty
sub-property-of:
marcont:hasDate
Domain:
marcont:Event
Range:
xsd:date

Property: marcont:hasContents

Used to identify table of contents (TOC)

OWL Type:
ObjectProperty
Domain:
marcont:Resource

Property: marcont:hasContributor

An entity responsible for making contributions to the content of the resource but not the author.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
foaf:Agent

Property: marcont:hasCoverage

The extent or the scope of the content of the given publication medium.

OWL Type:
ObjectProperty
Domain:
marcont:PublicationMedium
Range:
marcont:Coverage

Property: marcont:hasCreator

This property can be used to describe the creator of a given resource or of the given collection of resources. It can be either a person, a group or an organization.

OWL Type:
ObjectProperty
Range:
foaf:Agent

Property: marcont:hasDCMIType

Describes appropriate type for the resource according to the Dublin Core Metadata Initiative dictionary of types.

OWL Type:
ObjectProperty
Domain:
marcont:Resource

Property: marcont:hasDOI

Property refers to a Digital Object Identifier assigned to a given resource.

OWL Type:
DatatypeProperty
sub-property-of:
marcont:hasIdentifier

Property: marcont:hasDate

Date related to the entity. In case of Events, date of the occurrence.

OWL Type:
DatatypeProperty
sub-property-of:
dc:date
Domain:
marcont:Event
Range:
xsd:date

Property: marcont:hasDescription

Description of an event contains information that is to be viewable for the user (in contrast to dc:description property)

OWL Type:
DatatypeProperty
Domain:
marcont:Event
Range:
xsd:string

Property: marcont:hasDomain

Describes the domain of interest appropriate for the resource.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
skos:Concept

Property: marcont:hasEdition

The edition of a book, e.g., Second. This should be an ordinal, and should have the first letter capitalized, as shown here; the standard styles convert to lower case when necessary.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource
Range:
xsd:string

Property: marcont:hasEditor

Defines the editor of a given resource or collection of resources.

OWL Type:
ObjectProperty
sub-property-of:
marcont:hasHumanCreator

Property: marcont:hasEndDate

End date of copyright period.

OWL Type:
DatatypeProperty
sub-property-of:
marcont:hasDate
Domain:
marcont:Event
Range:
xsd:date

Property: marcont:hasHumanCreator

Property used to describe the creator of the resource or the collection of resources.

OWL Type:
ObjectProperty
sub-property-of:
marcont:hasCreator
Domain:
marcont:Resource
Range:
foaf:Person

Property: marcont:hasISBN

Assigns an identifier in the form of ISBN.

OWL Type:
DatatypeProperty
sub-property-of:
marcont:hasIdentifier
Domain:
marcont:Resource

Property: marcont:hasISSN

Represents the ISSN number assigned to a given resource.

OWL Type:
DatatypeProperty
sub-property-of:
marcont:hasIdentifier
Domain:
marcont:Resource

Property: marcont:hasIdentifier

This property represents the unique identifier of the resource.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource
Range:
xsd:string

Property: marcont:hasJournal

Journal where the article was published.

OWL Type:
ObjectProperty
Domain:
marcont:Article
Range:
marcont:Journal

Property: marcont:hasKeyword

Keyword related to the resource.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
skos:Concept

Property: marcont:hasMonth

The month in which the work was published or, for an unpublished work, in which it was written. You should use the standard three-letter abbreviation. Equivalent to bibtex:hasMonth property.

OWL Type:
DatatypeProperty
Domain:
marcont:Event, marcont:Resource
Range:
xsd:int

Property: marcont:hasNote

Any additional information that can help the reader.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource
Range:
xsd:string

Property: marcont:hasNumber

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

Property: marcont:hasOrder

Refers to the order of resources in Jerome Digital Library. Each resource is given a number to allow control over their order.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource
Range:
xsd:int

Property: marcont:hasOrganization

The organization that is involved in organizing an event or publishing given resource.

OWL Type:
ObjectProperty
Domain:
marcont:Resource, marcont:Event
Range:
marcont:Organization

Property: marcont:hasOriginalPublicationMedium

Describes an original publication medium of the resource. The medium is of a type marcont: AccessMedium.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
marcont:AccessMedium

Property: marcont:hasPages

Number of pages of the resource or chapter.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource
Range:
xsd:int

Property: marcont:hasPagesFrom

The starting page of the given document (article) in the collection (e.g., in-proceedings)

OWL Type:
DatatypeProperty
Domain:
marcont:Article
Range:
xsd:int

Property: marcont:hasPagesTo

The starting page of the given document (article) in the collection (e.g., in-proceedings)

OWL Type:
DatatypeProperty
Domain:
marcont:Article
Range:
xsd:int

Property: marcont:hasPublisher

Describes publisher of a given resource.

OWL Type:
ObjectProperty
OWL Type:
FunctionalProperty
Domain:
marcont:PublicationMedium
Range:
foaf:Agent

Property: marcont:hasRelatedEvent

Represents relation between a resource and an event.

OWL Type:
ObjectProperty
Domain:
marcont:PublicationMedium, marcont:Event
Range:
marcont:Event

Property: marcont:hasReview

Binds one (or more) reviews to the information object.

OWL Type:
ObjectProperty
OWL Type:
InverseFunctionalProperty
inverse-of:
sioc:related_to
Domain:
marcont:Resource
Range:
marcont:Review

Property: marcont:hasReviewDate

When the review of this library resource has been submitted.

OWL Type:
DatatypeProperty
OWL Type:
FunctionalProperty
sub-property-of:
marcont:hasDate
Domain:
marcont:Review
Range:
xsd:dateTime

Property: marcont:hasReviewer

Indicates who (or what process) has reviewed this library resource.

OWL Type:
ObjectProperty
OWL Type:
FunctionalProperty
sub-property-of:
sioc:has_creator
Domain:
marcont:Review
Range:
foaf:Agent

Property: marcont:hasReviewComment

Comment given by the reviewer in the review.

OWL Type:
DatatypeProperty
OWL Type:
FunctionalProperty
Domain:
marcont:Review
Range:
xsd:string

Property: marcont:hasSchool

University / school where the work was created/published

OWL Type:
ObjectProperty
sub-property-of:
marcont:hasOrganization
Domain:
marcont:Resource
Range:
marcont:University

Property: marcont:hasSeries

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

Property: marcont:hasSource

Used as citation property, equivalent to dc: source property.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
marcont:Resource

Property: marcont:hasSponsor

Sponsor of the Resource or the event.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
foaf:Agent

Property: marcont:hasTitle

The title of the work. This property is used to describe titles both of a given resource and an event.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource, marcont:Event
Range:
xsd:string

Property: marcont:hasTopic

Topic of the resource.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
skos:Concept

Property: marcont:hasURL

URI of the DCMI type or the resource.

OWL Type:
DatatypeProperty
Domain:
marcont:Event, marcont:Resource
Range:
xsd:string

Property: marcont:hasVolume

The volume of a journal or multi-volume book.

OWL Type:
DatatypeProperty
Range:
xsd:string

Property: marcont:hasYear

The year of publication or, for an unpublished work, the year it was written. Generally it should consist of four numerals, such as 1984.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource
Range:
xsd:string

Property: marcont:howPublished

How something strange has been published. The first word should be capitalized.

OWL Type:
DatatypeProperty
Domain:
marcont:Resource
Range:
xsd:string

Property: marcont:isPartOf

Represents a is-part-of relation between elements that belong to a collection or between collections.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
marcont:Resource

Property: marcont:isPeerOf

This property denotes that this agent is a peer of (in the scientific community meaning) another person 

OWL Type:
DatatypeProperty
OWL Type:
SymetricProperty
Domain:
foaf:Agent
Range:
foaf:Agent

Property: marcont:presentedAt

Relates given resource to an event where it was presented.

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
marcont:Event

Property: marcont:publishedIn

Defines publication medium where given resource was published  (Delete) rdfs:label : published in

OWL Type:
ObjectProperty
Domain:
marcont:Resource
Range:
marcont:PublicationMedium

Instance: marcont:IElectronic

Represents electronic media representations (CD-ROM and other)

RDF Type:
marcont:AccessMedium

Instance: marcont:IInternational

International coverage of a resource.

RDF Type:
marcont:Coverage

Instance: marcont:IInternet

Represents Internet accessible resources.

RDF Type:
marcont:AccessMedium

Instance: marcont:ILocal

Local coverage of the resource.

RDF Type:
marcont:Coverage

Instance: marcont:INational

National coverage of the resource.

RDF Type:
marcont:Coverage

Instance: marcont:IPrinted

Medium used to access resources physically available (e.g., printout)

RDF Type:
marcont:AccessMedium

JeromeDL Ontology 2.1 Specification

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

JeromeDL Ontology Index

An alphabetical index of JeromeDL terms, by class (categories or types) and by property.

Classes:

Properties:

JeromeDL cross-reference: Classes and Properties

JeromeDL structure ontology introduces the following classes and properties:

Class: jeromedl:BinaryResource

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.

sub-class-of:
jeromedl:InformationObject
in-domain-of:
jeromedl:hasMimeType, jeromedl:hasFileSize
in-range-of:
jeromedl:hasAttachment, jeromedl:hasRepresentation

Class: jeromedl:Chapter

Is a special type of jeromedl:Part information object for expressing chapter information.

sub-class-of:
jeromedl:Part

Class: jeromedl:ComputedResource

This is a virtual information object, which is computed out of other resources (disseminator).

sub-class-of:
jeromedl:InformationObject
in-domain-of:
jeromedl:actsOn, jeromedl:hasInvocationParam, jeromedl: invokesService
in-range-of:
jeromedl:hasRepresentation

Class: jeromedl:Context

This concept binds any kind of annotations to the information object.

in-range-of:
jeromedl:hasContext

Class: jeromedl:DynamicCollection

A collection created dynamically based on the provided specification.

in-domain-of:
jeromedl:hasSpecification, jeromedl:hasCollectionOrder, jeromedl:isSizeWithSubCollections, jeromedl:isUnion, jeromedl:hasCollectionSpecification, jeromedl:isVisible

Class: jeromedl:DynamicCollectionType

Class: jeromedl:ImageResource

The special type of media resources, i.e., all image resources (JPG, PNG).

sub-class-of:
jeromedl:MediaResource
in-range-of:
jeromedl:hasCover

Class: jeromedl:InformationObject

The most abstract type of a resource in the library (NOTE: this concept supersedes jdl1:Book)

in-domain-of:
jeromedl:hasSubmissionStatus, jeromedl:isUploadedBy, jeromedl:hasCopyrightsOwner,
jeromedl:hasVersionCreator, jeromedl: isReviewed, jeromedl:hasVersionNumber, jeromedl:hasVersionDate, jeromedl:hasCurrentVersion,
jeromedl:hasDescription, jeromedl:hasVersionComment, jeromedl: hasUploadDate,
jeromedl:hasContext, jeromedl:hasPreviousVersion
in-range-of:
jeromedl:hasPart, jeromedl:actsOn, jeromedl:hasCurrentVersion,
jeromedl:hasPreviousVersion

Class: jeromedl:MediaPart

The special type of jeromedl:Part, which references the multimedia content.

sub-class-of:
jeromedl:Part
in-domain-of:
jeromedl:hasSimplerRepresentation

Class: jeromedl:MediaResource

It is a generic binary type, the distinctive feature is its physical size and the scaling ability.

sub-class-of:
jeromedl:BinaryResource
in-domain-of:
jeromedl:isScaledToFit

Class: jeromedl:Page

Represents a single page in a chapter; usually used to capture a scanned page of an antique book.

sub-class-of:
jeromedl:Part
in-range-of:
jeromedl:hasPages

Class: jeromedl:Part

This is an information object that is a part of another information object.

sub-class-of:
jeromedl:Resource
in-domain-of:
jeromedl:hasRepresentation, jeromedl:hasNumberOfPages

Class: jeromedl:Resource

Represents the proper library resource (book, article, chapter, page).

sub-class-of:
jeromedl:InformationObject
in-domain-of:
jeromedl:hasPart, jeromedl:hasBookType, jeromedl:
isPreprintVersion

Class: jeromedl:ResourceType

Defines types of special Information Objects, i.e., Resources; these are the most high level information objects presented to the user.

in-domain-of:
skos:narrow
in-range-of:
jeromedl:hasBookType, skos:narrow

Class: jeromedl:ResourcesAggregationService

The aggregation service that can deliver a bunch of information objects in one go.

sub-class-of:
jeromedl:InformationObject
in-range-of:
jeromedl:hasParts

Class: jeromedl:SubmissionStatusType

Defines a list of individuals which cover the submission workflow status.

in-range-of:
jeromedl:hasSubmissionStatus

Property: jeromedl:actsOn

Specifies number of resources that are used as a source for computing the new resource.

OWL Type:
ObjectProperty
Domain:
jeromedl:ComputedResource
Range:
jeromedl:InformationObject

Property: jeromedl:hasAttachment

Indicates the attachment of an information object.

OWL Type:
ObjectProperty
sub-property-of:
jeromedl:hasPart
Range:
jeromedl:BinaryResource

Property: jeromedl:hasBookType

Defines type of the resource; used in the main classification scheme in JeromeDL

OWL Type:
ObjectProperty
Domain:
jeromedl:Resource
Range:
jeromedl:ResourceType

Property: jeromedl:hasCollectionOrder

The ordering number of the collection in the tree of collections (previously http://www.jeromedl.org/structure#collectionOrder)

OWL Type:
DatatypeProperty
Domain:
jeromedl:DynamicCollection
Range:
xsd:int

Property: jeromedl:hasCollectionSpecification

Literal/string representation of the specification of the collection (previously http://www.jeromedl.org/structure#collectionSpecification)

OWL Type:
DatatypeProperty
Domain:
jeromedl:DynamicCollection
Range:
xsd:string

Property: jeromedl:hasCollectionType

binds predefined type of collection to dynamic collection.

OWL Type:
ObjectProperty
OWL Type:
FunctionalProperty
Domain:
jeromedl:DynamicCollection
Range:
jeromedl:DynamicCollectionType

Property: jeromedl:hasContext

Used to bind multipurpose context to an information object

OWL Type:
ObjectProperty
OWL Type:
InverseFunctionalProperty (uniquely identifying property)
Domain:
jeromedl:InformationObject
Range:
jeromedl:Context

Property: jeromedl:hasCopyrightsOwner

Indicates who owns copyrights for given information object

OWL Type:
ObjectProperty
Domain:
jeromedl:InformationObject
Range:
foaf:Agent

Property: jeromedl:hasCover

Defines a binary resource (an image) that represents the cover of the information object; also used as a thumbnail of media resource

OWL Type:
ObjectProperty
sub-property-of:
jeromedl:hasPart
Range:
jeromedl:ImageResource

Property: jeromedl:hasCurrentVersion

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)

OWL Type:
ObjectProperty
Domain:
jeromedl:InformationObject
Range:
jeromedl:InformationObject

Property: jeromedl:hasDescription

A textual description on the information object

OWL Type:
DatatypeProperty
Domain:
jeromedl:InformationObject
Range:
xsd:string

Property: jeromedl:hasFileSize

Size of the binary file related to this resource

OWL Type:
DatatypeProperty
Domain:
jeromedl:BinaryResource
Range:
xsd:int

Property: jeromedl:hasInvocationParam

Defines parameter for invocation

OWL Type:
DatatypeProperty
Domain:
jeromedl:ComputedResource
Range:
xsd:string

Property: jeromedl:hasMimeType

MIME type of the binary resource

OWL Type:
DatatypeProperty
Domain:
jeromedl:BinaryResource
Range:
xsd:string

Property: jeromedl:hasNumberOfPages

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

OWL Type:
DatatypeProperty
Domain:
jeromedl:Part
Range:
xsd:int

Property: jeromedl:hasPages

Indicates the logical page in the resource (it can have binary resources like PNG, JPG and computed resources [disseminators] like DjVu)

OWL Type:
ObjectProperty
sub-property-of:
jeromedl:hasPart
Range:
jeromedl:Page

Property: jeromedl:hasPart

An abstract property to indicate that one information object contains another as its part

OWL Type:
ObjectProperty
Domain:
jeromedl:Resource
Range:
jeromedl:InformationObject

Property: jeromedl:hasParts

Points from an information object to aggregation service - e.g., we can point from chapter to a set of pages in one go

OWL Type:
ObjectProperty
sub-property-of:
jeromedl:hasPart
Range:
jeromedl:ResourcesAggregationService

Property: jeromedl:hasPosition

Used to indicate the position of the statement on the list

OWL Type:
DatatypeProperty
Range:
xsd:int

Property: jeromedl: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)

OWL Type:
ObjectProperty
OWL Type:
InverseFunctionalProperty (uniquely identifying property)
Domain:
jeromedl:InformationObject
Range:
jeromedl:InformationObject

Property: jeromedl:hasRepresentation

Binds binary resource or computed resource to the part resource

OWL Type:
ObjectProperty
sub-property-of:
jeromedl:hasPart
Domain:
jeromedl:Part
Range:
jeromedl:BinaryResource, jeromedl:ComputedResource

Property: jeromedl:hasSimplerRepresentation

Smaller representation of the file (e.g., SWF optimized for mobile access)

OWL Type:
ObjectProperty
sub-property-of:
jeromedl:hasRepresentation
Domain:
jeromedl:MediaPart

Property: jeromedl:hasSpecification

Defines the specification of a collection; can be a string literal with a structure processable by the dynamic collections module.

OWL Type:
ObjectProperty
Domain:
jeromedl:DynamicCollection

Property: jeromedl: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

OWL Type:
ObjectProperty
Domain:
jeromedl:InformationObject
Range:
jeromedl:SubmissionStatusType

Property: jeromedl:hasUploadDate

When the information object was uploaded

OWL Type:
DatatypeProperty
sub-property-of:
dc:date
Domain:
jeromedl:InformationObject
Range:
xsd:dateTime

Property: jeromedl:hasVersionComment

Comment explaining what has changed in this version

OWL Type:
DatatypeProperty
Domain:
jeromedl:InformationObject
Range:
xsd:string

Property: jeromedl:hasVersionCreator

A person who created this version

OWL Type:
ObjectProperty
Domain:
jeromedl:InformationObject
Range:
foaf:Person

Property: jeromedl:hasVersionDate

Defines date when this version of the information object was created

OWL Type:
DatatypeProperty
sub-property-of:
dc:date
Domain:
jeromedl:InformationObject
Range:
xsd:dateTime

Property: jeromedl:hasVersionNumber

A unique number of the version of the information object

OWL Type:
DatatypeProperty
Domain:
jeromedl:InformationObject
Range:
xsd:int

Property: jeromedl:invokesService

Defines the REST service which should be invoked to compute the result

OWL Type:
DatatypeProperty
Domain:
jeromedl:ComputedResource
Range:
xsd:string

Property: jeromedl:isPeerReviewed

Indicates whether the information object has been peer reviewed to check the correctness of the content

OWL Type:
DatatypeProperty
Domain:
jeromedl:Review
Range:
xsd:boolean

Property: jeromedl:isPreprintVersion

Defines if the information object is a preprint

OWL Type:
DatatypeProperty
Domain:
jeromedl:Resource
Range:
xsd:boolean

Property: jeromedl:isScaledToFit

Indicates should the media object be scaled to fit the content

OWL Type:
DatatypeProperty
Domain:
jeromedl:MediaResource
Range:
xsd:boolean

Property: jeromedl:isSizeWithSubCollections

Defines if collection contains items from sub-collection (previously
http://www.jeromedl.org/structure#sizeWithSubCollections)

OWL Type:
DatatypeProperty
Domain:
jeromedl:DynamicCollection
Range:
xsd:boolean

Property: jeromedl:isUnion

Defines if the collection is build as a union of specifications (previously
http://www.jeromedl.org/structure#isUnion)

OWL Type:
DatatypeProperty
Domain:
jeromedl:DynamicCollection
Range:
xsd:boolean

Property: jeromedl:isUploadedBy

The person who uploaded the given information object.

OWL Type:
ObjectProperty
Domain:
jeromedl:InformationObject
Range:
foaf:Agent

Property: jeromedl:isVisible

Defines if the collection is visible to the end user (previously jdl1:isVisible)

OWL Type:
DatatypeProperty
Domain:
jeromedl:DynamicCollection
Range:
xsd:boolean

Property: jeromedl:publishedAt

Specifies where a library resource was originally published

OWL Type:
ObjectProperty
Domain:
jeromedl:Resource

Evaluation Questionnaires

This appendix presents example of questionnaires (see Sec. 8.7) that were used during the evaluation (see Chapter 8) to gather users opinion, measure satisfaction and collect users answers in the question-answering tasks (see Sec. 8.2.3). Since participants using DSpace were asked to fill in slightly different questionnaires than those using JeromeDL we present both sets of questionnaires.

Additional and Detailed Evaluation Results

This appendix presents additional and more detailed results gathered during the evaluation (see Chapter 8).

Details of the Users Satisfaction Results

This section presents six tables with the details on user satisfaction metrics, gathered with the questionnaires during the evaluation. Table D.1 presents comparison of opinions of JeromeDL and DSpace users on various features implemented by both digital libraries. Since these tables deliver only more detailed view on results presented in Chapter 8 we do not describe them in details.

Table D.1: Tasks-based User Satisfaction Metrics
Evaluation task ease of understanding ease of execution intuitive- ness σ P
JeromeDL register 27.46 ( σ=25.01) 25.08 ( σ=22.47) 17.54 ( σ=24.42) 23.95  
DSpace register 32.69 ( σ=18.76) 29.77 ( σ=20.71) 22.31 ( σ=24.71) 28.89  
Δregistering
σ
-16.00% -15.76% -21.38% -17.12% 0.555
JeromeDL adv.search 33.15 ( σ=19.29) 15.46 ( σ=29.53) 11.15 ( σ=28.99) 21.81  
DSpace adv.search 32.62 ( σ=17.44) 17.46 ( σ=28.37) 13.69 ( σ=33.02) 22.88  
Δadv.search
σ
1.65% -11.45% -18.54% -4.66% 0.980
JeromeDL search 24.38 ( σ=24.65) 19.23 ( σ=23.54) 16.46 ( σ=23.91) 20.65  
DSpace search 31.08 ( σ=19.03) 21.08 ( σ=24.16) 13.85 ( σ=29.39) 23.3  
Δsearch
σ
-21.53% -8.76% 18.89% -11.37% 0.837
JeromeDL bookmark 32.00 ( σ=20.23) 20.46 ( σ=19.82) 20.31 ( σ=28.04) 25.36  
DSpace bookmark 19.85 ( σ=20.8) -3.08 ( σ=34.79) -7.23 ( σ=32.74) 5.56  
Δbookmarking
σ
61.24% -765.00% -380.85% 356.13% 0.029
JeromeDL task 1 24.38 ( σ=19.76) 10.77 ( σ=31.18) 7.15 ( σ=28.83) 15.57  
DSpace task 1 28.62 ( σ=24.43) 17.08 ( σ=22.74) 17.85 ( σ=20.55) 22.24  
Δtask.1
σ
-14.78% -36.94% -59.91% -29.99% 0.228

Table D.2: Tasks-based User Satisfaction Metrics (cont.)
Evaluation task ease ease intuitiveness σ  
  of understanding of execution     P
JeromeDL task 2 34.85 ( σ=16.55) 24.77 ( σ=22.54) 25.08 ( σ=21.85) 29.18  
DSpace task 2 11.00 ( σ=33.88) 1.00 ( σ=36.2) 3.00 ( σ=26.24) 5.86  
Δtask.2
σ
216.78% 2,376.92% 735.90% 398.12% 0.029
JeromeDL task 3 34.00 ( σ=19.08) 25.23 ( σ=22.9) 23.08 ( σ=22.01) 28.37  
DSpace task 3 10.38 ( σ=22.78) 18.15 ( σ=23.83) 11.46 ( σ=23.79) 12.91  
Δtask.3
σ
227.41% 38.98% 101.34% 119.74% 0.040

Table D.3 presents details of users satisfaction related to search and browsing mechanisms implemented by JeromeDL and DSpace systems.

Table D.3: Search-related Satisfaction
search task ease of use simplicity intuitiveness interestingness attractiveness usefulness
JeromeDL (1) 17.85 σ=22.06 17.46 σ=21.21 11.69 σ=20.1 17.31 σ=23.86 14.23 σ=21.89 20.77 σ=26.19
DSpace (1) 28.85 σ=19.81 16.15 σ=20.32 15.85 σ=18.52 -6.31 σ=17.61 -11.46 σ=20.18 9.38 σ=17.97
Δtask.1
σ [%]
-38.13% 8.10% -26.21% -374.39% -224.16% 121.31%
JeromeDL (2) 27.46 σ=19.58 21.77 σ=18.22 20.08 σ=21.5 17.92 σ=17.34 14.54 σ=21.08 21.77 σ=22.92
DSpace (2) 10.08 σ=28.01 6.38 σ=28.22 -0.85 σ=23.6 -14.08 σ=17.1 -16.92 σ=17.07 4.08 σ=24.62
Δtask.2
σ [%]
172.52% 240.96% -2,472.73% -227.32% -185.91% 433.96%
JeromeDL (3) 28.62 σ=15.71 23.46 σ=19.77 15.31 σ=21.44 22.38 σ=22.61 14.46 σ=23.13 24.00 σ=20.47
DSpace (3) 23.69 σ=25.75 15.85 σ=24.67 9.00 σ=25.64 -10.46 σ=17.75 -11.46 σ=17.9 4.62 σ=21.94
Δtask.3
σ [%]
20.78% 48.06% 70.09% -313.97% -226.17% 420.00%
           

Table D.4 compare satisfaction of JeromeDL related to semantic, social and recommendation features offered by the system.

Table D.4: Satisfaction Metrics for the Enhanced Features
Feature ease of use simplicity intuitiveness interestingness attractiveness usefulness σ
NLQ 7.85 σ=33.25 11.08 σ=26.54 8.69 σ=29.19 24.92 σ=27.26 12.31 σ=27.6 5.77 σ=27.6 9.8
TTM 4.54 σ=24.48 9.38 σ=20.75 0.62 σ=23.36 12.54 σ=19.51 3.85 σ=20.76 1.92 σ=24.23 4.65
Exhibit 9.38 σ=26.02 12.92 σ=17.38 5.23 σ=23.13 8.77 σ=21.7 10.08 σ=15.72 12.38 σ=22.55 10.04
MBB -6.38 σ=16.73 -2.85 σ=9.52 -3.23 σ=20.24 15.15 σ=20.16 13.54 σ=16.25 12.08 σ=16.29 2.8
SSCF 18.77 σ=28.69 16.31 σ=20.03 17.38 σ=22.13 19.54 σ=17.73 14.54 σ=19.46 18.46 σ=19.34 17.76
Collaborative Browse 6.92 σ=23.35 10.31 σ=14.11 10.23 σ=10.58 15.15 σ=17.38 8.77 σ=18.04 12.54 σ=15.81 10.28
Blog 14.92 σ=13.78 13.31 σ=12.65 13.00 σ=16.57 10.69 σ=14.07 9.77 σ=16.16 14.46 σ=18.39 13.44
Ranking 14.69 σ=23.16 13.85 σ=20.38 10.69 σ=21.46 8.46 σ=12.38 7.23 σ=14.17 13.62 σ=15.84 12.47
Recommend (Resource) 18.54 σ=21.77 21.77 σ=15.3 18.85 σ=19.74 20.08 σ=17.28 13.08 σ=18.45 20.62 σ=15.64 19.32
Recommend (SSCF) 20.85 σ=19.54 16.31 σ=21.43 10.23 σ=19.22 15.00 σ=18.56 10.92 σ=20.82 16.15 σ=17.26 15.83

Table D.5 compares users overall satisfaction measured before and after the evaluation.

Table D.5: Comparison between Overall Impression Before and After Using the Library
  ease of use simplicity intuitiveness interestingness attractiveness usefulness  
JeromeDL pre 13.46 ( σ=23.8) 8.54 ( σ=19.03) 8.15 ( σ=21.83) 11.54 ( σ=19.8) 14.54 ( σ=21.52) 24.15 ( σ=17.19)  
JeromeDL post 18.38 ( σ=22.52) 14.38 ( σ=18.28) 6.62 ( σ=24.71) 24.00 ( σ=18.77) 14.85 ( σ=21.38) 22.62 ( σ=19.87)  
DSpace pre 11.92 ( σ=24.36) 7.54 ( σ=18.43) 5.15 ( σ=22.02) -11.46 ( σ=22.73) -8.38 ( σ=24.26) 4.00 ( σ=19.7)  
DSpace post 16.69 ( σ=23.51) 5.92 ( σ=21.5) 6.77 ( σ=26.21) -12.85 ( σ=26.57) -14.85 ( σ=24.06) 9.92 ( σ=24.2)  
Δpre
σ [%]
12.90 13.27 58.21 200.67 273.39 503.85  
Δpost
σ [%]
10.14 142.86 -2.27 286.83 200.00 127.91  
             

Table D.6 compares overall satisfaction of JeromeDL users from using semantic and social features.

Table: General Satisfaction ( σ) of Semantic and Social Features
Enhancement type ease of use ease of understanding ease of execution simplicity intuitiveness
Semantic 4.54 σ=21.61 2.85 σ=21.38 4.46 σ=24.81 5.85 σ=17.58 1.08 σ=22.27
Social 25.62 σ=16.01 23.92 σ=12.61 15.23 σ=19.46 10.31 σ=19.73 11.46 σ=24.21
Enhancement type interestingness attractiveness usefulness σ  
Semantic 25.38 σ=18.18 12.77 σ=21.99 21.31 σ=25.21 8.65  
Social 26.77 σ=19.36 22.85 σ=23.45 29.77 σ=17.05 21.27  

Finally, Table D.7 compares satisfaction of JeromeDL and DSpace users during the memory task.

Table D.7: Task-based Satisfaction for the Memory Task
  ease of understanding ease of execution intuitiveness σ
JeromeDL 29.11 ( σ=18.95) 2.00 ( σ=27.11) 21.11 ( σ=16.13) 19.08
DSpace 10.89 ( σ=23.90) -17.22 ( σ=30.89) -1.00 ( σ=24.90) -0.54
σ 167.35% 111.61% 2,211.11% 3,635.37%

Users Opinion on Particular Search and Browsing Features

After the evaluation we have asked JeromeDL users to select up to three (3) features which they liked, did not liked, found useful, and found useless (see Fig. D.1).

Most of the JeromeDL users liked the simple search and bookmarking feature; only a few less liked SSCF (collaborative filtering), natural language queries (NLQ), TTM, and resource recommendations. Other features were not so highly rated, and some of them, e.g., Exhibit and MBB, were actually disliked by many participants. Surprisingly equally many participants did not like NLQ, TTM, and advanced search. This can be caused by the complexity of the latter two, and limited set of queries supported by NLQ during the evaluation (only those that come with the default JeromeDL distribution).

Figure D.1: Average Number of References




From the perspective of usability of features implemented in JeromeDL, the search and bookmarking (including SSCF) were the most favorable. TTM, MBB, NLQ, and Exhibit were found pretty useless. In our opinion, it was mainly caused by the complexity of these solutions compared to the tasks users were asked to perform, i.e., answer three questions.

JeromeDL Tutorial Videos

For the purpose of the evaluation presented in Chapter 8, we have recorded nine tutorial videos (screencasts) presenting key features of JeromeDL.

These tutorial videos were published on two movies sharing sites: http://blip.tv/ and http://www.vimeo.com/. On the blip.tv site a dedicated channel has been created to feature these and future JeromeDL tutorial videos: http://jeromedl.blip.tv/. Similar channel has been also created on the vimeo.com service: http://vimeo.com/channels/54414.

The complete set of JeromeDL tutorial videos consists of the following screencasts:

Additionally, a short tutorial on JeromeDL has been publish to
http://www.slideshare.net/skruk/jeromedl-tutorial. It provides some more details about JeromeDL, with pointers to the tutorial videos listed above.

Scores Assigned During the Evaluation

This appendix presents scores which were assigned to articles from the reference database (RefDB, see Table A.1) and other articles (see Table A.2) cited by the participants of the evaluation (see Chapter 8). The scores were assigned based on how well each article answered given questions; we used the Score(ref, q) function (see Eq. 8.2) defined in Chapter 8.

Table A.1: Scores Assigned to the Referenced Articles
Article Q1 Q2 Q3 Q4 Q5 Q6 Q7
Morahan-Martin and Schumacher (2003) 0 0 1 0 0 2 0
Metzger et al. (2003a) 2 2 0 0 2 0 0
Wathen and Burkell (2002) 2 2 0 0 2 0 0
Amiel and Sargent (2004) 0 0 2 0 0 2 0
Hills and Argyle (2003) 0 0 2 0 0 2 0
Liu (2004) 0 1 0 0 0 0 0
Landers and Lounsbury (2006) 0 0 2 0 0 2 0
Leung (2003) 0 0 0 1 0 0 1
Klein et al. (2003) 0 0 0 2 0 0 0
Flanagin and Metzger (2001) 2 2 0 0 2 0 0
Hebert and Vorauer (2003) 0 0 0 2 0 0 0
Sanders et al. (2000) 0 0 0 2 0 1 0
Amichai-Hamburger (2002) 0 0 2 0 0 2 0
Bierhoff and Vornefeld (2004) 0 0 0 1 1 0 0
McKenna and Green (2002) 0 0 0 1 0 0 0

Article Q1 Q2 Q3 Q4 Q5 Q6 Q7
Hamburger et al. (2004) 0 0 2 0 0 2 0
Swickert et al. (2002) 0 0 2 0 0 2 0
Jackson et al. (2001) 0 0 2 0 0 2 0
Nithya and Julius (2007) 0 0 2 0 0 2 0
Tidwell and Walther (2002) 0 0 0 2 0 0 0
Anolli et al. (2005) 0 0 2 0 0 2 0
Burgoon et al. (2000) 2 2 0 0 1 0 0
McKenna and Bargh (2000) 0 0 1 0 0 1 0
Kaye and Johnson (2004) 1 1 0 0 1 0 0
Metzger et al. (2003b) 2 2 0 0 2 0 0
Hamburger and Ben-Artzi (2000) 0 0 0 2 0 0 0
Kiousis (2001) 1 1 0 0 2 0 0
Flanagin and Metzger (2000) 2 2 0 0 2 0 0
Schrodt and Turman (2005) 0 0 0 0 0 0 2
Tseng and Fogg (1999) 1 1 0 0 0 0 0
Metzger et al. (2003c) 1 1 0 0 1 0 0
Kraut et al. (2002) 0 0 2 0 0 2 0
Bonebrake (2002) 0 0 2 0 0 2 0
Stanton and Stanton (2001) 0 0 1 0 0 2 0
Fogg and Tseng (1999) 0 2 0 0 0 0 0

Table A.2: Scores Assigned to the Non-Referenced Articles Cited by Participants
Article Q1 Q2 Q3 Q4 Q5 Q6 Q7
Enguix (2005a) -2 -2 -2 -2 -2 -2 -2
Enguix (2005b) -2 -2 -2 -2 -2 -2 -2
Dervan et al. (2006) -2 -2 -2 -2 -2 -2 -1
Hall et al. (2007) -2 -2 -2 -2 -2 -2 -1
Dervan and McDaniel (2007) -2 -2 -2 -2 -2 -2 -1
Duval et al. (2007) -2 -2 -2 -2 -2 -2 -1
Dobrzanski (2007) -2 -2 -2 -2 -2 -2 -2
Nagle and Golden (2006) -2 -2 -2 -2 -2 -2 -2
Eysenck and Keane (2005) -2 -2 -2 -2 1 -2 -2
Kruk et al. (2007) -2 -2 -2 -2 -2 -2 -2
Westerski et al. (2006) -2 -2 -2 -2 -2 -2 -2
Jankowski (2007) -2 -2 -2 -2 -2 -2 -2


Articles Correctly References in the Evaluation

  1. Amichai-Hamburger, Y. (2002).
    Internet and personality.
    Computers in Human Behavior, 18(1):1-10.
  2. Amiel, T. and Sargent, S. L. (2004).
    Individual differences in internet usage motives.
    Computers in Human Behavior, 20(6):711-726.
  3. Anolli, L., Villani, D., and Riva, G. (2005).
    Personality of people using chat: An on-line research.
    Cyberpsychol Behav., 8(1):89-95.
  4. Bierhoff, H.-W. and Vornefeld, B. (2004).
    The social psychlogy of trust with applications in the internet.
    Trust and Distrust in Online Communities: Theoretical and Methodological contributions from Social Psychology, 26:48-62.
  5. Bonebrake, K. (2002).
    College students' internet use, relationship formation, and personality correlates.
    CyberPsychology & Behavior, 5(6):551-557.
  6. Burgoon, J., Bonito, J., Bengtsson, B., Cederberg, C., Lundeberg, M., and Allspach, L. (2000).
    Interactivity in human - computer interaction: a study of credibility, understanding, and influence.
    Computers in Human Behavior, 16(6):553-574.
  7. Flanagin, A. J. and Metzger, M. J. (2000).
    Perceptions of internet information credibility.
    Journalism and Mass Communication Quarterly, 77(3):515-40.
  8. Flanagin, A. J. and Metzger, M. J. (2001).
    Internet use in the contemporary media environment.
    Human communication research, 27(1):153-181.
  9. Fogg, B. and Tseng, H. (1999).
    The elements of computer credibility.
    In Proceedings of the SIGCHI conference on Human factors in computing systems: the CHI is the limit, pages 80 - 87. ACM New York, NY, USA.
  10. Hamburger, Y. and Ben-Artzi, E. (2000).
    The relationship between extraversion and neuroticism and the different uses of the internet.
    Computers in Human Behavior, 16(4):441-449.
  11. Hamburger, Y., Fine, A., and Goldstein, A. (2004).
    The impact of internet interactivity and need for closure on consumer preference.
    Computers in Human Behavior, 20(1):103-117.
  12. Hebert, B. G. and Vorauer, J. D. (2003).
    Seeing through the screen: Is evaluative feedback communicated more effectively in face-to-face or computer-mediated exchanges?
    Computers in Human Behavior, 19(1):25-38.
  13. Hills, P. and Argyle, M. (2003).
    Uses of the internet and their relationships with individual differences in personality.
    Computers in Human Behavior, 19(1):59-70.
  14. Jackson, L. A., Ervin, K. S., Gardner, P. D., and Schmitt, N. (2001).
    Gender and the internet: Women communicating and men searching.
    Sex Roles, 44(5-6):363-379.
  15. Kaye, B. K. and Johnson, T. J. (2004).
    A web for all reasons: uses and gratifications of internet components for political information.
    Telematics and Informatics, 21(3):197-223.
  16. Kiousis, S. (2001).
    Public trust or mistrust? perceptions of media credibility in the information age.
    Mass Communication & Society, 4(4):381-403.
  17. Klein, E. E., Clark, C. C., and Herskovitz, P. J. (2003).
    Philosophical dimensions of anonymity in group support systems: Ethical implications of social psychological consequences.
    Computers in Human Behavior, 19(3):355-382.
  18. Kraut, R., Kiesler, S., Boneva, B., Cummings, J., Helgeson, V., and Crawford, A. (2002).
    Internet paradox revisited.
    Journal of social issues, 58(1):49-74.
  19. Landers, R. N. and Lounsbury, J. W. (2006).
    An investigation of big five and narrow personality traits in relation to internet usage.
    Computers in Human Behavior, 22(2):283-293.
  20. Leung, L. (2003).
    Impacts of net-generation attributes, seductive properties of the internet, and gratifications-obtained on internet use.
    Telematics and Informatics, 20(2):107 - 129.
  21. Liu, Z. (2004).
    Perceptions of credibility of scholarly information on the web.
    Information Processing and Management: an International Journal, 40(6):1027 - 1038.
  22. McKenna, K. Y. A. and Bargh, J. A. (2000).
    Plan 9 from cyberspace: The implications of the internet for personality and social psychology.
    Personality and social psychology review, 4(1):57-75.
  23. McKenna, K. Y. A. and Green, A. S. (2002).
    Group dynamics: Theory, research, and practice.
    Group Dynamics: Theory, Research, and Practice, 6(1):116-127.
  24. Metzger, M. J., Flanagin, A. J., Eyal, K., Lemus, D. R., and Mccann, R. M. (2003a).
    Credibility for the 21st century: Integrating perspectives on source, message, and media credibility in the contemporary media environment.
    Communication Yearbook, 27(1):293-335.
  25. Metzger, M. J., Flanagin, A. J., and Zwarun, L. (2003b).
    College student web use, perceptions of information credibility, and verification behavior.
    Computers & Education, 41(3):271 - 290.
  26. Metzger, M. J., Flanagin, A. J., and Zwarun, L. (2003c).
    An experimental examination of readers' perceptions of media bias.
    Journalism and Mass Communication Quarterly, 80(2):282-294.
  27. Morahan-Martin, J. and Schumacher, P. (2003).
    Computers in Human Behavior, 19(6):659-671.
  28. Nithya, H. and Julius, S. (2007).
    Extroversion, neuroticism and self-concept: Their impact on internet users in india.
    Computers in Human Behavior, 23(3):1322-1328.
  29. Sanders, C. E., Field, T. M., Diego, M., and Kaplan, M. (2000).
    The relationship of internet use to depression and social isolation among adolescents.
    Adolescence, 35(138):237-242.
  30. Schrodt, P. and Turman, P. D. (2005).
    The impact of instructional technology use, course design, and sex differences on students' initial perceptions of instructor credibility.
    Communication Studies, 56.
  31. Stanton, A. D. and Stanton, W. W. (2001).
    To click or not to click: Personality characteristics of internet versus non-internet purchasers.
  32. Swickert, R. J., Hittner, J. B., Harris, J. L., and Herring, J. A. (2002).
    Relationships among internet use, personality, and social support.
    Computers in Human Behavior, 18(4):437-451.
  33. Tidwell, L. C. and Walther, J. B. (2002).
    Computer-mediated communication effects on disclosure, impressions, and interpersonal evaluations: Getting to know one another a bit at a time.
    Human Communication Research, 28(3):317-348.
  34. Tseng, S. and Fogg, B. J. (1999).
    Credibility and computing technology.
    Communications of the ACM, 42(5):39 - 44.
  35. Wathen, C. N. and Burkell, J. (2002).
    Belive it or not: Factors influencing credibility on the web.
    Journal of the American Society for Information Science and Technology, 53(2):134 - 144.

Non-Referenced Articles Cited by Participants

  1. Dervan, S., McCosker, C., McDaniel, B., and O'Nuallain, C. (2006).
    Educational multimedia.
    In Proceeding of m-ICTE 2006.
  2. Dervan, S. and McDaniel, B. (2007).
    Practice perfect - an intelligent music tutoring system for assisting and improving practice and exam preparation.
    In ED-MEDIA-World Conference on Educational Multimedia, Hypermedia & Telecommunications.
  3. Dobrzanski, J. (2007).
    Employing social semantic information sources for e-learning.
    In Proceedings of the Faculty Research Day, NUIG.
  4. Duval, E., Klamma, R., and Wolpers, M. (2007).
    Creating New Learning Experiences on a Global Scale, volume 4753 of Lecture Notes in Computer Science.
    Springer.
  5. Enguix, C. F. (2005a).
    D03.02 semantic web data versioning methodology and implementation.
    Technical Report 1.03, DERI.
    DERI Lion Deliverable 1.03.
  6. Enguix, C. F. (2005b).
    Semantic web data versioning methodology and implementation.
    Technical report, DERI.
    DERI Lion Deliverables 1.03.
  7. Eysenck, M. and Keane, M. (2005).
    Cognitive Psychology - A Student's Handbook.
    Psychology Press Ltd.
  8. Hall, T., McCauley, V., and Dervan, S. (2007).
    Getting something ''out of school'' children's informal learning with novel technology.
    In Proceedings of American Educational Research Association.
  9. Jankowski, J. (2007).
    Copernicus - virtual encyclopedia.
    Deri elite project deliverable 1.6.11, DERI.
  10. Kruk, S. R., Gzella, A., Dobrzanski, J., McDaniel, B., and Woroniecki, T. (2007).
    E-learning on the social semantic information sources.
    In Second European Conference on Technology Enhanced Learning.
  11. Nagle, T. and Golden, W. (2006).
    E-learning bussiness models: a multiple case study.
    In The Irish Academy of Management Conference (2006).
  12. Westerski, A., Kruk, S. R., Samp, K., Woroniecki, T., Czaja, F., and O'Nuallain, C. (2006).
    E-learning based on the social semantic information sources.
    In Proceedings of LACLO 2006.
Syndicate content