diff --git a/.DS_Store b/.DS_Store
new file mode 100644
index 0000000..9a874b5
Binary files /dev/null and b/.DS_Store differ
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 0000000..b547f39
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by [contacting the project team](contact.md). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This code of conduct has been derived from the excellent code of conduct of the [ATOM project](https://github.com/atom/atom/blob/master/CODE_OF_CONDUCT.md) which in turn is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://contributor-covenant.org/version/1/4][version]
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..3adf6dc
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,97 @@
+# Contributing to KDSF VIVO Integration
+
+:+1: First of all: Thank you for taking the time to contribute!
+
+The following is a set of guidelines for contributing to KDSF-VIVO-INTEGRATION.
+These guidelines are not strict rules. Use your best judgment, and feel free to propose
+changes to this document in a pull request.
+
+## Table Of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Guidelines for Contributions and Requests](#contributions)
+ * [Reporting problems with the ontology](#reporting-bugs)
+ * [Requesting new terms](#requesting-terms)
+ * [Suggesting Enhancements](#suggesting-enhancements)
+ * [Fixing problems with the ontology by yourself](#fixing problems)
+ * [Adding new terms by yourself](#adding-terms)
+- [Best practices](#best-practices)
+ * [How to write a great issue?](#great-issues)
+ * [How to create a great pull/merge request?](#great-pulls)
+
+
+
+## Code of Conduct
+
+The KDSF VIVO Integration team strives to create a
+welcoming environment for editors, users and other contributors.
+Please carefully read our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+
+
+## Guidelines for Contributions and Requests
+
+
+
+### Reporting problems with the ontology
+
+Please use our [Issue Tracker](https://github.com/bua-vivo/VIVO-KDSF-Integration/issues/) for reporting problems with the ontology.
+To learn how to write a good issue [see here](#great-issues).
+
+
+
+### Requesting new terms
+
+Before you write a new request, please consider the following:
+
+- **Does the term already exist?** Before submitting suggestions for new ontology terms, check whether the term exist,
+either as a primary term or a synonym term.
+- **Can you provide a definition for the term?** It should be very clear what the term means, and you should be
+able to provide a concise definition, ideally with a scientific reference.
+- **Is the ontology in scope for the term?** Sometimes, it is hard to tell whether a term "belongs" in
+and ontology. A rule of thumb is "if a similar term already exists, the new term is probably in scope."
+It can be very helpful to mention a very similar concept as part of the term request!
+
+#### Who can request a term?
+
+Anyone can request new terms. However, there is not guarantee that your term will be added automatically. Since this is a
+community resource, it is often necessary to do at least some of the work of adding the term yourself, see below.
+
+#### How to write a new term request
+
+Request a new term _via_ the GitHub [Issue Tracker](https://github.com/bua-vivo/VIVO-KDSF-Integration/issues/).
+
+It is important to remember that it takes a lot of time for curators to process issues submitted to the tracker.
+To make this work easier, please always use issue templates if they are available (https://github.com/bua-vivo/VIVO-KDSF-Integration/issues/new/choose).
+
+For how to write a good term request, please read the [best practices carefully](#great-issues).
+
+
+
+### How to add a new term
+
+If you have never editted this ontology before, first follow a [general tutorial](https://oboacademy.github.io/obook/lesson/contributing-to-obo-ontologies)
+
+**Process**:
+
+1. Clone the repository (In case you are not an offical team member, create a fork first)
+1. Create new branch in git, for example `git checkout -b issue123`
+1. Open src/ontology/KDSF-VIVO-Integration-edit.owl in your favourite editor, i.e. [Protege](https://protege.stanford.edu/). **Careful:** double check you are editing the correct file. There are many ontology files in this repository, but only one _editors file_!
+1. Perform your edit and save your changes
+1. Commit changes to branch
+1. Push changes upstream
+1. Create pull request
+
+## Best Practices
+
+
+
+### How to write great issues?
+
+Please refer to the [OBO Academy best practices](https://oboacademy.github.io/obook/lesson/term-request/).
+
+
+
+### How to create a great pull/merge request?
+
+Please refer to the [OBO Academy best practices](https://oboacademy.github.io/obook/howto/github-create-pull-request/)
\ No newline at end of file
diff --git a/KDSF-VIVO-Integration-base.owl b/KDSF-VIVO-Integration-base.owl
new file mode 100644
index 0000000..9229918
--- /dev/null
+++ b/KDSF-VIVO-Integration-base.owl
@@ -0,0 +1,1804 @@
+
+
+
+
+
+
+ kdsf
+ This ontology is an adoption of the Research Core Dataset (KDSF). This alignment was originally created by Tatiana Walther, Anna Kasprzik and Christian Hauschke (Technische Informationsbibliothek (TIB)) for use in current research information system VIVO. The prior version vas tested with VIVO 1.9."
+
+The ontology is forked for update to the current KDSF standard at version 1.3 for use by the Berlin University Alliance, and redeveloped by Rolf Guescini (Humboldt-Universität Berlin), and will be tested in VIVO 1.13.x
+ This ontology is available under the Creative Commons Attribution-ShareAlike 4.0 International.
+ KDSF-VIVO-Alignment
+ 2017-01-04
+ 2023-01-27
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Fi5
+
+
+
+ true
+ hat Art
+
+
+
+
+
+
+
+
+
+
+ Fi11
+
+
+ true
+
+ true
+ hat Betreiber
+
+
+
+
+
+
+
+
+
+
+ Fi13
+
+
+ true
+
+ true
+ hat Betriebspersonal
+
+
+
+
+
+
+
+
+
+
+ Na47
+
+
+ true
+
+ true
+ hat Erstbetreuerin / Erstbetreuer
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Be38
+ Dr28
+ Na2
+ Pa1
+ Pu138
+
+
+
+ true
+ hat Fach
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Be8
+ Na14
+ 10
+
+
+
+ true
+ hat Finanzierungsform
+
+
+
+
+
+
+
+
+
+
+ Fi12
+
+
+ true
+
+ true
+ hat Koordinator
+
+
+
+
+
+
+
+
+
+
+ Dr12
+
+
+
+ true
+ hat Mittelgeber
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Be75
+ Dr121
+ Na92
+ Pa35
+ Pu140
+
+
+ true
+
+ true
+ hat Organisationseinheit
+
+
+
+
+
+
+
+
+
+
+ Fi14
+
+
+ true
+
+ true
+ hat Publikation
+
+
+
+
+
+
+
+
+
+
+ Be9
+ 6
+
+
+
+ true
+ hat Qualifikation
+
+
+
+
+
+
+
+
+
+
+ Na4a
+ 7
+
+
+ true
+
+ true
+ hat Qualifizierungsverfahren
+
+
+
+
+
+
+
+
+
+
+ Na17
+
+
+ true
+
+ true
+ hat Sprecher
+
+
+
+
+
+
+
+
+
+
+ Be32
+ 5
+
+
+
+ true
+ hat Tätigkeitsart
+
+
+
+
+
+
+
+
+
+
+ Dr10
+
+
+ true
+
+ true
+ hat übergeordnetes Projekt
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Pu86
+ Pu90
+ dcterms.funding
+ kds.funding.grantnumber
+
+
+ true
+
+ true
+ Alternativ zu den direkten Eigenschaften Förderer (Pu86) und Förderkennzeichen (Pu90), kann eine Verbindung zu Drittmittelprojekt bzw. Promotionsprogramm angegeben werden, worüber sich Förderer und Förderkennzeichen ableiten lassen
+ hat Unterstützung durch
+
+
+
+
+
+
+
+
+
+
+ Fi6
+
+
+
+ true
+ Art des Zugangs
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Fi28
+
+
+
+ Anzahl genutzte Stunden
+
+
+
+
+
+
+
+
+
+ Fi7
+
+
+
+ Anzahl Nutzer
+
+
+
+
+
+
+
+
+
+ Fi29
+
+
+
+ Anzahl Nutzungszugriffe
+
+
+
+
+
+
+
+
+
+
+ Dr88
+
+
+
+ Bewilligungssume
+
+
+
+
+
+
+
+
+
+ Be41
+
+
+
+ Bezeichnung der Professur
+
+
+
+
+
+
+
+
+
+
+ Dr1a
+
+
+
+ Drittmitteleinnahmen
+
+
+
+
+
+
+
+
+
+
+ Dr1b
+
+
+
+ Drittmittelerträge
+
+
+
+
+
+
+
+
+
+ Dr13
+
+
+
+ Förderkennzeichen des Drittmittelprojekts
+
+
+
+
+
+
+
+
+
+
+ Pu90
+ kds.funding.grantnumber
+
+
+
+ Das Förderkennzeichen des Mittelgebers, sofern in der Publikation angegeben.
+ Förderkennzeichen der Publikation
+
+
+
+
+
+
+
+
+
+
+ Dr142
+
+
+
+ Koordinationsrolle (Einrichtung)
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Na94
+
+
+
+
+ Außeruniversitäre Forschungseinrichtung
+
+
+
+
+
+
+
+
+
+ Pu37
+
+
+
+
+ Arbeitspapier/Forschungsbericht
+
+
+
+
+
+
+
+
+
+ Pu25
+
+
+
+
+ Artikel
+
+
+
+
+
+
+
+
+ Pa39
+
+ Ausgründung
+
+
+
+
+
+
+
+
+ Be89
+
+
+
+
+ Ausserplanmässiger Professor
+
+
+
+
+
+
+
+
+
+ Pu39
+
+
+
+
+ Beiträge bzw. Interviews in nicht-wissenschaftlichen Medien
+
+
+
+
+
+
+
+
+ Be0
+
+
+
+
+ Personen, die in einem Beschäftigungsverhältnis sind.
+ Beschäftigte / Beschäftigter
+
+
+
+
+
+
+
+
+ Pu129
+
+
+
+
+ Bibliographie [Journalartikel]
+
+
+
+
+
+
+
+
+ Pu24
+
+
+
+
+ Bibliographie [Buch]
+
+
+
+
+
+
+
+
+
+ Pu22
+
+
+
+
+ Buch
+
+
+
+
+
+
+
+
+
+ Pu38
+
+
+
+
+ Datensammlung
+
+
+
+
+
+
+
+
+ Pu34
+
+
+
+
+ Dissertation
+
+
+
+
+
+
+
+
+ Dr2a
+ Dr30
+ Drittmittelprojekte im Sinne des Kerndatensatzes sind zeitlich befristet geförderte Forschungsaktivitäten mit Startdatum, Enddatum und Forschungsgegenstand, deren Finanzierung aus Drittmitteln erfolgt.
+
+
+
+
+ Drittmittelprojekt
+
+
+
+
+
+
+
+
+
+ Pu121
+
+
+
+
+ Editorial
+
+
+
+
+
+
+
+
+ Na93
+
+
+
+
+ Fachhochschule
+
+
+
+
+
+
+
+ Be38
+ Dr28
+ Na2
+ Pa1
+ Pu138
+
+
+
+ Fach
+
+
+
+
+
+
+
+ Be8
+ Na14
+
+
+
+ Finanzierungsform
+
+
+
+
+
+
+
+ Fi2
+ Forschungsinfrastrukturen im Sinne des Kerndatensatzes sind umfangreiche / aufwendige Instrumente, Ressourcen oder Serviceeinrichtungen für die Forschung in allen Wissenschaftsgebieten, die sich durch eine mindestens überregionale Bedeutung für das jeweilige Wissenschaftsgebiet sowie durch eine mittel- bis langfristige Lebensdauer (mehr als 5 Jahre) auszeichnen und für eine externe Nutzung zur Verfügung stehen für die Zugangs- bzw. Nutzungsregelungen etabliert sind.
+
+
+
+
+ Forschungsinfrastruktur
+
+
+
+
+
+
+
+ Fi5
+
+
+
+ Art der Forschungsinfrastruktur
+
+
+
+
+
+
+
+
+
+
+ Fi15
+
+
+
+
+ Großgeräte und Instrumente
+
+
+
+
+
+
+
+
+
+ Be16
+ Na44
+ Habilitation
+
+
+
+
+
+
+
+
+ Pu35
+
+
+
+
+ Habilitationsschrift
+
+
+
+
+
+
+
+
+ Be30
+
+
+
+
+ Hauptberuflicher Gastprofessor
+
+
+
+
+
+
+
+
+ Pu51
+
+
+
+
+ Herausgeberschaft eines Sonderhefts einer Zeitschrift
+
+
+
+
+
+
+
+
+ Pu48
+
+
+
+
+ Herausgegebenes Buch
+
+
+
+
+
+
+
+
+ Fi17
+
+
+
+
+ Informations- und Kommunikationsinfrastrukturen
+
+
+
+
+
+
+
+
+ Pu11
+
+
+
+
+ Journalartikel
+
+
+
+
+
+
+
+
+ Be29
+
+
+
+
+ Juniorprofessor
+
+
+
+
+
+
+
+
+
+ Pu26
+
+
+
+
+ Konferenzposter
+
+
+
+
+
+
+
+
+ Pu120
+
+
+
+
+ Letter to the Editor
+
+
+
+
+
+
+
+
+ Pu48
+
+
+
+
+ Meeting Abstract
+
+
+
+
+
+
+
+ Dr12
+
+
+
+ Mittelgeber
+
+
+
+
+
+
+
+
+ Pu13
+
+
+
+
+ Monographie
+
+
+
+
+
+
+
+
+ Pu111
+
+
+
+
+ Neuer Publikations- oder Dokumenttyp
+
+
+
+
+
+
+
+
+ Be37
+
+
+
+
+ Ordentlicher Professor
+
+
+
+
+
+
+
+
+ Be75
+ Dr121
+ Na92
+ Pa35
+ Pu140
+
+
+
+
+ Organisationseinheit
+
+
+
+
+
+
+
+
+ Pa2
+ Pa25
+
+
+
+
+ Technisch einmalige erteilte Patente. Erteilungen für die gleiche Erfindung in zwei oder mehr Ländern werden nur einfach gezählt. Wenn ein technisch einmaliges erteiltes Patent im Vorjahr gezählt wurde, kann es nicht noch einmal aufgeführt werden.
+ Patent
+
+
+
+
+
+
+
+
+
+
+
+
+ Zusammenfassendes Konzept für die Darstellung aller personenbezogenen Eigenschaften und Attribute
+ Person
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Be19
+
+
+
+
+ Professor
+
+
+
+
+
+
+
+
+
+ Be17
+ Na43
+ Promotion
+
+
+
+
+
+
+
+
+ Na86
+
+
+
+
+ Promotionskooperationspartner
+
+
+
+
+
+
+
+
+ Pu1
+ Pu4a
+
+
+
+
+ Publikation
+
+
+
+
+
+
+
+ Be9
+
+
+
+ Qualifikation
+
+
+
+
+
+
+
+
+
+ Pu146
+
+
+
+
+ Qualifikationsschrift
+
+
+
+
+
+
+
+
+ Na4a
+
+
+
+ Qualifizierungsverfahren
+
+
+
+
+
+
+
+
+ Pu130
+
+
+
+
+ Quellenedition [Journalartikel]
+
+
+
+
+
+
+
+
+ Pu47
+
+
+
+
+ Quellenedition [Buch]
+
+
+
+
+
+
+
+
+ Pu114
+
+
+
+
+ Review
+
+
+
+
+
+
+
+
+
+ Pu30
+
+
+
+
+ Rezension
+
+
+
+
+
+
+
+
+ Pu23
+
+
+
+
+ Sammelband
+
+
+
+
+
+
+
+
+ Pu110
+
+
+
+
+ Sammelbandbeitrag
+
+
+
+
+
+
+
+
+ Be31
+
+
+
+
+ Seniorprofessor
+
+
+
+
+
+
+
+
+
+ Pu45
+
+
+
+
+ Software
+
+
+
+
+
+
+
+
+ Be73
+ Umfasst Personal, das nicht wissenschaftlich oder wissenschaftsunterstützend arbeitet und kein Verwaltungspersonal ist.
+
+
+
+
+
+
+
+
+
+
+
+
+ Be59
+
+
+
+
+ Stiftungsprofessor
+
+
+
+
+
+
+
+
+ Na3
+ Na48
+
+
+
+
+ Strukturiertes Promotionsprogramm
+
+
+
+
+
+
+
+ Be32
+
+
+
+ Tätigkeitsart
+
+
+
+
+
+
+
+
+
+ Na96
+
+
+
+
+ Universität
+
+
+
+
+
+
+
+
+ Pu67
+ dcterms.publisher
+
+
+
+
+ Verlag
+
+
+
+
+
+
+
+
+ Be58
+
+
+
+
+ Vertretungsprofessor/Lehrstuhlvertreter
+
+
+
+
+
+
+
+
+ Be28
+
+
+
+
+ Verwaltungspersonal
+
+
+
+
+
+
+
+
+ Be18
+
+
+
+
+ Wissenschaftliche oder künstlerische Hilfskräfte
+
+
+
+
+
+
+
+
+ Be22
+
+
+
+
+ Wissenschaftliche und künstlerische Mitarbeiter
+
+
+
+
+
+
+
+
+
+ Pu44
+
+
+
+
+ Wissenschaftliche Vortragsfolien
+
+
+
+
+
+
+
+
+
+ Pu112
+
+
+
+
+ Wissenschaftlicher Artikel
+
+
+
+
+
+
+
+
+ Be68
+
+
+
+
+ Wissenschaftliches und künstlerisches Personal
+
+
+
+
+
+
+
+
+ Be63
+ Fi26
+
+
+
+
+ Wissenschaftsunterstützendes Personal
+
+
+
+
+
+
+
+
+ Fi16
+
+
+
+
+ Wissensressourcen
+
+
+
+
+
+
+
+ Fi6
+
+
+
+ Art des Zugangs
+
+
+
+
+
+
+
+
+ Pu29
+
+
+
+
+ ePaper
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/KDSF-VIVO-Integration-base.ttl b/KDSF-VIVO-Integration-base.ttl
new file mode 100644
index 0000000..6cb6494
--- /dev/null
+++ b/KDSF-VIVO-Integration-base.ttl
@@ -0,0 +1,1377 @@
+@prefix : .
+@prefix owl: .
+@prefix rdf: .
+@prefix xml: .
+@prefix xsd: .
+@prefix rdfs: .
+@base .
+
+ rdf:type owl:Ontology ;
+ owl:versionIRI ;
+ ;
+ ;
+ "kdsf" ;
+ rdfs:comment """This ontology is an adoption of the Research Core Dataset (KDSF). This alignment was originally created by Tatiana Walther, Anna Kasprzik and Christian Hauschke (Technische Informationsbibliothek (TIB)) for use in current research information system VIVO. The prior version vas tested with VIVO 1.9.\"
+
+The ontology is forked for update to the current KDSF standard at version 1.3 for use by the Berlin University Alliance, and redeveloped by Rolf Guescini (Humboldt-Universität Berlin), and will be tested in VIVO 1.13.x"""^^xsd:string ,
+ "This ontology is available under the Creative Commons Attribution-ShareAlike 4.0 International."^^xsd:string ;
+ rdfs:label "KDSF-VIVO-Alignment"@de-de ;
+ owl:versionInfo "2017-01-04"^^xsd:string ,
+ "2023-01-27"^^xsd:string .
+
+#################################################################
+# Annotation properties
+#################################################################
+
+### http://kerndatensatz-forschung.de/owl/Meta#inhaltlicheDefinition
+ rdf:type owl:AnnotationProperty .
+
+
+### http://kerndatensatz-forschung.de/owl/Meta#pgbid
+ rdf:type owl:AnnotationProperty .
+
+
+### http://purl.obolibrary.org/obo/IAO_0000115
+ rdf:type owl:AnnotationProperty .
+
+
+### http://purl.org/dc/terms/rights
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#descriptionAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#displayRankAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#hiddenFromDisplayBelowRoleLevelAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#hiddenFromPublishBelowRoleLevelAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#inClassGroup
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#offerCreateNewOptionAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#ontologyPrefixAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#prohibitedFromUpdateBelowRoleLevelAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#publicDescriptionAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+### http://vitro.mannlib.cornell.edu/ns/vitro/0.7#selectFromExistingAnnot
+ rdf:type owl:AnnotationProperty .
+
+
+#################################################################
+# Object Properties
+#################################################################
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatArt
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Fi5" ;
+ ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Art"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatBetreiber
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Fi11" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Betreiber"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatBetriebspersonal
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Fi13" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Betriebspersonal"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatErstbetreuer
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Na47" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Erstbetreuerin / Erstbetreuer"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatFach
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain [ rdf:type owl:Class ;
+ owl:unionOf (
+
+
+
+ )
+ ] ;
+ rdfs:range ;
+ "Be38" ,
+ "Dr28" ,
+ "Na2" ,
+ "Pa1" ,
+ "Pu138" ;
+ ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Fach"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatFinanzierungsform
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain [ rdf:type owl:Class ;
+ owl:unionOf (
+
+ )
+ ] ;
+ rdfs:range ;
+ "Be8" ,
+ "Na14" ;
+ "10"^^xsd:int ;
+ ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Finanzierungsform"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatKoordinator
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Fi12" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Koordinator"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatMittelgeber
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Dr12" ;
+ ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Mittelgeber"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatOrganisationseinheit
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain [ rdf:type owl:Class ;
+ owl:unionOf (
+
+
+
+ )
+ ] ;
+ rdfs:range ;
+ "Be75" ,
+ "Dr121" ,
+ "Na92" ,
+ "Pa35" ,
+ "Pu140" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Organisationseinheit"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatPublikation
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Fi14" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Publikation"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatQualifikation
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Be9" ;
+ "6"^^xsd:int ;
+ ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Qualifikation"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatQualifizierungsverfahren
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Na4a" ;
+ "7"^^xsd:int ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Qualifizierungsverfahren"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatSprecher
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Na17" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Sprecher"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatTaetigkeitsart
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Be32" ;
+ "5"^^xsd:int ;
+ ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat Tätigkeitsart"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatUebergeordnetesProjekt
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Dr10" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "hat übergeordnetes Projekt"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatUnterstuetzungDurch
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf ;
+ rdfs:domain ;
+ rdfs:range [ rdf:type owl:Class ;
+ owl:unionOf (
+
+ )
+ ] ;
+ "Pu86" ,
+ "Pu90" ;
+ "dcterms.funding" ,
+ "kds.funding.grantnumber" ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:comment "Alternativ zu den direkten Eigenschaften Förderer (Pu86) und Förderkennzeichen (Pu90), kann eine Verbindung zu Drittmittelprojekt bzw. Promotionsprogramm angegeben werden, worüber sich Förderer und Förderkennzeichen ableiten lassen" ;
+ rdfs:label "hat Unterstützung durch"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#hatZugangsart
+ rdf:type owl:ObjectProperty ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ rdfs:domain ;
+ rdfs:range ;
+ "Fi6" ;
+ ;
+ ;
+ ;
+ "true"^^xsd:boolean ;
+ rdfs:label "Art des Zugangs"@de-de .
+
+
+### http://vivoweb.org/ontology/core#informationResourceSupportedBy
+ rdf:type owl:ObjectProperty .
+
+
+#################################################################
+# Data properties
+#################################################################
+
+### http://kerndatensatz-forschung.de/owl/Basis#AnzahlGenutzteStunden
+ rdf:type owl:DatatypeProperty ;
+ rdfs:domain ;
+ rdfs:range xsd:nonNegativeInteger ;
+ "Fi28" ;
+ ;
+ ;
+ ;
+ rdfs:label "Anzahl genutzte Stunden"@de-de .
+
+
+### http://kerndatensatz-forschung.de/owl/Basis#AnzahlNutzer
+ rdf:type owl:DatatypeProperty ;
+ rdfs:domain ;
+ rdfs:range xsd:nonNegativeInteger ;
+ "Fi7" ;
+ ;
+