ColActDOnt - Collaborative Actions on Documents Ontology
type: Ontology
version IRI: https://w3id.org/ColActDOnt/1.0
creator: Martin Just
creator: Petra Schubert
date: 06/2022
description: The Collaborative Actions on Documents Ontology (ColActDOnt) expresses the structure of actions on documents within collaboration systems.
publisher: https://ceir.de
rights: https://creativecommons.org/licenses/by/4.0
version info: 1.0

action
type: DatatypeProperty
type: FunctionalProperty
domain: Event
range: string
range: Datatype
  one of: CREATED
  one of: DELETED
  one of: READ
  one of: UPDATED

Account
type: Class
subclass of: Restriction
  on property: account contained in system
  qualified cardinality: 1
  on class: System
subclass of: Restriction
  on property: account of agent
  qualified cardinality: 1
  on class: Agent
subclass of: Restriction
  on property: account has socialProfile
  max qualified cardinality: 1
  on class: SocialProfile
disjoint with: Agent
disjoint with: DigitalWorkspace
disjoint with: Event
disjoint with: Group
disjoint with: OrganisationalGroup
disjoint with: Role
disjoint with: System
disjoint with: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: An Account is the technical means for an Agent to connect to a computer system.

Agent
type: Class
disjoint with: DigitalWorkspace
disjoint with: Event
disjoint with: Group
disjoint with: OrganisationalGroup
disjoint with: Role
disjoint with: System
disjoint with: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: An Agent is the meta term for a real Person, an ArtificialAgent (e. g. a bot) or an Organisation.

ArtificialAgent
type: Class
subclass of: Agent
disjoint with: Organisation
disjoint with: Person
comment: The ArtificialAgent is an entity to address bots or similar non-human Agents.

Calendar
type: Class
subclass of: Container
disjoint with: ChatChannel
disjoint with: FileLibrary
disjoint with: MailContainer
disjoint with: MeetingContainer
disjoint with: SocialProfileContainer
disjoint with: MessageBoard
disjoint with: MicroBlog
disjoint with: TaskContainer
disjoint with: Weblog
disjoint with: Wiki
comment: The Calendar entity corresponds to a Container that can contain CalendarEvents.

CalendarEntry
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: calendarEntry contained in calendar
  qualified cardinality: 1
  on class: Calendar
disjoint with: ChatMessage
disjoint with: Folder
disjoint with: MailMessage
disjoint with: Meeting
disjoint with: SocialProfile
disjoint with: WikiPage
disjoint with: BlogPost
disjoint with: BoardPost
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: CalendarEntries describe the Entities that hold information on records in a Calendar.

ChatChannel
type: Class
subclass of: Container
disjoint with: FileLibrary
disjoint with: MailContainer
disjoint with: MeetingContainer
disjoint with: SocialProfileContainer
disjoint with: MessageBoard
disjoint with: MicroBlog
disjoint with: TaskContainer
disjoint with: Weblog
disjoint with: Wiki
comment: The ChatChannel entity corresponds to a Container that can hold ChatMessages.

ChatMessage
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: chatMessage contained in chatChannel
  qualified cardinality: 1
  on class: ChatChannel
disjoint with: Folder
disjoint with: MailMessage
disjoint with: Meeting
disjoint with: SocialProfile
disjoint with: WikiPage
disjoint with: BlogPost
disjoint with: BoardPost
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: ChatMessages are text which is stored within ChatChannels.

DigitalWorkspace
type: Class
subclass of: Restriction
  on property: digitalWorkspace contains system
  min qualified cardinality: 1
  on class: System
subclass of: Restriction
  on property: digitalWorkspace has agent
  min qualified cardinality: 1
  on class: Agent
disjoint with: Event
disjoint with: Group
disjoint with: OrganisationalGroup
disjoint with: Role
disjoint with: System
disjoint with: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: A DigitalWorkspace is a combination of functional modules selected for a specific work group (multi-system concept).

Event
type: Class
subclass of: Restriction
  on property: event affects item
  qualified cardinality: 1
  on class: Item
subclass of: Restriction
  on property: event performed by account
  qualified cardinality: 1
  on class: Account
disjoint with: Group
disjoint with: OrganisationalGroup
disjoint with: Role
disjoint with: System
disjoint with: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: Events are digital records of the use of software functions by users in software. They are stored in event logs. For use in Process Mining, events must contain (1) an attribute that can be used to identify a particular process instance (the so-called Case ID), (2) the user and the performed activity and (3) a timestamp. In collaboration systems, events describe user actions on content items.

