diff --git a/MANIFEST.in b/MANIFEST.in
index 4088c3b25..d97f0504b 100644
--- a/MANIFEST.in
+++ b/MANIFEST.in
@@ -2,5 +2,6 @@ include README.md
 include knora/dsplib/utils/knora-schema.json
 include knora/dsplib/utils/knora-schema-lists.json
 include knora/dsplib/utils/knora-schema-lists-only.json
+include knora/dsplib/utils/knora-schema-resources-only.json
 include knora/dsplib/utils/knora-data-schema.xsd
 include knora/dsplib/utils/language-codes-3b2_csv.csv
diff --git a/docs/assets/images/img-resources-example.png b/docs/assets/images/img-resources-example.png
new file mode 100644
index 000000000..cf0745fd5
Binary files /dev/null and b/docs/assets/images/img-resources-example.png differ
diff --git a/docs/dsp-tools-create.md b/docs/dsp-tools-create.md
index c1846e818..db0ef5758 100644
--- a/docs/dsp-tools-create.md
+++ b/docs/dsp-tools-create.md
@@ -431,7 +431,8 @@ The nodes section must contain the field:
 
 - _folder_: Path to the folder where the Excel files are stored
 
-Further details to this functionality can be read [here](dsp-tools-excel.md).
+Further details to this functionality can be read
+[here](dsp-tools-excel#create-a-json-list-file-from-one-or-several-excel-files.md).
 
 The lists element is optional. If there are no lists, this element has to be omitted.
 
diff --git a/docs/dsp-tools-excel.md b/docs/dsp-tools-excel.md
index 3e2b6194e..a5f106c83 100644
--- a/docs/dsp-tools-excel.md
+++ b/docs/dsp-tools-excel.md
@@ -1,29 +1,50 @@
 [![PyPI version](https://badge.fury.io/py/dsp-tools.svg)](https://badge.fury.io/py/dsp-tools)
 
 # Excel files for data modelling and data import
-dsp-tools is able to process Excel files and output the appropriate JSON or XML file. The JSON/XML file can then
-be used to create the ontology on the DSP server or import data to the DSP repository. dsp-tools can also be used to
-create a list from an Excel file.
 
-## Create the data model JSON from an Excel file
+dsp-tools is able to process Excel files and output the appropriate JSON or XML file. The JSON/XML file can then be used to create
+the ontology on the DSP server or import data to the DSP repository. dsp-tools can also be used to create a list from an Excel
+file.
+
+## Create the resources for a data model from an Excel file
+
+With dsp-tools the `resources` section used in a data model (JSON) can be created from an Excel file. Only the first worksheet of
+the Excel file is considered and only `XLSX` files are allowed. The `resources` section can be inserted into the ontology file and
+then be uploaded onto a DSP server.
+
+The Excel sheet must have the following format:
+![img-resources-example.png](assets/images/img-resources-example.png)
+
+The expected columns are:
+
+- `name` : The name of the resource
+- `super` : The base resource of the resource
+- `en`, `de`, `fr`, `it` : The labels of the resource in different languages, at least one language has to be provided
+
+For further information about resources, see [here](./dsp-tools-create.md#resources).
+
+## Create the properties for a data model from an Excel file
+
 [not yet implemented]
 
 ## Create a DSP-conform XML file from an Excel file
+
 [not yet implemented]
 
 ## Create a list from one or several Excel files
-With dsp-tools a JSON list can be created from one or several Excel files. The list can then be inserted into a JSON ontology 
-and uploaded to a DSP server. The expected format of the Excel files is described [here](./dsp-tools-create.md#lists-from-excel). 
-It is possible to create multilingual lists. In this case, a separate Excel file has to be created for each language. The data 
-has to be in the first worksheet of the Excel file(s). It is important that all the Excel lists have the same structure. So, 
-the translation(s) of a label in one Excel sheet has to be in the exact same cell (i.e. with the same cell index) in its own 
-Excel sheet.
-
-Only Excel files with file extension `.xlsx` are considered. All Excel files have to be located in the same directory. When 
-calling the `excel` command, this folder is provided as an argument to the call. The language of the labels has to be provided in 
-the Excel file's file name after an underline and before the file extension, p.ex. `liste_de.xlsx` would be considered a list with 
-German (`de`) labels, `list_en.xlsx` a list with English (`en`) labels. The language has to be a valid ISO 639-1 or ISO
-639-2 language code.
+
+With dsp-tools a JSON list can be created from one or several Excel files. The list can then be inserted into a JSON ontology and
+uploaded to a DSP server. The expected format of the Excel files is described [here](./dsp-tools-create.md#lists-from-excel). It
+is possible to create multilingual lists. In this case, a separate Excel file has to be created for each language. The data has to
+be in the first worksheet of the Excel file(s). It is important that all the Excel lists have the same structure. So, the
+translation(s) of a label in one Excel sheet has to be in the exact same cell (i.e. with the same cell index) in its own Excel
+sheet.
+
+Only Excel files with file extension `.xlsx` are considered. All Excel files have to be located in the same directory. When
+calling the `excel` command, this folder is provided as an argument to the call. The language of the labels has to be provided in
+the Excel file's file name after an underline and before the file extension, p.ex. `liste_de.xlsx` would be considered a list with
+German (`de`) labels, `list_en.xlsx` a list with English (`en`) labels. The language has to be a valid ISO 639-1 or ISO 639-2
+language code.
 
 The following example shows how to create a JSON list from two Excel files which are in a directory called `lists`. The output is
 written to the file `list.json`.
@@ -32,7 +53,7 @@ written to the file `list.json`.
 dsp-tools excel lists list.json
 ```
 
-The two Excel files `liste_de.xlsx` and `list_en.xlsx` are located in a folder called `lists`. `liste_de.xlsx` contains German 
+The two Excel files `liste_de.xlsx` and `list_en.xlsx` are located in a folder called `lists`. `liste_de.xlsx` contains German
 labels for the list, `list_en.xlsx` contains the English labels.
 
 ```
@@ -41,8 +62,8 @@ lists
     |__ list_en.xlsx
 ```
 
-For each list node, the `label`s are read from the Excel files. The language code, provided in the file name, is then used for 
-the labels. As node `name`, a simplified version of the English label is taken if English is one of the available languages. If
+For each list node, the `label`s are read from the Excel files. The language code, provided in the file name, is then used for the
+labels. As node `name`, a simplified version of the English label is taken if English is one of the available languages. If
 English is not available, one of the other languages is chosen (which one depends on the representation of the file order). If
 there are two node names with the same name, an incrementing number is appended to the `name`.
 
@@ -79,5 +100,5 @@ there are two node names with the same name, an incrementing number is appended
 }, ...
 ```
 
-After the creation of the list, a validation against the JSON schema for lists is performed. An error message ist printed out if 
+After the creation of the list, a validation against the JSON schema for lists is performed. An error message ist printed out if
 the list is not valid. Furthermore, it is checked that no two nodes are the same.
diff --git a/docs/dsp-tools-usage.md b/docs/dsp-tools-usage.md
index c867674f0..23b9dae3b 100644
--- a/docs/dsp-tools-usage.md
+++ b/docs/dsp-tools-usage.md
@@ -1,7 +1,8 @@
 [![PyPI version](https://badge.fury.io/py/dsp-tools.svg)](https://badge.fury.io/py/dsp-tools)
 
 # Installation and usage
-The following paragraphs gives you an overview of how to install and use dsp-tools. 
+
+The following paragraphs gives you an overview of how to install and use dsp-tools.
 
 ## Installation
 
@@ -29,20 +30,20 @@ The following options are available:
 - `-u` | `--user` _username_: username used for authentication with the DSP API (default: root@example.com)
 - `-p` | `--password` _password_: password used for authentication with the DSP API (default: test)
 - `-V` | `--validate`: If set, only the validation of the JSON file is performed.
-- `-l` | `--lists`: If set, only the lists are created using a [simplified schema](./dsp-tools-create.md#lists). Please note
-  that in this case the project must already exist.
+- `-l` | `--lists`: If set, only the lists are created using a [simplified schema](./dsp-tools-create.md#lists). Please note that
+  in this case the project must already exist.
 - `-v` | `--verbose`: If set, some information about the progress is printed to the console.
-  
-The command is used to read the definition of a data model (provided in a JSON file) and create it on the
-DSP server. The following example shows how to load the ontology defined in `data_model_definition.json` onto the DSP
+
+The command is used to read the definition of a data model (provided in a JSON file) and create it on the DSP server. The
+following example shows how to load the ontology defined in `data_model_definition.json` onto the DSP
 server `https://api.dsl.server.org` provided with the `-s` option. The username `root@example.com` and the password
-  `test` are used.
+`test` are used.
 
 ```bash
 dsp-tools create -s https://api.dsl.server.org -u root@example.com -p test data_model_definition.json
 ```
 
-The description of the expected JSON format can be found [here](./dsp-tools-create.md). 
+The description of the expected JSON format can be found [here](./dsp-tools-create.md).
 
 ## Get a data model from a DSP server
 
@@ -59,10 +60,10 @@ The following options are available:
   [IRI](https://en.wikipedia.org/wiki/Internationalized_Resource_Identifier) of the project
 - `-v` | `--verbose`: If set, some information about the progress is printed to the console.
 
-The command is used to get the definition of a data model from a DSP server and write it into a JSON file. This JSON file
-could then be used to upload the data model to another DSP server. The following example shows how to get the data model
-from a DSP server `https://api.dsl.server.org` provided with the `-s` option. The username `root@example.com` and the
-password `test` are used. The data model is saved into the output file `output_file.json`.
+The command is used to get the definition of a data model from a DSP server and write it into a JSON file. This JSON file could
+then be used to upload the data model to another DSP server. The following example shows how to get the data model from a DSP
+server `https://api.dsl.server.org` provided with the `-s` option. The username `root@example.com` and the password `test` are
+used. The data model is saved into the output file `output_file.json`.
 
 ```bash
 dsp-tools get -s https://api.dsl.server.org -u root@example.com -p test output_file.json
@@ -83,16 +84,16 @@ The following options are available:
 - `-S` | `--sipi` _SIPIserver_: URL of the SIPI IIIF server (default: http://0.0.0.0:1024)
 - `-v` | `--verbose`: If set, more information about the uploaded resources is printed to the console.
 
-The command is used to upload data defined in an XML file onto a DSP server. The following example shows how to upload
-data from an XML file `xml_data_file.xml` onto the DSP server `https://api.dsl.server.org` provided with the `-s` option.
-The username `root@example.com` and the password `test` are used. The interface for the SIPI IIIF server is provided
-with the `-S` option (`https://iiif.dsl.server.org`).
+The command is used to upload data defined in an XML file onto a DSP server. The following example shows how to upload data from
+an XML file `xml_data_file.xml` onto the DSP server `https://api.dsl.server.org` provided with the `-s` option. The
+username `root@example.com` and the password `test` are used. The interface for the SIPI IIIF server is provided with the `-S`
+option (`https://iiif.dsl.server.org`).
 
 ```bash
 dsp-tools xmlupload -s https://api.dsl.server.org -u root@example.com -p test -S https://iiif.dsl.server.org xml_data_file.xml
 ```
 
-The description of the expected XML format can be found [here](./dsp-tools-xmlupload.md). 
+The description of the expected XML format can be found [here](./dsp-tools-xmlupload.md).
 
 ## Create a JSON list file from one or several Excel files
 
@@ -105,9 +106,9 @@ The following option is available:
 - `-l` | `--listname` _listname_: name to be used for the list (filename before last occurrence of `_` is used if omitted)
 
 The command is used to create a JSON list file from one or several Excel files. It is possible to create multilingual lists.
-Therefore, an Excel file for each language has to be provided. The data has to be in the first worksheet of the Excel 
-file and all Excel files have to be in the same directory. When calling the `excel` command, this directory has to be provided 
-as an argument to the call.
+Therefore, an Excel file for each language has to be provided. The data has to be in the first worksheet of the Excel file and all
+Excel files have to be in the same directory. When calling the `excel` command, this directory has to be provided as an argument
+to the call.
 
 The following example shows how to create a JSON list from Excel files in a directory called `lists`.
 
@@ -115,5 +116,24 @@ The following example shows how to create a JSON list from Excel files in a dire
 dsp-tools excel lists list.json
 ```
 
-The description of the expected Excel format can be found [here](./dsp-tools-create.md#lists-from-excel). More information 
-about the usage of this command can be found [here](./dsp-tools-excel.md#create-a-list-from-one-or-several-excel-files).
+The description of the expected Excel format can be found [here](./dsp-tools-create.md#lists-from-excel). More information about
+the usage of this command can be found [here](./dsp-tools-excel.md#create-a-list-from-one-or-several-excel-files).
+
+## Create resources from an Excel file
+
+```bash
+dsp-tools excel2resources excel_file.xlsx output_file.json
+```
+
+The command is used to create the resource section of an ontology from an Excel file. Therefore, an Excel file has to be provided
+with the data in the first worksheet of the Excel file.
+
+The following example shows how to create the resources section from an Excel file called `Resources.xlsx`.
+
+```bash
+dsp-tools excel2resources Resources.xlsx resources.json
+```
+
+More information about the usage of this command can be
+found [here](./dsp-tools-excel.md#create-the-resources-for-a-data-model-from-an-excel-file)
+.
\ No newline at end of file
diff --git a/docs/index.md b/docs/index.md
index cbde50829..682e6938b 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -4,22 +4,25 @@
 
 dsp-tools is a command line tool that helps you interact with the DaSCH Service Platform server (DSP server).
 
-In order to archive your data on the DaSCH Service Platform, you need a data model (ontology) that describes your data.
-The data model is defined in a JSON file which has to be transmitted to the DSP server. If the DSP server is aware of
-the data model for your project, conforming data can be uploaded into the DSP repository.
+In order to archive your data on the DaSCH Service Platform, you need a data model (ontology) that describes your data. The data
+model is defined in a JSON file which has to be transmitted to the DSP server. If the DSP server is aware of the data model for
+your project, conforming data can be uploaded into the DSP repository.
 
-Often, data is initially added in large quantities. Therefore, dsp-tools allows you to perform bulk imports of your data.
-In order to do so, the data has to be described in an XML file. dsp-tools is able to read the XML file and upload all data
-to the DSP server.
+Often, data is initially added in large quantities. Therefore, dsp-tools allows you to perform bulk imports of your data. In order
+to do so, the data has to be described in an XML file. dsp-tools is able to read the XML file and upload all data to the DSP
+server.
 
 dsp-tools helps you with the following tasks:
 
-- [`dsp-tools create`](./dsp-tools-usage.md#create-a-data-model-on-a-dsp-server) creates the data model (ontology) on a
-  DSP server from a provided JSON file containing the data model.
-- [`dsp-tools get`](./dsp-tools-usage.md#get-a-data-model-from-a-dsp-server) reads a data model from a DSP server and
-  writes it into a JSON file.
-- [`dsp-tools xmlupload`](./dsp-tools-usage.md#upload-data-to-a-dsp-server) uploads data from a provided XML file (bulk
-  data import).
+- [`dsp-tools create`](./dsp-tools-usage.md#create-a-data-model-on-a-dsp-server) creates the data model (ontology) on a DSP server
+  from a provided JSON file containing the data model.
+- [`dsp-tools get`](./dsp-tools-usage.md#get-a-data-model-from-a-dsp-server) reads a data model from a DSP server and writes it
+  into a JSON file.
+- [`dsp-tools xmlupload`](./dsp-tools-usage.md#upload-data-to-a-dsp-server) uploads data from a provided XML file (bulk data
+  import).
 - [`dsp-tools excel`](./dsp-tools-usage.md#create-a-json-list-file-from-one-or-several-excel-files)
-  creates a JSON or XML file from one or several Excel files. The created data can then be uploaded to a DSP server with 
-  `dsp-tools create`.
+  creates a JSON or XML file from one or several Excel files. The created data can either be integrated into an ontology or be
+  uploaded directly to a DSP server with `dsp-tools create`.
+- [`dsp-tools excel2resources`](./dsp-tools-usage.md#create-resources-from-an-excel-file)
+  creates the ontology's resource section from an Excel file. The resources can be integrated into an ontology and then be
+  uploaded to a DSP server with `dsp-tools create`.
diff --git a/knora/dsp_tools.py b/knora/dsp_tools.py
index 2d4a1ce6f..df0617b99 100644
--- a/knora/dsp_tools.py
+++ b/knora/dsp_tools.py
@@ -14,6 +14,7 @@
 from dsplib.utils.onto_create_ontology import create_ontology
 from dsplib.utils.onto_get import get_ontology
 from dsplib.utils.excel_to_json_lists import list_excel2json, validate_list_with_schema
+from dsplib.utils.excel_to_json_resources import resources_excel2json
 from dsplib.utils.onto_validate import validate_ontology
 from dsplib.utils.xml_upload import xml_upload
 
@@ -84,6 +85,14 @@ def program(args: list) -> None:
     parser_excel_lists.add_argument('excelfolder', help='Path to the folder containing the Excel file(s)', default='lists')
     parser_excel_lists.add_argument('outfile', help='Path to the output JSON file containing the list data', default='list.json')
 
+    parser_excel_resources = subparsers.add_parser('excel2resources', help='Create a JSON file from an Excel file containing '
+                                                                           'resources for a DSP ontology. ')
+    parser_excel_resources.set_defaults(action='excel2resources')
+    parser_excel_resources.add_argument('excelfile', help='Path to the Excel file containing the resources',
+                                        default='resources.xlsx')
+    parser_excel_resources.add_argument('outfile', help='Path to the output JSON file containing the resource data',
+                                        default='resources.json')
+
     args = parser.parse_args(args)
 
     if not hasattr(args, 'action'):
@@ -133,6 +142,9 @@ def program(args: list) -> None:
         list_excel2json(listname=args.listname,
                         excelfolder=args.excelfolder,
                         outfile=args.outfile)
+    elif args.action == 'excel2resources':
+        resources_excel2json(excelfile=args.excelfile,
+                             outfile=args.outfile)
 
 
 def main():
diff --git a/knora/dsplib/utils/BUILD.bazel b/knora/dsplib/utils/BUILD.bazel
index c1ee8ae18..874eb98b9 100644
--- a/knora/dsplib/utils/BUILD.bazel
+++ b/knora/dsplib/utils/BUILD.bazel
@@ -14,6 +14,16 @@ py_library(
     ]
 )
 
+py_library(
+    name = "excel_to_json_resources",
+    visibility = ["//visibility:public"],
+    srcs = ["excel_to_json_resources.py"],
+    deps = [
+        requirement("jsonschema"),
+        requirement("openpyxl")
+    ]
+)
+
 py_library(
     name = "expand_all_lists",
     visibility = ["//visibility:public"],
diff --git a/knora/dsplib/utils/excel_to_json_resources.py b/knora/dsplib/utils/excel_to_json_resources.py
new file mode 100644
index 000000000..4cb0bca96
--- /dev/null
+++ b/knora/dsplib/utils/excel_to_json_resources.py
@@ -0,0 +1,102 @@
+import json
+import os
+
+import jsonschema
+from openpyxl import load_workbook
+
+
+def validate_resources_with_schema(json_file: str) -> bool:
+    """
+        This function checks if the json resources are valid according to the schema.
+
+        Args:
+            json_file: the json with the resources to be validated
+
+        Returns:
+            True if the data passed validation, False otherwise
+
+        """
+    current_dir = os.path.dirname(os.path.realpath(__file__))
+    with open(os.path.join(current_dir, 'knora-schema-resources-only.json')) as schema:
+        resources_schema = json.load(schema)
+
+    try:
+        jsonschema.validate(instance=json_file, schema=resources_schema)
+    except jsonschema.exceptions.ValidationError as err:
+        print(err)
+        return False
+    print('Resource data passed schema validation.')
+    return True
+
+
+def resources_excel2json(excelfile: str, outfile: str):
+    """
+        Converts properties described in an Excel file into a properties section which can be integrated into a DSP ontology
+
+        Args:
+            excelfile: path to the Excel file containing the properties
+            outfile: path to the output JSON file containing the properties section for the ontology
+
+        Returns:
+            None
+    """
+    # load file
+    wb = load_workbook(excelfile, read_only=True)
+
+    # get overview
+    sheet = wb['classes']
+    resource_list = [c for c in sheet.iter_rows(min_row=2, values_only=True)]
+
+    prefix = '"resources":'
+    resources = []
+    # for each resource in resources overview
+    for res in resource_list:
+        # get name
+        name = res[0]
+        # get labels
+        labels = {}
+        if res[1]:
+            labels['en'] = res[1]
+        if res[2]:
+            labels['de'] = res[2]
+        if res[3]:
+            labels['fr'] = res[3]
+        if res[4]:
+            labels['it'] = res[4]
+        # get super
+        sup = res[5]
+
+        # load details for this resource
+        sh = wb[name]
+        property_list = [c for c in sh.iter_rows(min_row=2, values_only=True)]
+
+        cards = []
+        # for each of the detail sheets
+        for i, prop in enumerate(property_list):
+            # get name and cardinality.
+            # GUI-order is equal to order in the sheet.
+            property_ = {
+                "propname": ":" + prop[0],
+                "cardinality": str(prop[1]),
+                "gui_order": i + 1
+            }
+            cards.append(property_)
+
+        # build resource dict
+        resource = {
+            "name": name,
+            "labels": labels,
+            "super": sup,
+            "cardinalities": cards
+        }
+        # append to resources list
+        resources.append(resource)
+
+    if validate_resources_with_schema(json.loads(json.dumps(resources, indent=4))):
+        # write final list to JSON file if list passed validation
+        with open(file=outfile, mode='w+', encoding='utf-8') as file:
+            file.write(prefix)
+            json.dump(resources, file, indent=4)
+            print('Resource file was created successfully and written to file:', outfile)
+    else:
+        print('Resource data is not valid according to schema.')
diff --git a/knora/dsplib/utils/knora-schema-lists-only.json b/knora/dsplib/utils/knora-schema-lists-only.json
index f01b56b1a..393277a17 100644
--- a/knora/dsplib/utils/knora-schema-lists-only.json
+++ b/knora/dsplib/utils/knora-schema-lists-only.json
@@ -1,5 +1,5 @@
 {
-  "$schema": "http://json-schema.org/draft-07/schema-list-only#",
+  "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "http://knora.org/pyknora/ontology/knora-schema-list-only.json",
   "title": "Knora JSON schema for lists only",
   "description": "JSON schema for lists used in Knora ontologies",
@@ -48,7 +48,6 @@
       "additionalProperties": false
     }
   },
-
   "type": "object",
   "properties": {
     "name": {
diff --git a/knora/dsplib/utils/knora-schema-resources-only.json b/knora/dsplib/utils/knora-schema-resources-only.json
new file mode 100644
index 000000000..41c92ab57
--- /dev/null
+++ b/knora/dsplib/utils/knora-schema-resources-only.json
@@ -0,0 +1,132 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "http://knora.org/pyknora/ontology/knora-schema-resources-only.json",
+  "title": "Knora JSON schema for resources only",
+  "description": "JSON schema for resources used in Knora ontologies",
+  "definitions": {
+    "langstring": {
+      "anyOf": [
+        {
+          "type": "object",
+          "patternProperties": {
+            "^(en|de|fr|it)": {
+              "type": "string"
+            }
+          },
+          "additionalProperties": false
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    "label": {
+      "$ref": "#/definitions/langstring"
+    },
+    "comment": {
+      "$ref": "#/definitions/langstring"
+    },
+    "resourcedef": {
+      "type": [
+        "string",
+        "array"
+      ],
+      "oneOf": [
+        {
+          "enum": [
+            "Resource",
+            "StillImageRepresentation",
+            "TextRepresentation",
+            "AudioRepresentation",
+            "DDDRepresentation",
+            "DocumentRepresentation",
+            "MovingImageRepresentation",
+            "Annotation",
+            "LinkObj",
+            "Region"
+          ]
+        },
+        {
+          "pattern": "^([\\w-]*)?:(\\w+)$"
+        },
+        {
+          "pattern": "^(http)(s)?://.*"
+        }
+      ],
+      "items": {
+        "$ref": "#/definitions/resourcedef"
+      }
+    },
+    "resource": {
+      "type": "object",
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "super": {
+          "$ref": "#/definitions/resourcedef"
+        },
+        "labels": {
+          "$ref": "#/definitions/label"
+        },
+        "comments": {
+          "$ref": "#/definitions/comment"
+        },
+        "cardinalities": {
+          "type": "array",
+          "items": {
+            "$ref": "#/definitions/cardinality"
+          }
+        }
+      },
+      "required": [
+        "name",
+        "super",
+        "labels",
+        "cardinalities"
+      ],
+      "additionalProperties": false
+    },
+    "cardinality": {
+      "type": "object",
+      "properties": {
+        "propname": {
+          "type": "string",
+          "oneOf": [
+            {
+              "enum": [
+                "Region",
+                "isPartOf",
+                "seqnum"
+              ]
+            },
+            {
+              "pattern": "^(([\\w-]*)?:([\\w ]+))$"
+            }
+          ]
+        },
+        "cardinality": {
+          "type": "string",
+          "enum": [
+            "1",
+            "0-1",
+            "1-n",
+            "0-n"
+          ]
+        },
+        "gui_order": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "propname",
+        "cardinality"
+      ],
+      "additionalProperties": false
+    }
+  },
+  "type": "array",
+  "items": {
+    "$ref": "#/definitions/resource"
+  }
+}
diff --git a/test/BUILD.bazel b/test/BUILD.bazel
index ef499ebfe..15d7c23d4 100644
--- a/test/BUILD.bazel
+++ b/test/BUILD.bazel
@@ -132,7 +132,8 @@ py_test(
         "//knora/dsplib/utils:onto_validate",
         "//knora/dsplib/utils:onto_create_ontology",
         "//knora/dsplib/utils:xml_upload",
-        "//knora/dsplib/utils:excel_to_json_lists"
+        "//knora/dsplib/utils:excel_to_json_lists",
+        "//knora/dsplib/utils:excel_to_json_resources"
     ],
     data = [
         "//testdata:testdata",
diff --git a/test/test_tools.py b/test/test_tools.py
index 096cc9913..574ed126b 100644
--- a/test/test_tools.py
+++ b/test/test_tools.py
@@ -4,6 +4,7 @@
 
 from knora.dsplib.utils import excel_to_json_lists
 from knora.dsplib.utils.excel_to_json_lists import list_excel2json
+from knora.dsplib.utils.excel_to_json_resources import resources_excel2json
 from knora.dsplib.utils.onto_create_ontology import create_ontology
 from knora.dsplib.utils.onto_get import get_ontology
 from knora.dsplib.utils.onto_validate import validate_ontology
@@ -22,6 +23,8 @@ def tearDown(self) -> None:
         excel_to_json_lists.cell_names = []
 
     def test_get(self):
+        global other_tree_list, other_tree_list_out, not_used_list, not_used_list_out, tree_list_root, tree_list_root_out
+
         with open('testdata/anything-onto.json') as f:
             onto_json_str = f.read()
         anything_onto = json.loads(onto_json_str)
@@ -75,11 +78,15 @@ def test_get(self):
         # TODO fix this test
         # self.assertEqual(anything_onto['project']['ontologies'], anything_onto_out['project']['ontologies'])
 
-    def test_excel(self):
+    def test_excel_to_json_list(self):
         list_excel2json(listname='my_test_list',
                         excelfolder='testdata/lists',
                         outfile='_lists-out.json')
 
+    def test_excel_to_json_resources(self):
+        resources_excel2json(excelfile='testdata/Resources.xlsx',
+                             outfile='_resources-out.json')
+
     def test_validate_ontology(self):
         validate_ontology('testdata/test-onto.json')
 
diff --git a/testdata/BUILD.bazel b/testdata/BUILD.bazel
index a2a6d1caf..9c6edfd52 100644
--- a/testdata/BUILD.bazel
+++ b/testdata/BUILD.bazel
@@ -9,6 +9,7 @@ filegroup(
     visibility = ["//visibility:public"],
     srcs = [
         "anything-onto.json",
+        "Resources.xlsx",
         "lists/description_en.xlsx",
         "lists/Beschreibung_de.xlsx",
         "test-data.xml",
diff --git a/testdata/Resources.xlsx b/testdata/Resources.xlsx
new file mode 100644
index 000000000..8a5c21be5
Binary files /dev/null and b/testdata/Resources.xlsx differ