Annotation
literal: Martin Just

Annotation
literal: Petra Schubert

Annotation
literal: 06/2022

Annotation
literal: The Collaborative Actions on Documents Ontology (ColActDOnt) expresses the structure of actions on documents within collaboration systems.

Annotation
literal: ColActDOnt - Collaborative Actions on Documents Ontology

Annotation
literal: 1.0

DataPropertyRange
data one of:
  literal: CREATED
  literal: DELETED
  literal: READ
  literal: UPDATED

AnnotationAssertion
IRI: /1.0#Account
literal: An Account is the technical means for an Agent to connect to a computer system.

AnnotationAssertion
IRI: /1.0#Account
literal: Account

AnnotationAssertion
IRI: /1.0#Agent
literal: An Agent is the meta term for a real Person, an ArtificialAgent (e. g. a bot) or an Organisation.

AnnotationAssertion
IRI: /1.0#Agent
literal: Agent

AnnotationAssertion
IRI: /1.0#ArtificialAgent
literal: The ArtificialAgent is an entity to address bots or similar non-human Agents.

AnnotationAssertion
IRI: /1.0#ArtificialAgent
literal: ArtificialAgent

AnnotationAssertion
IRI: /1.0#Calendar
literal: The Calendar entity corresponds to a Container that can contain CalendarEvents.

AnnotationAssertion
IRI: /1.0#Calendar
literal: Calendar

AnnotationAssertion
IRI: /1.0#CalendarEntry
literal: CalendarEntries describe the Entities that hold information on records in a Calendar.

AnnotationAssertion
IRI: /1.0#CalendarEntry
literal: CalendarEntry

AnnotationAssertion
IRI: /1.0#ChatChannel
literal: The ChatChannel entity corresponds to a Container that can hold ChatMessages.

AnnotationAssertion
IRI: /1.0#ChatChannel
literal: ChatChannel

AnnotationAssertion
IRI: /1.0#ChatMessage
literal: ChatMessages are text which is stored within ChatChannels.

AnnotationAssertion
IRI: /1.0#ChatMessage
literal: ChatMessage

AnnotationAssertion
IRI: /1.0#DigitalWorkspace
literal: A DigitalWorkspace is a combination of functional modules selected for a specific work group (multi-system concept).

AnnotationAssertion
IRI: /1.0#DigitalWorkspace
literal: DigitalWorkspace

AnnotationAssertion
IRI: /1.0#Event
literal: 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.

AnnotationAssertion
IRI: /1.0#Event
literal: Event

AnnotationAssertion
IRI: /1.0#FileLibrary
literal: FileLibraries serve as a parent structure for Files and Folders.

AnnotationAssertion
IRI: /1.0#FileLibrary
literal: FileLibrary

AnnotationAssertion
IRI: /1.0#Folder
literal: Folders are used to structure Files within FileLibraries. Folders may only inherit little or no intellectual content.

AnnotationAssertion
IRI: /1.0#Folder
literal: Folder

AnnotationAssertion
IRI: /1.0#Follow
literal: 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.

AnnotationAssertion
IRI: /1.0#Follow
literal: Follow

AnnotationAssertion
IRI: /1.0#Group
literal: Groups usually reflect organisational structures or working groups within Systems.

AnnotationAssertion
IRI: /1.0#Group
literal: Group

AnnotationAssertion
IRI: /1.0#MailContainer
literal: MailContainers are Containers that can contain MailMessages.

AnnotationAssertion
IRI: /1.0#MailContainer
literal: MailContainer

AnnotationAssertion
IRI: /1.0#MailMessage
literal: A MailMessage is an IntellectualEntity that can hold various intellectualContent and is stored in MailContainers.

AnnotationAssertion
IRI: /1.0#MailMessage
literal: MailMessage

AnnotationAssertion
IRI: /1.0#Meeting
literal: 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.

