@tiangong-lca/tidas-sdk 0.3.1 → 0.4.1

package/dist/data/bundled-methodologies.json

@@ -671,9 +671,37 @@
         },
         "processes": {
             "metadata": {
-                "version": "1.0.0",
-                "last_updated": "2024-01-15",
-                "applies_to": "ILCD/Tidas Process Dataset v1.1"
+                "version": "1.1.0",
+                "last_updated": "2026-09-22",
+                "applies_to": "ILCD/Tidas Process Dataset v1.1",
+                "ef_baseline": "EF Data Guide 2.0 (2020), EF 3.1 addendum (November 2022), and EF eILCD modelling 2.1 (June 2020); source-bound additions, not universal TIDAS gates.",
+                "ef_sources": {
+                    "ef-data-guide-2.0": {
+                        "title": "Guide for EF compliant data sets, Version 2.0",
+                        "authors": "Simone Fazio, Luca Zampori, An De Schryver, Oliver Kusche, Lionel Thellier, Edward Diaconu",
+                        "publisher": "European Commission, Joint Research Centre; Publications Office of the European Union",
+                        "year": 2020,
+                        "identifier": "JRC120340; EUR 30175 EN; doi:10.2760/537292",
+                        "url": "https://eplca.jrc.ec.europa.eu/permalink/Guide_EF_DATA.pdf",
+                        "license": "CC BY 4.0; https://creativecommons.org/licenses/by/4.0/",
+                        "attribution": "Adapted and condensed into field-oriented guidance by TIDAS; wording, organization and examples are changed. No endorsement by the original authors is implied."
+                    },
+                    "ef-3.1-addendum-2022": {
+                        "title": "Updates on Guide for EF compliant data sets (Version 2.0) to reflect the changes in the Environmental Footprint 3.1 reference package",
+                        "authors": "Antonio Valente, Oliver Kusche, Fulvio Ardente",
+                        "date": "2022-11",
+                        "url": "https://eplca.jrc.ec.europa.eu/permalink/EF_Data_Guide_EF3.1_addendum.pdf",
+                        "use": "Source of factual compliance-system updates; source text and tables are not reproduced."
+                    },
+                    "ef-eilcd-modelling-2.1": {
+                        "title": "Modelling requirements on LCI models under the Environmental footprint for interoperable data exchange via the eILCD format",
+                        "authors": "Luca Zampori, Marc Andree Wolf, Katarzyna Cenian, Rutger Schurgers, Ingo Meinshausen, Sebastian Schulz, Lucia Valsasina, Gregor Wernet, Oliver Kusche, Lionel Thellier",
+                        "version": "2.1",
+                        "date": "2020-06",
+                        "url": "https://eplca.jrc.ec.europa.eu/permalink/InterfacePaper_Modelling_eILCD.pdf",
+                        "use": "Source of factual modelling constraints; source text and figures are not reproduced."
+                    }
+                }
             },
             "global_rules": {
                 "multi_language_support": {
@@ -689,6 +717,157 @@
                             "purpose": "确保本地用户可理解性"
                         }
                     ]
+                },
+                "ef_scope": {
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.scope",
+                            "normative_level": "informative",
+                            "applicability": "Readers and consumers applying the EF-specific methodology entries.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-data-guide-2.0",
+                                    "section": "Introduction; 5.1; 6"
+                                },
+                                {
+                                    "source": "ef-3.1-addendum-2022",
+                                    "section": "Introduction"
+                                },
+                                {
+                                    "source": "ef-eilcd-modelling-2.1",
+                                    "section": "1"
+                                }
+                            ],
+                            "requirement": "Apply this source-bound EF guidance only when assessing the stated EF compliance scope; retain ordinary TIDAS requirements outside that scope.",
+                            "content_requirements": [
+                                "This baseline is the 2020 Data Guide plus its November 2022 EF 3.1 addendum and the June 2020 eILCD modelling paper. It is not a claim that these documents exhaust every current PEF/OEF or sector requirement.",
+                                "ILCD entry-level requirements, the applicable PEF/OEF method and PEFCR/OEFSR remain additional source dependencies. Record their versions and resolve a conflict against the applicable authoritative source before claiming compliance.",
+                                "The 2022 addendum replaces Guide sections 2 and 5.2.15 and updates supporting-dataset declarations. Its reference to section 5.4.1 describes supporting datasets, covered under section 5.4.2 in the Guide.",
+                                "The elementary-flow duplication permission in the Guide does not override the stricter eILCD exchange requirement when that model-exchange scope applies.",
+                                "These are content requirements, not execution phases, severity, write permission, automatic repair instructions, or a compliance certificate."
+                            ]
+                        }
+                    ]
+                },
+                "ef_reference_package": {
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.reference-package",
+                            "normative_level": "shall",
+                            "applicability": "EF datasets and their supporting package, including level-1 subprocesses.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-3.1-addendum-2022",
+                                    "section": "2; 5.2.15"
+                                },
+                                {
+                                    "source": "ef-data-guide-2.0",
+                                    "section": "4; 5.4.2"
+                                }
+                            ],
+                            "requirement": "Use the EF reference package applicable to the declared method/category-rule generation, and keep the central dataset and all its subprocesses compatible with that package.",
+                            "content_requirements": [
+                                "The addendum identifies EF 3.1 for new transition-phase PEFCRs and their studies; older category rules can require their corresponding older package. Record the exact package instead of silently mixing releases.",
+                                "Deliver the referenced flows, flow properties, unit groups, sources, contacts and LCIA methods needed by the ILCD/eILCD package, including compliance-system sources.",
+                                "Use the official reference nomenclature and characterization methods. A conversion does not authorize changing the EF characterization factors."
+                            ]
+                        }
+                    ]
+                },
+                "ef_eilcd_connections": {
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.eilcd-connections",
+                            "normative_level": "shall",
+                            "applicability": "EF eILCD lifecycle models and their linked processes.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-eilcd-modelling-2.1",
+                                    "section": "2.3; Figure 1; footnote 7"
+                                }
+                            ],
+                            "requirement": "Represent eILCD connections using the permitted Figure 1 option C; do not use one exchange for multiple connections.",
+                            "content_requirements": [
+                                "A connection between two newly created EF datasets uses the same product flow at both ends.",
+                                "For existing-to-new connections reuse the existing product flow in the new dataset; different-UUID connections are limited to unavoidable existing-dataset cases. Intermediate/conversion processes are an available remedy.",
+                                "Keep the reference exchange of the reference process unlinked as specified in footnote 7 to avoid double linking.",
+                                "Do not create country-specific flows without checking the supply identities and connections. The lifecycle-model file owns these connections; this Process methodology records the cross-file requirement."
+                            ]
+                        }
+                    ]
+                },
+                "ef_eilcd_model": {
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.eilcd-model",
+                            "normative_level": "shall",
+                            "applicability": "EF models exchanged in eILCD format.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-eilcd-modelling-2.1",
+                                    "section": "2.2-2.4"
+                                }
+                            ],
+                            "requirement": "Identify the reference process explicitly and scale the model to its reference-flow quantity and unit.",
+                            "content_requirements": [
+                                "Do not reuse a newly created dataset multiple times with different parameter values in an eILCD PEF model; create an appropriate new dataset. The paper expressly exempts level-1 disaggregated datasets from this provision.",
+                                "Life-cycle-stage declarations are optional; if present, use the cited default stages or the applicable PEFCR/OEFSR convention, documenting any justified subdivisions/additions.",
+                                "Avoid unnecessarily complex multi-scenario parameter models as recommended by the paper. Model declarations and scenario selection are lifecycle-model concerns, not new Process JSON fields."
+                            ]
+                        }
+                    ]
+                },
+                "ef_eilcd_documentation": {
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.eilcd-documentation",
+                            "normative_level": "shall",
+                            "applicability": "EF models exchanged in eILCD format.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-eilcd-modelling-2.1",
+                                    "section": "2.5"
+                                }
+                            ],
+                            "requirement": "Place whole-model metadata on the reference process and reference the aggregated result process.",
+                            "content_requirements": [
+                                "Copy the aggregated-version metadata to the corresponding reference-process fields; include that aggregated dataset in the processes directory.",
+                                "For complex representative-product models describe at least the represented product/process in the reference-process metadata and explain detailed assumptions in the study report.",
+                                "Report all EF impact-category results on the reference process and ensure they match the aggregated result dataset.",
+                                "referenceToReferenceProcess and referenceToResultingProcess belong to the lifecycle-model representation; their absence from the Process schema is not permission to drop the requirement."
+                            ]
+                        }
+                    ]
+                },
+                "ef_provider_obligations": {
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.provider-context",
+                            "normative_level": "informative",
+                            "applicability": "EF data providers and node/data-stock operators under the stated source baseline.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-data-guide-2.0",
+                                    "section": "3.2-3.6; 7; 8.3"
+                                }
+                            ],
+                            "requirement": "Preserve the source requirements for data-stock documentation, update communication and review availability as provider obligations.",
+                            "content_requirements": [
+                                "Maintain the applicable overall/core change logs and predecessor availability, with dates and affected identities on the provider landing page.",
+                                "Section 3.4 describes user notification, temporary removal from download, restricted corrected upload and EF-helpdesk coordination; these are transition-phase provider procedures, not actions a content validator may execute.",
+                                "Section 7 requires stock names prefixed with the EF reference-package version and a consistent flow list within each stock, even when EF and ILCD compliance levels coexist.",
+                                "Explain stock structure on the landing page, link the EULA, provide a contact address and obtain the required EULA agreement. Create a source dataset with description and hyperlink for each new node and stock; provider responsibility for quality/review remains.",
+                                "Confirm current node, registry and communication procedures before operational use.",
+                                "Make the EF review report available with the dataset and visible in the registry as required by section 8.3. This methodology grants no authority to publish, notify users or change access."
+                            ]
+                        }
+                    ]
                 }
             },
             "processDataSet": {
@@ -904,6 +1083,76 @@
                                     "examples": [
                                         "该数据集代表现代超临界电厂的燃煤发电。系统边界包括煤炭处理、\n燃烧和烟气处理。净效率假定为45%。数据质量高，基于2023年\n实测电厂数据。\n"
                                     ]
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.supporting-identification",
+                                    "normative_level": "shall",
+                                    "applicability": "Non-primary supporting sub-datasets used only within their corresponding EF level-1 model.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.4.2"
+                                        }
+                                    ],
+                                    "requirement": "Identify the central process by exact name and UUID and direct users there for full model documentation.",
+                                    "content_requirements": [
+                                        "Use the prescribed supporting-subprocess general-comment wording in section 5.4.2 item 4 with the central process name and UUID substituted.",
+                                        "Supporting processes must not be used independently or with another central dataset; they do not require a separate DQR or review.",
+                                        "Where no clear classification exists, the Guide recommends Services / Other services."
+                                    ]
+                                }
+                            ]
+                        },
+                        "<rules>": [
+                            {
+                                "language": "all",
+                                "id": "ef.identity",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "5.2"
+                                    }
+                                ],
+                                "requirement": "Provide a UUID and the structured ILCD process name with its applicable technical, treatment, mix/location-type and quantitative qualifiers."
+                            }
+                        ],
+                        "referenceToExternalDocumentation": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.study-report",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets. Applies when a PEF study exists.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.1"
+                                        }
+                                    ],
+                                    "requirement": "Reference the PEF study report when a PEF study has been performed."
+                                }
+                            ]
+                        },
+                        "complementingProcesses": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.level1-complementing-processes",
+                                    "normative_level": "shall",
+                                    "applicability": "EF level-1 central datasets; the prohibition on complementingProcesses applies to aggregated datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.4.1; footnote 27"
+                                        }
+                                    ],
+                                    "requirement": "Reference all and only the central dataset subprocesses, with their UUIDs and exact names.",
+                                    "content_requirements": [
+                                        "Leave complementingProcesses unfilled for aggregated datasets; it is not a general list of related datasets."
+                                    ]
                                 }
                             ]
                         }
@@ -959,6 +1208,26 @@
                                     ]
                                 }
                             ]
+                        },
+                        "common:referenceYear": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.reference-year",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.4"
+                                        }
+                                    ],
+                                    "requirement": "State the validity start year, or the environmentally representative year for mixed-year data, with the validity period and justification.",
+                                    "content_requirements": [
+                                        "Do not advance the reference year merely because the EF reference package changed or an update left the LCI content unchanged."
+                                    ]
+                                }
+                            ]
                         }
                     },
                     "geography": {
@@ -1018,6 +1287,26 @@
                                         ]
                                     }
                                 ]
+                            },
+                            "@location": {
+                                "<rules>": [
+                                    {
+                                        "language": "all",
+                                        "id": "ef.geography",
+                                        "normative_level": "shall",
+                                        "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                        "source_refs": [
+                                            {
+                                                "source": "ef-data-guide-2.0",
+                                                "section": "5.2.3"
+                                            }
+                                        ],
+                                        "requirement": "Use the Guide designation EU+EFTA+UK for its complete-European coverage and the two-letter ISO country code for individual countries.",
+                                        "content_requirements": [
+                                            "The Guide also identifies PT-MA, ES-CA, BQ-SE and BQ-SB. Verify representability in the target location vocabulary; do not silently substitute a different geography."
+                                        ]
+                                    }
+                                ]
                             }
                         }
                     },
@@ -1059,6 +1348,143 @@
                                     ]
                                 }
                             ]
+                        },
+                        "referenceToTechnologyFlowDiagrammOrPicture": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.system-diagram",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2; 5.4.1"
+                                        }
+                                    ],
+                                    "requirement": "Reference a source containing the system-boundary diagram and relevant subprocesses.",
+                                    "content_requirements": [
+                                        "For a level-1 central dataset, add a complete model graph showing all subprocesses, physical connections, directions and included/excluded boundaries; retain the activity diagram as well."
+                                    ]
+                                }
+                            ]
+                        },
+                        "referenceToIncludedProcesses": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.aggregated-included-processes",
+                                    "normative_level": "may",
+                                    "applicability": "Aggregated EF LCI-result datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.3"
+                                        }
+                                    ],
+                                    "requirement": "An aggregated dataset may reference included subprocesses when these also exist as separate datasets."
+                                }
+                            ]
+                        },
+                        "<rules>": [
+                            {
+                                "language": "all",
+                                "id": "ef.level1-structure",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant level-1 partly disaggregated central datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "4"
+                                    }
+                                ],
+                                "requirement": "Preserve the minimum level-1 decomposition and one defined reference exchange.",
+                                "content_requirements": [
+                                    "Separate energy subprocesses per energy dataset, including fuel conversion and direct emissions where relevant.",
+                                    "Separate incoming transport per transported material/component and transport dataset; represent transported mass and distance as separate central-process parameters.",
+                                    "Represent avoided-product systems on the output side, retain the original datasets and use the described sign-inverting modelling process where system expansion requires it.",
+                                    "Separate main material inputs so virgin/recycled input and CFF R1 can be adapted; aggregate the remaining background processes into an input subprocess.",
+                                    "Provide a subprocess for foreground direct emissions and resource inputs; allow distinct co-products while selecting one reference exchange."
+                                ]
+                            }
+                        ]
+                    },
+                    "quantitativeReference": {
+                        "<rules>": [
+                            {
+                                "language": "all",
+                                "id": "ef.reference-flow",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "4; 5.2; 6"
+                                    }
+                                ],
+                                "requirement": "Identify exactly one reference exchange for the EF process; it may be an input or an output and must exist in the exchange list.",
+                                "content_requirements": [
+                                    "Use referenceToReferenceFlow to identify the exchange by its internal ID, not by the referenced flow UUID.",
+                                    "Document the functional unit when applicable. Multiple distinct co-products do not establish multiple EF reference exchanges."
+                                ],
+                                "examples": {
+                                    "positive": [
+                                        "One reference input in a treatment dataset; several co-products with one reference output."
+                                    ],
+                                    "negative": [
+                                        "Two reference exchange IDs or a reference ID absent from the exchange list."
+                                    ]
+                                }
+                            }
+                        ]
+                    },
+                    "mathematicalRelations": {
+                        "variableParameter": {
+                            "comment": {
+                                "<rules>": [
+                                    {
+                                        "language": "all",
+                                        "id": "ef.parameter-defaults",
+                                        "normative_level": "shall",
+                                        "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to parameterized datasets.",
+                                        "source_refs": [
+                                            {
+                                                "source": "ef-data-guide-2.0",
+                                                "section": "5.2.5"
+                                            }
+                                        ],
+                                        "requirement": "Document every parameter default in its comment, units and defaults information."
+                                    }
+                                ]
+                            },
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.eilcd-parameters",
+                                    "normative_level": "shall",
+                                    "applicability": "Processes participating in EF models exchanged in eILCD format.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-eilcd-modelling-2.1",
+                                            "section": "2.1"
+                                        }
+                                    ],
+                                    "requirement": "Use process-local parameters with the eILCD name and formula restrictions.",
+                                    "content_requirements": [
+                                        "A parameter name starts with a letter, is at most 15 characters, and otherwise uses only letters, digits, underscores or hyphens.",
+                                        "A formula is at most 255 characters. Permitted operators are +, -, *, /, ^, >, <, >=, <= and =; permitted functions are IF, POW and AND/OR/NOT with parentheses.",
+                                        "References may target other variables/formulas in this process but must not form cycles or cause division by zero. References to parameters outside this process are prohibited; lifecycle-model parameter settings are a separate model capability."
+                                    ],
+                                    "examples": {
+                                        "positive": [
+                                            "yield_1 refers to an acyclic formula in the same process."
+                                        ],
+                                        "negative": [
+                                            "A process formula reads a global parameter or participates in a circular dependency."
+                                        ]
+                                    }
+                                }
+                            ]
                         }
                     }
                 },
@@ -1075,6 +1501,23 @@
                                         "Partly terminated system"
                                     ],
                                     "description": "Defines the type and aggregation level of the process"
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.dataset-type",
+                                    "normative_level": "shall",
+                                    "applicability": "EF aggregated, partly disaggregated, supporting and avoided-product-system datasets, according to their role.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "1; 5.2.2; 5.4.1; 5.4.2"
+                                        }
+                                    ],
+                                    "requirement": "Use LCI result for an aggregated EF dataset and Partly terminated system for a partly disaggregated central dataset.",
+                                    "content_requirements": [
+                                        "Use Unit process, single operation for a non-primary supporting sub-dataset. Identify an avoided-product system as required for that modelling role.",
+                                        "Preserve the source distinction if a required value cannot be represented by the current target schema; report the representation gap rather than relabel it."
+                                    ]
                                 }
                             ]
                         },
