The ontology used within My2Sec to represent events, actvities, tasks and projects. It is used to log the time spent by workers on tasks.
My2Sec is the innovative online platform that facilitates remote work by keeping track of daily progress in real time. Essential to have an overview updated in real time of the project. My2Sec makes it easy and immediate to make decisions promptly and accurately. Planning, defining objectives and evaluating results with My2Sec is quick and easy thanks to the fully customizable dashboard. My2Sec collects in real time a flow of data generated by the worker which, through an Artificial Intelligence algorithm, are automatically linked to specific activities carried out within a project. The information, stored in a highly secure decentralized cloud, is easily viewable at any time in customizable dashboards. Thanks to an integrated open source system, My2Sec offers an immediate view of the work progress from any device. At the end of the day the user can share the details of the progress of the work done by selecting them from his customizable report in full compliance with the GDPR legislation on sensitive data.
This ontology describe the application My2Sec. It works as a solution for smart-workers want to track their activity and manage remote work.
My2Sec
Be attach to something.
attachedTo
Every project is composed by some tasks.
composedBy
Every LogTime refers to an activity.
hasActivity
Every actvity is associated with an activitytype.
hasActivityType
This property link also the subtask with his own activity type define by Project Manager.
This property match also the training event with the right activitytype.
Every TrainingEvent refers to a specific event
hasEvent
Every activity has his own logtime.
hasLogTime
Every Event has an URI reference to the member who raised it.
hasURI
Has a task. This property make possible the association between task and activity.
hasTask
Every subtask is part of Task.
partOf
Every event has APP title.
hasAPPTitle
Every Meeting has a name.
hasMeetingName
Every event has a Title.
hasTitle
Every meeting event haas a type (start/stop)
hasType
1 = start 0 = stop
Every event has URL.
hasURL
Every task has an ID.
idTask
Every project has a name.
projectName
The username used to identify the user within the system
This class contain Event generated by Activity Watch.
AWEvent
Duration of time meanwile members doing one specific activity.
Activity
The type of working activity.
ActivityType
An Afk event.
AfkEvent
This class contain Event generated by sistem control.
ControlEvent
Specific activity types of a developer (e.g., developing, testing, documenting)
An event is something that happen in one moment and has no temporal duration. It is characterized by timestamp, apptitle and activitytype.
Event
Specifically it should be characterized by an eventtype (which must coincide with the activitytype)
Duration of time spent on a specific activity by one member. It is characterized by date, hours ad an activity.
LogTime
A meeting Event
MeetingEvent
A member is a generic Worker.
Member
A Not Shutdown Event.
NotShutdownEvent
A project (a collective endeavour of some kind).
Project
An event that marks the beginning of a working day.
StartEvent
an event that marks the end of a working day
StopEvent
Every Task is composed by different subtasks. They have a specific type.
SubTask
A task is an assignment given to members.
Task
This class contain dataset used for train AI or something like that.
TrainingData
This class contains Events linked to a specific task.
TrainingEvent
An event signals the dispatch of events to the aggregator.
UploadEvent
A window event is a particular event visualized as a window.
WindowsEvent
Temporal Instant
Time Instant
A temporal Instant or Interval
TemporalEntity
This rule associates each activity with its task.