AnnotationAssertion
IRI: /1.0#Meeting
literal: Meeting

AnnotationAssertion
IRI: /1.0#MeetingContainer
literal: MeetingContainers are the parent structure (Container) for Meetings like video conferences and voice chats.

AnnotationAssertion
IRI: /1.0#MeetingContainer
literal: MeetingContainer

AnnotationAssertion
IRI: /1.0#Organisation
literal: 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.

AnnotationAssertion
IRI: /1.0#Organisation
literal: Organisation

AnnotationAssertion
IRI: /1.0#OrganisationalGroup
literal: OrganisationalGroups aggregate Agents and relate those to DigitalWorkspaces.

AnnotationAssertion
IRI: /1.0#OrganisationalGroup
literal: OrganisationalGroup

AnnotationAssertion
IRI: /1.0#Person
literal: 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.

AnnotationAssertion
IRI: /1.0#Person
literal: Person

AnnotationAssertion
IRI: /1.0#Reaction
literal: A Reaction usually refers to emojis or similar that occur as a "reaction" to an Item.

AnnotationAssertion
IRI: /1.0#Reaction
literal: Reaction

AnnotationAssertion
IRI: /1.0#Role
literal: Roles (e.g. manager, member) originate from system-internal rights management and can be assigned to Accounts and Groups.

AnnotationAssertion
IRI: /1.0#Role
literal: Role

AnnotationAssertion
IRI: /1.0#SocialProfile
literal: 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.

AnnotationAssertion
IRI: /1.0#SocialProfile
literal: SocialProfile

AnnotationAssertion
IRI: /1.0#SocialProfileContainer
literal: A SocialProfileContainer contains the SocialProfiles of Accounts. Thus, this concept contains the informational user directory.

AnnotationAssertion
IRI: /1.0#SocialProfileContainer
literal: SocialProfileContainer

AnnotationAssertion
IRI: /1.0#Subscription
literal: 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.

AnnotationAssertion
IRI: /1.0#Subscription
literal: Subscription

AnnotationAssertion
IRI: /1.0#System
literal: 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).

AnnotationAssertion
IRI: /1.0#System
literal: System

AnnotationAssertion
IRI: /1.0#Vote
literal: Votes are SimpleComponents, which represent feedback on other Items.

AnnotationAssertion
IRI: /1.0#Vote
literal: Vote

AnnotationAssertion
IRI: /1.0#WikiPage
literal: 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.

AnnotationAssertion
IRI: /1.0#WikiPage
literal: WikiPage

AnnotationAssertion
abbreviated IRI: socdont:Attachment
literal: The Attachment is one of the IntellectualComponents and describes an appendage of intellectual content to an IntellectualEntity or to a Comment.

AnnotationAssertion
abbreviated IRI: socdont:Attachment
literal: Attachment

AnnotationAssertion
abbreviated IRI: socdont:BlogPost
literal: BlogPosts belong to the IntellectualEntities and thus describe entries that are posted in Weblogs.

AnnotationAssertion
abbreviated IRI: socdont:BlogPost
literal: BlogPost

AnnotationAssertion
abbreviated IRI: socdont:BoardPost
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:BoardPost
literal: BoardPost

AnnotationAssertion
abbreviated IRI: socdont:Collection
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:Collection
literal: Collection

AnnotationAssertion
abbreviated IRI: socdont:Comment
literal: The Comment entity is an IntellectualComponent that contains intellectual content about Attachments or IntellectualEntities.

AnnotationAssertion
abbreviated IRI: socdont:Comment
literal: Comment

AnnotationAssertion
abbreviated IRI: socdont:Component
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:Component
literal: Component

AnnotationAssertion
abbreviated IRI: socdont:Container
literal: 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).

AnnotationAssertion
abbreviated IRI: socdont:Container
literal: Container

AnnotationAssertion
abbreviated IRI: socdont:File
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:File
literal: File