@@ -1105,6 +1548,141 @@
                                         "capacity_factor: 0.85",
                                         "lifetime_years: 30"
                                     ]
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.modelling-constants",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.11"
+                                        }
+                                    ],
+                                    "requirement": "Explain at least the treatment of biogenic carbon, emission offsets and capital goods.",
+                                    "content_requirements": [
+                                        "This documentation duty does not permit offsets: the EF modelling requirement prohibits their inclusion."
+                                    ]
+                                }
+                            ]
+                        },
+                        "<rules>": [
+                            {
+                                "language": "all",
+                                "id": "ef.method-and-allocation",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "5.2; 5.2.8; 6"
+                                    }
+                                ],
+                                "requirement": "Document LCI method principles and approaches, their deviations, and foreground and background allocation separately.",
+                                "content_requirements": [
+                                    "Resolve multifunctionality through subdivision or system expansion first, then an underlying physical relationship, then another justified relationship.",
+                                    "Apply the agricultural-specific rules where relevant; do not infer a method solely from a dataset type or label."
+                                ]
+                            },
+                            {
+                                "language": "all",
+                                "id": "ef.electricity",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "6"
+                                    }
+                                ],
+                                "requirement": "Use the country consumption electricity mix, or construct a representative EU/regional consumption mix where the country mix is unavailable.",
+                                "content_requirements": [
+                                    "Sector-specific green-electricity information requires the applicable PEF/OEF contractual-instrument criteria, documented and confirmed by the reviewer; model remaining electricity with the residual mix."
+                                ]
+                            },
+                            {
+                                "language": "all",
+                                "id": "ef.offsets-and-time",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "6; 6.3"
+                                    }
+                                ],
+                                "requirement": "Exclude emission offsets and model emissions/removals at the start of the assessment period without time discounting."
+                            },
+                            {
+                                "language": "all",
+                                "id": "ef.carbon-modelling",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "6.3"
+                                    }
+                                ],
+                                "requirement": "Distinguish fossil, biogenic and land-use/change carbon with the appropriate elementary flows from the applicable EF reference package.",
+                                "content_requirements": [
+                                    "Under the Guide fossil-carbonation simplification, omit the corresponding uptake/emission pair from the PEF profile; additional information may use the specified fossil uptake flow.",
+                                    "Where biogenic exchanges are modelled, use biogenic flows, mass allocation and the factory-gate reference-flow carbon property.",
+                                    "For native forests include the connected emissions, products/residues and soil emissions under land-use/change and exclude their CO2 uptake.",
+                                    "Inventory uptake and emission separately; follow the cited PAS 2050/2050-1 provisions for land-use change.",
+                                    "Treat aboveground non-native residues as biogenic; exclude soil-carbon accumulation through improved management from the model, although it may be reported as metadata."
+                                ]
+                            },
+                            {
+                                "language": "all",
+                                "id": "ef.agriculture-allocation",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to agricultural multifunctionality.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "6.2"
+                                    }
+                                ],
+                                "requirement": "Apply the cited LEAP agricultural multifunctionality guidance; document, justify and review deviations."
+                            }
+                        ],
+                        "deviationsFromLCIMethodApproaches": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.cff",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.10; 6"
+                                        }
+                                    ],
+                                    "requirement": "Apply the CFF at least to the product materials, their waste treatments and the product packaging, using the applicable PEF/OEF method.",
+                                    "content_requirements": [
+                                        "Document where it applies, the substitution point, assumptions and nonzero parameter values in the method-approach explanation.",
+                                        "Omitted CFF parameters may mean zero only with the Guide-required general declaration on the provider landing page. Absence alone is not evidence of zero."
+                                    ]
+                                }
+                            ]
+                        },
+                        "referenceToLCAMethodDetails": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.method-report",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.12"
+                                        }
+                                    ],
+                                    "requirement": "Reference the source dataset for the applicable current PEF method and, where relevant, the applicable PEFCR."
                                 }
                             ]
                         }
@@ -1121,6 +1699,131 @@
                                         "2023-01 to 2023-12",
                                         "2022-06 to 2023-05"
                                     ]
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.agriculture-averaging",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to agricultural cultivation.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "6.2"
+                                        }
+                                    ],
+                                    "requirement": "Use cultivation periods that represent seasonal variation and crop development.",
+                                    "content_requirements": [
+                                        "Annual crops: at least three years; a justified unavailable-data/new-system exception may use a shorter period, never below one year.",
+                                        "Perennials: three years at a representative steady state; justify corrections for disproportionate development stages.",
+                                        "Crops harvested within a year: at least three recent consecutive production cycles. Account for the Guide greenhouse and long-harvest-cycle distinctions."
+                                    ]
+                                }
+                            ]
+                        },
+                        "dataCutOffAndCompletenessPrinciples": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.boundary-and-cutoff",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2; 6"
+                                        }
+                                    ],
+                                    "requirement": "Include supply-chain processes, capital goods/infrastructure and their end of life unless justified under the Guide cut-off rule.",
+                                    "content_requirements": [
+                                        "The Guide permits up to 3.0% exclusion assessed against material, energy and environmental significance; this is not an unconditional mass-only allowance.",
+                                        "Document exclusions and deviations and obtain reviewer confirmation of their environmental significance.",
+                                        "Model included waste and other included activities through to elementary flows."
+                                    ]
+                                }
+                            ]
+                        },
+                        "referenceToDataSource": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.background-source-references",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.13"
+                                        }
+                                    ],
+                                    "requirement": "Reference each EF-compliant data stock and each gap-filling source through the corresponding source dataset."
+                                }
+                            ]
+                        },
+                        "dataSelectionAndCombinationPrinciples": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.background-selection",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "6.1"
+                                        }
+                                    ],
+                                    "requirement": "Use an available EF-compliant background dataset before an ILCD entry-level compliant alternative.",
+                                    "content_requirements": [
+                                        "Section 6.1 additionally specifies the designated Thinkstep-node aggregated datasets for energy, transport, packaging and end-of-life under that baseline.",
+                                        "The historical supplier/node requirement is source context, not a verified current endpoint or permission to select an arbitrary replacement. Confirm the applicable supply requirement for the declared EF generation; document unresolved availability.",
+                                        "Commercial datasets are permitted subject to their access and license terms."
+                                    ]
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.agriculture-specific-data",
+                                    "normative_level": "should",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to agricultural cultivation.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "6.2"
+                                        }
+                                    ],
+                                    "requirement": "Prefer crop- and country/region/climate-specific yield, water/land use, land-use change, fertilizer and pesticide data per hectare and year."
+                                }
+                            ]
+                        },
+                        "useAdviceForDataSet": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.use-advice",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2"
+                                        }
+                                    ],
+                                    "requirement": "State methodological use advice where needed, including recycling boundaries and any use-phase behaviour the user must model."
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.supporting-use-advice",
+                                    "normative_level": "shall",
+                                    "applicability": "Non-primary supporting sub-datasets used only within their corresponding EF level-1 model.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.4.2 item 3"
+                                        }
+                                    ],
+                                    "requirement": "Include the source-prescribed notice restricting the supporting dataset to its corresponding level-1 partly disaggregated dataset.",
+                                    "content_requirements": [
+                                        "Use the exact notice in section 5.4.2 item 3, which points to the General comment for the central dataset name and UUID."
+                                    ]
                                 }
                             ]
                         }
@@ -1144,8 +1847,155 @@
                                         "requirement": "At least one review recommended for published datasets"
                                     }
                                 ]
+                            },
+                            "common:dataQualityIndicators": {
+                                "<rules>": [
+                                    {
+                                        "language": "all",
+                                        "id": "ef.dqr",
+                                        "normative_level": "shall",
+                                        "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                        "source_refs": [
+                                            {
+                                                "source": "ef-data-guide-2.0",
+                                                "section": "5.2.17; Tables 2; Equation F.1"
+                                            }
+                                        ],
+                                        "requirement": "Calculate and document TeR, GR, TiR, P and overall DQR before aggregating subprocesses or elementary flows.",
+                                        "content_requirements": [
+                                            "For secondary datasets select the most relevant subprocesses/direct foreground elementary flows covering at least 80% of the weighted single score, then normalize contributions within that selected set.",
+                                            "Assign each component rating using Table 2. For process contributions use activity-data TiR/P and secondary-dataset TeR/TiR/GR; average the two TiR ratings.",
+                                            "Compute contribution-weighted criteria, then DQR = (TeR + GR + TiR + P) / 4. Each resulting criterion must not exceed 3.0, not merely the overall mean.",
+                                            "Report text and one-decimal numeric values for the four criteria and overall DQR; set methodological appropriateness and completeness to Not applicable.",
+                                            "The Guide notes pilot-phase tender exceptions with documented alternative approaches. Non-primary supporting sub-datasets do not require their own DQR.",
+                                            "If numeric ratings cannot be represented by the current target indicator enum, retain them in review documentation and report the representation gap; do not replace them with a qualitative label and claim equivalent compliance."
+                                        ],
+                                        "examples": {
+                                            "positive": [
+                                                "Weighted criteria 2.0, 2.0, 2.0, 2.0 give DQR 2.0."
+                                            ],
+                                            "negative": [
+                                                "Criteria 4.0, 1.0, 1.0, 1.0 have mean 1.75 but fail the individual-criterion limit."
+                                            ]
+                                        }
+                                    }
+                                ]
+                            },
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.review-team",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "8.1-8.2; Tables 3-4"
+                                        }
+                                    ],
+                                    "requirement": "Use an eligible independent review team: at least two independent reviewers including at least one external reviewer.",
+                                    "content_requirements": [
+                                        "The Guide permits type 1 (at least three independent reviewers, including one external) or type 2 (two independent reviewers, including one external). A single external reviewer is not sufficient.",
+                                        "The team collectively needs more than two years of environmental audit/review practice, more than two reviews, more than two years of LCA practice, participation in more than four LCI works, and more than two years of relevant sector experience.",
+                                        "Verify independence/conflicts and identify reviewers and institutions, scope and method. Supporting sub-datasets are exempt from separate review under section 5.4.2."
+                                    ]
+                                }
+                            ],
+                            "common:referenceToCompleteReviewReport": {
+                                "<rules>": [
+                                    {
+                                        "language": "all",
+                                        "id": "ef.review-report",
+                                        "normative_level": "shall",
+                                        "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                        "source_refs": [
+                                            {
+                                                "source": "ef-data-guide-2.0",
+                                                "section": "8.3; Table 5"
+                                            }
+                                        ],
+                                        "requirement": "Attach one agreed and signed EF review report and one agreed dataset DQR for the assessed dataset, using the source review template.",
+                                        "content_requirements": [
+                                            "Document dataset identity/locator, commissioner, reviewers, method/scope/date, compliance system and EF package version.",
+                                            "Assess method/category requirements, allocation, CFF, LCIA consistency, nomenclature, documentation, ILCD validation, DQR and cut-off; resolve non-compliance before declaring EF compliance.",
+                                            "Reference documents used in the review and include the reviewers compliance declaration. Review affected parts again after core-content changes.",
+                                            "One EF report does not mean exactly one TIDAS review object: multiple review records may reference the same agreed report. General TIDAS optional-report semantics remain unchanged."
+                                        ],
+                                        "examples": {
+                                            "positive": [
+                                                "Several TIDAS review records reference one team-approved EF report."
+                                            ],
+                                            "negative": [
+                                                "A missing report is treated as proof of EF review solely because the general TIDAS schema accepts its absence."
+                                            ]
+                                        }
+                                    }
+                                ]
                             }
                         }
+                    },
+                    "completeness": {
+                        "referenceToSupportedImpactAssessmentMethods": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.supported-methods",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.14"
+                                        }
+                                    ],
+                                    "requirement": "Individually reference only the applied EF impact-category methods in the supported-methods field."
+                                }
+                            ]
+                        }
+                    },
+                    "complianceDeclarations": {
+                        "<rules>": [
+                            {
+                                "language": "all",
+                                "id": "ef.compliance-declarations",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-3.1-addendum-2022",
+                                        "section": "5.2.15 (replacement Table 1)"
+                                    }
+                                ],
+                                "requirement": "Declare the five required compliance systems, plus the applicable PEFCR when present, using the source datasets and aspect values specified in the addendum.",
+                                "content_requirements": [
+                                    "Select one applicable 2021/2279 method source: Annex I PEF 779fb9ea-de54-4707-b7fc-6154661552b5; Annex II PEFCR 909ae358-42e0-4365-8767-22b92c3229f4; Annex III OEF cbeab91f-74a4-4b5a-84dc-69915a22dc71; Annex IV OEFSR cec792b1-58ce-4310-bc09-6612256633b8. Set all aspects Fully compliant only when substantiated.",
+                                    "Where a PEFCR applies, reference its dedicated source and the required fully compliant aspects.",
+                                    "ILCD entry-level d92a1a12-2545-49e2-a585-55c259997756: quality Not defined; other aspects Fully compliant.",
+                                    "ISO 14040 1ea48531-e397-4ca7-ac08-056e4fa11826: nomenclature, documentation and quality Not defined; other aspects Fully compliant.",
+                                    "ISO 14044 1adb438d-4a8b-4919-885e-0a66da3c0f2a: nomenclature, review and quality Not defined; other aspects Fully compliant.",
+                                    "Reference-package declaration: nomenclature Fully compliant and all other aspects Not defined. EF 3.1 source UUID is 0eb2b770-2cb1-43cf-9fbc-215df36fe9f0; use the matching source for another applicable package.",
+                                    "Do not add unrelated compliance systems in this EF declaration set. Include the referenced source datasets in the delivered package. A package nomenclature declaration alone is not overall EF compliance."
+                                ]
+                            },
+                            {
+                                "language": "all",
+                                "id": "ef.supporting-compliance",
+                                "normative_level": "shall",
+                                "applicability": "Non-primary supporting sub-datasets used only within their corresponding EF level-1 model.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-3.1-addendum-2022",
+                                        "section": "Update to supporting-sub-dataset compliance table (page 5)"
+                                    }
+                                ],
+                                "requirement": "Use the special supporting-dataset declaration and the same EF reference-package declaration as the central dataset.",
+                                "content_requirements": [
+                                    "Supporting source 2f8a3ebd-befc-4ea9-a6de-34bb6d426d2f: quality Not defined; all other aspects Fully compliant.",
+                                    "Reference-package source: nomenclature Fully compliant; all other aspects Not defined. For EF 3.1 use 0eb2b770-2cb1-43cf-9fbc-215df36fe9f0.",
+                                    "Do not require the full five/six-system declaration set or an independent review/DQR for this special supporting role."
+                                ]
+                            }
+                        ]
                     }
                 },
                 "administrativeInformation": {
@@ -1186,6 +2036,30 @@
                                         "01.01.000",
                                         "02.00.000"
                                     ]
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.version",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2"
+                                        }
+                                    ],
+                                    "requirement": "For this EF baseline use the three-part version NN.NN.NNN, separating major, minor/correction and internal development increments.",
+                                    "content_requirements": [
+                                        "This scoped EF convention does not remove the ordinary TIDAS allowance for NN.NN."
+                                    ],
+                                    "examples": {
+                                        "positive": [
+                                            "01.02.003 meets the EF representation convention."
+                                        ],
+                                        "negative": [
+                                            "01.02 is valid under the general TIDAS Version schema but does not satisfy this EF convention."
+                                        ]
+                                    }
                                 }
                             ]
                         },
@@ -1201,8 +2075,99 @@
                                     ]
                                 }
                             ]
+                        },
+                        "<rules>": [
+                            {
+                                "language": "all",
+                                "id": "ef.publication-metadata",
+                                "normative_level": "shall",
+                                "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "5.2"
+                                    }
+                                ],
+                                "requirement": "Declare the workflow/publication status and license type, and fill other administrative fields at the ILCD-recommended level.",
+                                "content_requirements": [
+                                    "Use evidence of the actual dataset status; a formatting or conversion operation does not establish publication or review completion."
+                                ]
+                            },
+                            {
+                                "language": "all",
+                                "id": "ef.update-lineage",
+                                "normative_level": "shall",
+                                "applicability": "Updates of EF-compliant datasets/data stocks covered by Guide section 3.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-data-guide-2.0",
+                                        "section": "3.1-3.3; 3.5-3.6"
+                                    }
+                                ],
+                                "requirement": "Classify an update before assigning its identity and retain the original published dataset/version.",
+                                "content_requirements": [
+                                    "A1: provider changes to LCI, DQR, LCIA, process name or other core semantics require a new UUID, updated review and a predecessor reference with UUID/version/URI; the Guide specifies an Updated+year name prefix and normally the same data stock.",
+                                    "A2: non-core provider corrections retain UUID, increment version and keep the original stock. A dataset used correctly in a PEFCR/OEFSR but uploaded incorrectly follows A2.",
+                                    "B: adaptation to a new EF reference package retains UUID/name, increments version, links the predecessor, updates compliance and uses a new, package-consistent stock.",
+                                    "Additional provider changes during package migration or a tender require their own A1/A2 classification; do not hide them in case B. These are published-EF update procedures, not instructions to renumber ordinary working drafts."
+                                ]
+                            }
+                        ],
+                        "common:dateOfLastRevision": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.revision-date",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2"
+                                        }
+                                    ],
+                                    "requirement": "Record and update the last revision using an ISO 8601 date-time with its time-zone information when dataset content changes."
+                                }
+                            ]
                         }
-                    }
+                    },
+                    "common:commissionerAndGoal": {
+                        "common:intendedApplications": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.intended-applications",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2"
+                                        }
+                                    ],
+                                    "requirement": "Document the intended applications of the dataset."
+                                }
+                            ]
+                        }
+                    },
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.supporting-administration",
+                            "normative_level": "shall",
+                            "applicability": "Non-primary supporting sub-datasets used only within their corresponding EF level-1 model.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-data-guide-2.0",
+                                    "section": "5.4.2 items 1 and 6"
+                                }
+                            ],
+                            "requirement": "Copy owner, commissioner, license type and access/use restrictions exactly from the central dataset.",
+                            "content_requirements": [
+                                "For delivered supporting datasets the Guide specifies Data set finalised; entirely published as the workflow/publication status. This requirement does not authorize publishing a working draft."
+                            ]
+                        }
+                    ]
                 },
                 "exchanges": {
                     "exchange": {
@@ -1216,6 +2181,22 @@
                                         "waste_flows": "Prefix with 'waste' or '废物'"
                                     },
                                     "validation": "Must reference existing flow dataset UUID"
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.reference-flow-content",
+                                    "normative_level": "shall",
+                                    "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.9; 6.3"
+                                        }
+                                    ],
+                                    "requirement": "Store nonzero factory-gate water and biogenic-carbon content as properties of the reference product/waste flow, in the property reference units.",
+                                    "content_requirements": [
+                                        "These quantities characterize the product, not the process. Retain native-forest origin information and the required land-use-change carbon treatment."
+                                    ]
                                 }
                             ]
                         },