FileLibrary
type: Class
subclass of: Container
disjoint with: MailContainer
disjoint with: MeetingContainer
disjoint with: SocialProfileContainer
disjoint with: MessageBoard
disjoint with: MicroBlog
disjoint with: TaskContainer
disjoint with: Weblog
disjoint with: Wiki
comment: FileLibraries serve as a parent structure for Files and Folders.

Folder
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: folder contained in fileLibrary
  qualified cardinality: 1
  on class: FileLibrary
subclass of: Restriction
  on property: folder has parent
  max qualified cardinality: 1
  on class: Folder
disjoint with: MailMessage
disjoint with: Meeting
disjoint with: SocialProfile
disjoint with: WikiPage
disjoint with: BlogPost
disjoint with: BoardPost
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: Folders are used to structure Files within FileLibraries. Folders may only inherit little or no intellectual content.

Follow
type: Class
subclass of: SimpleComponent
disjoint with: Reaction
disjoint with: Subscription
disjoint with: Vote
disjoint with: Like
disjoint with: Tag
comment: A Follow is a SimpleComponent that describes that an IntellectualEntity (and theoretically also an IntellectualComponent) is followed. This means that the user is informed about changes to the corresponding Item within the System.

Group
type: Class
disjoint with: OrganisationalGroup
disjoint with: Role
disjoint with: System
disjoint with: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: Groups usually reflect organisational structures or working groups within Systems.

MailContainer
type: Class
subclass of: Container
disjoint with: MeetingContainer
disjoint with: SocialProfileContainer
disjoint with: MessageBoard
disjoint with: MicroBlog
disjoint with: TaskContainer
disjoint with: Weblog
disjoint with: Wiki
comment: MailContainers are Containers that can contain MailMessages.

MailMessage
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: mailMessage contained in mailContainer
  qualified cardinality: 1
  on class: MailContainer
disjoint with: Meeting
disjoint with: SocialProfile
disjoint with: WikiPage
disjoint with: BlogPost
disjoint with: BoardPost
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: A MailMessage is an IntellectualEntity that can hold various intellectualContent and is stored in MailContainers.

Meeting
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: meeting contained in meetingContainer
  qualified cardinality: 1
  on class: MeetingContainer
disjoint with: SocialProfile
disjoint with: WikiPage
disjoint with: BlogPost
disjoint with: BoardPost
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: We refer to Meetings as persistent information retained from synchronous communitcations such as voice chat or video conferencing. This type of IntellectualEntity can be transcripts or audio/video files of the actual Meetings.

MeetingContainer
type: Class
subclass of: Container
disjoint with: SocialProfileContainer
disjoint with: MessageBoard
disjoint with: MicroBlog
disjoint with: TaskContainer
disjoint with: Weblog
disjoint with: Wiki
comment: MeetingContainers are the parent structure (Container) for Meetings like video conferences and voice chats.

Organisation
type: Class
subclass of: Agent
disjoint with: Person
comment: The Organisation entity is a subclass of the Agent entity and describes a company as an Agent to which an Account can be assigned. Even though each employee usually has his or her own Account in an ECS, it is still possible for there to be a "company account". Further Agents (e.g. a Person) can also be assigned to an Organisation. In this way, it is possible to observe processes across company boundaries in later analyses.

OrganisationalGroup
type: Class
disjoint with: Role
disjoint with: System
disjoint with: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: OrganisationalGroups aggregate Agents and relate those to DigitalWorkspaces.

Person
type: Class
subclass of: Agent
comment: A Person is a specific form of Agent. Persons correspond to "natural" persons and are used to be able to analyse a real person across different Systems. This is made possible by the fact that the Accounts from the different Systems converge here.

Reaction
type: Class
subclass of: SimpleComponent
disjoint with: Subscription
disjoint with: Vote
disjoint with: Like
disjoint with: Tag
comment: A Reaction usually refers to emojis or similar that occur as a "reaction" to an Item.

Role
type: Class
disjoint with: System
disjoint with: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: Roles (e.g. manager, member) originate from system-internal rights management and can be assigned to Accounts and Groups.

SocialProfile
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: socialProfile contained in socialProfileContainer
  qualified cardinality: 1
  on class: SocialProfileContainer
