New Crowdin updates

code/build-preview.py

@@ -5,10 +5,12 @@
 
 languages = [
   {'text': 'Čeština', 'href': '/cs/'},
+  {'text': 'Deutsch', 'href': '/de/'},
   {'text': 'Español', 'href': '/es/'},
   {'text': 'Français', 'href': '/fr/'},
   {'text': '日本語', 'href': '/ja/'},
   {'text': '한국어', 'href': '/ko/'},
+  {'text': 'Português', 'href': '/pt/'},
   {'text': 'Русский', 'href': '/ru/'},
   {'text': '繁體中文', 'href': '/zh-Hant/'}
 ]

code/build-webpages.py

@@ -21,7 +21,7 @@
 # -----------------
 # Configuration section
 # -----------------
-languages = ['en', 'es', 'pt', 'de', 'fr', 'ko', 'nl', 'ru', 'zh-Hant']
+languages = ['en', 'cs', 'de', 'es', 'fr', 'ja', 'ko', 'nl', 'pt', 'ru', 'zh-Hant']
 
 # -----------------
 # Command line arguments
@@ -322,7 +322,7 @@ def generate_vocabulary_tables(self, locale):
                 if self.vocab_type == 1:
                     text += '\t\t<tr>\n'
                     text += '\t\t\t<td></td>\n'
-                    text += '\t\t\t<td><b>%s:</b> %s -- <b>%s:</b> %s</td>\n' % (self.t('required'), self.t_val(row, 'tdwgutility_required', l), self.t('repeatable'), self.t_val(row, 'tdwgutility_repeatable', l))
+                    text += '\t\t\t<td><b>%s:</b> %s – <b>%s:</b> %s</td>\n' % (self.t('required'), self.t_val(row, 'tdwgutility_required', l), self.t('repeatable'), self.t_val(row, 'tdwgutility_repeatable', l))
                     text += '\t\t</tr>\n'
 
                 if row['term_deprecated'] != '':

code/cd-template/termlist-header.ar.md

