-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathFundingStateExample.ttl
More file actions
76 lines (66 loc) · 3.89 KB
/
FundingStateExample.ttl
File metadata and controls
76 lines (66 loc) · 3.89 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
# This is an example of how an organization (i.e. a funder) would share their own custom list of cids:FundingState instances.
@base <https://www.example-funder.org/FundingStateExample> . # this is the URL and filename (without suffix) where this list file would be stored on the organization's own web server.
@prefix : <#> .
@prefix cids: <https://ontology.commonapproach.org/cids#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix fstate: <https://codelist.commonapproach.org/FundingState#> . # added prefix for the Common Approach funding state list, per the vann: recommended prefix in that file.
@prefix org: <http://ontology.eil.utoronto.ca/tove/organization#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix voaf: <http://purl.org/vocommons/voaf#> .
@prefix vann: <http://purl.org/vocab/vann/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<>
a voaf:Vocabulary, owl:Ontology, skos:ConceptScheme ;
owl:imports <https://ontology.commonapproach.org/cids> ;
vann:preferredNamespacePrefix "exfs" ; # the funder recommended a prefix for their list items, for use by others (as the fstate: prefix is used here, recommended by the Common Approach list)
vann:preferredNamespaceUri <> ;
dcterms:creator <https://www.example-funder.org/Organization/Organization1> ; # this is the URI the funder uses to identify their own organization
dcterms:date "2025-11-05"^^xsd:date ; # the date that the list is published
owl:versionInfo "1.0" ; # the version of the list
skos:prefLabel "FundingState Codelist by Example Funder"@en ;
dcterms:title "FundingState Codelist by Example Funder"@en ;
dcterms:description "A codelist vocabulary of funding states to describe funding applications to Example Funder."@en .
:expressedinterest
a cids:FundingState ;
org:hasName "Expressed Interest" ;
skos:prefLabel "Expressed Interest"@en ;
cids:hasDescription "The organization has expressed interest to the funder for funding" ;
skos:definition "The organization has expressed interest to the funder for funding"@en ;
org:hasIdentifier "eoi" ;
skos:notation "eoi" ;
cids:definedBy cids:ac ;
cids:hasSpecification <> ;
rdfs:isDefinedBy <> ;
skos:inScheme <> ;
skos:broader fstate:applied # if applicable, different skos: terms (narrower, exactMatch broader) can be used to show how this list item is conceptually related to the "applied" item in the Common Approach list of terms.
.
:duediligence
a cids:FundingState ;
org:hasName "Due Diligence" ;
skos:prefLabel "Due Diligence"@en ;
cids:hasDescription "The organization's application is in due diligence review" ;
skos:definition "The organization's application is in due diligence review"@en ;
org:hasIdentifier "diligence" ;
skos:notation "diligence" ;
cids:definedBy cids:ac ;
cids:hasSpecification <> ;
rdfs:isDefinedBy <> ;
skos:inScheme <> ;
skos:broader fstate:applied # if applicable, different skos: terms (narrower, exactMatch broader) can be used to show how this list item is conceptually related to the "applied" item in the Common Approach list of terms.
.
:exited
a cids:FundingState ;
org:hasName "Exited" ;
skos:prefLabel "Exited"@en ;
cids:hasDescription "The funder has exited investment in the applicant organization" ;
skos:definition "The funder has exited investment in the applicant organization"@en ;
org:hasIdentifier "exited" ;
skos:notation "exited" ;
cids:definedBy cids:ac ;
cids:hasSpecification <> ;
rdfs:isDefinedBy <> ;
skos:inScheme <> ;
skos:broader fstate:invested # if applicable, different skos: terms (narrower, exactMatch broader) can be used to show how this list item is conceptually related to the "applied" item in the Common Approach list of terms.
.