disjoint with: WikiPage
disjoint with: BlogPost
disjoint with: BoardPost
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: The SocialProfiles represent the informational user directory, while the Accounts are stored in the technical user directory. The separation of the two entities was done because not every ECS has an informational user directory. In addition, it makes sense to assign certain object properties to only one of the two user directories, since there are technical differences between these entities within the systems. The entity belongs to the IntellectualEntities and carries the content of the profile as content. In the FOAF ontology, the PersonalProfileDocument entity is defined, which assigns further properties to a person in relation to a "document". Accordingly, the focus of the entity from the FOAF ontology is on the "Document", whereas in the ColActDOnt the profile itself is understood as intellectual content.

SocialProfileContainer
type: Class
subclass of: Container
disjoint with: MessageBoard
disjoint with: MicroBlog
disjoint with: TaskContainer
disjoint with: Weblog
disjoint with: Wiki
comment: A SocialProfileContainer contains the SocialProfiles of Accounts. Thus, this concept contains the informational user directory.

Subscription
type: Class
subclass of: SimpleComponent
disjoint with: Vote
disjoint with: Like
disjoint with: Tag
comment: A Subscription describes that an IntellectualEntity is "subscribed". The difference between Follow and Subscription lies in the fact that Subscription is based on the assumption of a system-external notification by email.

System
type: Class
subclass of: Restriction
  on property: system contains account
  min qualified cardinality: 1
  on class: Account
disjoint with: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: ColActDOnt uses the term system for a software product that provides functional modules that allow users to create content (items). A very small system can consist of only one functional module. Integrated systems contain multiple different functional modules under a joint interface. A system is characterised by the following important aspects. A system… … provides spaces for groups. Spaces are areas of the system that can only be accessed by the users that are in the member list of that space. … has its own independent user directory (UD). This “internal” UD needs to be linked to the central UD to enable single-sign-on (SSO) for users. … uses its own proprietary logging format. In many cases, systems are provided by a single software vendor. Integrated systems, however, can contain functional modules from third parties which then become an integral part of the system (e. g. HuddoBoards in HCL Connections). Following this definition, systems in ColActDOnt can range from lightweight tools with one/few functions to large-scale integrated Enterprise Collaboration Systems (ECS) (e.g. Alfresco or HCL Connections) with many different software modules. Organisations combine portfolios of “systems” to build Enterprise Collaboration Platforms (ECP).

Vote
type: Class
subclass of: SimpleComponent
disjoint with: Like
disjoint with: Tag
comment: Votes are SimpleComponents, which represent feedback on other Items.

WikiPage
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: wikiPage contained in wiki
  qualified cardinality: 1
  on class: Wiki
subclass of: Restriction
  on property: wikiPage has parent
  max qualified cardinality: 1
  on class: WikiPage
disjoint with: BlogPost
disjoint with: BoardPost
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: WikiPages correspond to the entries in a wiki. Within a wiki, they are usually represented as a separate "page". Replies to a WikiPage are mapped to the Comment entity. Attachments, which are not part of the actual content, are called Attachment.

Attachment
type: Class
subclass of: IntellectualComponent
subclass of: Restriction
  on property: attachment contained in comment
  max qualified cardinality: 1
  on class: Comment
disjoint with: Comment
comment: The Attachment is one of the IntellectualComponents and describes an appendage of intellectual content to an IntellectualEntity or to a Comment.

BlogPost
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: blogPost contained in weblog
  qualified cardinality: 1
  on class: Weblog
disjoint with: BoardPost
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: BlogPosts belong to the IntellectualEntities and thus describe entries that are posted in Weblogs.

BoardPost
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: boardPost contained in messageBoard
  qualified cardinality: 1
  on class: MessageBoard
disjoint with: File
disjoint with: MicroblogPost
disjoint with: Task
comment: BoardPosts belong to the IntellectualEntities and thus describe entries that are made in message boards, also called forums. Responses to BoardPosts are called Comments, since they, as an IntellectualComponents, extend SocialDocuments.

Collection
type: Class
subclass of: Restriction
  on property: collection contains socialDocument
  min qualified cardinality: 2
  on class: SocialDocument
subclass of: Restriction
  on property: collection has parent
  max qualified cardinality: 1
  on class: Collection
disjoint with: Container
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: A Collection is a set of at least two SocialDocuments, which is used to group SocialDocuments. Collections can be used to represent hierarchical structures through the child and parent relations.

Comment
type: Class
subclass of: IntellectualComponent
subclass of: Restriction
  on property: comment has parent
  max qualified cardinality: 1
  on class: Comment