@@ -0,0 +1,69 @@
+# {document_title}
+
+Title
+: {document_title}
+
+Namespace IRI
+: <http://rs.tdwg.org/accd/values/>
+
+Preferred namespace abbreviation
+: accd:
+
+Date version issued
+: {ratification_date}
+
+Date created
+: {created_date}
+
+Part of TDWG Standard
+: <{standard_iri}>
+
+This version
+: <{current_iri}{ratification_date}>
+
+Latest version
+: <{current_iri}>
+
+{previous_version_slot}
+
+Abstract
+: {abstract}
+
+Contributors
+: {contributors}
+
+Creator
+: {creator}
+
+Bibliographic citation
+: {creator}. {year}. {document_title}. {publisher}. <{current_iri}{ratification_date}>
+
+## 1 Introduction (informative)
+
+This document includes terms intended to be used as controlled values for Audiovisual Core terms `Iptc4xmpExt:CVterm` and `ac:CVtermLiteral`.
+
+### 1.1 Status of the content of this document
+
+Section 1 is informative (non-normative).
+
+Section 2 is normative.
+
+Section 3 is informative (non-normative).
+
+In Section 4, the values of the `Term IRI`, `Definition`, and `Controlled value` are normative. The value of `Usage` (if it exists for a given term) is normative. The values of `Term Name` are non-normative, although one can expect that the namespace abbreviation prefix is one commonly used for the term namespace.  `Label` and the values of all other properties are non-normative.
+
+### 1.2 RFC 2119 key words
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [BCP 14](https://www.rfc-editor.org/info/bcp14) [\[RFC 2119\]](https://datatracker.ietf.org/doc/html/rfc2119) and [\[RFC 8174\]](https://datatracker.ietf.org/doc/html/rfc8174) when, and only when, they appear in all capitals, as shown here.
+
+## 2 Use of Terms
+
+### 2.1 Relationship of value types to property terms
+
+In accordance with [the Audiovisual Core Term List document](http://rs.tdwg.org/ac/doc/termlist/), unabbreviated term IRIs SHOULD be used as values of the property `Iptc4xmpExt:CVterm`. Controlled value strings SHOULD be used as values of the property `ac:CVtermLiteral`.
+
+### 2.2 Relationship between values of ac:CVtermLiteral and Iptc4xmpExt:CVterm
+
+An IRI for a term in this vocabulary denotes the same concept as the concept denoted by the controlled value string for the same term. Thus a client MAY infer an IRI value for `Iptc4xmpExt:CVterm` given a controlled value string for `ac:CVtermLiteral` even if that IRI is not explicitly stated. The practical implication is that data aggregators MAY materialize values for the preferred `Iptc4xmpExt:CVterm` property in cases where providers only provide values for `ac:CVtermLiteral`.
+
+## 3 Term index

code/cd-template/termlist-header.cs.md

@@ -0,0 +1,69 @@
+# {document_title}
+
+Title
+: {document_title}
+
+Namespace IRI
+: <http://rs.tdwg.org/accd/values/>
+
+Preferred namespace abbreviation
+: accd:
+
+Datum vydání verze
+: {ratification_date}
+
+Datum vytvoření
+: {created_date}
+
+Část standardu TDWG
+: <{standard_iri}>
+
+Tato verze
+: <{current_iri}{ratification_date}>
+
+Aktuální verze
+: <{current_iri}>
+
+{previous_version_slot}
+
+Abstract
+: {abstract}
+
+Přispěvatelé
+: {contributors}
+
+Tvůrce
+: {creator}
+
+Bibliografická citace
+: {creator}. {year}. {document_title}. {publisher}. <{current_iri}{ratification_date}>
+
+## 1 Úvod (informativní)
+
+This document includes terms intended to be used as controlled values for Audiovisual Core terms `Iptc4xmpExt:CVterm` and `ac:CVtermLiteral`.
+
+### 1.1 Status obsahu tohoto dokumentu
+
+Oddíl 1 je informativní (nenormativní).
+
+Oddíl 2 je normativní.
+
+Oddíl 3 je informativní (nenormativní).
+
+V oddíle 4 jsou hodnoty `Term IRI`, `Definice` a `Kontrolovaná hodnota` normativní. Hodnota `Použití` (pokud pro daný termín existuje) je normativní. Hodnoty `Název termínu` nejsou normativní, ačkoli lze očekávat, že prefix zkratky jmenného prostoru je prefix běžně používaný pro jmenný prostor termínu.  `Štítek` a hodnoty všech ostatních vlastností nejsou normativní.
+
+### 1.2 Klíčová slova RFC 2119
+
+Klíčová slova "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" a "OPTIONAL" v tomto dokumentu je třeba interpretovat tak, jak je popsáno v [BCP 14](https://www.rfc-editor.org/info/bcp14) [\[RFC 2119\]](https://datatracker.ietf.org/doc/html/rfc2119) a [\[RFC 8174\]](https://datatracker.ietf.org/doc/html/rfc8174), pokud a pouze pokud jsou uvedena velkými písmeny, jak je uvedeno zde.
+
+## 2 Použití termínů
+
+### 2.1 Vztah hodnotových typů k pojmům vlastnictví
+
+In accordance with [the Audiovisual Core Term List document](http://rs.tdwg.org/ac/doc/termlist/), unabbreviated term IRIs SHOULD be used as values of the property `Iptc4xmpExt:CVterm`. Controlled value strings SHOULD be used as values of the property `ac:CVtermLiteral`.
+
+### 2.2 Relationship between values of ac:CVtermLiteral and Iptc4xmpExt:CVterm
+
+IRI pro termín v tomto slovníku označuje stejný pojem jako pojem označený řízeným řetězcem hodnot pro stejný termín. Thus a client MAY infer an IRI value for `Iptc4xmpExt:CVterm` given a controlled value string for `ac:CVtermLiteral` even if that IRI is not explicitly stated. The practical implication is that data aggregators MAY materialize values for the preferred `Iptc4xmpExt:CVterm` property in cases where providers only provide values for `ac:CVtermLiteral`.
+
+## 3 Index termínů

code/cd-template/termlist-header.de.md

@@ -0,0 +1,69 @@
+# {document_title}
+
+Title
+: {document_title}
+
+Namespace IRI
+: <http://rs.tdwg.org/accd/values/>
+
+Preferred namespace abbreviation
+: accd:
+
+Date version issued
+: {ratification_date}
+
+Date created
+: {created_date}
+
+Part of TDWG Standard
+: <{standard_iri}>
+
+This version
+: <{current_iri}{ratification_date}>
+
+Latest version
+: <{current_iri}>
+
+{previous_version_slot}
+
+Abstract
+: {abstract}
+
+Contributors
+: {contributors}
+
+Creator
+: {creator}
+
+Bibliographic citation
+: {creator}. {year}. {document_title}. {publisher}. <{current_iri}{ratification_date}>
+
+## 1 Introduction (informative)
+
+This document includes terms intended to be used as controlled values for Audiovisual Core terms `Iptc4xmpExt:CVterm` and `ac:CVtermLiteral`.
+
+### 1.1 Status of the content of this document
+
+Section 1 is informative (non-normative).
+
+Section 2 is normative.
+
+Section 3 is informative (non-normative).
+
+In Section 4, the values of the `Term IRI`, `Definition`, and `Controlled value` are normative. The value of `Usage` (if it exists for a given term) is normative. The values of `Term Name` are non-normative, although one can expect that the namespace abbreviation prefix is one commonly used for the term namespace.  `Label` and the values of all other properties are non-normative.
+
+### 1.2 RFC 2119 key words
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [BCP 14](https://www.rfc-editor.org/info/bcp14) [\[RFC 2119\]](https://datatracker.ietf.org/doc/html/rfc2119) and [\[RFC 8174\]](https://datatracker.ietf.org/doc/html/rfc8174) when, and only when, they appear in all capitals, as shown here.
+
+## 2 Use of Terms
+
+### 2.1 Relationship of value types to property terms
+
+In accordance with [the Audiovisual Core Term List document](http://rs.tdwg.org/ac/doc/termlist/), unabbreviated term IRIs SHOULD be used as values of the property `Iptc4xmpExt:CVterm`. Controlled value strings SHOULD be used as values of the property `ac:CVtermLiteral`.
+
+### 2.2 Relationship between values of ac:CVtermLiteral and Iptc4xmpExt:CVterm
+
+An IRI for a term in this vocabulary denotes the same concept as the concept denoted by the controlled value string for the same term. Thus a client MAY infer an IRI value for `Iptc4xmpExt:CVterm` given a controlled value string for `ac:CVtermLiteral` even if that IRI is not explicitly stated. The practical implication is that data aggregators MAY materialize values for the preferred `Iptc4xmpExt:CVterm` property in cases where providers only provide values for `ac:CVtermLiteral`.
+
+## 3 Term index

code/cd-template/termlist-header.es.md

@@ -0,0 +1,69 @@
+# {document_title}
+
+Título
+: {document_title}
+
+Espacio de nombres IRI
+: <http://rs.tdwg.org/accd/values/>
+
+Abreviatura preferida del namespce
+: accd:
+
+Fecha de publicación de la versión
+: {ratification_date}
+
+Fecha de creación
+: {created_date}
+
+Parte del Estándar TDWG
+: <{standard_iri}>
+
+Esta versión
+: <{current_iri}{ratification_date}>
+
+Última versión
+: <{current_iri}>
+
+{previous_version_slot}
+
+Resumen
+: {abstract}
+
+Colaboradores
+: {contributors}
+
+Creador
+: {creator}
+
+Cita bibliográfica
+: {creator}. {year}. {document_title}. {publisher}. <{current_iri}{ratification_date}>
+
+## 1. Introducción (Informativa)
+
+Este documento incluye términos destinados a ser utilizados como valores controlados para los términos principales de Audiovisual Core `Iptc4xmpExt:CVterm` y `ac:CVtermLiteral`.
+
+### 1.1 Estado del contenido de este documento
+
+La Sección 1 es informativa (no normativa).
+
+La sección 2 es normativa.
+
+La Sección 3 es informativa (no normativa).
+
+En la Sección 4, los valores de `Término IRI`, `Definición` y `Valor controlado` son normativos. El valor de `Uso` (si existe para un término determinado) también es normativo. Los valores del `Nombre del término` no son normativos, aunque se puede esperar que el prefijo del namespace abreviado sea uno comúnmente utilizado para ese namespace.  La `Etiqueta` y los valores de todas las demás propiedades no son normativos.
+
+### 1.2 Palabras clave RFC 2119
+
+Las palabras clave "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" y "OPTIONAL" en este documento deben interpretarse como se describe en [BCP 14](https://www.rfc-editor.org/info/bcp14) [\[RFC 2119\]](https://datatracker.ietf.org/doc/html/rfc2119) y [\[RFC 8174\]](https://datatracker.ietf.org/doc/html/rfc8174), únicamente cuando aparezcan en mayúsculas, tal como se muestra aquí.
+
+## 2 Uso de los Términos
+
+### 2.1 Relación de los tipos de valor con los términos de propiedad
+
+De acuerdo con el [documento de la Lista de Términos Básicos Audiovisuales](http://rs.tdwg.org/ac/doc/termlist/), los términos IRI no abreviados DEBEN usarse como valores de la propiedad `Iptc4xmpExt:CVterm`. Las cadenas de valores controlados DEBEN usarse como valores de la propiedad `ac:CVtermLiteral`.
+
+### 2.2 Relación entre los valores de ac:CVtermLiteral y Iptc4xmpExt:CVterm
+
+Una IRI para un término en este vocabulario denota la misma clase que la clase denotada por la cadena de valor controlado para el mismo término. Por lo tanto, un cliente PUEDE inferir un valor IRI para `Iptc4xmpExt:CVterm` dada una cadena de valor controlado para `ac:CVtermLiteral` incluso si ese IRI no se indica explícitamente. La implicación práctica es que los agregadores de datos PUEDEN materializar valores para la propiedad preferida `Iptc4xmpExt:CVterm` en los casos en que los proveedores solo proporcionan valores para `ac:CVtermLiteral`.
+
+## 3 Índice de Términos

code/cd-template/termlist-header.fr.md

@@ -0,0 +1,70 @@
+# {document_title}
+
+Title
+: {document_title}
+
+Namespace IRI
+: <http://rs.tdwg.org/accd/values/>
+
+Preferred namespace abbreviation
+: accd:
+
+Date de publication de la dernière mise à jour
+: {ratification_date}
+
+Date de création
+: {created_date}
+
+Fait partie du standard TDWG
+: <{standard_iri}>
+
+Cette version
+: <{current_iri}{ratification_date}>
+
+Dernière version
+: <{current_iri}>
+
+Version précédente
+: {previous_version_slot}
+
+Abstract
+: {abstract}
+
+Contributeurs
+: {contributors}
+
+Créateur :
+{creator}
+
+Citation :
+{creator}. {year}. {document_title}. {publisher}. <{current_iri}{ratification_date}>
+
+## 1 Introduction (informative)
+
+This document includes terms intended to be used as controlled values for Audiovisual Core terms `Iptc4xmpExt:CVterm` and `ac:CVtermLiteral`.
+
+### 1.1 Statut du contenu de ce document
+
+Section 1 is informative (non-normative).
+
+La section 2 est normative.
+
+Section 3 is informative (non-normative).
+
+Dans la section 4, les valeurs de l'`IRI du terme`, de la `Définition` et de la `Valeur contrôlée` sont normatives. La valeur de `Utilisation` (si elle existe pour un terme donné) est normative. Les valeurs de `Nom du Terme` ne sont pas normatives, bien que l'on puisse s'attendre à ce que le préfixe de l'abréviation de l'espace de noms soit celui couramment utilisé pour l'espace de noms du terme.  `Label` and the values of all other properties are non-normative.
+
+### 1.2 Mots clés RFC 2119
+
+Les mots clés "MUST/DOIT", "MUST NOT/NE DOIT PAS", "REQUIRED/OBLIGATOIRE", "SHALL/DEVRA", "SHALL NOT/NE DEVRA PAS", "SHOULD/DEVRAIT", "SHOULD NOT/NE DEVRAIT PAS", "RECOMMENDED/RECOMMANDÉ", "MAY/POURRAIT", et "OPTIONAL/OPTIONNEL" dans ce document doivent être interprétés comme défini dans les références [BCP 14](https://www.rfc-editor.org/info/bcp14) [\[RFC 2119\]](https://datatracker.ietf.org/doc/html/rfc2119) et [\[RFC 8174\]](https://datatracker.ietf.org/doc/html/rfc8174)] uniquement lorsqu’ils apparaissent en majuscules, comme ci-dessus.
+
+## 2 Utilisation des termes
+
+### 2.1 Relationship of value types to property terms
+
+In accordance with [the Audiovisual Core Term List document](http://rs.tdwg.org/ac/doc/termlist/), unabbreviated term IRIs SHOULD be used as values of the property `Iptc4xmpExt:CVterm`. Controlled value strings SHOULD be used as values of the property `ac:CVtermLiteral`.
+
+### 2.2 Relationship between values of ac:CVtermLiteral and Iptc4xmpExt:CVterm
+
+An IRI for a term in this vocabulary denotes the same concept as the concept denoted by the controlled value string for the same term. Thus a client MAY infer an IRI value for `Iptc4xmpExt:CVterm` given a controlled value string for `ac:CVtermLiteral` even if that IRI is not explicitly stated. The practical implication is that data aggregators MAY materialize values for the preferred `Iptc4xmpExt:CVterm` property in cases where providers only provide values for `ac:CVtermLiteral`.
+
+## 3 Index des termes