SemCMD

Project Documentation

Loading Content

Please wait while we load your data...

Models Items

Digital Curating Service Digital Hosting Service Digital Machine Event Group Persistent Dataset Persistent Software Person Project Team Research Project Schema Service Service Project Volatile Dataset Volatile Software

Models

Service Project

ID: SEMM.10

Scope: PE46 Service Project

System Name:

service_project

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.10

Volatile Dataset

ID: SEMM.4

Scope: PE24 Volatile Dataset

An instance of `PE24 Volatile Dataset` is "in a process of continual potential change". The identity of a volatile dataset is ascertained "by reference to a curation plan which indicates the overall goal of the process of management of this object and can be referenced by the snapshots of the data stream which give an identity to the volatile object for some time span." (CRMpem 3.1) Volatile datasets are always curated by an instance of `E39 Actor`.

System Name:

volatile_dataset

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.4

Project Team

ID: SEMM.1

Scope: PE34 Team

A project team (PE34) is any group (E74) of persons (E21) "who come together for some defined project. The identity of the team is given by the collective will to achieve and support some project/aim. Membership in the group is determined by official association to the team for the purpose of contributing to the achievement of its aim. Membership need not be mediated by institutional association. An instance of PE34 Team is identified by its commonality of purpose and not by its membership at any one time. A PE34 Team instance comes into existence with the agreement to maintain its collective project. So long as the will to maintain the project is upheld by a minimal membership of the team (1), the team can be said to exist, although any or all of its members may change over time." (CRMpem 3.1) A project team is the aggregation of all persons that are considered to have worked on a particular project at some point in time.

System Name:

project_team

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.1

Digital Hosting Service

ID: SEMM.9.1

Scope: PE5 Digital Hosting Service

System Name:

digital_hosting_service

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.9.1

Persistent Dataset

ID: SEMM.5

Scope: PE22 Persistent Dataset

System Name:

persistent_dataset

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.5

Digital Curating Service

ID: SEMM.9.2

Scope: PE10 Digital Curating Service

System Name:

digital_curating_service

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.9.2

Person

ID: SEMM.3

Scope: E21 Person

A person (E21) "comprises real persons who live or are assumed to have lived." (CIDOC CRM 7.1.2) A person may be a member of project teams (PE34), and as such the person has participated, at some point in time, in a project (PE1). A person may also be a member of one ore more groups (E74).

System Name:

person

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.3

Digital Machine Event

ID: SEMM.0.1

Scope: D7 Digital Machine Event

System Name:

digital_machine_event

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.0.1

Schema

ID: SEMM.8

Scope: PE38 Schema

System Name:

schema

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.8

Volatile Software

ID: SEMM.6

Scope: PE23 Volatile Software

System Name:

volatile_software

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.6

Research Project

ID: SEMM.11

Scope: PE45 Research Project

System Name:

research_project

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.11

Service

ID: SEMM.9

Scope: PE1 Service

Service that curates data, which implies the active work on the data and taking care of the data according to some curation plan, but without handling the hosting (storing) and e-provisioning of the data.

System Name:

service

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.9

Group

ID: SEMM.2

Scope: E74 Group

A group (E74) "comprises any gatherings or organizations of human individuals or groups that act collectively or in a similar way due to any form of unifying relationship. (…) A gathering of people becomes an instance of E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together." (CIDOC CRM 7.1.2) In the context of the CKG, a group (E74) is any kind of group that is not a project team (PE34).

System Name:

group

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.2

Persistent Software

ID: SEMM.7

Scope: PE21 Persistent Software

System Name:

persistent_software

Version:

—

Version Date:

—

Last Modified:

2025-08-13

Author:

George Bruseker

Funder:

Takin Solutions

Funding Project:

semcmd

Ontology:

rdfs_1.1, crmdig_3.2.1, crmpe_3.1.1, crm_7.1.1

Project:

semcmd

URI:

http://takin.solutions/space/semcmd/composite/SEMM.7

Loading Content

Please wait while we load your data...