subclass of: Restriction
  on property: comment of attachment
  max qualified cardinality: 1
  on class: Attachment
comment: The Comment entity is an IntellectualComponent that contains intellectual content about Attachments or IntellectualEntities.

Component
type: Class
subclass of: Item
subclass of: Restriction
  on property: component of intellectualEntity
  qualified cardinality: 1
  on class: IntellectualEntity
disjoint with: IntellectualEntity
comment: The Component entity is an abstract class that is used to assign an IntellectualEntity to each of the subclasses IntellectualComponent and SimpleComponent. Accordingly, this class only supports the "bundling" of the sub-classes.

Container
type: Class
subclass of: Restriction
  on property: container contained in space
  qualified cardinality: 1
  on class: Space
disjoint with: Item
disjoint with: SocialDocument
disjoint with: Space
comment: The Container entity serves as a superclass for the various subordinate classes, which in turn can contain the various forms of IntellectualEntities. With the Containers, just as with the Collections, nested structures can be created through the child-parent relations. The concept is always assigned to a Space and contains SocialDocuments whose IntellectualEntities correspond to the same type. Containers can be created automatically by the application or manually by the user. A Container is the content store used by a functional module. To give an example, a chat message in Skype (= the functional module) is stored in a “chat channel” (= the container).

File
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: file contained in fileLibrary
  qualified cardinality: 1
  on class: FileLibrary
disjoint with: MicroblogPost
disjoint with: Task
comment: A file is used to represent files that have been created within or uploaded to a collaboration system. Files that are to be assigned to other IntellectualEntities are excluded.

GroupWorkspace
type: Class
subclass of: Space
disjoint with: OrganisationalPlatform
disjoint with: UserWorkspace
comment: GroupWorkspaces describe spaces that are accessible to several people. Thus, they are positioned between UserWorkspace and OrganisationalPlatform and enable collaborative work, since they include the respective containers.

IntellectualComponent
type: Class
subclass of: Component
subclass of: Restriction
  on property: intellectualComponent has recentVersion
  qualified cardinality: 1
  on class: IntellectualComponent
disjoint with: SimpleComponent
comment: Attachments and Comments are subordinated to the IntellectualComponent entity. These differ from SimpleComponents by their "intellectual content".

IntellectualEntity
type: Class
subclass of: Item
subclass of: Restriction
  on property: intellectualEntity contained in container
  qualified cardinality: 1
  on class: Container
subclass of: Restriction
  on property: intellectualEntity has recentVersion
  qualified cardinality: 1
  on class: IntellectualEntity
subclass of: Restriction
  on property: intellectualEntity has nextVersion
  max qualified cardinality: 1
  on class: IntellectualEntity
subclass of: Restriction
  on property: intellectualEntity has previousVersion
  max qualified cardinality: 1
  on class: IntellectualEntity
comment: IntellectualEntities describe the core of a SocialDocument, for example a File or a BlogPost, which can be enriched by Components.

Item
type: Class
subclass of: Restriction
  on property: item created by account
  qualified cardinality: 1
  on class: Account
subclass of: Restriction
  on property: item contained in socialDocument
  qualified cardinality: 1
  on class: SocialDocument
disjoint with: SocialDocument
disjoint with: Space
comment: Through the Item entity, all properties that are consistent for the components of a SocialDocument are bundled. For this reason, the object properties are of a general nature and yet each represent a single piece of social content. The Item also serves to provide the link to the actual SocialDocument, which consists of at least one IntellectualEntity. Items are objects that are created, read, updated or deleted by a user. They represent intellectual content (e.g. text) or simple pieces of content (e.g. an emoticon).

Like
type: Class
subclass of: SimpleComponent
disjoint with: Tag
comment: The entity Like, which is also called "recommendation", is a SimpleComponent, which can be related to an IntellectualComponent or an IntellectualEntity. Since they have no inherent intellectual content, they, as all SimpleComponents, are not mutually related. Since a like within SocDOnt can only refer to IntellectualEntities, it is not possible to represent the "liking" of a Container.

MessageBoard
type: Class
subclass of: Container
disjoint with: MicroBlog
disjoint with: TaskContainer
disjoint with: Weblog
disjoint with: Wiki
comment: MessageBoards are often called "forums" within ECS and contain any number of BoardPosts. This Container type can therefore contain several IntellectualEntities. The answers to the original message in the MessageBoard are represented by Comments.