@@ -1248,16 +2229,196 @@
                                 {
                                     "language": "all",
                                     "consistency_rule": "Should align with process location unless specifically different\n(e.g., imported materials, exported products)\n"
+                                },
+                                {
+                                    "language": "all",
+                                    "id": "ef.regionalized-elementary-flows",
+                                    "normative_level": "shall",
+                                    "applicability": "EF elementary-flow modelling under the stated baseline.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "5.2.6; Annex 1"
+                                        }
+                                    ],
+                                    "requirement": "Use regionalized elementary flows within the source-defined locations and substances.",
+                                    "content_requirements": [
+                                        "Land Use and Water Use permit all locations in the Guide; other categories are restricted to the substances/countries in Annex 1.",
+                                        "Resolve the authorized flow and location from the applicable reference package. The source annex is a dependency, not a license to create arbitrary localized elementary-flow identities."
+                                    ]
+                                }
+                            ]
+                        },
+                        "generalComment": {
+                            "<rules>": [
+                                {
+                                    "language": "all",
+                                    "id": "ef.elementary-duplicates",
+                                    "normative_level": "may",
+                                    "applicability": "EF process datasets assessed under the Data Guide, outside the stricter eILCD model-exchange requirement.",
+                                    "source_refs": [
+                                        {
+                                            "source": "ef-data-guide-2.0",
+                                            "section": "4; 5.2.7; 6"
+                                        }
+                                    ],
+                                    "requirement": "Duplicate elementary input/output flows are permitted by the Data Guide when each occurrence documents its source in the exchange comment.",
+                                    "content_requirements": [
+                                        "The Guide describes merging only matching UUID and location pairs, retaining source comments/amount provenance; differing locations must not be silently merged.",
+                                        "This permission does not apply to the stricter EF eILCD model-exchange scope."
+                                    ],
+                                    "examples": {
+                                        "positive": [
+                                            "Documented elementary-flow occurrences from two sources in a Data-Guide dataset."
+                                        ],
+                                        "negative": [
+                                            "Treating this permission as permission to repeat a product flow or as an exception to eILCD uniqueness."
+                                        ]
+                                    }
+                                }
+                            ]
+                        },
+                        "<rules>": [
+                            {
+                                "language": "all",
+                                "id": "ef.eilcd-defined-amount",
+                                "normative_level": "shall",
+                                "applicability": "Processes participating in EF models exchanged in eILCD format.",
+                                "source_refs": [
+                                    {
+                                        "source": "ef-eilcd-modelling-2.1",
+                                        "section": "2.3"
+                                    }
+                                ],
+                                "requirement": "Provide a defined amount for every flow independently of accumulation, storage or time."
+                            }
+                        ]
+                    },
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.product-waste-uniqueness",
+                            "normative_level": "shall",
+                            "applicability": "EF process exchanges, including level-1 models.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-data-guide-2.0",
+                                    "section": "4; 6"
+                                }
+                            ],
+                            "requirement": "Do not repeat the same product or waste flow on the same input or output side; do not model using the other-flows type.",
+                            "content_requirements": [
+                                "Resolve flow identity from the referenced UUID, not the displayed name. Compare input and output sides separately.",
+                                "Different amounts, locations, suppliers or reference versions do not alone establish a different flow identity. Do not invent a new UUID or merge distinct supplies solely to silence a finding."
+                            ],
+                            "examples": {
+                                "positive": [
+                                    "One occurrence of flow A on input and one on output is not a duplicate on either side."
+                                ],
+                                "negative": [
+                                    "Two input exchanges reference product flow A with amounts 0.3 and 0.7, even if their locations differ."
+                                ]
+                            }
+                        },
+                        {
+                            "language": "all",
+                            "id": "ef.eilcd-flow-uniqueness",
+                            "normative_level": "shall",
+                            "applicability": "Processes participating in EF models exchanged in eILCD format.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-eilcd-modelling-2.1",
+                                    "section": "2.3"
+                                }
+                            ],
+                            "requirement": "In an EF eILCD process, each flow may occur only once on the input side and only once on the output side.",
+                            "content_requirements": [
+                                "This applies to elementary flows as well as product/waste flows. A location or supplier difference alone does not satisfy it when the referenced flow identity is unchanged.",
+                                "Enforce identity per side, not uniqueness of whole exchange objects. Distinct exchange IDs or amounts do not remove duplicate flow references.",
+                                "This rule does not imply that every country always needs a new flow; a remedy must preserve the source meaning and compatible upstream/downstream connections."
+                            ],
+                            "examples": {
+                                "positive": [
+                                    "Distinct flow identities on the input side with consistent supplier output references."
+                                ],
+                                "negative": [
+                                    "Two input occurrences of the same elementary flow, even though a non-eILCD EF dataset could document them."
+                                ]
+                            }
+                        },
+                        {
+                            "language": "all",
+                            "id": "ef.water-balance",
+                            "normative_level": "shall",
+                            "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-data-guide-2.0",
+                                    "section": "6"
+                                }
+                            ],
+                            "requirement": "Distinguish water withdrawal, release and evaporation at foreground and background level and use consistent regionalization for matching inputs and outputs.",
+                            "content_requirements": [
+                                "Use country-level water flows; use an unspecified location where the country is not covered by the reference package.",
+                                "For continental datasets use constituent-country shares; unspecified location is allowed for large macro-regions such as RoW.",
+                                "Analyse balances per country and explain negative balances in the metadata; do not silently discard or alter the exchanges."
+                            ]
+                        },
+                        {
+                            "language": "all",
+                            "id": "ef.agriculture-emissions",
+                            "normative_level": "shall",
+                            "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to agricultural modelling; later applicable method/category-rule provisions require separate source verification.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-data-guide-2.0",
+                                    "section": "6.2"
                                 }
+                            ],
+                            "requirement": "Model agricultural inputs and their emissions explicitly under the source-specific assumptions.",
+                            "content_requirements": [
+                                "Model pesticides by active ingredient with the Guide default distribution 90% agricultural soil, 9% air, 1% water; more specific data need documentation and review.",
+                                "Differentiate fertilizer/manure types; cover NH3, direct/indirect N2O and lime/urea CO2 to air, nitrate to water, and phosphate/phosphorus losses to water. Do not model nitrogen emissions to soil.",
+                                "For nitrogen fertilizers the Guide recommends IPCC 2006 Tier 1 factors as specified in the applicable PEF/OEF method; record the selected model.",
+                                "Represent heavy metals to soil/water with oxidation state for water flows and document the selected crop-uptake treatment.",
+                                "Include rice methane per the cited IPCC calculation and drained-peat CO2 through drainage/oxidation modelling.",
+                                "Include applicable seed, peat, lime, machinery and residue inputs/emissions unless within justified cut-off. Include drying/storage, and field operations unless manual operation is documented."
                             ]
                         }
