opentrust/wpml-config.xml at main · EtticDevelopment/opentrust · GitHub

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
77
78
79
80
81
82
83
84
<wpml-config>

    <!--
    Translation configuration for WPML and Polylang. Both plugins read this
    file from the plugin root at activation time and use it to:

      1. Register Open Trust Center's four custom post types as translatable content,
         so multilingual editors can create per-language variants of policies,
         certifications, subprocessors, and data practices.
      2. Tell the translation plugin which custom meta fields carry
         human-readable text that should be translated, versus slugs, dates,
         IDs, or booleans that should be copied verbatim across languages.

    The custom taxonomies list is empty because Open Trust Center does not register
    any taxonomies — policy category, certification status, and data-practice
    legal basis are enum slugs stored in post meta, not WordPress taxonomies.
    -->

    <custom-types>
        <custom-type translate="1">ettotc_policy</custom-type>
        <custom-type translate="1">ettotc_certification</custom-type>
        <custom-type translate="1">ettotc_subprocessor</custom-type>
        <custom-type translate="1">ettotc_data_practice</custom-type>
    </custom-types>

    <custom-fields>
        <!-- ── Certifications ──────────────────────────── -->
        <!-- Issuing body and description are human-readable and locale-specific. -->
        <custom-field action="translate">_ettic_otc_cert_issuing_body</custom-field>
        <custom-field action="translate">_ettic_otc_cert_description</custom-field>
        <!-- Type, status, dates, and the badge + proof-artifact attachment IDs
             are language-agnostic. -->
        <custom-field action="copy">_ettic_otc_cert_type</custom-field>
        <custom-field action="copy">_ettic_otc_cert_status</custom-field>
        <custom-field action="copy">_ettic_otc_cert_issue_date</custom-field>
        <custom-field action="copy">_ettic_otc_cert_expiry_date</custom-field>
        <custom-field action="copy">_ettic_otc_cert_badge_id</custom-field>
        <custom-field action="copy">_ettic_otc_cert_artifact_id</custom-field>

        <!-- ── Policies ────────────────────────────────── -->
        <custom-field action="copy">_ettic_otc_policy_category</custom-field>
        <custom-field action="copy">_ettic_otc_policy_effective_date</custom-field>
        <custom-field action="copy">_ettic_otc_policy_review_date</custom-field>
        <custom-field action="copy">_ettic_otc_policy_sort_order</custom-field>
        <!-- Policy ID is language-agnostic (POL-012 is the same reference in
             every locale). Framework citations are control IDs (SOC 2 CC6.1,
             ISO 27001 A.9.2) which are also identifiers, not prose. The PDF
             attachment is copied verbatim; translators can override the
             translation-post's attachment meta if they have a localized PDF. -->
        <custom-field action="copy">_ettic_otc_policy_ref_id</custom-field>
        <custom-field action="copy">_ettic_otc_policy_citations</custom-field>
        <custom-field action="copy">_ettic_otc_policy_attachment_id</custom-field>
        <!-- AI summary used by the chat engine's corpus index. Per-translation:
             each translated policy gets its own summary in its own language,
             generated by the configured chat model on save_post. The updated-
             at timestamp and origin flag are scalars copied verbatim — the
             save_post hook re-sets them when each translation is generated. -->
        <custom-field action="translate">_ettic_otc_policy_chat_summary</custom-field>
        <custom-field action="copy">_ettic_otc_policy_chat_summary_updated_at</custom-field>
        <custom-field action="copy">_ettic_otc_policy_chat_summary_origin</custom-field>

        <!-- ── Subprocessors ───────────────────────────── -->
        <!-- Purpose, data processed, and country are displayed text. -->
        <custom-field action="translate">_ettic_otc_sub_purpose</custom-field>
        <custom-field action="translate">_ettic_otc_sub_data_processed</custom-field>
        <custom-field action="translate">_ettic_otc_sub_country</custom-field>
        <!-- Website URL and DPA flag are language-agnostic. -->
        <custom-field action="copy">_ettic_otc_sub_website</custom-field>
        <custom-field action="copy">_ettic_otc_sub_dpa_signed</custom-field>

        <!-- ── Data Practices ──────────────────────────── -->
        <custom-field action="translate">_ettic_otc_dp_purpose</custom-field>
        <custom-field action="translate">_ettic_otc_dp_retention_period</custom-field>
        <custom-field action="translate">_ettic_otc_dp_data_items</custom-field>
        <custom-field action="translate">_ettic_otc_dp_shared_with</custom-field>
        <custom-field action="copy">_ettic_otc_dp_legal_basis</custom-field>
        <custom-field action="copy">_ettic_otc_dp_sort_order</custom-field>
        <!-- Legacy v1 fields retained for migration; ignored by translation. -->
        <custom-field action="ignore">_ettic_otc_dp_collection_method</custom-field>
        <custom-field action="ignore">_ettic_otc_dp_data_type</custom-field>
        <custom-field action="ignore">_ettic_otc_dp_is_sensitive</custom-field>
    </custom-fields>

</wpml-config>