New translations termlist-header.en.md (Chinese Simplified)

Author: TDWG-Crowdin

code/cd-template/termlist-header.zh-Hans.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