-                    }
+                    ]
+                },
+                "LCIAResults": {
+                    "<rules>": [
+                        {
+                            "language": "all",
+                            "id": "ef.lcia-results",
+                            "normative_level": "shall",
+                            "applicability": "EF-compliant process datasets other than non-primary supporting sub-datasets.",
+                            "source_refs": [
+                                {
+                                    "source": "ef-data-guide-2.0",
+                                    "section": "5.2.16; 6; 8.3 Table 5"
+                                },
+                                {
+                                    "source": "ef-3.1-addendum-2022",
+                                    "section": "Introduction"
+                                }
+                            ],
+                            "requirement": "Supply characterized results for all 16 default EF impact categories using the applicable official reference package.",
+                            "content_requirements": [
+                                "Place results in the dedicated LCIA results section and serialize them in scientific notation in ILCD XML; this is not a requirement to change the TIDAS numeric schema.",
+                                "The Guide requires Look@LCI calculation/verification with the official package; its review template treats discrepancies above 1% as non-compliant.",
+                                "The section 6 footnote permits a different arrangement only when decided at the kick-off meeting; retain that evidence rather than assume an exception.",
+                                "The EF 3.1 addendum changes factors and expected results but explicitly leaves section 5.2.16 in force. Recompute results for the declared package; do not modify its factors."
+                            ]
+                        }
+                    ]
                 }
             }
         }
     },
     "methodologyTexts": {
         "flows": "# Flow Dataset Content Rules and Guidelines\n# 流量数据集内容规则与指南\n#\n# Rule Structure:\n# <rules>: [\n#   {\n#     language: \"en\" | \"zh\" | \"all\",\n#     examples: [...] (optional),\n#     ... other custom fields\n#   }\n# ]\n\nmetadata:\n  version: \"1.0.0\"\n  last_updated: \"2024-01-15\"\n  applies_to: \"ILCD/Tidas Flow Dataset v1.1\"\n\n# Global rules\nglobal_rules:\n  multi_language_support:\n    <rules>:\n      - language: \"en\"\n        requirement: \"English version is mandatory for all multilingual fields\"\n        purpose: \"Ensures international accessibility\"\n      - language: \"zh\"\n        requirement: \"中文版本建议提供，特别是中国地区的数据\"\n        purpose: \"确保本地用户可理解性\"\n\nflowDataSet:\n  flowInformation:\n    dataSetInformation:\n      name:\n        baseName:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                provide the general descriptive name of the flow using technical language.\n                - State the substance, product, or waste exactly as used in industry or customer communication.\n                - Avoid abbreviations unless paired with the fully written term.\n                - Indicate relevant states or grades (e.g., gaseous, granulate, recycled) when needed for identification.\n              content_requirements:\n                - \"Use commas to separate descriptors within the base name; do not use semicolons.\"\n                - \"Prefer commonly accepted trivial names over rare chemical nomenclature for known substances.\"\n                - \"Avoid including geographical, temporal, or quantitative data; capture those in dedicated fields.\"\n                - \"For emissions, rely solely on the base name unless Rule 16 qualifiers are essential.\"\n              examples:\n                - \"Polypropylene, PP, granulate\"\n                - \"Sulfur dioxide, gaseous\"\n                - \"Waste glass cullet, mixed colors\"\n              best_practices:\n                - \"Mirror terminology used in authoritative datasets to support searches.\"\n                - \"Spell out acronyms on first use and retain the acronym after a comma if widely used.\"\n                - \"Check for outdated terminology and update to current industry usage.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                使用行业技术语言准确描述该流的通用名称。\n                - 先写全称，再根据需要补充常用缩写。\n                - 在必要时说明形态或等级（例如 气态、颗粒、再生料）。\n                - 避免不必要的地理、时间或定量信息。\n              content_requirements:\n                - \"同一字段内使用逗号分隔描述，不使用分号。\"\n                - \"优先采用通用俗名；仅当需要时使用复杂化学命名。\"\n                - \"排除地理与时间信息，相关数据在其他字段填写。\"\n                - \"对排放类流量通常仅需基础名称，除非需要补充定量属性。\"\n              examples:\n                - \"聚丙烯，PP，颗粒料\"\n                - \"二氧化硫，气态\"\n                - \"废玻璃碎片，混色\"\n              best_practices:\n                - \"与权威数据集保持术语一致，方便检索。\"\n                - \"首次出现缩写时保留全称+缩写组合。\"\n                - \"定期核对术语，避免使用过时名称。\"\n\n        treatmentStandardsRoutes:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                capture qualitative technical qualifiers as comma-separated phrases.\n                - List treatments, fulfilled standards, product qualities, intended uses, and production routes.\n                - Arrange entries from intrinsic modifications (treatment) to contextual qualifiers (use information).\n              content_requirements:\n                - \"Document surface or material treatments (e.g., hot rolled, sterilised, refined).\"\n                - \"Reference applicable standards or grades (e.g., EN 10025 S355, ASTM D4806).\"\n                - \"Capture key performance attributes (e.g., UV-resistant, food-grade).\"\n                - \"Include intended use qualifiers when they define the flow (e.g., for wafer production).\"\n                - \"Identify primary or secondary origin and specific routes when relevant (e.g., secondary feedstock, steam cracking route).\"\n              examples:\n                - \"Hot rolled, EN 10025 S355, primary production route\"\n                - \"Refined, ASTM D4806, fuel-grade ethanol\"\n                - \"Sterilised, ISO 11137 compliant, medical packaging\"\n              best_practices:\n                - \"Use terminology recognised by the supplying industry and reference documents.\"\n                - \"Keep each qualifier concise (ideally two to three words).\"\n                - \"Avoid marketing adjectives; focus on technical differentiators.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                以逗号连接处理方式、标准、质量属性、用途及工艺路线等限定词。\n                - 先写处理方式，再写标准或等级，随后补充质量与用途信息。\n                - 根据需要注明原料来源或路线。\n              content_requirements:\n                - \"写明处理方式（如 热轧、精制、灭菌等）。\"\n                - \"引用适用标准或等级（如 EN 10025 S355、ASTM D4806 等）。\"\n                - \"记录关键性能属性（如 抗紫外、食品级）。\"\n                - \"用途限定清晰表达（如 用于晶圆生产、医用包装）。\"\n                - \"注明原生或再生来源，以及具体路线（如 再生料、蒸汽裂解路线）。\"\n              examples:\n                - \"热轧，EN 10025 S355，原生生产路线\"\n                - \"精制，符合 ASTM D4806，燃料级乙醇\"\n                - \"灭菌，符合 ISO 11137，医疗包装用\"\n              best_practices:\n                - \"使用行业公认术语，必要时核对标准文档。\"\n                - \"限定词保持简洁，避免冗长描述。\"\n                - \"杜绝宣传性词汇，突出技术差异。\"\n\n        mixAndLocationTypes:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                state mix and location type qualifiers separated by commas.\n                - Distinguish between production mix, consumption mix, or technology-specific flows.\n                - Describe the delivery point or availability location using \"at\" (handover) or \"to\" (including transport).\n              content_requirements:\n                - \"Indicate whether the dataset averages multiple production routes (production mix) or includes trade (consumption mix).\"\n                - \"Specify nodes such as at plant, at wholesale, at point-of-sale, to consumer.\"\n                - \"Use 'to' when transport burdens up to that node are included (e.g., to wholesale, to waste incineration plant).\"\n                - \"Leave the field empty only when both mix and location qualifiers are inapplicable.\"\n              examples:\n                - \"Production mix, at plant\"\n                - \"Consumption mix, to consumer\"\n                - \"Technology-specific, to wholesale\"\n                - \"Production mix, to waste incineration plant\"\n              best_practices:\n                - \"Validate the qualifiers against the system boundary description.\"\n                - \"Keep language consistent across flows representing the same market.\"\n                - \"Avoid mixing intended use descriptions; place them in treatmentStandardsRoutes.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                用逗号标注混合类型与交付位置。\n                - 区分生产混合、消费混合或特定技术。\n                - 使用“在”表示交割点，“至”表示包含运输至该节点。\n              content_requirements:\n                - \"说明是否为生产混合（多路线平均）或消费混合（包含进出口）。\"\n                - \"标出交付/可得位置（如 在工厂、在批发、在零售点、至终端消费者）。\"\n                - \"需要时补充至废物处理设施等描述。\"\n                - \"若两类信息均不适用，可留空；否则需提供。\"\n              examples:\n                - \"生产混合，在工厂\"\n                - \"消费混合，至终端消费者\"\n                - \"特定技术，至批发商\"\n                - \"生产混合，至废物焚烧厂\"\n              best_practices:\n                - \"确认与系统边界叙述一致。\"\n                - \"同一市场的描述保持统一表述。\"\n                - \"用途限定应写在 treatmentStandardsRoutes 字段，避免混淆。\"\n\n        flowProperties:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                express quantitative specifying properties with explicit bases.\n                - Provide constituent or energy content per reference unit.\n                - Use comma-separated entries for multiple properties.\n                - Include the measurement basis if it deviates from mass fraction.\n              content_requirements:\n                - \"Quantify key components or properties (e.g., 45 % Fe, 9.6 MJ/kg net calorific value).\"\n                - \"Clarify basis such as by volume, molar, per dry mass when applicable.\"\n                - \"Express values using SI units or widely accepted industrial units.\"\n                - \"Avoid redundant data that is recorded in dedicated property fields.\"\n              examples:\n                - \"45 % Fe mass/mass\"\n                - \"9.6 MJ/kg net calorific value\"\n                - \"90.5 % methane by volume\"\n                - \"750 g/L total dissolved solids\"\n              best_practices:\n                - \"Align significant figures with data quality documentation.\"\n                - \"Cross-check against laboratory reports or data sources.\"\n                - \"Display multiple properties in descending relevance.\"\n            - language: \"zh\"\n              naming_convention: |\n                用逗号列出定量属性，并明确计量基准。\n                - 列出关键组分含量或能量密度。\n                - 若计量基准不同于质量分数，需额外说明。\n              content_requirements:\n                - \"量化核心属性（如 45 % Fe、9.6 MJ/kg 净热值）。\"\n                - \"注明体积分数、摩尔分数或干基等特殊基准。\"\n                - \"使用 SI 单位或行业惯用单位。\"\n                - \"避免重复其他字段已有的信息。\"\n              examples:\n                - \"45 % Fe 质量分数\"\n                - \"9.6 MJ/kg 净热值\"\n                - \"90.5 % 甲烷 体积分数\"\n                - \"750 g/L 总溶解固体\"\n              best_practices:\n                - \"与数据质量说明一致地保留有效数字。\"\n                - \"对照实验或来源数据核实取值。\"\n                - \"按重要性排序多个属性。\"\n\n\n      common:synonyms:\n        <rules>:\n          - language: \"en\"\n            usage: |\n              Provide alternative names, trade names, or abbreviations separated by semicolons.\n              - Include synonyms that improve discoverability in databases.\n              - Keep language consistent with the specified locale.\n            content_requirements:\n              - \"List only validated synonyms used in reputable sources.\"\n              - \"Avoid duplicate entries already covered in the base name.\"\n              - \"Reflect different English variants if they aid searching (e.g., aluminium; aluminum).\"\n            examples:\n              - \"Polypropylene homopolymer; PP homo; propene polymer\"\n              - \"Sulfur dioxide; sulphur dioxide\"\n\n          - language: \"zh\"\n            usage: |\n              以分号分隔提供中文同义词、商品名或常用缩写。\n              - 仅记录实际使用且经过验证的称谓。\n              - 与对应语言环境保持一致。\n            content_requirements:\n              - \"避免与基础名称重复。\"\n              - \"必要时提供简体与繁体或常用别名。\"\n            examples:\n              - \"聚丙烯均聚物; 丙烯聚合物\"\n              - \"二氧化硫; 亚硫酸酐\"\n\n      classificationInformation:\n        common:elementaryFlowCategorization:\n          <rules>:\n            - language: \"en\"\n              guidance: |\n                Use the ILCD elementary flow category hierarchy to classify elementary flows.\n                - Provide up to three levels (0–2) following the controlled vocabulary.\n                - Record the official category identifier (`@catId`) and the exact label text from `tidas_flows_elementary_category.json`.\n              content_requirements:\n                - \"Select categories by referencing the maintained `tidas_flows_elementary_category.json` list; each level must use a valid `@catId`.\"\n                - \"Ensure level numbering is continuous starting at level 0.\"\n                - \"Use one entry per level; do not duplicate levels.\"\n                - \"When a level is omitted, no deeper level may be provided (e.g., skip level 1 only if level 2 is also omitted).\"\n              examples:\n                - level 0: \"Emissions to air\"\n                - level 1: \"Emissions to air, non-methane VOC\"\n                - level 2: \"Emissions to air, aromatic compounds\"\n              best_practices:\n                - \"Verify category assignments with environmental experts when ambiguous.\"\n                - \"Update categorisation promptly if the flow type changes.\"\n                - \"Implement validation that checks the selected `@catId` values exist in the controlled list and match the base name's flow type (e.g., emissions, resource).\"\n\n            - language: \"zh\"\n              guidance: |\n                根据 ILCD 基本流分类层级填写，最多提供 0–2 级。\n                - 使用 `tidas_flows_elementary_category.json` 中的分类标识和标准名称。\n                - 各层级仅填写一次，保持层级连贯。\n              content_requirements:\n                - \"分类必须引用 `tidas_flows_elementary_category.json` 中的有效 `@catId`。\"\n                - \"层级编号自0开始，依次递增。\"\n                - \"如无更细分类，可省略更深层级，不能跳级。\"\n              examples:\n                - \"第0级：空气排放\"\n                - \"第1级：空气排放，非甲烷挥发性有机物\"\n                - \"第2级：空气排放，芳香族化合物\"\n              best_practices:\n                - \"对于难以归类的流量，先与专业人员确认。\"\n                - \"当流量属性发生变化时及时更新分类。\"\n                - \"建议在数据录入时校验 `@catId` 是否存在，并核对基础名称是否属于该分类类型。\"\n\n        common:classification:\n          <rules>:\n            - language: \"en\"\n              guidance: |\n                Classify product or waste flows using the CPC product flow hierarchy.\n                - Supply sequential levels (0–4) as applicable.\n                - Ensure `@classId` references controlled entries in `product_flow_category_index.json`.\n              content_requirements:\n                - \"Match each textual label to its official class identifier.\"\n                - \"Do not skip intermediate levels when deeper levels are provided.\"\n                - \"Avoid mixing elementary and product classifications; choose the relevant branch.\"\n                - \"Confirm every `@classId` exists in the maintained hierarchy and follows parent-child relationships.\"\n              examples:\n                - level 0: \"Products\"\n                - level 1: \"Materials\"\n                - level 2: \"Metals\"\n                - level 3: \"Ferrous metals\"\n                - level 4: \"Steel, flat rolled\"\n              best_practices:\n                - \"Coordinate with database governance when introducing new classes.\"\n                - \"Review class assignments during dataset version updates.\"\n                - \"Apply validation to ensure selected classes align with the base name (e.g., avoid classifying an emission as a product).\"\n\n            - language: \"zh\"\n              guidance: |\n                按照 CPC 产品/废物流分类层级填写，最多支持0–4级。\n                - `@classId` 必须引用 `product_flow_category_index.json` 中的受控条目。\n                - 如填写更深层级，不得跳过中间层级。\n              content_requirements:\n                - \"确保标签文字与官方分类名称一致。\"\n                - \"区分产品/废物流与基本流分类，避免混用。\"\n                - \"每个 `@classId` 均需在维护的层级结构中存在，并遵循父子关系。\"\n              examples:\n                - \"第0级：产品\"\n                - \"第1级：材料\"\n                - \"第2级：金属材料\"\n                - \"第3级：黑色金属\"\n                - \"第4级：钢，板材\"\n              best_practices:\n                - \"新增分类前与数据库管理者沟通确认。\"\n                - \"版本更新时复核分类是否仍然准确。\"\n                - \"在录入时增加校验：确认所选分类存在且与基础名称性质一致（例如 排放不得归入产品类目）。\"\n\n    quantitativeReference:\n      referenceToReferenceFlowProperty:\n        <rules>:\n          - language: \"all\"\n            definition: |\n              Integer key pointing to the `@dataSetInternalID` of the reference flow property listed in `flowProperties`.\n              - Mandatory for every flow dataset.\n              - Typically links to the mass or energy flow property that represents the functional unit of the flow.\n            content_requirements:\n              - \"Use a positive integer matching an existing `flowProperties.flowProperty.@dataSetInternalID`.\"\n              - \"Ensure the referenced flow property has `meanValue = 1` relative to itself.\"\n              - \"Whenever the reference property changes, update this link and all dependent ratios.\"\n            validation:\n              - \"Reject IDs that are absent from the local `flowProperties` list.\"\n              - \"Cross-verify that the referenced flow property is consistent with `modellingAndValidation.LCIMethod.typeOfDataSet` (e.g., mass for product flows, substance amount for elementary emissions).\"\n            examples:\n              - \"1  (points to flow property entry 1: Mass, kg)\"\n              - \"3  (points to flow property entry 3: Net calorific value, MJ)\"\n\n  flowProperties:\n    flowProperty:\n      referenceToFlowPropertyDataSet:\n        <rules>:\n          - language: \"all\"\n            definition: |\n              Global reference (`GlobalReferenceType`) to the flow property dataset defining the unit, quantity dimension, and conversion factors (e.g., mass, energy).\n            content_requirements:\n              - \"Use maintained references (UUID + version) from the organisation's flow property catalogue.\"\n              - \"Populate all required `GlobalReferenceType` fields: `@type`, `@refObjectId` (UUID), `@version`, `@uri`, and `common:shortDescription`.\"\n              - \"Ensure the referenced dataset corresponds to the intended physical quantity.\"\n              - \"Keep references updated if the canonical flow property dataset is revised.\"\n            validation:\n              - \"Verify referenced datasets exist and are accessible.\"\n              - \"Cross-check that unit symbols in name/meanValue match the referenced dataset's reference unit.\"\n              - \"Validate UUID formatting against the 8-4-4-4-12 pattern.\"\n            examples:\n              - \"UUID: 123e4567-e89b-12d3-a456-426614174000; version 01.00.000 (Mass, kg)\"\n              - \"UUID: 223e4567-e89b-12d3-a456-426614174111; version 01.00.000 (Energy, MJ)\"\n\n      meanValue:\n        <rules>:\n          - language: \"en\"\n            definition: |\n              Numerical relation expressing how the flow amount converts between the reference flow property and the current property.\n            content_requirements:\n              - \"Set to 1.0 for the reference flow property (the one pointed to by `referenceToReferenceFlowProperty`).\"\n              - \"For additional properties, provide conversion ratios (e.g., net calorific value per kg).\"\n              - \"Use significant figures that reflect measurement accuracy; avoid trailing precision beyond data quality.\"\n            validation:\n              - \"Ensure values are positive real numbers.\"\n              - \"For energy or composition properties, cross-check with laboratory or literature sources.\"\n              - \"If uncertainty fields are provided, confirm their ranges align with the mean value.\"\n            examples:\n              - \"1.0\"\n              - \"42.5\"\n              - \"0.85\"\n\n          - language: \"zh\"\n            definition: |\n              表示参考流属性与当前属性之间换算关系的数值。\n            content_requirements:\n              - \"被定量参考指向的流属性应设置为 1.0。\"\n              - \"其他属性填写换算系数，例如 每千克对应的净热值。\"\n              - \"保留的有效数字需与测量精度相符。\"\n            validation:\n              - \"数值需为正实数。\"\n              - \"能量或组分属性须与实验或文献数据核对。\"\n              - \"若填写不确定性字段，应与该平均值的量级保持一致。\"\n            examples:\n              - \"1.0\"\n              - \"42.5\"\n              - \"0.85\"\n\n  modellingAndValidation:\n    LCIMethod:\n      typeOfDataSet:\n        <rules>:\n          - language: \"all\"\n            definition: |\n              Mandatory ILCD field indicating whether the flow is an \"Elementary flow\", \"Product flow\", or \"Waste flow\".\n            valid_values:\n              - \"Elementary flow\"\n              - \"Product flow\"\n              - \"Waste flow\"\n            content_requirements:\n              - \"Select exactly one value from the allowed list; do not customise.\"\n              - \"Elementary flow: substances exchanged with the environment without human transformation.\"\n              - \"Product flow: goods or services entering/exiting the technosphere as products.\"\n              - \"Waste flow: outputs destined for treatment or disposal services.\"\n              - \"Ensure consistency with `classificationInformation` and the chosen reference flow property (e.g., emissions require elementary flow).\"\n            validation:\n              - \"Enforce completion before publication.\"\n              - \"Add rule-based checks comparing the chosen value with classification IDs and base name phrasing.\"\n            examples:\n              - \"\\\"Elementary flow\\\"\"\n              - \"\\\"Product flow\\\"\"\n              - \"\\\"Waste flow\\\"\"\n\n    complianceDeclarations:\n      compliance:\n        referenceToComplianceSystem:\n          <rules>:\n            - language: \"all\"\n              definition: |\n                Global reference identifying the compliance or review scheme applied to this dataset.\n              content_requirements:\n                - \"Populate `common:referenceToComplianceSystem` with the Global Reference to the applied compliance or review system (e.g., ILCD Entry-Level).\"\n                - \"Complete the `GlobalReferenceType` fields for the compliance system: `@type`, `@refObjectId` (UUID), `@version`, `@uri`, and `common:shortDescription`.\"\n                - \"Refer only to recognised schemes and keep references aligned with current organisational compliance policy.\"\n              validation:\n                - \"Ensure the referenced compliance dataset exists and is accessible.\"\n                - \"Validate UUID format and, when provided, the resolvability of the URI.\"\n                - \"Warn when the referenced scheme is obsolete or not approved for the dataset type.\"\n              examples:\n                - \"referenceToComplianceSystem → UUID of ILCD Entry-Level compliance\"\n                - \"Corporate QA scheme reference with documented version\"\n\n        common:approvalOfOverallCompliance:\n          <rules>:\n            - language: \"all\"\n              definition: |\n                Declares the overall compliance outcome derived from the referenced scheme.\n              valid_values:\n                - \"Fully compliant\"\n                - \"Not compliant\"\n                - \"Not defined\"\n              content_requirements:\n                - \"Select one statement from the allowed list.\"\n                - \"Provide justification whenever \\\"Not compliant\\\" or \\\"Not defined\\\" is used.\"\n                - \"Ensure the chosen status matches evidence supplied by the compliance reference.\"\n              validation:\n                - \"Reject entries outside the `valid_values` set.\"\n                - \"When marked \\\"Fully compliant\\\", confirm a valid, current compliance reference is provided.\"\n              examples:\n                - \"\\\"Fully compliant\\\"\"\n                - \"\\\"Not compliant\\\"\"\n                - \"\\\"Not defined\\\" (pending external review)\"\n            \n\n  administrativeInformation:\n    dataEntryBy:\n      common:timeStamp:\n        <rules>:\n          - language: \"en\"\n            definition: |\n              ISO 8601 date-time indicating when the dataset was last generated or saved.\n            content_requirements:\n              - \"Record with full date and time including time zone (e.g., 2024-04-30T10:15:00+08:00).\"\n              - \"Update automatically upon each validated modification.\"\n              - \"If manual edit is necessary, ensure it reflects the actual publication instant.\"\n            validation:\n              - \"Reject timestamps without offset information.\"\n              - \"Prevent future-dated entries unless creating forward-dated publications.\"\n\n          - language: \"zh\"\n            definition: |\n              记录数据集生成或保存时间的 ISO 8601 日期时间（含时区）。\n            content_requirements:\n              - \"填写完整日期、时间与时区（如 2024-04-30T10:15:00+08:00）。\"\n              - \"每次有效修改后需自动更新。\"\n              - \"如需人工调整，应与实际发布时刻一致。\"\n            validation:\n              - \"禁止缺少时区的时间戳。\"\n              - \"除非为预发布版本，不得填写未来时间。\"\n\n      common:referenceToDataSetFormat:\n        <rules>:\n          - language: \"all\"\n            definition: |\n              Global reference to the ILCD data format description used to encode the dataset.\n            content_requirements:\n              - \"Populate all `GlobalReferenceType` fields: `@type`, `@refObjectId` (UUID), `@version`, `@uri`, and `common:shortDescription`.\"\n              - \"Update the reference when migrating to a newer schema version.\"\n            validation:\n              - \"Check that the referenced format dataset exists and matches the namespaces declared at the dataset root.\"\n              - \"Validate UUID and URI syntax.\"\n\n      common:referenceToPersonOrEntityEnteringTheData:\n        <rules>:\n          - language: \"all\"\n            definition: |\n              Global reference identifying the person or organisation that documented or entered the dataset.\n            content_requirements:\n              - \"Provide a maintained contact dataset using `GlobalReferenceType` with `@type`, `@refObjectId` (UUID), `@version`, `@uri`, and `common:shortDescription`.\"\n              - \"Ensure the referenced entity is authorised for data entry or maintenance.\"\n              - \"Update the reference whenever responsibilities change.\"\n            validation:\n              - \"Confirm UUID and URI syntax and that the reference resolves to an active contact.\"\n              - \"Flag mismatches where the listed entity lacks required permissions.\"\n            examples:\n              - \"UUID referencing the corporate LCA team contact dataset.\"\n\n    publicationAndOwnership:\n      common:dataSetVersion:\n        <rules>:\n          - language: \"en\"\n            definition: |\n              Version number of the dataset.\n            content_requirements:\n              - \"Follow semantic-style numbering (e.g., 01.00.000)\"\n              - \"Increment the version whenever content changes; document major vs. minor revisions.\"\n              - \"Synchronise version entries with repository tags or release notes.\"\n            validation:\n              - \"Enforce the numeric pattern with three groups separated by dots.\"\n              - \"Verify that the version increases monotonically compared to preceding datasets.\"\n            examples:\n              - \"01.00.000\"\n              - \"01.01.000\"\n              - \"02.00.000\"\n\n          - language: \"zh\"\n            definition: |\n              数据集版本号。\n            content_requirements:\n              - \"遵循三段式数字格式（例如 01.00.000）\"\n              - \"每次内容调整均需递增版本号，并区分主次版本。\"\n              - \"与代码仓库标签或发布说明保持一致。\"\n            validation:\n              - \"校验格式是否符合三段数字模式。\"\n              - \"确认相较于上一版本递增。\"\n            examples:\n              - \"01.00.000\"\n              - \"01.01.000\"\n              - \"02.00.000\"\n\n      common:referenceToOwnershipOfDataSet:\n        <rules>:\n          - language: \"all\"\n            definition: |\n              Global reference to the contact or organisation owning the dataset rights.\n            content_requirements:\n              - \"Link to a maintained ownership/contact dataset containing legal entity details.\"\n              - \"Update when ownership transfers or licensing terms change.\"\n              - \"Ensure alignment with publication statements and licences.\"\n            validation:\n              - \"Confirm the referenced ownership record exists and is current.\"\n              - \"Warn if the owner differs from the `dataEntryBy` entity without explanatory notes.\"\n            examples:\n              - \"UUID referencing company legal entity contact dataset.\"\n",
-        "processes": "# Process Dataset Content Rules and Guidelines\n# 流程数据集内容规则与指南\n#\n# Rule Structure:\n# <rules>: [\n#   {\n#     language: \"en\" | \"zh\" | \"all\",\n#     examples: [...] (optional),\n#     ... other custom fields\n#   }\n# ]\n\nmetadata:\n  version: \"1.0.0\"\n  last_updated: \"2024-01-15\"\n  applies_to: \"ILCD/Tidas Process Dataset v1.1\"\n\n# Global rules\nglobal_rules:\n  multi_language_support:\n    <rules>:\n      - language: \"en\"\n        requirement: \"English version is mandatory for all multilingual fields\"\n        purpose: \"Ensures international accessibility\"\n      - language: \"zh\"\n        requirement: \"中文版本建议提供，特别是中国地区的数据\"\n        purpose: \"确保本地用户可理解性\"\n\nprocessDataSet:\n  processInformation:\n    dataSetInformation:\n      name:\n        baseName:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                Follow ILCD Rule 20: align the process base name with the reference flow naming structure.\n                - Single reference flow: reuse the reference flow's technical name as the process name.\n                - Multiple reference flows: start with the technology or plant descriptor and append each reference flow name separated by commas.\n                - Exclude geographical or temporal qualifiers from the base name; capture them in the dedicated metadata fields.\n              content_requirements:\n                - \"Use technical terminology as applied in the supplying industry or towards customers.\"\n                - \"Separate descriptors within the base name using commas and avoid semicolons or brackets.\"\n                - \"Spell out terms before adding widely recognised abbreviations (e.g., \\\"Polypropylene, PP\\\").\"\n                - \"Cover every reference flow explicitly when the dataset is multi-functional.\"\n                - \"Keep the wording concise enough for interface display (target 200 characters or fewer).\"\n              examples:\n                - \"Electricity from hard coal, modern supercritical power plant\"\n                - \"Steel sheet, electric arc furnace, recycled scrap route\"\n                - \"Combined heat and power plant, natural gas, electricity and heat as reference flows\"\n              best_practices:\n                - \"Match the single-output reference flow name exactly.\"\n                - \"For multiple reference flows, list them by decreasing quantitative relevance.\"\n                - \"Cross-check terminology against existing datasets to support searchability.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                遵循 ILCD 规则20：基础名称需与参考流命名结构保持一致。\n                - 单一参考流：直接沿用参考流的技术名称作为流程名称。\n                - 多功能数据集：以技术或装置描述开头，用逗号串联每个参考流名称。\n                - 地理位置、时间等信息不要写入基础名称，在对应元数据字段中填写。\n              content_requirements:\n                - \"使用行业通用的技术术语，必要时先写全称再补充常用缩写（例如 Polypropylene, PP）。\"\n                - \"同一字段内部使用逗号分隔描述，避免使用分号或括号。\"\n                - \"多参考流数据集需在名称中逐一覆盖所有参考流。\"\n                - \"名称应便于界面展示，建议控制在200个字符以内。\"\n              examples:\n                - \"电力生产，燃煤，现代超临界机组\"\n                - \"钢板，电弧炉，再生废钢路线\"\n                - \"天然气联合热电机组，电力与热量为参考流\"\n              best_practices:\n                - \"单产出数据集的名称需与参考流名称完全一致。\"\n                - \"多参考流时按重要性排序，保持跨数据集表述一致。\"\n                - \"发布前与现有数据集对比，避免重复或冲突命名。\"\n\n        treatmentStandardsRoutes:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                Follow ILCD Rule 14: capture qualitative technical qualifiers separated by commas.\n                - Combine treatment received, standards fulfilled, product quality, use information, and route descriptors as needed.\n                - Use concise technical terms; avoid generic marketing language.\n                - Order entries from most intrinsic (treatment) to contextual qualifiers (use information).\n              content_requirements:\n                - \"Name surface or material treatments (e.g., polished, sterilised, chromium plated).\"\n                - \"Reference applicable standards or grades (e.g., EN 10202 prime quality, GB/T 13296).\"\n                - \"Indicate product quality or performance attributes (e.g., UV-resistant, flame-retardant).\"\n                - \"Document intended use qualifiers when relevant (e.g., for wafer production, indoor use).\"\n                - \"Identify production routes or feedstock types (e.g., steam cracking route, secondary material).\"\n              examples:\n                - \"Chromium plated, EN 10202 prime quality, indoor use\"\n                - \"Sterilised, ISO 13485 compliant, medical device grade\"\n                - \"Steam cracking route, bottle grade, primary feedstock\"\n              best_practices:\n                - \"Stick to industry-recognised terminology and spell out uncommon abbreviations.\"\n                - \"Group related qualifiers and keep each to two or three words for readability.\"\n                - \"Cross-reference standards and routes with authoritative documentation.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                遵循 ILCD 规则14：使用逗号串联处理方式、标准、质量等级等技术限定词。\n                - 按需要组合处理方式、满足的标准、产品质量、用途信息和路线描述。\n                - 采用简洁专业术语，避免宣传性或模糊表述。\n                - 建议按“处理→标准→质量/用途→路线”顺序排列。\n              content_requirements:\n                - \"写明处理方式（如抛光、灭菌、铬镀层等）。\"\n                - \"引用适用的标准或等级（如 EN 10202 一级、GB/T 13296 等）。\"\n                - \"指出关键质量或性能属性（如 抗紫外、阻燃）。\"\n                - \"必要时补充用途限定（如 用于晶圆生产、室内使用）。\"\n                - \"标识生产路线或原料属性（如 蒸汽裂解路线、再生料）。\"\n              examples:\n                - \"铬镀层，EN 10202 一级，室内使用\"\n                - \"灭菌，符合 ISO 13485，医疗器械级\"\n                - \"蒸汽裂解路线，瓶级，原生原料\"\n              best_practices:\n                - \"优先采用行业通用术语并在首次出现时写出全称。\"\n                - \"将相关限定词集中表述，控制在两到三个词组之内。\"\n                - \"与标准文本或工艺文件核对，确保引用准确。\"\n\n        mixAndLocationTypes:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                Follow ILCD Rule 15: describe mix and location types using comma-separated qualifiers.\n                - State whether the dataset represents a production mix, consumption mix, or single technology.\n                - Indicate the delivery or availability point (e.g., at plant, to consumer).\n                - Use \"to\" when transport to a node is included; use \"at\" when it represents the point of handover.\n              content_requirements:\n                - \"Clarify production versus consumption mix status; omit if not applicable.\"\n                - \"Specify the commercial or logistical location type (e.g., at wholesale, at point-of-sale).\"\n                - \"Add other relevant availability descriptors (e.g., to waste incineration plant).\"\n                - \"Avoid confusing location type with intended use; reserve use-related qualifiers for treatmentStandardsRoutes.\"\n              examples:\n                - \"Production mix, at plant\"\n                - \"Consumption mix, to consumer\"\n                - \"Technology-specific, to wholesale\"\n                - \"Production mix, to waste incineration plant\"\n              best_practices:\n                - \"Align mix terminology with documented system boundaries.\"\n                - \"Keep qualifiers consistent across datasets representing the same market.\"\n                - \"Review transport assumptions to choose between \\\"at\\\" and \\\"to\\\" correctly.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                遵循 ILCD 规则15：用逗号标注混合类型与交付地点类型。\n                - 说明是否为生产混合、消费混合或特定技术数据。\n                - 明确交付或可用位置（如 产地交付、批发交付、终端消费者）。\n                - 涉及运输到某节点时使用“至”，表示交接点时使用“在”。\n              content_requirements:\n                - \"区分生产混合与消费混合；若不适用可省略。\"\n                - \"标注物流或商业节点（如 在批发、在零售点）。\"\n                - \"根据需要补充其他可得性描述（如 至焚烧厂）。\"\n                - \"避免与用途混淆，真正的用途限定应写在 treatmentStandardsRoutes 字段。\"\n              examples:\n                - \"生产混合，在工厂\"\n                - \"消费混合，至终端消费者\"\n                - \"特定技术，至批发商\"\n                - \"生产混合，至废物焚烧厂\"\n              best_practices:\n                - \"与系统边界描述保持一致。\"\n                - \"同一市场的可交付点描述应保持统一。\"\n                - \"核对运输假设，正确选择“在”或“至”。\"\n\n        functionalUnitFlowProperties:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                Follow ILCD Rule 16: document quantitative qualifying properties with explicit units and comma separation.\n                - Express constituent content or energy content per functional unit.\n                - Use percentage, concentration, or energy density formats that mirror measurement data.\n                - State the reference basis when it is not the default mass/mass relation.\n              content_requirements:\n                - \"Quantify key constituents or energy content (e.g., 24 % Fe, 9.6 MJ/kg net calorific value).\"\n                - \"Indicate the measurement basis explicitly when different from mass fraction (e.g., by volume, molar).\"\n                - \"Include multiple properties as separate comma-separated entries.\"\n                - \"Avoid duplicating information stored in dedicated property fields (e.g., CAS numbers).\"\n              examples:\n                - \"24 % Fe mass/mass\"\n                - \"9.6 MJ/kg net calorific value\"\n                - \"90.5 % methane by volume\"\n                - \"0.05 % sulfur mass/mass, 30 MJ/m3 lower heating value\"\n              best_practices:\n                - \"Use significant figures consistent with data quality statements.\"\n                - \"Adopt SI units or widely accepted industrial units.\"\n                - \"Cross-check values against reference flow documentation for consistency.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                遵循 ILCD 规则16：用逗号分隔定量属性，明确单位与计量基准。\n                - 表达关键组分含量或能量含量，并指明参考单位。\n                - 常用百分比、浓度或能量密度形式，与测量数据保持一致。\n                - 当基准不是质量分数时需额外说明（如 体积分数、摩尔分数）。\n              content_requirements:\n                - \"量化主要组分或能量（如 24 % Fe、9.6 MJ/kg 净热值）。\"\n                - \"若基准不同于质量分数，应明确写出（如 体积分数、摩尔）。\"\n                - \"多项属性分别列出并以逗号分隔。\"\n                - \"避免重复记录已在其他属性字段中的信息（如 CAS 号）。\"\n              examples:\n                - \"24 % Fe 质量分数\"\n                - \"9.6 MJ/kg 净热值\"\n                - \"90.5 % 甲烷 体积分数\"\n                - \"0.05 % 硫 质量分数，30 MJ/m3 低位发热量\"\n              best_practices:\n                - \"保持与数据质量声明一致的有效数字。\"\n                - \"优先使用 SI 单位或行业通行单位。\"\n                - \"与参考流文档核对，确保数值一致。\"\n\n      common:generalComment:\n        <rules>:\n          - language: \"en\"\n            structure: |\n              Recommended structure:\n              1. Process overview and purpose\n              2. System boundaries description\n              3. Key assumptions and limitations\n              4. Data quality considerations\n              5. Special remarks or warnings\n            writing_style:\n              - \"Write in third person\"\n              - \"Use present tense for current processes\"\n              - \"Be objective and factual\"\n            examples:\n              - |\n                This dataset represents electricity production from hard coal in a modern \n                supercritical power plant. The system boundary includes coal handling, \n                combustion, and flue gas treatment. Efficiency is assumed at 45% net. \n                Data quality is high, based on measured plant data from 2023.\n\n          - language: \"zh\"\n            structure: |\n              建议结构：\n              1. 流程概述和目的\n              2. 系统边界描述\n              3. 关键假设和限制\n              4. 数据质量考虑\n              5. 特别说明或警告\n            writing_style:\n              - \"使用第三人称\"\n              - \"当前流程使用现在时\"\n              - \"客观、事实性描述\"\n            examples:\n              - |\n                该数据集代表现代超临界电厂的燃煤发电。系统边界包括煤炭处理、\n                燃烧和烟气处理。净效率假定为45%。数据质量高，基于2023年\n                实测电厂数据。\n\n    time:\n      referenceYear:\n        <rules>:\n          - language: \"all\"\n            format: \"YYYY (4-digit year)\"\n            requirements:\n              - \"Must be 4-digit format\"\n              - \"Should represent the year of data validity\"\n              - \"For future scenarios, clearly indicate in comments\"\n            examples:\n              valid: [\"2023\", \"2020\", \"2025\"]\n              invalid: [\"23\", \"2020-2021\", \"2020s\"]\n\n      timeRepresentativenessDescription:\n        <rules>:\n          - language: \"en\"\n            content_guide:\n              - \"How well the reference year represents the technology\"\n              - \"Expected changes or trends\"\n              - \"Validity period justification\"\n            examples:\n              - |\n                Data represents average 2023 technology. The technology is mature with \n                minimal expected changes until 2030. Annual efficiency improvements of \n                0.5% may occur.\n\n          - language: \"zh\"\n            content_guide:\n              - \"参考年份对技术的代表性\"\n              - \"预期变化或趋势\"\n              - \"有效期说明\"\n            examples:\n              - |\n                数据代表2023年平均技术水平。技术成熟，预计2030年前变化较小。\n                年效率可能提升0.5%。\n\n    geography:\n      locationOfOperationSupplyOrProduction:\n        location:\n          <rules>:\n            - language: \"all\"\n              naming_convention: \"ISO 3166-1 alpha-2 codes\"\n              code_mapping:\n                countries:\n                  CN: \"China\"\n                  US: \"United States\"\n                  DE: \"Germany\"\n                regions:\n                  GLO: \"Global\"\n                  RER: \"Europe region\"\n                  RNA: \"North America region\"\n                  RAF: \"Africa region\"\n                  RAS: \"Asia region\"\n                  RLA: \"Latin America region\"\n                  ROW: \"Rest of World\"\n              subdivision_format: \"ISO 3166-2 (e.g., CN-GD for Guangdong)\"\n              examples:\n                - \"CN\"\n                - \"GLO\"\n                - \"CN-GD\"\n\n        descriptionOfRestrictions:\n          <rules>:\n            - language: \"en\"\n              content_requirements:\n                - \"Explain any geographic limitations\"\n                - \"Mention climate or regional factors\"\n                - \"Note infrastructure dependencies\"\n              examples:\n                - |\n                  Valid for temperate climate zones. Requires access to waterways for \n                  cooling. Grid connection assumes European standard voltage.\n\n            - language: \"zh\"\n              content_requirements:\n                - \"说明地理限制\"\n                - \"提及气候或区域因素\"\n                - \"说明基础设施依赖\"\n              examples:\n                - |\n                  适用于温带气候区。需要水路用于冷却。电网连接假定欧洲标准电压。\n\n    technology:\n      technologyDescriptionAndIncludedProcesses:\n        <rules>:\n          - language: \"en\"\n            structure:\n              - \"Technology type and generation\"\n              - \"Process steps included\"\n              - \"Auxiliary processes\"\n              - \"Excluded processes (cut-off)\"\n            writing_guidelines:\n              - \"Use technical but accessible language\"\n              - \"Define acronyms on first use\"\n              - \"List process steps sequentially\"\n            examples:\n              - |\n                Ultra-supercritical (USC) pulverized coal combustion technology, \n                600°C/620°C steam conditions. Includes: coal grinding, combustion, \n                steam generation, turbine operation, condensation. Auxiliary: \n                DeNOx (SCR), DeSOx (FGD), ESP for particulates. Excludes: \n                coal mining, ash disposal infrastructure.\n\n          - language: \"zh\"\n            structure:\n              - \"技术类型和代别\"\n              - \"包含的工艺步骤\"\n              - \"辅助过程\"\n              - \"排除的过程（截断）\"\n            writing_guidelines:\n              - \"使用专业但易懂的语言\"\n              - \"首次使用时定义缩略词\"\n              - \"按顺序列出工艺步骤\"\n            examples:\n              - |\n                超超临界(USC)煤粉燃烧技术，600°C/620°C蒸汽条件。包括：磨煤、\n                燃烧、蒸汽发生、汽轮机运行、冷凝。辅助：脱硝(SCR)、脱硫(FGD)、\n                静电除尘器。不包括：煤炭开采、灰渣处理基础设施。\n\n  modellingAndValidation:\n    LCIMethodAndAllocation:\n      typeOfDataSet:\n        <rules>:\n          - language: \"all\"\n            valid_values:\n              - \"Unit process, single operation\"\n              - \"Unit process, black box\"\n              - \"LCI result\"\n              - \"Partly terminated system\"\n            description: \"Defines the type and aggregation level of the process\"\n\n      LCIMethodPrinciple:\n        <rules>:\n          - language: \"all\"\n            valid_values:\n              - \"Attributional\"\n              - \"Consequential\"\n              - \"Not applicable\"\n            applicability: \"Required for LCI results\"\n\n      modellingConstants:\n        <rules>:\n          - language: \"all\"\n            format: \"key-value pairs\"\n            naming_convention:\n              - \"Use lowercase with underscores\"\n              - \"Include units in the name or separately\"\n            examples:\n              - \"efficiency: 0.45\"\n              - \"capacity_factor: 0.85\"\n              - \"lifetime_years: 30\"\n\n    dataSourcesTreatmentAndRepresentativeness:\n      dataCollectionPeriod:\n        <rules>:\n          - language: \"all\"\n            format: \"YYYY-MM to YYYY-MM or YYYY\"\n            alignment: \"Should align with referenceYear\"\n            examples:\n              - \"2023\"\n              - \"2023-01 to 2023-12\"\n              - \"2022-06 to 2023-05\"\n\n    validation:\n      review:\n        scope:\n          <rules>:\n            - language: \"all\"\n              valid_scopes:\n                - \"Raw data\"\n                - \"Unit process(es), single operation\"\n                - \"Unit process(es), black box\"\n                - \"LCI results or Partly terminated system\"\n                - \"LCIA results\"\n                - \"Life cycle inventory methods\"\n                - \"Goal and scope definition\"\n                - \"LCIA methods\"\n              requirement: \"At least one review recommended for published datasets\"\n\n  administrativeInformation:\n    dataEntryBy:\n      common:timeStamp:\n        <rules>:\n          - language: \"all\"\n            format: \"ISO 8601\"\n            pattern: \"YYYY-MM-DDTHH:MM:SS\"\n            examples:\n              - \"2024-01-15T10:30:00\"\n              - \"2023-12-31T23:59:59\"\n\n    publicationAndOwnership:\n      common:dataSetVersion:\n        <rules>:\n          - language: \"all\"\n            definition: |\n              Dataset version identifier using two fixed-width numeric groups and an optional three-digit development component, as allowed by the TIDAS Version schema.\n            format: \"NN.NN or NN.NN.NNN\"\n            content_requirements:\n              - \"Use leading zeros to keep fixed-width groups (e.g., 01.00 or 01.00.000).\"\n              - \"Increment the version whenever content changes; document major versus minor revisions.\"\n              - \"Keep the version in sync with release notes or repository tags.\"\n            validation:\n              - \"Reject values that do not match the two-group pattern with an optional three-digit third group.\"\n              - \"Ensure each new dataset version number is greater than the previous published version.\"\n            examples:\n              - \"01.00\"\n              - \"01.00.000\"\n              - \"01.01.000\"\n              - \"02.00.000\"\n\n      permanentDataSetURI:\n        <rules>:\n          - language: \"all\"\n            requirement: \"Optional but recommended for published datasets\"\n            format: \"Resolvable URI\"\n            examples:\n              - \"https://example.org/ilcd/processes/550e8400-e29b-41d4\"\n              - \"https://data.ecoinvent.org/process/abc-123-def\"\n\n  exchanges:\n    exchange:\n      referenceToFlowDataSet:\n        <rules>:\n          - language: \"all\"\n            naming_convention:\n              elementary_flows: \"Follow ILCD nomenclature\"\n              product_flows: \"Follow process name rules\"\n              waste_flows: \"Prefix with 'waste' or '废物'\"\n            validation: \"Must reference existing flow dataset UUID\"\n\n      meanAmount:\n        <rules>:\n          - language: \"all\"\n            data_type: \"Decimal number\"\n            requirement: \"Required unless resultingAmount is provided\"\n            sign_convention: \"Positive or negative depending on direction\"\n\n      dataSourceType:\n        <rules>:\n          - language: \"all\"\n            valid_values:\n              - \"Primary data\"\n              - \"Secondary data\"\n              - \"Calculated\"\n              - \"Unknown\"\n            requirement: \"Required for all exchanges\"\n            \n      location:\n        <rules>:\n          - language: \"all\"\n            consistency_rule: |\n              Should align with process location unless specifically different\n              (e.g., imported materials, exported products)\n"
+        "processes": "# Process Dataset Content Rules and Guidelines\n# 流程数据集内容规则与指南\n#\n# Rule Structure:\n# <rules>: [\n#   {\n#     language: \"en\" | \"zh\" | \"all\",\n#     examples: [...] (optional),\n#     ... other custom fields\n#   }\n# ]\n\nmetadata:\n  version: \"1.1.0\"\n  last_updated: \"2026-09-22\"\n  applies_to: \"ILCD/Tidas Process Dataset v1.1\"\n  ef_baseline: EF Data Guide 2.0 (2020), EF 3.1 addendum (November 2022), and EF eILCD modelling 2.1 (June 2020);\n    source-bound additions, not universal TIDAS gates.\n  ef_sources:\n    ef-data-guide-2.0:\n      title: Guide for EF compliant data sets, Version 2.0\n      authors: Simone Fazio, Luca Zampori, An De Schryver, Oliver Kusche, Lionel Thellier, Edward Diaconu\n      publisher: European Commission, Joint Research Centre; Publications Office of the European Union\n      year: 2020\n      identifier: JRC120340; EUR 30175 EN; doi:10.2760/537292\n      url: https://eplca.jrc.ec.europa.eu/permalink/Guide_EF_DATA.pdf\n      license: CC BY 4.0; https://creativecommons.org/licenses/by/4.0/\n      attribution: Adapted and condensed into field-oriented guidance by TIDAS; wording, organization and examples\n        are changed. No endorsement by the original authors is implied.\n    ef-3.1-addendum-2022:\n      title: Updates on Guide for EF compliant data sets (Version 2.0) to reflect the changes in the Environmental\n        Footprint 3.1 reference package\n      authors: Antonio Valente, Oliver Kusche, Fulvio Ardente\n      date: 2022-11\n      url: https://eplca.jrc.ec.europa.eu/permalink/EF_Data_Guide_EF3.1_addendum.pdf\n      use: Source of factual compliance-system updates; source text and tables are not reproduced.\n    ef-eilcd-modelling-2.1:\n      title: Modelling requirements on LCI models under the Environmental footprint for interoperable data exchange\n        via the eILCD format\n      authors: Luca Zampori, Marc Andree Wolf, Katarzyna Cenian, Rutger Schurgers, Ingo Meinshausen, Sebastian\n        Schulz, Lucia Valsasina, Gregor Wernet, Oliver Kusche, Lionel Thellier\n      version: \"2.1\"\n      date: 2020-06\n      url: https://eplca.jrc.ec.europa.eu/permalink/InterfacePaper_Modelling_eILCD.pdf\n      use: Source of factual modelling constraints; source text and figures are not reproduced.\n\n# Global rules\nglobal_rules:\n  multi_language_support:\n    <rules>:\n      - language: \"en\"\n        requirement: \"English version is mandatory for all multilingual fields\"\n        purpose: \"Ensures international accessibility\"\n      - language: \"zh\"\n        requirement: \"中文版本建议提供，特别是中国地区的数据\"\n        purpose: \"确保本地用户可理解性\"\n  ef_scope:\n    <rules>:\n      - language: all\n        id: ef.scope\n        normative_level: informative\n        applicability: Readers and consumers applying the EF-specific methodology entries.\n        source_refs:\n          - source: ef-data-guide-2.0\n            section: Introduction; 5.1; 6\n          - source: ef-3.1-addendum-2022\n            section: Introduction\n          - source: ef-eilcd-modelling-2.1\n            section: \"1\"\n        requirement: Apply this source-bound EF guidance only when assessing the stated EF compliance scope; retain\n          ordinary TIDAS requirements outside that scope.\n        content_requirements:\n          - This baseline is the 2020 Data Guide plus its November 2022 EF 3.1 addendum and the June 2020\n            eILCD modelling paper. It is not a claim that these documents exhaust every current PEF/OEF or\n            sector requirement.\n          - ILCD entry-level requirements, the applicable PEF/OEF method and PEFCR/OEFSR remain additional\n            source dependencies. Record their versions and resolve a conflict against the applicable\n            authoritative source before claiming compliance.\n          - The 2022 addendum replaces Guide sections 2 and 5.2.15 and updates supporting-dataset\n            declarations. Its reference to section 5.4.1 describes supporting datasets, covered under section\n            5.4.2 in the Guide.\n          - The elementary-flow duplication permission in the Guide does not override the stricter eILCD\n            exchange requirement when that model-exchange scope applies.\n          - These are content requirements, not execution phases, severity, write permission, automatic repair\n            instructions, or a compliance certificate.\n  ef_reference_package:\n    <rules>:\n      - language: all\n        id: ef.reference-package\n        normative_level: shall\n        applicability: EF datasets and their supporting package, including level-1 subprocesses.\n        source_refs:\n          - source: ef-3.1-addendum-2022\n            section: 2; 5.2.15\n          - source: ef-data-guide-2.0\n            section: 4; 5.4.2\n        requirement: Use the EF reference package applicable to the declared method/category-rule generation, and keep\n          the central dataset and all its subprocesses compatible with that package.\n        content_requirements:\n          - The addendum identifies EF 3.1 for new transition-phase PEFCRs and their studies; older category\n            rules can require their corresponding older package. Record the exact package instead of silently\n            mixing releases.\n          - Deliver the referenced flows, flow properties, unit groups, sources, contacts and LCIA methods\n            needed by the ILCD/eILCD package, including compliance-system sources.\n          - Use the official reference nomenclature and characterization methods. A conversion does not\n            authorize changing the EF characterization factors.\n  ef_eilcd_connections:\n    <rules>:\n      - language: all\n        id: ef.eilcd-connections\n        normative_level: shall\n        applicability: EF eILCD lifecycle models and their linked processes.\n        source_refs:\n          - source: ef-eilcd-modelling-2.1\n            section: 2.3; Figure 1; footnote 7\n        requirement: Represent eILCD connections using the permitted Figure 1 option C; do not use one exchange for\n          multiple connections.\n        content_requirements:\n          - A connection between two newly created EF datasets uses the same product flow at both ends.\n          - For existing-to-new connections reuse the existing product flow in the new dataset; different-UUID\n            connections are limited to unavoidable existing-dataset cases. Intermediate/conversion processes\n            are an available remedy.\n          - Keep the reference exchange of the reference process unlinked as specified in footnote 7 to avoid\n            double linking.\n          - Do not create country-specific flows without checking the supply identities and connections. The\n            lifecycle-model file owns these connections; this Process methodology records the cross-file\n            requirement.\n  ef_eilcd_model:\n    <rules>:\n      - language: all\n        id: ef.eilcd-model\n        normative_level: shall\n        applicability: EF models exchanged in eILCD format.\n        source_refs:\n          - source: ef-eilcd-modelling-2.1\n            section: 2.2-2.4\n        requirement: Identify the reference process explicitly and scale the model to its reference-flow quantity and\n          unit.\n        content_requirements:\n          - Do not reuse a newly created dataset multiple times with different parameter values in an eILCD\n            PEF model; create an appropriate new dataset. The paper expressly exempts level-1 disaggregated\n            datasets from this provision.\n          - Life-cycle-stage declarations are optional; if present, use the cited default stages or the\n            applicable PEFCR/OEFSR convention, documenting any justified subdivisions/additions.\n          - Avoid unnecessarily complex multi-scenario parameter models as recommended by the paper. Model\n            declarations and scenario selection are lifecycle-model concerns, not new Process JSON fields.\n  ef_eilcd_documentation:\n    <rules>:\n      - language: all\n        id: ef.eilcd-documentation\n        normative_level: shall\n        applicability: EF models exchanged in eILCD format.\n        source_refs:\n          - source: ef-eilcd-modelling-2.1\n            section: \"2.5\"\n        requirement: Place whole-model metadata on the reference process and reference the aggregated result process.\n        content_requirements:\n          - Copy the aggregated-version metadata to the corresponding reference-process fields; include that\n            aggregated dataset in the processes directory.\n          - For complex representative-product models describe at least the represented product/process in the\n            reference-process metadata and explain detailed assumptions in the study report.\n          - Report all EF impact-category results on the reference process and ensure they match the\n            aggregated result dataset.\n          - referenceToReferenceProcess and referenceToResultingProcess belong to the lifecycle-model\n            representation; their absence from the Process schema is not permission to drop the requirement.\n  ef_provider_obligations:\n    <rules>:\n      - language: all\n        id: ef.provider-context\n        normative_level: informative\n        applicability: EF data providers and node/data-stock operators under the stated source baseline.\n        source_refs:\n          - source: ef-data-guide-2.0\n            section: 3.2-3.6; 7; 8.3\n        requirement: Preserve the source requirements for data-stock documentation, update communication and review\n          availability as provider obligations.\n        content_requirements:\n          - Maintain the applicable overall/core change logs and predecessor availability, with dates and\n            affected identities on the provider landing page.\n          - Section 3.4 describes user notification, temporary removal from download, restricted corrected\n            upload and EF-helpdesk coordination; these are transition-phase provider procedures, not actions a\n            content validator may execute.\n          - Section 7 requires stock names prefixed with the EF reference-package version and a consistent\n            flow list within each stock, even when EF and ILCD compliance levels coexist.\n          - Explain stock structure on the landing page, link the EULA, provide a contact address and obtain\n            the required EULA agreement. Create a source dataset with description and hyperlink for each new\n            node and stock; provider responsibility for quality/review remains.\n          - Confirm current node, registry and communication procedures before operational use.\n          - Make the EF review report available with the dataset and visible in the registry as required by\n            section 8.3. This methodology grants no authority to publish, notify users or change access.\n\nprocessDataSet:\n  processInformation:\n    dataSetInformation:\n      name:\n        baseName:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                Follow ILCD Rule 20: align the process base name with the reference flow naming structure.\n                - Single reference flow: reuse the reference flow's technical name as the process name.\n                - Multiple reference flows: start with the technology or plant descriptor and append each reference flow name separated by commas.\n                - Exclude geographical or temporal qualifiers from the base name; capture them in the dedicated metadata fields.\n              content_requirements:\n                - \"Use technical terminology as applied in the supplying industry or towards customers.\"\n                - \"Separate descriptors within the base name using commas and avoid semicolons or brackets.\"\n                - \"Spell out terms before adding widely recognised abbreviations (e.g., \\\"Polypropylene,\n                  PP\\\").\"\n                - \"Cover every reference flow explicitly when the dataset is multi-functional.\"\n                - \"Keep the wording concise enough for interface display (target 200 characters or fewer).\"\n              examples:\n                - \"Electricity from hard coal, modern supercritical power plant\"\n                - \"Steel sheet, electric arc furnace, recycled scrap route\"\n                - \"Combined heat and power plant, natural gas, electricity and heat as reference flows\"\n              best_practices:\n                - \"Match the single-output reference flow name exactly.\"\n                - \"For multiple reference flows, list them by decreasing quantitative relevance.\"\n                - \"Cross-check terminology against existing datasets to support searchability.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                遵循 ILCD 规则20：基础名称需与参考流命名结构保持一致。\n                - 单一参考流：直接沿用参考流的技术名称作为流程名称。\n                - 多功能数据集：以技术或装置描述开头，用逗号串联每个参考流名称。\n                - 地理位置、时间等信息不要写入基础名称，在对应元数据字段中填写。\n              content_requirements:\n                - \"使用行业通用的技术术语，必要时先写全称再补充常用缩写（例如 Polypropylene, PP）。\"\n                - \"同一字段内部使用逗号分隔描述，避免使用分号或括号。\"\n                - \"多参考流数据集需在名称中逐一覆盖所有参考流。\"\n                - \"名称应便于界面展示，建议控制在200个字符以内。\"\n              examples:\n                - \"电力生产，燃煤，现代超临界机组\"\n                - \"钢板，电弧炉，再生废钢路线\"\n                - \"天然气联合热电机组，电力与热量为参考流\"\n              best_practices:\n                - \"单产出数据集的名称需与参考流名称完全一致。\"\n                - \"多参考流时按重要性排序，保持跨数据集表述一致。\"\n                - \"发布前与现有数据集对比，避免重复或冲突命名。\"\n\n        treatmentStandardsRoutes:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                Follow ILCD Rule 14: capture qualitative technical qualifiers separated by commas.\n                - Combine treatment received, standards fulfilled, product quality, use information, and route descriptors as needed.\n                - Use concise technical terms; avoid generic marketing language.\n                - Order entries from most intrinsic (treatment) to contextual qualifiers (use information).\n              content_requirements:\n                - \"Name surface or material treatments (e.g., polished, sterilised, chromium plated).\"\n                - \"Reference applicable standards or grades (e.g., EN 10202 prime quality, GB/T 13296).\"\n                - \"Indicate product quality or performance attributes (e.g., UV-resistant, flame-retardant).\"\n                - \"Document intended use qualifiers when relevant (e.g., for wafer production, indoor use).\"\n                - \"Identify production routes or feedstock types (e.g., steam cracking route, secondary\n                  material).\"\n              examples:\n                - \"Chromium plated, EN 10202 prime quality, indoor use\"\n                - \"Sterilised, ISO 13485 compliant, medical device grade\"\n                - \"Steam cracking route, bottle grade, primary feedstock\"\n              best_practices:\n                - \"Stick to industry-recognised terminology and spell out uncommon abbreviations.\"\n                - \"Group related qualifiers and keep each to two or three words for readability.\"\n                - \"Cross-reference standards and routes with authoritative documentation.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                遵循 ILCD 规则14：使用逗号串联处理方式、标准、质量等级等技术限定词。\n                - 按需要组合处理方式、满足的标准、产品质量、用途信息和路线描述。\n                - 采用简洁专业术语，避免宣传性或模糊表述。\n                - 建议按“处理→标准→质量/用途→路线”顺序排列。\n              content_requirements:\n                - \"写明处理方式（如抛光、灭菌、铬镀层等）。\"\n                - \"引用适用的标准或等级（如 EN 10202 一级、GB/T 13296 等）。\"\n                - \"指出关键质量或性能属性（如 抗紫外、阻燃）。\"\n                - \"必要时补充用途限定（如 用于晶圆生产、室内使用）。\"\n                - \"标识生产路线或原料属性（如 蒸汽裂解路线、再生料）。\"\n              examples:\n                - \"铬镀层，EN 10202 一级，室内使用\"\n                - \"灭菌，符合 ISO 13485，医疗器械级\"\n                - \"蒸汽裂解路线，瓶级，原生原料\"\n              best_practices:\n                - \"优先采用行业通用术语并在首次出现时写出全称。\"\n                - \"将相关限定词集中表述，控制在两到三个词组之内。\"\n                - \"与标准文本或工艺文件核对，确保引用准确。\"\n\n        mixAndLocationTypes:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                Follow ILCD Rule 15: describe mix and location types using comma-separated qualifiers.\n                - State whether the dataset represents a production mix, consumption mix, or single technology.\n                - Indicate the delivery or availability point (e.g., at plant, to consumer).\n                - Use \"to\" when transport to a node is included; use \"at\" when it represents the point of handover.\n              content_requirements:\n                - \"Clarify production versus consumption mix status; omit if not applicable.\"\n                - \"Specify the commercial or logistical location type (e.g., at wholesale, at point-of-sale).\"\n                - \"Add other relevant availability descriptors (e.g., to waste incineration plant).\"\n                - \"Avoid confusing location type with intended use; reserve use-related qualifiers for\n                  treatmentStandardsRoutes.\"\n              examples:\n                - \"Production mix, at plant\"\n                - \"Consumption mix, to consumer\"\n                - \"Technology-specific, to wholesale\"\n                - \"Production mix, to waste incineration plant\"\n              best_practices:\n                - \"Align mix terminology with documented system boundaries.\"\n                - \"Keep qualifiers consistent across datasets representing the same market.\"\n                - \"Review transport assumptions to choose between \\\"at\\\" and \\\"to\\\" correctly.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                遵循 ILCD 规则15：用逗号标注混合类型与交付地点类型。\n                - 说明是否为生产混合、消费混合或特定技术数据。\n                - 明确交付或可用位置（如 产地交付、批发交付、终端消费者）。\n                - 涉及运输到某节点时使用“至”，表示交接点时使用“在”。\n              content_requirements:\n                - \"区分生产混合与消费混合；若不适用可省略。\"\n                - \"标注物流或商业节点（如 在批发、在零售点）。\"\n                - \"根据需要补充其他可得性描述（如 至焚烧厂）。\"\n                - \"避免与用途混淆，真正的用途限定应写在 treatmentStandardsRoutes 字段。\"\n              examples:\n                - \"生产混合，在工厂\"\n                - \"消费混合，至终端消费者\"\n                - \"特定技术，至批发商\"\n                - \"生产混合，至废物焚烧厂\"\n              best_practices:\n                - \"与系统边界描述保持一致。\"\n                - \"同一市场的可交付点描述应保持统一。\"\n                - \"核对运输假设，正确选择“在”或“至”。\"\n\n        functionalUnitFlowProperties:\n          <rules>:\n            - language: \"en\"\n              naming_convention: |\n                Follow ILCD Rule 16: document quantitative qualifying properties with explicit units and comma separation.\n                - Express constituent content or energy content per functional unit.\n                - Use percentage, concentration, or energy density formats that mirror measurement data.\n                - State the reference basis when it is not the default mass/mass relation.\n              content_requirements:\n                - \"Quantify key constituents or energy content (e.g., 24 % Fe, 9.6 MJ/kg net calorific value).\"\n                - \"Indicate the measurement basis explicitly when different from mass fraction (e.g., by\n                  volume, molar).\"\n                - \"Include multiple properties as separate comma-separated entries.\"\n                - \"Avoid duplicating information stored in dedicated property fields (e.g., CAS numbers).\"\n              examples:\n                - \"24 % Fe mass/mass\"\n                - \"9.6 MJ/kg net calorific value\"\n                - \"90.5 % methane by volume\"\n                - \"0.05 % sulfur mass/mass, 30 MJ/m3 lower heating value\"\n              best_practices:\n                - \"Use significant figures consistent with data quality statements.\"\n                - \"Adopt SI units or widely accepted industrial units.\"\n                - \"Cross-check values against reference flow documentation for consistency.\"\n\n            - language: \"zh\"\n              naming_convention: |\n                遵循 ILCD 规则16：用逗号分隔定量属性，明确单位与计量基准。\n                - 表达关键组分含量或能量含量，并指明参考单位。\n                - 常用百分比、浓度或能量密度形式，与测量数据保持一致。\n                - 当基准不是质量分数时需额外说明（如 体积分数、摩尔分数）。\n              content_requirements:\n                - \"量化主要组分或能量（如 24 % Fe、9.6 MJ/kg 净热值）。\"\n                - \"若基准不同于质量分数，应明确写出（如 体积分数、摩尔）。\"\n                - \"多项属性分别列出并以逗号分隔。\"\n                - \"避免重复记录已在其他属性字段中的信息（如 CAS 号）。\"\n              examples:\n                - \"24 % Fe 质量分数\"\n                - \"9.6 MJ/kg 净热值\"\n                - \"90.5 % 甲烷 体积分数\"\n                - \"0.05 % 硫 质量分数，30 MJ/m3 低位发热量\"\n              best_practices:\n                - \"保持与数据质量声明一致的有效数字。\"\n                - \"优先使用 SI 单位或行业通行单位。\"\n                - \"与参考流文档核对，确保数值一致。\"\n\n      common:generalComment:\n        <rules>:\n          - language: \"en\"\n            structure: |\n              Recommended structure:\n              1. Process overview and purpose\n              2. System boundaries description\n              3. Key assumptions and limitations\n              4. Data quality considerations\n              5. Special remarks or warnings\n            writing_style:\n              - \"Write in third person\"\n              - \"Use present tense for current processes\"\n              - \"Be objective and factual\"\n            examples:\n              - |\n                This dataset represents electricity production from hard coal in a modern \n                supercritical power plant. The system boundary includes coal handling, \n                combustion, and flue gas treatment. Efficiency is assumed at 45% net. \n                Data quality is high, based on measured plant data from 2023.\n\n          - language: \"zh\"\n            structure: |\n              建议结构：\n              1. 流程概述和目的\n              2. 系统边界描述\n              3. 关键假设和限制\n              4. 数据质量考虑\n              5. 特别说明或警告\n            writing_style:\n              - \"使用第三人称\"\n              - \"当前流程使用现在时\"\n              - \"客观、事实性描述\"\n            examples:\n              - |\n                该数据集代表现代超临界电厂的燃煤发电。系统边界包括煤炭处理、\n                燃烧和烟气处理。净效率假定为45%。数据质量高，基于2023年\n                实测电厂数据。\n          - language: all\n            id: ef.supporting-identification\n            normative_level: shall\n            applicability: Non-primary supporting sub-datasets used only within their corresponding EF level-1 model.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.4.2\n            requirement: Identify the central process by exact name and UUID and direct users there for full model\n              documentation.\n            content_requirements:\n              - Use the prescribed supporting-subprocess general-comment wording in section 5.4.2 item 4 with\n                the central process name and UUID substituted.\n              - Supporting processes must not be used independently or with another central dataset; they do\n                not require a separate DQR or review.\n              - Where no clear classification exists, the Guide recommends Services / Other services.\n      <rules>:\n        - language: all\n          id: ef.identity\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: \"5.2\"\n          requirement: Provide a UUID and the structured ILCD process name with its applicable technical, treatment,\n            mix/location-type and quantitative qualifiers.\n      referenceToExternalDocumentation:\n        <rules>:\n          - language: all\n            id: ef.study-report\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets. Applies when a\n              PEF study exists.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.1\n            requirement: Reference the PEF study report when a PEF study has been performed.\n      complementingProcesses:\n        <rules>:\n          - language: all\n            id: ef.level1-complementing-processes\n            normative_level: shall\n            applicability: EF level-1 central datasets; the prohibition on complementingProcesses applies to aggregated\n              datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.4.1; footnote 27\n            requirement: Reference all and only the central dataset subprocesses, with their UUIDs and exact names.\n            content_requirements:\n              - Leave complementingProcesses unfilled for aggregated datasets; it is not a general list of\n                related datasets.\n\n    time:\n      referenceYear:\n        <rules>:\n          - language: \"all\"\n            format: \"YYYY (4-digit year)\"\n            requirements:\n              - \"Must be 4-digit format\"\n              - \"Should represent the year of data validity\"\n              - \"For future scenarios, clearly indicate in comments\"\n            examples:\n              valid: [ \"2023\", \"2020\", \"2025\" ]\n              invalid: [ \"23\", \"2020-2021\", \"2020s\" ]\n\n      timeRepresentativenessDescription:\n        <rules>:\n          - language: \"en\"\n            content_guide:\n              - \"How well the reference year represents the technology\"\n              - \"Expected changes or trends\"\n              - \"Validity period justification\"\n            examples:\n              - |\n                Data represents average 2023 technology. The technology is mature with \n                minimal expected changes until 2030. Annual efficiency improvements of \n                0.5% may occur.\n\n          - language: \"zh\"\n            content_guide:\n              - \"参考年份对技术的代表性\"\n              - \"预期变化或趋势\"\n              - \"有效期说明\"\n            examples:\n              - |\n                数据代表2023年平均技术水平。技术成熟，预计2030年前变化较小。\n                年效率可能提升0.5%。\n      common:referenceYear:\n        <rules>:\n          - language: all\n            id: ef.reference-year\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.4\n            requirement: State the validity start year, or the environmentally representative year for mixed-year data,\n              with the validity period and justification.\n            content_requirements:\n              - Do not advance the reference year merely because the EF reference package changed or an update\n                left the LCI content unchanged.\n\n    geography:\n      locationOfOperationSupplyOrProduction:\n        location:\n          <rules>:\n            - language: \"all\"\n              naming_convention: \"ISO 3166-1 alpha-2 codes\"\n              code_mapping:\n                countries:\n                  CN: \"China\"\n                  US: \"United States\"\n                  DE: \"Germany\"\n                regions:\n                  GLO: \"Global\"\n                  RER: \"Europe region\"\n                  RNA: \"North America region\"\n                  RAF: \"Africa region\"\n                  RAS: \"Asia region\"\n                  RLA: \"Latin America region\"\n                  ROW: \"Rest of World\"\n              subdivision_format: \"ISO 3166-2 (e.g., CN-GD for Guangdong)\"\n              examples:\n                - \"CN\"\n                - \"GLO\"\n                - \"CN-GD\"\n\n        descriptionOfRestrictions:\n          <rules>:\n            - language: \"en\"\n              content_requirements:\n                - \"Explain any geographic limitations\"\n                - \"Mention climate or regional factors\"\n                - \"Note infrastructure dependencies\"\n              examples:\n                - |\n                  Valid for temperate climate zones. Requires access to waterways for \n                  cooling. Grid connection assumes European standard voltage.\n\n            - language: \"zh\"\n              content_requirements:\n                - \"说明地理限制\"\n                - \"提及气候或区域因素\"\n                - \"说明基础设施依赖\"\n              examples:\n                - |\n                  适用于温带气候区。需要水路用于冷却。电网连接假定欧洲标准电压。\n        \"@location\":\n          <rules>:\n            - language: all\n              id: ef.geography\n              normative_level: shall\n              applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n              source_refs:\n                - source: ef-data-guide-2.0\n                  section: 5.2.3\n              requirement: Use the Guide designation EU+EFTA+UK for its complete-European coverage and the two-letter ISO\n                country code for individual countries.\n              content_requirements:\n                - The Guide also identifies PT-MA, ES-CA, BQ-SE and BQ-SB. Verify representability in the\n                  target location vocabulary; do not silently substitute a different geography.\n\n    technology:\n      technologyDescriptionAndIncludedProcesses:\n        <rules>:\n          - language: \"en\"\n            structure:\n              - \"Technology type and generation\"\n              - \"Process steps included\"\n              - \"Auxiliary processes\"\n              - \"Excluded processes (cut-off)\"\n            writing_guidelines:\n              - \"Use technical but accessible language\"\n              - \"Define acronyms on first use\"\n              - \"List process steps sequentially\"\n            examples:\n              - |\n                Ultra-supercritical (USC) pulverized coal combustion technology, \n                600°C/620°C steam conditions. Includes: coal grinding, combustion, \n                steam generation, turbine operation, condensation. Auxiliary: \n                DeNOx (SCR), DeSOx (FGD), ESP for particulates. Excludes: \n                coal mining, ash disposal infrastructure.\n\n          - language: \"zh\"\n            structure:\n              - \"技术类型和代别\"\n              - \"包含的工艺步骤\"\n              - \"辅助过程\"\n              - \"排除的过程（截断）\"\n            writing_guidelines:\n              - \"使用专业但易懂的语言\"\n              - \"首次使用时定义缩略词\"\n              - \"按顺序列出工艺步骤\"\n            examples:\n              - |\n                超超临界(USC)煤粉燃烧技术，600°C/620°C蒸汽条件。包括：磨煤、\n                燃烧、蒸汽发生、汽轮机运行、冷凝。辅助：脱硝(SCR)、脱硫(FGD)、\n                静电除尘器。不包括：煤炭开采、灰渣处理基础设施。\n      referenceToTechnologyFlowDiagrammOrPicture:\n        <rules>:\n          - language: all\n            id: ef.system-diagram\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2; 5.4.1\n            requirement: Reference a source containing the system-boundary diagram and relevant subprocesses.\n            content_requirements:\n              - For a level-1 central dataset, add a complete model graph showing all subprocesses, physical\n                connections, directions and included/excluded boundaries; retain the activity diagram as well.\n      referenceToIncludedProcesses:\n        <rules>:\n          - language: all\n            id: ef.aggregated-included-processes\n            normative_level: may\n            applicability: Aggregated EF LCI-result datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: \"5.3\"\n            requirement: An aggregated dataset may reference included subprocesses when these also exist as separate\n              datasets.\n      <rules>:\n        - language: all\n          id: ef.level1-structure\n          normative_level: shall\n          applicability: EF-compliant level-1 partly disaggregated central datasets.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: \"4\"\n          requirement: Preserve the minimum level-1 decomposition and one defined reference exchange.\n          content_requirements:\n            - Separate energy subprocesses per energy dataset, including fuel conversion and direct emissions\n              where relevant.\n            - Separate incoming transport per transported material/component and transport dataset; represent\n              transported mass and distance as separate central-process parameters.\n            - Represent avoided-product systems on the output side, retain the original datasets and use the\n              described sign-inverting modelling process where system expansion requires it.\n            - Separate main material inputs so virgin/recycled input and CFF R1 can be adapted; aggregate the\n              remaining background processes into an input subprocess.\n            - Provide a subprocess for foreground direct emissions and resource inputs; allow distinct\n              co-products while selecting one reference exchange.\n    quantitativeReference:\n      <rules>:\n        - language: all\n          id: ef.reference-flow\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: 4; 5.2; 6\n          requirement: Identify exactly one reference exchange for the EF process; it may be an input or an output and\n            must exist in the exchange list.\n          content_requirements:\n            - Use referenceToReferenceFlow to identify the exchange by its internal ID, not by the referenced\n              flow UUID.\n            - Document the functional unit when applicable. Multiple distinct co-products do not establish\n              multiple EF reference exchanges.\n          examples:\n            positive:\n              - One reference input in a treatment dataset; several co-products with one reference output.\n            negative:\n              - Two reference exchange IDs or a reference ID absent from the exchange list.\n    mathematicalRelations:\n      variableParameter:\n        comment:\n          <rules>:\n            - language: all\n              id: ef.parameter-defaults\n              normative_level: shall\n              applicability: EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to\n                parameterized datasets.\n              source_refs:\n                - source: ef-data-guide-2.0\n                  section: 5.2.5\n              requirement: Document every parameter default in its comment, units and defaults information.\n        <rules>:\n          - language: all\n            id: ef.eilcd-parameters\n            normative_level: shall\n            applicability: Processes participating in EF models exchanged in eILCD format.\n            source_refs:\n              - source: ef-eilcd-modelling-2.1\n                section: \"2.1\"\n            requirement: Use process-local parameters with the eILCD name and formula restrictions.\n            content_requirements:\n              - A parameter name starts with a letter, is at most 15 characters, and otherwise uses only\n                letters, digits, underscores or hyphens.\n              - A formula is at most 255 characters. Permitted operators are +, -, *, /, ^, >, <, >=, <= and\n                =; permitted functions are IF, POW and AND/OR/NOT with parentheses.\n              - References may target other variables/formulas in this process but must not form cycles or\n                cause division by zero. References to parameters outside this process are prohibited;\n                lifecycle-model parameter settings are a separate model capability.\n            examples:\n              positive:\n                - yield_1 refers to an acyclic formula in the same process.\n              negative:\n                - A process formula reads a global parameter or participates in a circular dependency.\n\n  modellingAndValidation:\n    LCIMethodAndAllocation:\n      typeOfDataSet:\n        <rules>:\n          - language: \"all\"\n            valid_values:\n              - \"Unit process, single operation\"\n              - \"Unit process, black box\"\n              - \"LCI result\"\n              - \"Partly terminated system\"\n            description: \"Defines the type and aggregation level of the process\"\n          - language: all\n            id: ef.dataset-type\n            normative_level: shall\n            applicability: EF aggregated, partly disaggregated, supporting and avoided-product-system datasets, according\n              to their role.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 1; 5.2.2; 5.4.1; 5.4.2\n            requirement: Use LCI result for an aggregated EF dataset and Partly terminated system for a partly\n              disaggregated central dataset.\n            content_requirements:\n              - Use Unit process, single operation for a non-primary supporting sub-dataset. Identify an\n                avoided-product system as required for that modelling role.\n              - Preserve the source distinction if a required value cannot be represented by the current\n                target schema; report the representation gap rather than relabel it.\n\n      LCIMethodPrinciple:\n        <rules>:\n          - language: \"all\"\n            valid_values:\n              - \"Attributional\"\n              - \"Consequential\"\n              - \"Not applicable\"\n            applicability: \"Required for LCI results\"\n\n      modellingConstants:\n        <rules>:\n          - language: \"all\"\n            format: \"key-value pairs\"\n            naming_convention:\n              - \"Use lowercase with underscores\"\n              - \"Include units in the name or separately\"\n            examples:\n              - \"efficiency: 0.45\"\n              - \"capacity_factor: 0.85\"\n              - \"lifetime_years: 30\"\n          - language: all\n            id: ef.modelling-constants\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.11\n            requirement: Explain at least the treatment of biogenic carbon, emission offsets and capital goods.\n            content_requirements:\n              - \"This documentation duty does not permit offsets: the EF modelling requirement prohibits their\n                inclusion.\"\n      <rules>:\n        - language: all\n          id: ef.method-and-allocation\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: 5.2; 5.2.8; 6\n          requirement: Document LCI method principles and approaches, their deviations, and foreground and background\n            allocation separately.\n          content_requirements:\n            - Resolve multifunctionality through subdivision or system expansion first, then an underlying\n              physical relationship, then another justified relationship.\n            - Apply the agricultural-specific rules where relevant; do not infer a method solely from a\n              dataset type or label.\n        - language: all\n          id: ef.electricity\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: \"6\"\n          requirement: Use the country consumption electricity mix, or construct a representative EU/regional\n            consumption mix where the country mix is unavailable.\n          content_requirements:\n            - Sector-specific green-electricity information requires the applicable PEF/OEF\n              contractual-instrument criteria, documented and confirmed by the reviewer; model remaining\n              electricity with the residual mix.\n        - language: all\n          id: ef.offsets-and-time\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: 6; 6.3\n          requirement: Exclude emission offsets and model emissions/removals at the start of the assessment period\n            without time discounting.\n        - language: all\n          id: ef.carbon-modelling\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: \"6.3\"\n          requirement: Distinguish fossil, biogenic and land-use/change carbon with the appropriate elementary flows\n            from the applicable EF reference package.\n          content_requirements:\n            - Under the Guide fossil-carbonation simplification, omit the corresponding uptake/emission pair\n              from the PEF profile; additional information may use the specified fossil uptake flow.\n            - Where biogenic exchanges are modelled, use biogenic flows, mass allocation and the factory-gate\n              reference-flow carbon property.\n            - For native forests include the connected emissions, products/residues and soil emissions under\n              land-use/change and exclude their CO2 uptake.\n            - Inventory uptake and emission separately; follow the cited PAS 2050/2050-1 provisions for\n              land-use change.\n            - Treat aboveground non-native residues as biogenic; exclude soil-carbon accumulation through\n              improved management from the model, although it may be reported as metadata.\n        - language: all\n          id: ef.agriculture-allocation\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to\n            agricultural multifunctionality.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: \"6.2\"\n          requirement: Apply the cited LEAP agricultural multifunctionality guidance; document, justify and review\n            deviations.\n      deviationsFromLCIMethodApproaches:\n        <rules>:\n          - language: all\n            id: ef.cff\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.10; 6\n            requirement: Apply the CFF at least to the product materials, their waste treatments and the product\n              packaging, using the applicable PEF/OEF method.\n            content_requirements:\n              - Document where it applies, the substitution point, assumptions and nonzero parameter values in\n                the method-approach explanation.\n              - Omitted CFF parameters may mean zero only with the Guide-required general declaration on the\n                provider landing page. Absence alone is not evidence of zero.\n      referenceToLCAMethodDetails:\n        <rules>:\n          - language: all\n            id: ef.method-report\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.12\n            requirement: Reference the source dataset for the applicable current PEF method and, where relevant, the\n              applicable PEFCR.\n\n    dataSourcesTreatmentAndRepresentativeness:\n      dataCollectionPeriod:\n        <rules>:\n          - language: \"all\"\n            format: \"YYYY-MM to YYYY-MM or YYYY\"\n            alignment: \"Should align with referenceYear\"\n            examples:\n              - \"2023\"\n              - \"2023-01 to 2023-12\"\n              - \"2022-06 to 2023-05\"\n          - language: all\n            id: ef.agriculture-averaging\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to\n              agricultural cultivation.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: \"6.2\"\n            requirement: Use cultivation periods that represent seasonal variation and crop development.\n            content_requirements:\n              - \"Annual crops: at least three years; a justified unavailable-data/new-system exception may use\n                a shorter period, never below one year.\"\n              - \"Perennials: three years at a representative steady state; justify corrections for\n                disproportionate development stages.\"\n              - \"Crops harvested within a year: at least three recent consecutive production cycles. Account\n                for the Guide greenhouse and long-harvest-cycle distinctions.\"\n      dataCutOffAndCompletenessPrinciples:\n        <rules>:\n          - language: all\n            id: ef.boundary-and-cutoff\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2; 6\n            requirement: Include supply-chain processes, capital goods/infrastructure and their end of life unless\n              justified under the Guide cut-off rule.\n            content_requirements:\n              - The Guide permits up to 3.0% exclusion assessed against material, energy and environmental\n                significance; this is not an unconditional mass-only allowance.\n              - Document exclusions and deviations and obtain reviewer confirmation of their environmental\n                significance.\n              - Model included waste and other included activities through to elementary flows.\n      referenceToDataSource:\n        <rules>:\n          - language: all\n            id: ef.background-source-references\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.13\n            requirement: Reference each EF-compliant data stock and each gap-filling source through the corresponding\n              source dataset.\n      dataSelectionAndCombinationPrinciples:\n        <rules>:\n          - language: all\n            id: ef.background-selection\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: \"6.1\"\n            requirement: Use an available EF-compliant background dataset before an ILCD entry-level compliant\n              alternative.\n            content_requirements:\n              - Section 6.1 additionally specifies the designated Thinkstep-node aggregated datasets for\n                energy, transport, packaging and end-of-life under that baseline.\n              - The historical supplier/node requirement is source context, not a verified current endpoint or\n                permission to select an arbitrary replacement. Confirm the applicable supply requirement for\n                the declared EF generation; document unresolved availability.\n              - Commercial datasets are permitted subject to their access and license terms.\n          - language: all\n            id: ef.agriculture-specific-data\n            normative_level: should\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to\n              agricultural cultivation.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: \"6.2\"\n            requirement: Prefer crop- and country/region/climate-specific yield, water/land use, land-use change,\n              fertilizer and pesticide data per hectare and year.\n      useAdviceForDataSet:\n        <rules>:\n          - language: all\n            id: ef.use-advice\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: \"5.2\"\n            requirement: State methodological use advice where needed, including recycling boundaries and any use-phase\n              behaviour the user must model.\n          - language: all\n            id: ef.supporting-use-advice\n            normative_level: shall\n            applicability: Non-primary supporting sub-datasets used only within their corresponding EF level-1 model.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.4.2 item 3\n            requirement: Include the source-prescribed notice restricting the supporting dataset to its corresponding\n              level-1 partly disaggregated dataset.\n            content_requirements:\n              - Use the exact notice in section 5.4.2 item 3, which points to the General comment for the\n                central dataset name and UUID.\n\n    validation:\n      review:\n        scope:\n          <rules>:\n            - language: \"all\"\n              valid_scopes:\n                - \"Raw data\"\n                - \"Unit process(es), single operation\"\n                - \"Unit process(es), black box\"\n                - \"LCI results or Partly terminated system\"\n                - \"LCIA results\"\n                - \"Life cycle inventory methods\"\n                - \"Goal and scope definition\"\n                - \"LCIA methods\"\n              requirement: \"At least one review recommended for published datasets\"\n        common:dataQualityIndicators:\n          <rules>:\n            - language: all\n              id: ef.dqr\n              normative_level: shall\n              applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n              source_refs:\n                - source: ef-data-guide-2.0\n                  section: 5.2.17; Tables 2; Equation F.1\n              requirement: Calculate and document TeR, GR, TiR, P and overall DQR before aggregating subprocesses or\n                elementary flows.\n              content_requirements:\n                - For secondary datasets select the most relevant subprocesses/direct foreground elementary\n                  flows covering at least 80% of the weighted single score, then normalize contributions\n                  within that selected set.\n                - Assign each component rating using Table 2. For process contributions use activity-data\n                  TiR/P and secondary-dataset TeR/TiR/GR; average the two TiR ratings.\n                - Compute contribution-weighted criteria, then DQR = (TeR + GR + TiR + P) / 4. Each resulting\n                  criterion must not exceed 3.0, not merely the overall mean.\n                - Report text and one-decimal numeric values for the four criteria and overall DQR; set\n                  methodological appropriateness and completeness to Not applicable.\n                - The Guide notes pilot-phase tender exceptions with documented alternative approaches.\n                  Non-primary supporting sub-datasets do not require their own DQR.\n                - If numeric ratings cannot be represented by the current target indicator enum, retain them\n                  in review documentation and report the representation gap; do not replace them with a\n                  qualitative label and claim equivalent compliance.\n              examples:\n                positive:\n                  - Weighted criteria 2.0, 2.0, 2.0, 2.0 give DQR 2.0.\n                negative:\n                  - Criteria 4.0, 1.0, 1.0, 1.0 have mean 1.75 but fail the individual-criterion limit.\n        <rules>:\n          - language: all\n            id: ef.review-team\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 8.1-8.2; Tables 3-4\n            requirement: \"Use an eligible independent review team: at least two independent reviewers including at least\n              one external reviewer.\"\n            content_requirements:\n              - The Guide permits type 1 (at least three independent reviewers, including one external) or\n                type 2 (two independent reviewers, including one external). A single external reviewer is not\n                sufficient.\n              - The team collectively needs more than two years of environmental audit/review practice, more\n                than two reviews, more than two years of LCA practice, participation in more than four LCI\n                works, and more than two years of relevant sector experience.\n              - Verify independence/conflicts and identify reviewers and institutions, scope and method.\n                Supporting sub-datasets are exempt from separate review under section 5.4.2.\n        common:referenceToCompleteReviewReport:\n          <rules>:\n            - language: all\n              id: ef.review-report\n              normative_level: shall\n              applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n              source_refs:\n                - source: ef-data-guide-2.0\n                  section: 8.3; Table 5\n              requirement: Attach one agreed and signed EF review report and one agreed dataset DQR for the assessed\n                dataset, using the source review template.\n              content_requirements:\n                - Document dataset identity/locator, commissioner, reviewers, method/scope/date, compliance\n                  system and EF package version.\n                - Assess method/category requirements, allocation, CFF, LCIA consistency, nomenclature,\n                  documentation, ILCD validation, DQR and cut-off; resolve non-compliance before declaring EF\n                  compliance.\n                - Reference documents used in the review and include the reviewers compliance declaration.\n                  Review affected parts again after core-content changes.\n                - \"One EF report does not mean exactly one TIDAS review object: multiple review records may\n                  reference the same agreed report. General TIDAS optional-report semantics remain unchanged.\"\n              examples:\n                positive:\n                  - Several TIDAS review records reference one team-approved EF report.\n                negative:\n                  - A missing report is treated as proof of EF review solely because the general TIDAS schema\n                    accepts its absence.\n    completeness:\n      referenceToSupportedImpactAssessmentMethods:\n        <rules>:\n          - language: all\n            id: ef.supported-methods\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.14\n            requirement: Individually reference only the applied EF impact-category methods in the supported-methods\n              field.\n    complianceDeclarations:\n      <rules>:\n        - language: all\n          id: ef.compliance-declarations\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n          source_refs:\n            - source: ef-3.1-addendum-2022\n              section: 5.2.15 (replacement Table 1)\n          requirement: Declare the five required compliance systems, plus the applicable PEFCR when present, using the\n            source datasets and aspect values specified in the addendum.\n          content_requirements:\n            - \"Select one applicable 2021/2279 method source: Annex I PEF\n              779fb9ea-de54-4707-b7fc-6154661552b5; Annex II PEFCR 909ae358-42e0-4365-8767-22b92c3229f4; Annex\n              III OEF cbeab91f-74a4-4b5a-84dc-69915a22dc71; Annex IV OEFSR\n              cec792b1-58ce-4310-bc09-6612256633b8. Set all aspects Fully compliant only when substantiated.\"\n            - Where a PEFCR applies, reference its dedicated source and the required fully compliant aspects.\n            - \"ILCD entry-level d92a1a12-2545-49e2-a585-55c259997756: quality Not defined; other aspects Fully\n              compliant.\"\n            - \"ISO 14040 1ea48531-e397-4ca7-ac08-056e4fa11826: nomenclature, documentation and quality Not\n              defined; other aspects Fully compliant.\"\n            - \"ISO 14044 1adb438d-4a8b-4919-885e-0a66da3c0f2a: nomenclature, review and quality Not defined;\n              other aspects Fully compliant.\"\n            - \"Reference-package declaration: nomenclature Fully compliant and all other aspects Not defined.\n              EF 3.1 source UUID is 0eb2b770-2cb1-43cf-9fbc-215df36fe9f0; use the matching source for another\n              applicable package.\"\n            - Do not add unrelated compliance systems in this EF declaration set. Include the referenced\n              source datasets in the delivered package. A package nomenclature declaration alone is not\n              overall EF compliance.\n        - language: all\n          id: ef.supporting-compliance\n          normative_level: shall\n          applicability: Non-primary supporting sub-datasets used only within their corresponding EF level-1 model.\n          source_refs:\n            - source: ef-3.1-addendum-2022\n              section: Update to supporting-sub-dataset compliance table (page 5)\n          requirement: Use the special supporting-dataset declaration and the same EF reference-package declaration as\n            the central dataset.\n          content_requirements:\n            - \"Supporting source 2f8a3ebd-befc-4ea9-a6de-34bb6d426d2f: quality Not defined; all other aspects\n              Fully compliant.\"\n            - \"Reference-package source: nomenclature Fully compliant; all other aspects Not defined. For EF\n              3.1 use 0eb2b770-2cb1-43cf-9fbc-215df36fe9f0.\"\n            - Do not require the full five/six-system declaration set or an independent review/DQR for this\n              special supporting role.\n\n  administrativeInformation:\n    dataEntryBy:\n      common:timeStamp:\n        <rules>:\n          - language: \"all\"\n            format: \"ISO 8601\"\n            pattern: \"YYYY-MM-DDTHH:MM:SS\"\n            examples:\n              - \"2024-01-15T10:30:00\"\n              - \"2023-12-31T23:59:59\"\n\n    publicationAndOwnership:\n      common:dataSetVersion:\n        <rules>:\n          - language: \"all\"\n            definition: |\n              Dataset version identifier using two fixed-width numeric groups and an optional three-digit development component, as allowed by the TIDAS Version schema.\n            format: \"NN.NN or NN.NN.NNN\"\n            content_requirements:\n              - \"Use leading zeros to keep fixed-width groups (e.g., 01.00 or 01.00.000).\"\n              - \"Increment the version whenever content changes; document major versus minor revisions.\"\n              - \"Keep the version in sync with release notes or repository tags.\"\n            validation:\n              - \"Reject values that do not match the two-group pattern with an optional three-digit third\n                group.\"\n              - \"Ensure each new dataset version number is greater than the previous published version.\"\n            examples:\n              - \"01.00\"\n              - \"01.00.000\"\n              - \"01.01.000\"\n              - \"02.00.000\"\n          - language: all\n            id: ef.version\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: \"5.2\"\n            requirement: For this EF baseline use the three-part version NN.NN.NNN, separating major, minor/correction and\n              internal development increments.\n            content_requirements:\n              - This scoped EF convention does not remove the ordinary TIDAS allowance for NN.NN.\n            examples:\n              positive:\n                - 01.02.003 meets the EF representation convention.\n              negative:\n                - 01.02 is valid under the general TIDAS Version schema but does not satisfy this EF\n                  convention.\n\n      permanentDataSetURI:\n        <rules>:\n          - language: \"all\"\n            requirement: \"Optional but recommended for published datasets\"\n            format: \"Resolvable URI\"\n            examples:\n              - \"https://example.org/ilcd/processes/550e8400-e29b-41d4\"\n              - \"https://data.ecoinvent.org/process/abc-123-def\"\n      <rules>:\n        - language: all\n          id: ef.publication-metadata\n          normative_level: shall\n          applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: \"5.2\"\n          requirement: Declare the workflow/publication status and license type, and fill other administrative fields at\n            the ILCD-recommended level.\n          content_requirements:\n            - Use evidence of the actual dataset status; a formatting or conversion operation does not\n              establish publication or review completion.\n        - language: all\n          id: ef.update-lineage\n          normative_level: shall\n          applicability: Updates of EF-compliant datasets/data stocks covered by Guide section 3.\n          source_refs:\n            - source: ef-data-guide-2.0\n              section: 3.1-3.3; 3.5-3.6\n          requirement: Classify an update before assigning its identity and retain the original published dataset/version.\n          content_requirements:\n            - \"A1: provider changes to LCI, DQR, LCIA, process name or other core semantics require a new\n              UUID, updated review and a predecessor reference with UUID/version/URI; the Guide specifies an\n              Updated+year name prefix and normally the same data stock.\"\n            - \"A2: non-core provider corrections retain UUID, increment version and keep the original stock. A\n              dataset used correctly in a PEFCR/OEFSR but uploaded incorrectly follows A2.\"\n            - \"B: adaptation to a new EF reference package retains UUID/name, increments version, links the\n              predecessor, updates compliance and uses a new, package-consistent stock.\"\n            - Additional provider changes during package migration or a tender require their own A1/A2\n              classification; do not hide them in case B. These are published-EF update procedures, not\n              instructions to renumber ordinary working drafts.\n      common:dateOfLastRevision:\n        <rules>:\n          - language: all\n            id: ef.revision-date\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: \"5.2\"\n            requirement: Record and update the last revision using an ISO 8601 date-time with its time-zone information\n              when dataset content changes.\n    common:commissionerAndGoal:\n      common:intendedApplications:\n        <rules>:\n          - language: all\n            id: ef.intended-applications\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: \"5.2\"\n            requirement: Document the intended applications of the dataset.\n    <rules>:\n      - language: all\n        id: ef.supporting-administration\n        normative_level: shall\n        applicability: Non-primary supporting sub-datasets used only within their corresponding EF level-1 model.\n        source_refs:\n          - source: ef-data-guide-2.0\n            section: 5.4.2 items 1 and 6\n        requirement: Copy owner, commissioner, license type and access/use restrictions exactly from the central dataset.\n        content_requirements:\n          - For delivered supporting datasets the Guide specifies Data set finalised; entirely published as\n            the workflow/publication status. This requirement does not authorize publishing a working draft.\n\n  exchanges:\n    exchange:\n      referenceToFlowDataSet:\n        <rules>:\n          - language: \"all\"\n            naming_convention:\n              elementary_flows: \"Follow ILCD nomenclature\"\n              product_flows: \"Follow process name rules\"\n              waste_flows: \"Prefix with 'waste' or '废物'\"\n            validation: \"Must reference existing flow dataset UUID\"\n          - language: all\n            id: ef.reference-flow-content\n            normative_level: shall\n            applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.9; 6.3\n            requirement: Store nonzero factory-gate water and biogenic-carbon content as properties of the reference\n              product/waste flow, in the property reference units.\n            content_requirements:\n              - These quantities characterize the product, not the process. Retain native-forest origin\n                information and the required land-use-change carbon treatment.\n\n      meanAmount:\n        <rules>:\n          - language: \"all\"\n            data_type: \"Decimal number\"\n            requirement: \"Required unless resultingAmount is provided\"\n            sign_convention: \"Positive or negative depending on direction\"\n\n      dataSourceType:\n        <rules>:\n          - language: \"all\"\n            valid_values:\n              - \"Primary data\"\n              - \"Secondary data\"\n              - \"Calculated\"\n              - \"Unknown\"\n            requirement: \"Required for all exchanges\"\n\n      location:\n        <rules>:\n          - language: \"all\"\n            consistency_rule: |\n              Should align with process location unless specifically different\n              (e.g., imported materials, exported products)\n          - language: all\n            id: ef.regionalized-elementary-flows\n            normative_level: shall\n            applicability: EF elementary-flow modelling under the stated baseline.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 5.2.6; Annex 1\n            requirement: Use regionalized elementary flows within the source-defined locations and substances.\n            content_requirements:\n              - Land Use and Water Use permit all locations in the Guide; other categories are restricted to\n                the substances/countries in Annex 1.\n              - Resolve the authorized flow and location from the applicable reference package. The source\n                annex is a dependency, not a license to create arbitrary localized elementary-flow identities.\n      generalComment:\n        <rules>:\n          - language: all\n            id: ef.elementary-duplicates\n            normative_level: may\n            applicability: EF process datasets assessed under the Data Guide, outside the stricter eILCD model-exchange\n              requirement.\n            source_refs:\n              - source: ef-data-guide-2.0\n                section: 4; 5.2.7; 6\n            requirement: Duplicate elementary input/output flows are permitted by the Data Guide when each occurrence\n              documents its source in the exchange comment.\n            content_requirements:\n              - The Guide describes merging only matching UUID and location pairs, retaining source\n                comments/amount provenance; differing locations must not be silently merged.\n              - This permission does not apply to the stricter EF eILCD model-exchange scope.\n            examples:\n              positive:\n                - Documented elementary-flow occurrences from two sources in a Data-Guide dataset.\n              negative:\n                - Treating this permission as permission to repeat a product flow or as an exception to eILCD\n                  uniqueness.\n      <rules>:\n        - language: all\n          id: ef.eilcd-defined-amount\n          normative_level: shall\n          applicability: Processes participating in EF models exchanged in eILCD format.\n          source_refs:\n            - source: ef-eilcd-modelling-2.1\n              section: \"2.3\"\n          requirement: Provide a defined amount for every flow independently of accumulation, storage or time.\n    <rules>:\n      - language: all\n        id: ef.product-waste-uniqueness\n        normative_level: shall\n        applicability: EF process exchanges, including level-1 models.\n        source_refs:\n          - source: ef-data-guide-2.0\n            section: 4; 6\n        requirement: Do not repeat the same product or waste flow on the same input or output side; do not model using\n          the other-flows type.\n        content_requirements:\n          - Resolve flow identity from the referenced UUID, not the displayed name. Compare input and output\n            sides separately.\n          - Different amounts, locations, suppliers or reference versions do not alone establish a different\n            flow identity. Do not invent a new UUID or merge distinct supplies solely to silence a finding.\n        examples:\n          positive:\n            - One occurrence of flow A on input and one on output is not a duplicate on either side.\n          negative:\n            - Two input exchanges reference product flow A with amounts 0.3 and 0.7, even if their locations\n              differ.\n      - language: all\n        id: ef.eilcd-flow-uniqueness\n        normative_level: shall\n        applicability: Processes participating in EF models exchanged in eILCD format.\n        source_refs:\n          - source: ef-eilcd-modelling-2.1\n            section: \"2.3\"\n        requirement: In an EF eILCD process, each flow may occur only once on the input side and only once on the\n          output side.\n        content_requirements:\n          - This applies to elementary flows as well as product/waste flows. A location or supplier difference\n            alone does not satisfy it when the referenced flow identity is unchanged.\n          - Enforce identity per side, not uniqueness of whole exchange objects. Distinct exchange IDs or\n            amounts do not remove duplicate flow references.\n          - This rule does not imply that every country always needs a new flow; a remedy must preserve the\n            source meaning and compatible upstream/downstream connections.\n        examples:\n          positive:\n            - Distinct flow identities on the input side with consistent supplier output references.\n          negative:\n            - Two input occurrences of the same elementary flow, even though a non-eILCD EF dataset could\n              document them.\n      - language: all\n        id: ef.water-balance\n        normative_level: shall\n        applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n        source_refs:\n          - source: ef-data-guide-2.0\n            section: \"6\"\n        requirement: Distinguish water withdrawal, release and evaporation at foreground and background level and use\n          consistent regionalization for matching inputs and outputs.\n        content_requirements:\n          - Use country-level water flows; use an unspecified location where the country is not covered by the\n            reference package.\n          - For continental datasets use constituent-country shares; unspecified location is allowed for large\n            macro-regions such as RoW.\n          - Analyse balances per country and explain negative balances in the metadata; do not silently\n            discard or alter the exchanges.\n      - language: all\n        id: ef.agriculture-emissions\n        normative_level: shall\n        applicability: EF-compliant process datasets other than non-primary supporting sub-datasets. Applies to\n          agricultural modelling; later applicable method/category-rule provisions require separate source\n          verification.\n        source_refs:\n          - source: ef-data-guide-2.0\n            section: \"6.2\"\n        requirement: Model agricultural inputs and their emissions explicitly under the source-specific assumptions.\n        content_requirements:\n          - Model pesticides by active ingredient with the Guide default distribution 90% agricultural soil,\n            9% air, 1% water; more specific data need documentation and review.\n          - Differentiate fertilizer/manure types; cover NH3, direct/indirect N2O and lime/urea CO2 to air,\n            nitrate to water, and phosphate/phosphorus losses to water. Do not model nitrogen emissions to\n            soil.\n          - For nitrogen fertilizers the Guide recommends IPCC 2006 Tier 1 factors as specified in the\n            applicable PEF/OEF method; record the selected model.\n          - Represent heavy metals to soil/water with oxidation state for water flows and document the\n            selected crop-uptake treatment.\n          - Include rice methane per the cited IPCC calculation and drained-peat CO2 through\n            drainage/oxidation modelling.\n          - Include applicable seed, peat, lime, machinery and residue inputs/emissions unless within\n            justified cut-off. Include drying/storage, and field operations unless manual operation is\n            documented.\n  LCIAResults:\n    <rules>:\n      - language: all\n        id: ef.lcia-results\n        normative_level: shall\n        applicability: EF-compliant process datasets other than non-primary supporting sub-datasets.\n        source_refs:\n          - source: ef-data-guide-2.0\n            section: 5.2.16; 6; 8.3 Table 5\n          - source: ef-3.1-addendum-2022\n            section: Introduction\n        requirement: Supply characterized results for all 16 default EF impact categories using the applicable\n          official reference package.\n        content_requirements:\n          - Place results in the dedicated LCIA results section and serialize them in scientific notation in\n            ILCD XML; this is not a requirement to change the TIDAS numeric schema.\n          - The Guide requires Look@LCI calculation/verification with the official package; its review\n            template treats discrepancies above 1% as non-compliant.\n          - The section 6 footnote permits a different arrangement only when decided at the kick-off meeting;\n            retain that evidence rather than assume an exception.\n          - The EF 3.1 addendum changes factors and expected results but explicitly leaves section 5.2.16 in\n            force. Recompute results for the declared package; do not modify its factors.\n"
     }
 }