MicroBlog
type: Class
subclass of: Container
disjoint with: TaskContainer
disjoint with: Weblog
disjoint with: Wiki
comment: The Microblog, like the MessageBoard, is a Container. The entity can contain MicroblogPosts, whose responses within the SocDOnt are called Comments.

MicroblogPost
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: microblogPost contained in microblog
  qualified cardinality: 1
  on class: MicroBlog
disjoint with: Task
comment: MicroblogPosts are among the IntellectualEntities and are contained in Microblogs. As with the other IntellectualEntities, replies are represented in the form of Comments.

OrganisationalPlatform
type: Class
subclass of: Space
disjoint with: UserWorkspace
comment: The OrganisationalPlatform entity describes a space that is accessible to all participants of the system.

SimpleComponent
type: Class
subclass of: Component
subclass of: Restriction
  on property: simpleComponent of intellectualComponent
  max qualified cardinality: 1
  on class: IntellectualComponent
comment: SimpleComponents add further data (Likes and Tags) to IntellectualComponents or IntellectualEntities. With the exception of the Tag, these types of Components do not carry any other data properties and thus no intellectual content. Because of their lack of intellectual content, Tags and Likes can never be associated with each other or with any other instance of themselves. This is because tagging a tag, liking a like, or tagging a like makes no sense. While liking a Tag would be conceivable, it is a very atypical use case. In some ECS, it is possible to also like a Space or Container, but in the context of SocDOnt, the focus is on applying these Components to SocialDocuments.

SocialDocument
type: Class
subclass of: Restriction
  on property: socialDocument contains item
  min qualified cardinality: 1
  on class: Item
subclass of: Restriction
  on property: socialDocument contained in container
  qualified cardinality: 1
  on class: Container
disjoint with: Space
comment: The SocialDocument represents, as the name of the ontology already indicates, a central element of SocDOnt. This "compound document" (Williams, Mosen and Schubert, 2020, p. 3) is composed of IntellectualEntity, IntellectualComponents and SimpleComponents. Only the IntellectualEntity is mandatory. The SocialDocument is assigned to the same container as the corresponding IntellectualEntity. For the SocialDocument, no distinction is made within the SocDOnt as to whether this already originally has "social content" (collaboratively created content) (for example, a WikiPage edited by two authors) or only becomes such through Components (for example, in the case of a PDF or Word file). Hausmann (2018, p. 210) calls these different forms "born social" and "become social" and refers to Hodge (2000), who first described documents that are created and distributed in electronic form in this way.

Space
type: Class
subclass of: Restriction
  on property: space contained in system
  qualified cardinality: 1
  on class: System
comment: A space provides a bundle of functional modules and their respective containers in a specific system (single-system concept).
comment: The types of Spaces describe the different areas in which social content is created (Williams, Mosen, and Schubert, 2020). The different container types are assigned to the Spaces.

Tag
type: Class
subclass of: SimpleComponent
comment: Tags belong to SimpleComponents and include a label that identifies the Tag. Tags are used to describe IntellectualComponents or IntellectualEntities more detailed.

Task
type: Class
subclass of: IntellectualEntity
subclass of: Restriction
  on property: task contained in taskContainer
  qualified cardinality: 1
  on class: TaskContainer
subclass of: Restriction
  on property: task has parent
  max qualified cardinality: 1
  on class: Task
comment: The Task entity belongs to the IntellectualEntities and describes a task. These Tasks can be organized in hierarchical structures, since parent-child relations are given. Subordinate Tasks can also be called subtasks, but they follow the same structure as parent Tasks.

TaskContainer
type: Class
subclass of: Container
disjoint with: Weblog
disjoint with: Wiki
comment: TaskContainers can hold any number of Tasks. TaskContainers are unambiguously assigned to a Space.

UserWorkspace
type: Class
subclass of: Space
comment: The UserWorkspace serves as a space that is only accessible to a specific user. Thus, this type of space represents the counterpart to an organizational platform, which is accessible to all users.

Weblog
type: Class
subclass of: Container
disjoint with: Wiki
comment: Weblogs are regularly referred to as "blogs" within ECS and contain BlogPosts. This Container can therefore hold several IntellectualEntities. The contained replies to the original message in the Weblog are Comments.

Wiki
type: Class
subclass of: Container
comment: Wikis serve as containers for WikiPages and are subordinate to the concept of Spaces. Containers of this type can also hold multiple IntellectualEntities.