AnnotationAssertion
abbreviated IRI: socdont:GroupWorkspace
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:GroupWorkspace
literal: GroupWorkspace

AnnotationAssertion
abbreviated IRI: socdont:IntellectualComponent
literal: Attachments and Comments are subordinated to the IntellectualComponent entity. These differ from SimpleComponents by their "intellectual content".

AnnotationAssertion
abbreviated IRI: socdont:IntellectualComponent
literal: IntellectualComponent

AnnotationAssertion
abbreviated IRI: socdont:IntellectualEntity
literal: IntellectualEntities describe the core of a SocialDocument, for example a File or a BlogPost, which can be enriched by Components.

AnnotationAssertion
abbreviated IRI: socdont:IntellectualEntity
literal: IntellectualEntity

AnnotationAssertion
abbreviated IRI: socdont:Item
literal: 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).

AnnotationAssertion
abbreviated IRI: socdont:Item
literal: Item

AnnotationAssertion
abbreviated IRI: socdont:Like
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:Like
literal: Like

AnnotationAssertion
abbreviated IRI: socdont:MessageBoard
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:MessageBoard
literal: MessageBoard

AnnotationAssertion
abbreviated IRI: socdont:MicroBlog
literal: The Microblog, like the MessageBoard, is a Container. The entity can contain MicroblogPosts, whose responses within the SocDOnt are called Comments.

AnnotationAssertion
abbreviated IRI: socdont:MicroBlog
literal: MicroBlog

AnnotationAssertion
abbreviated IRI: socdont:MicroblogPost
literal: MicroblogPosts are among the IntellectualEntities and are contained in Microblogs. As with the other IntellectualEntities, replies are represented in the form of Comments.

AnnotationAssertion
abbreviated IRI: socdont:MicroblogPost
literal: MicroblogPost

AnnotationAssertion
abbreviated IRI: socdont:OrganisationalPlatform
literal: The OrganisationalPlatform entity describes a space that is accessible to all participants of the system.

AnnotationAssertion
abbreviated IRI: socdont:OrganisationalPlatform
literal: OrganisationalPlatform

AnnotationAssertion
abbreviated IRI: socdont:SimpleComponent
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:SimpleComponent
literal: SimpleComponent

AnnotationAssertion
abbreviated IRI: socdont:SocialDocument
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:SocialDocument
literal: SocialDocument

AnnotationAssertion
abbreviated IRI: socdont:Space
literal: A space provides a bundle of functional modules and their respective containers in a specific system (single-system concept).

AnnotationAssertion
abbreviated IRI: socdont:Space
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:Space
literal: Space

AnnotationAssertion
abbreviated IRI: socdont:Tag
literal: Tags belong to SimpleComponents and include a label that identifies the Tag. Tags are used to describe IntellectualComponents or IntellectualEntities more detailed.

AnnotationAssertion
abbreviated IRI: socdont:Tag
literal: Tag

AnnotationAssertion
abbreviated IRI: socdont:Task
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:Task
literal: Task

AnnotationAssertion
abbreviated IRI: socdont:TaskContainer
literal: TaskContainers can hold any number of Tasks. TaskContainers are unambiguously assigned to a Space.

AnnotationAssertion
abbreviated IRI: socdont:TaskContainer
literal: TaskContainer

AnnotationAssertion
abbreviated IRI: socdont:UserWorkspace
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:UserWorkspace
literal: UserWorkspace

AnnotationAssertion
abbreviated IRI: socdont:Weblog
literal: 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.

AnnotationAssertion
abbreviated IRI: socdont:Weblog
literal: Weblog

AnnotationAssertion
abbreviated IRI: socdont:Wiki
literal: Wikis serve as containers for WikiPages and are subordinate to the concept of Spaces. Containers of this type can also hold multiple IntellectualEntities.

AnnotationAssertion
abbreviated IRI: socdont:Wiki
literal: Wiki