...
122 | """
123 | return re.sub(r'`([^`]*)`', r'\1
', text_with_backticks)
124 |
125 | def convert_link(text_with_urls):
126 | """Takes all links in a text field and converts it to the html tagged
127 | version of the link
128 | """
129 | def _handle_matched(inputstring):
130 | """quick hack version of url handling on the current prime versions data"""
131 | url = inputstring.group()
132 | return "{}".format(url, url)
133 |
134 | regx = "(http[s]?://[\w\d:#@%/;$()~_?\+-;=\\\.&]*)(?{% for example in examples %}Term Name ' + curie + ' | \n' 336 | text += '\t\t|||||
---|---|---|---|---|---|
Term IRI | \n' 341 | uri = row['pref_ns_uri'] + row['term_localName'] 342 | text += '\t\t\t' + uri + ' | \n' 343 | text += '\t\t||||
Modified | \n' 346 | text += '\t\t\t' + row['term_modified'] + ' | \n' 347 | text += '\t\t||||
Term version IRI | \n' 352 | text += '\t\t\t' + row['version_iri'] + ' | \n' 353 | text += '\t\t||||
Label | \n' 357 | text += '\t\t\t' + row['label'] + ' | \n' 358 | text += '\t\t||||
\n' 363 | text += '\t\t\t | This term is deprecated and should no longer be used. | \n' 364 | text += '\t\t||||
Is replaced by | \n' 370 | text += '\t\t\t' + dep_row['pref_ns_uri'] + dep_row['term_localName'] + ' | \n' 371 | text += '\t\t||||
Is replaced by | \n' 375 | text += '\t\t\t' + dep_row['pref_ns_uri'] + dep_row['term_localName'] + ' | \n' 376 | text += '\t\t||||
Definition | \n' 380 | text += '\t\t\t' + row['rdfs_comment'] + ' | \n' 381 | #text += '\t\t\t' + row['definition'] + ' | \n' 382 | text += '\t\t|||
Notes | \n' 388 | text += '\t\t\t' + convert_link(convert_code(row['dcterms_description'])) + ' | \n' 389 | #text += '\t\t\t' + createLinks(row['notes']) + ' | \n' 390 | text += '\t\t|||
Examples | \n' 396 | text += '\t\t\t' + convert_examples(convert_link(convert_code(row['examples']))) + ' | \n' 397 | #text += '\t\t\t' + createLinks(row['usage']) + ' | \n' 398 | text += '\t\t|||
ABCD equivalence | \n' 404 | text += '\t\t\t' + convert_link(convert_code(row['tdwgutility_abcdEquivalence'])) + ' | \n' 405 | text += '\t\t||||
Controlled value | \n' 410 | text += '\t\t\t' + row['controlled_value_string'] + ' | \n' 411 | text += '\t\t||||
Has broader concept | \n' 416 | curieAnchor = row['skos_broader'].replace(':','_') 417 | text += '\t\t\t' + row['skos_broader'] + ' | \n' 418 | text += '\t\t||||
Type | \n' 422 | if row['rdf_type'] == 'http://www.w3.org/1999/02/22-rdf-syntax-ns#Property': 423 | #if row['type'] == 'http://www.w3.org/1999/02/22-rdf-syntax-ns#Property': 424 | text += '\t\t\tProperty | \n' 425 | elif row['rdf_type'] == 'http://www.w3.org/2000/01/rdf-schema#Class': 426 | #elif row['type'] == 'http://www.w3.org/2000/01/rdf-schema#Class': 427 | text += '\t\t\tClass | \n' 428 | elif row['rdf_type'] == 'http://www.w3.org/2004/02/skos/core#Concept': 429 | #elif row['type'] == 'http://www.w3.org/2004/02/skos/core#Concept': 430 | text += '\t\t\tConcept | \n' 431 | else: 432 | text += '\t\t\t' + row['rdf_type'] + ' | \n' # this should rarely happen 433 | #text += '\t\t\t' + row['type'] + ' | \n' # this should rarely happen 434 | text += '\t\t
Executive Committee decision | \n' 441 | text += '\t\t\thttp://rs.tdwg.org/decisions/' + drow['decision_localName'] + ' | \n' 442 | text += '\t\t
...
147 | """
148 | return re.sub(r'`([^`]*)`', r'\1
', text_with_backticks)
149 |
150 | @staticmethod
151 | def convert_link(text_with_urls):
152 | """Takes all links in a text field and converts it to the html tagged
153 | version of the link
154 | """
155 | def _handle_matched(inputstring):
156 | """quick hack version of url handling on the current prime versions data"""
157 | url = inputstring.group()
158 | return "{}".format(url, url)
159 |
160 | regx = "(http[s]?://[\w\d:#@%/;$()~_?\+-;=\\\.&]*)(?
110 |
111 | '''
112 | # Insert the previous version information into the designated slot.
113 | header = header.replace('{previous_version_slot}\n\n', previous_version_metadata_string)
114 | else:
115 | # If there was no previous version, remove the slot from the header.
116 | header = header.replace('{previous_version_slot}\n\n', '')
117 |
118 | outputObject = open(outFileName, 'wt', encoding='utf-8')
119 | outputObject.write(header)
120 | outputObject.close()
121 |
122 | print('done')
123 |
--------------------------------------------------------------------------------
/build/dwc_doc_hierarchy/index.md:
--------------------------------------------------------------------------------
1 | # {document_title}
2 |
3 | Title
4 | : {document_title}
5 |
6 | Date version issued
7 | : {ratification_date}
8 |
9 | Date created
10 | : {created_date}
11 |
12 | Part of TDWG Standard
13 | : <{standard_iri}>
14 |
15 | This version
16 | : <{current_iri}{ratification_date}>
17 |
18 | Latest version
19 | : <{current_iri}>
20 |
21 | {previous_version_slot}
22 |
23 | Abstract
24 | : {abstract}
25 |
26 | Contributors
27 | : {contributors}
28 |
29 | Creator
30 | : {creator}
31 |
32 | Bibliographic citation
33 | : {creator}. {year}. {document_title}. {publisher}. <{current_iri}{ratification_date}>
34 |
35 |
36 | ## 1 Introduction (non-normative)
37 |
38 | ### 1.1 Status of the content of this document
39 |
40 | Section 3 of this document is normative, serving as official guidelines
41 | in application of the Humboldt Extension. The other sections are
42 | non-normative and designed to help improve overall understanding in
43 | application and interpretation of the Extension.
44 |
45 | ### 1.2 RFC 2119 keywords
46 | ---------------------
47 |
48 | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
49 | "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to
50 | be interpreted as described in [BCP 14](https://datatracker.ietf.org/doc/html/bcp14)
51 | [[RFC2119]](https://datatracker.ietf.org/doc/html/rfc2119)
52 | [[RFC8174]](https://datatracker.ietf.org/doc/html/rfc8174)
53 | when, and only when, they are written in capitals (as shown here).
54 |
55 | ## 1.3 Namespaces and terminology
56 |
57 | The namespace `eco:` abbreviates terms minted for the Humboldt Extension
58 | for ecological inventories
59 | ([http://rs.tdwg.org/eco/terms/](http://rs.tdwg.org/eco/terms/)).
60 | `dwc:` abbreviates terms from the main Darwin Core vocabulary namespace
61 | ([http://rs.tdwg.org/dwc/terms/](http://rs.tdwg.org/dwc/terms/)).
62 |
63 | Words in `code markup` are term IRIs or literal values. The word
64 | "organism" is used colloquially and is not used in the technical sense
65 | of the dwc:Organism class, unless specifically presented as
66 | "dwc:Organism." The word "Event" is used in the technical sense of the
67 | dwc:Event class. "Humboldt Extension" is an abbreviation for the
68 | "Humboldt Extension for Ecological Inventories."
69 |
70 | ### 1.4 Intended audience and use for this document
71 |
72 | The information in this document is targeted at data providers, data
73 | aggregators, and data consumers. *Data providers* are the individuals
74 | responsible for mapping ecological inventory data into an Event-based
75 | [Darwin Core
76 | Archive](https://ipt.gbif.org/manual/en/ipt/latest/dwca-guide)
77 | format that includes the Humboldt Extension. *Data aggregators* and
78 | *data consumers* can use this document to better understand the data
79 | shared by data providers, specifically with respect to the
80 | **relationships between hierarchical dwc:Event levels** and **when it is
81 | or is not appropriate to make inferences** about attributes such as
82 | abundance or absence of detection.
83 |
84 |
85 | ## 2 Rationale (non-normative)
86 |
87 | Ecological inventories in the context of Darwin Core can be considered
88 | as types of [dwc:Events](http://rs.tdwg.org/dwc/terms/Event)
89 | --- they are actions that occur at specific locations over defined
90 | periods of time. The terms in the Humboldt Extension are all properties
91 | of a dwc:Event.
92 |
93 | There are many types of ecological inventory, ranging from singular
94 | observations of individual taxa (1 event:1 observation; Example 1 in
95 | Figure 1) to highly structured and deeply nested observations within
96 | other observations (e.g., 1 event:2 sub-events, each sub-event:2
97 | sub-sub-events; Example 4 in Figure 1). The need for guidance on **how
98 | to capture the details of nested observations** (dwc:Event hierarchies)
99 | is the rationale for this document. Nested sampling designs can be
100 | translated into a relational database schema of parent-child dwc:Event
101 | relationships (a parent event with one or more child sub-events; Figure
102 | 1). This document describes the circumstances under which specific
103 | properties of parent and child dwc:Events SHOULD be populated based on
104 | the parent-child relationship.
105 |
106 | Note that the proposed structure for sharing ecological inventories does
107 | not follow typical database practice. Whilst a (relational) database
108 | would store information in multiple tables to avoid repetition of key
109 | information, datasets shared using the Darwin Core archive format and
110 | the Humboldt Extension instead use a "flattened" structure. In order to
111 | share inventory data such that no information is lost and no information
112 | is incorrectly inferred, one SHOULD **report all information at all
113 | applicable levels**. The rules for applicability and how to populate
114 | terms at parent and child levels in the dwc:Event hierarchy are captured
115 | in section *3.2 Guiding principles* and in section *3.3 Implementation principles*.
116 |
117 |
118 | 
119 |
120 | **Figure 1.** Visual representation of an ecological inventory
121 | illustrating four examples of occurrence data associated with dwc:Events
122 | nested within parent dwc:Events, at varying levels of complexity ranging
123 | from low (Example 1) to high (Example 4).
124 |
125 |
126 | ## 3 Usage guidelines (normative)
127 |
128 | ### 3.1 Definitions
129 |
130 | **Inventory dataset** - An inventory (dataset) consists of one or more
131 | dwc:Events that MAY be related to each other in a hierarchy of parent
132 | and child dwc:Events. This is not new to the capabilities or intentions
133 | of Darwin Core.
134 |
135 | **Inventory hierarchy** - A set of related dwc:Events, in which a
136 | narrower dwc:Event (child) points to the related broader dwc:Event
137 | (parent) via the child's dwc:parentEventID. A higher-level dwc:Event
138 | generally contains information about the inventory design that applies
139 | to all of its children.
140 |
141 | **Parent dwc:Event** - A parent dwc:Event is any dwc:Event whose
142 | dwc:eventID is a dwc:parentEventID for at least one other dwc:Event
143 | (e.g. EVENT_01 in Figure 2).
144 |
145 | **Child dwc:Event** - A child dwc:Event is any dwc:Event whose
146 | dwc:parentEventID is populated with the dwc:eventID of another dwc:Event
147 | (e.g. EVENT_02 or EVENT_03 in Figure 2).
148 |
149 | 
150 |
151 | **Figure 2.** Visual representation of an inventory hierarchy
152 | illustrating parent-child dwc:Event relations. The higher-level (parent)
153 | dwc:Event, EVENT_01, may include general information about the inventory
154 | design. Species occurrences are captured for two child dwc:Events
155 | (EVENT_02 and EVENT_03).
156 |
157 |
158 | ## 3.2 Guiding principles
159 |
160 |
161 | ### 3.2.1 Principle of spatiotemporal coverage
162 |
163 | **A parent dwc:Event MUST encompass its child dwc:Events spatially
164 | and temporally.** Specifically, the spatial extent and temporal
165 | interval of a parent dwc:Event MUST contain the spatial extents and
166 | temporal intervals of all of its children. For example, if child
167 | dwc:Events took place in various locations throughout, and only within,
168 | Burundi, then the spatial extent of the parent dwc:Event would be
169 | Burundi. Similarly, if the child dwc:Events took place periodically
170 | throughout the year 2019, the temporal interval of the parent dwc:Event
171 | would begin when the earliest child dwc:Event began and end when the
172 | latest child dwc:Event ended.
173 |
174 |
175 | ### 3.2.2 Principle of applicability
176 |
177 | **Humboldt Extension terms SHOULD contain data explicitly at every level
178 | in the dwc:Event hierarchy to which they *directly* apply.** The value
179 | of a term for a dwc:Event SHOULD be populated for the Event itself
180 | rather than merely summarized in a higher-level dwc:Event. For example,
181 | a child dwc:Event (**C**) with multiple dwc:Occurrences, some of which
182 | resulted in voucher specimens, SHOULD possess a value of `true` for
183 | the term eco:hasVouchers. The data user SHOULD NOT be expected to look
184 | at the eco:hasVouchers term for the parent dwc:Event (**P**) of **C** in
185 | order to find the value.
186 |
187 | If a term genuinely applies at multiple levels of an dwc:Event
188 | hierarchy, values SHOULD be reported explicitly at *each* of those
189 | levels. The values for child dwc:Events might be the same as their
190 | parental values, or child dwc:Events might possess their own more
191 | specific values. This principle allows child dwc:Events to be
192 | "autonomous" to the greatest degree possible, and avoids uncertainty
193 | about where to look for the values of properties of any given dwc:Event.
194 |
195 |
196 | ### 3.2.3 Principle of non-derivation
197 |
198 | As a complement to the *Principle of applicability*, **Humboldt
199 | Extension terms SHOULD NOT be populated by deriving or summarizing
200 | information from child dwc:Events to their common parent dwc:Event**. If
201 | a term does not directly apply to a given level of dwc:Event (i.e., it
202 | is not an actual property of that dwc:Event), it SHOULD NOT be populated
203 | with a value. For example, if the parent dwc:Event **P** from the
204 | example in section *3.2.2* above is not directly linked to
205 | dwc:Occurrences, then the term eco:hasVouchers does not apply at that
206 | dwc:Event level and SHOULD be left unpopulated. Data providers SHOULD
207 | NOT construct a value for a parent dwc:Event from values at the level of
208 | child dwc:Events.
209 |
210 | In some cases, including the example above, it would not be valid to
211 | derive or summarize information from child dwc:Events to populate a
212 | parent dwc:Event. Suppose parent dwc:Event **P** has two child
213 | dwc:Events, one with eco:hasVouchers `true` and one with
214 | eco:hasVouchers `false`. The value of eco:hasVouchers for **P** cannot
215 | be derived or summarized from its children, as it is neither `true`
216 | nor `false` for all of them (the only two values consistent with the
217 | recommended controlled vocabulary for the term). It would be neither
218 | desirable nor reliable to use the values of the child dwc:Events to
219 | infer a value for the parent dwc:Event. The *Principle of inference*
220 | (below) provides a further example, where *scope* terms of parent
221 | dwc:Events MUST NOT be populated by summarizing from lower levels
222 | (either through the scope values of child dwc:Events or, for example,
223 | through taxa detected in child dwc:Events).
224 |
225 | There are terms which could theoretically be populated for a parent
226 | dwc:Event from the primary data already provided for that dwc:Event\'s
227 | children (e.g., eco:materialSampleTypes). Populating the parent term
228 | could facilitate the discovery of higher-level dwc:Events among whose
229 | children there is a particular value of a property (e.g., a search
230 | through the highest-level dwc:Events in datasets to find datasets in
231 | which there are particular eco:materialSampleTypes). However, providing
232 | such summary values is specifically NOT RECOMMENDED. Doing so a\) adds no
233 | information to the dataset (the summary information is already available
234 | by inspecting the primary data in the dwc:Events in the dataset), b\)
235 | adds an extra burden of summary upon the data provider, and c\) is
236 | susceptible to errors (ambiguities, inconsistencies, incompleteness)
237 | when trying to construct secondary summary information for higher-level
238 | Events.
239 |
240 |
241 | ### 3.2.4 Principle of inference
242 |
243 | **Certain terms in the Humboldt Extension support inferences.** Examples
244 | of terms that help data users to determine whether or not inferences can
245 | be made include those describing the *scope* of the inventory, such as
246 | eco:targetTaxonomicScope and eco:excludedTaxonomicScope, and terms
247 | describing *completeness*, such as eco:taxonCompletenessReported,
248 | eco:taxonCompletenessProtocols and eco:isTaxonomicScopeFullyReported.
249 | The values of these terms in a dwc:Event have implications for the
250 | interpretation of all of that dwc:Event's child dwc:Events. These terms
251 | MUST be populated for the highest level dwc:Event to which they apply,
252 | and all of its child dwc:Events.
253 |
254 | **The *scope* terms of a dwc:Event MUST be populated whenever the scope
255 | was in effect**. Having this information in a dwc:Event is the only way
256 | **to be able to infer absences of detection** within that dwc:Event,
257 | whenever the dwc:Occurrences linked to that dwc:Event do not explicitly
258 | state zero counts or when there are no dwc:Occurrence records for a
259 | given taxon that fell within the taxonomic scope (the combination of
260 | eco:targetTaxonomicScope and eco:excludedTaxonomicScope). The ability to
261 | "implicitly" support inferences about undetected dwc:Taxa (and other
262 | organismal targets) was a high priority objective in the design and
263 | structure of the Humboldt Extension. By "implicitly support
264 | inferences" we mean that a dwc:organismQuantity of zero individuals
265 | within a particular scope does not need to be provided explicitly as a
266 | separate dwc:Occurrence record, for a dwc:Event that does declare an
267 | encompassing scope and where all the taxa/targets that *were* detected
268 | were fully reported. Instead, those zero counts can be reconstituted by
269 | data users based on the data contained in other terms. When the target
270 | taxonomic scope (the combination of eco:targetTaxonomicScope and
271 | eco:excludedTaxonomicScope) is determined in advance of inventory data
272 | collection, and eco:isTaxonomicScopeFullyReported = `true`, then all
273 | dwc:Taxa that fall within the taxonomic scope but are not reported in
274 | the dwc:Occurrences of any child dwc:Events **can be inferred to be
275 | dwc:Occurrences with a dwc:organismQuantity of zero** (i.e., undetected
276 | dwc:Taxa).
277 |
278 | These inferred zero counts, in combination with information about
279 | sampling effort (i.e., eco:samplingEffortProtocol,
280 | eco:samplingEffortValue and eco:samplingEffortUnit), can then be used to
281 | estimate the likelihood that a count of zero organisms represents a
282 | *true* absence of a dwc:Taxon. However, if eco:taxonCompletenessReported
283 | = `reported incomplete` and/or eco:isTaxonomicScopeFullyReported =
284 | `false` for a dwc:Event, then future users SHOULD NOT make assumptions
285 | about absences.
286 |
287 | Data providers **MUST NOT retrospectively infer and populate
288 | eco:targetTaxonomicScope, or other *scope* terms**, for inclusion in a
289 | dataset shared with the Humboldt Extension. This is a further example of
290 | the *Principle of non-derivation* (*3.2.3*). Likewise, data users SHOULD
291 | NOT assume or reconstruct a scope that was not explicitly given by the
292 | data provider. There are at least two reasons for this: (1) Artificial
293 | construction of scope: retrospective inference of target scope by a data
294 | provider by aggregating information across all child dwc:Events may
295 | result in a reported scope that is narrower than the actual intended
296 | scope of the inventory. (2) Artificial broadening of scope: it is
297 | possible that the inferred scope can be described in multiple ways. For
298 | example, the scope of a list of species within a single genus could be
299 | described as the genus, as the family containing that genus, or as an
300 | even broader taxonomic concept. Thus, unless the true taxonomic scope is
301 | a known variable in the inventory protocol, then a presumed scope may be
302 | too broad or too narrow, leading to errors when inferring counts of
303 | zero.
304 |
305 |
306 | ## 3.3 Implementation principles
307 |
308 | 1. A Darwin Core-based inventory dataset MUST consist of at least one
309 | dwc:Event record.
310 |
311 | 2. Each dwc:Event in an inventory dataset MUST have a non-empty value
312 | for dwc:eventID that is unique within the dataset. More benefits
313 | are realizable if the dwc:eventIDs are also globally unique.
314 |
315 | 3. Any association of a Humboldt Extension record with a dwc:Event
316 | record MUST be done via that dwc:Event\'s dwc:eventID; the
317 | associated records MUST use the same dwc:eventID. It is
318 | permissible to have dwc:Event records without associated Humboldt
319 | Extension records.
320 |
321 | 4. An inventory hierarchy MUST be realized by explicitly relating each
322 | child dwc:Event to a parent dwc:Event through the child
323 | dwc:Event's dwc:parentEventID.
324 |
325 | 5. Data providers SHOULD follow [Darwin Core principle
326 | 4](https://dwc.tdwg.org/simple/#5-are-there-any-rules-normative),
327 | which is to fill the values of as many terms as possible, subject
328 | to the *Principle of applicability* and the *Principle of
329 | non-derivation* (sections *3.2.2* and *3.2.3*, respectively).
330 |
331 | 6. A child dwc:Event MUST NOT be assumed to implicitly "inherit" the
332 | value of any property of any of its parent dwc:Events; rather, the
333 | value SHOULD be provided explicitly as discussed in section *3.2.2
334 | Principle of applicability*.
335 |
336 | 7. A parent dwc:Event term SHOULD NOT be populated by deriving or
337 | summarizing information from child dwc:Events; rather, the value
338 | SHOULD be provided explicitly if appropriate to the nature and
339 | level of the dwc:Event, as discussed in section *3.2.3 Principle of non-derivation*.
340 |
341 |
342 | ## 4 Examples (non-normative)
343 |
344 | 
345 |
346 | **Figure 3.** Example illustrating the [Implementation
347 | principles](#implementation). Numbering of colored
348 | rectangles indicates the relevant principle; lines, arrows or rectangles
349 | in the same color indicate that the cells, columns or records are
350 | affected by the principle. *Notolepis coatsi* and *Cranchiidae* are not
351 | within the reported eco:targetTaxonomicScope. Principle 1 - an inventory
352 | dataset must have at least one dwc:Event record; here, 3 records can be
353 | identified. Principle 2 - each dwc:Event record must have a unique
354 | dwc:eventID. Principle 3 - Humboldt Extension records must be linked to
355 | the core dwc:Events via shared dwc:eventIDs. Principle 4 - every child
356 | dwc:Event must be related to its parent dwc:Event through a
357 | dwc:parentEventID. Principle 5 - term values for dwc:Events should be
358 | populated whenever possible; in the figure all records follow Darwin
359 | Core principle 4, subject to the *Principle of applicability* and the
360 | *Principle of non-derivation*. Principle 6 - terms for child dwc:Events
361 | must be explicitly populated rather than "inheriting" values from
362 | their parent dwc:Events. Principle 7 - terms for parent dwc:Events
363 | should be populated whenever relevant, but not be derived or summarized
364 | from their child dwc:Events.
365 |
--------------------------------------------------------------------------------
/build/dwc_doc_inclusive/index.md:
--------------------------------------------------------------------------------
1 | # {document_title}
2 |
3 | Title
4 | : {document_title}
5 |
6 | Date version issued
7 | : {ratification_date}
8 |
9 | Date created
10 | : {created_date}
11 |
12 | Part of TDWG Standard
13 | : <{standard_iri}>
14 |
15 | This version
16 | : <{current_iri}{ratification_date}>
17 |
18 | Latest version
19 | : <{current_iri}>
20 |
21 | {previous_version_slot}
22 |
23 | Abstract
24 | : {abstract}
25 |
26 | Contributors
27 | : {contributors}
28 |
29 | Creator
30 | : {creator}
31 |
32 | Bibliographic citation
33 | : {creator}. {year}. {document_title}. {publisher}. <{current_iri}{ratification_date}>
34 |
35 | ## 1 Introduction (non-normative)
36 |
37 | This document elaborates upon the meaning and use of the term `eco:isLeastSpecificTargetCategoryQuantityInclusive`. Use of this term is necessary in order to describe how to treat counts of organisms (or any other organisms quantity) when records from a single `dwc:Event` (...
121 | """
122 | return re.sub(r'`([^`]*)`', r'\1
', text_with_backticks)
123 |
124 | def convert_link(text_with_urls):
125 | """Takes all links in a text field and converts it to the html tagged
126 | version of the link
127 | """
128 | def _handle_matched(inputstring):
129 | """quick hack version of url handling on the current prime versions data"""
130 | url = inputstring.group()
131 | return "{}".format(url, url)
132 |
133 | regx = "(http[s]?://[\w\d:#@%/;$()~_?\+-;=\\\.&]*)(?{% for example in examples %}Term Name ' + curie + ' | \n' 299 | text += '\t\t||||
---|---|---|---|---|
Term IRI | \n' 304 | uri = row['pref_ns_uri'] + row['term_localName'] 305 | text += '\t\t\t' + uri + ' | \n' 306 | text += '\t\t|||
Modified | \n' 309 | text += '\t\t\t' + row['term_modified'] + ' | \n' 310 | text += '\t\t|||
Term version IRI | \n' 315 | text += '\t\t\t' + row['version_iri'] + ' | \n' 316 | text += '\t\t|||
Label | \n' 320 | text += '\t\t\t' + row['label'] + ' | \n' 321 | text += '\t\t|||
\n' 326 | text += '\t\t\t | This term is deprecated and should no longer be used. | \n' 327 | text += '\t\t|||
Definition | \n' 331 | text += '\t\t\t' + row['definition'] + ' | \n' 332 | text += '\t\t|||
Usage | \n' 337 | text += '\t\t\t' + convert_link(convert_code(row['usage'])) + ' | \n' 338 | text += '\t\t|||
Notes | \n' 343 | text += '\t\t\t' + convert_link(convert_code(row['notes'])) + ' | \n' 344 | text += '\t\t|||
Controlled value | \n' 349 | text += '\t\t\t' + row['controlled_value_string'] + ' | \n' 350 | text += '\t\t|||
Has broader concept | \n' 355 | curieAnchor = row['skos_broader'].replace(':','_') 356 | text += '\t\t\t' + row['skos_broader'] + ' | \n' 357 | text += '\t\t|||
Type | \n' 361 | if row['type'] == 'http://www.w3.org/1999/02/22-rdf-syntax-ns#Property': 362 | text += '\t\t\tProperty | \n' 363 | elif row['type'] == 'http://www.w3.org/2000/01/rdf-schema#Class': 364 | text += '\t\t\tClass | \n' 365 | elif row['type'] == 'http://www.w3.org/2004/02/skos/core#Concept': 366 | text += '\t\t\tConcept | \n' 367 | else: 368 | text += '\t\t\t' + row['type'] + ' | \n' # this should rarely happen 369 | text += '\t\t
Executive Committee decision | \n' 376 | text += '\t\t\thttp://rs.tdwg.org/decisions/' + drow['decision_localName'] + ' | \n' 377 | text += '\t\t
{{ class_group.label }} Class | |
---|---|
Identifier | {{ class_group.iri }} |
Definition | {{ class_group.definition }} |
Comments | {{ class_group.comments }} |
Examples | {{ class_group.examples }} |
42 | {% if term.namespace != "dwciri" %}{% endif %} 43 |
44 | {% set examples = term.examples.split("; ") %} 45 |{{ term.label }} Property | |
---|---|
Identifier | {{ term.iri }} |
Definition | {{ term.definition }} |
Comments | {{ term.comments }} |
Examples | {% if examples | length == 1 %}{{ examples | first }}{% else %}
|
Term Name ecotcr:tcr | 75 ||
---|---|
Term IRI | 80 |http://rs.tdwg.org/ecotcr/values/tcr | 81 |
Modified | 84 |2024-02-28 | 85 |
Term version IRI | 88 |http://rs.tdwg.org/ecotcr/values/version/tcr-2024-02-28 | 89 |
Label | 92 |taxon completeness reported concept scheme | 93 |
Definition | 96 |a SKOS concept scheme for categorizing taxon completeness reporting | 97 |
Type | 100 |http://www.w3.org/2004/02/skos/core#ConceptScheme | 101 |
Executive Committee decision | 104 |http://rs.tdwg.org/decisions/decision-2024-02-28_42 | 105 |
Term Name ecotcr:tcr00 | 113 ||
---|---|
Term IRI | 118 |http://rs.tdwg.org/ecotcr/values/tcr00 | 119 |
Modified | 122 |2024-02-28 | 123 |
Term version IRI | 126 |http://rs.tdwg.org/ecotcr/values/version/tcr00-2024-02-28 | 127 |
Label | 130 |not reported | 131 |
Definition | 134 |Taxonomic completeness was not assessed or reported for the dwc:Event. | 135 |
Controlled value | 138 |notReported | 139 |
Type | 142 |Concept | 143 |
Executive Committee decision | 146 |http://rs.tdwg.org/decisions/decision-2024-02-28_42 | 147 |
Term Name ecotcr:tcr01 | 155 ||
---|---|
Term IRI | 160 |http://rs.tdwg.org/ecotcr/values/tcr01 | 161 |
Modified | 164 |2024-02-28 | 165 |
Term version IRI | 168 |http://rs.tdwg.org/ecotcr/values/version/tcr01-2024-02-28 | 169 |
Label | 172 |reported complete | 173 |
Definition | 176 |Taxonomic completeness was assessed for the dwc:Event, and it was determined to be complete. | 177 |
Controlled value | 180 |reportedComplete | 181 |
Type | 184 |Concept | 185 |
Executive Committee decision | 188 |http://rs.tdwg.org/decisions/decision-2024-02-28_42 | 189 |
Term Name ecotcr:tcr02 | 197 ||
---|---|
Term IRI | 202 |http://rs.tdwg.org/ecotcr/values/tcr02 | 203 |
Modified | 206 |2024-02-28 | 207 |
Term version IRI | 210 |http://rs.tdwg.org/ecotcr/values/version/tcr02-2024-02-28 | 211 |
Label | 214 |reported incomplete | 215 |
Definition | 218 |Taxonomic completeness was assessed for the dwc:Event, and it was determined to be incomplete. | 219 |
Controlled value | 222 |reportedIncomplete | 223 |
Type | 226 |Concept | 227 |
Executive Committee decision | 230 |http://rs.tdwg.org/decisions/decision-2024-02-28_42 | 231 |