Meaning
XML processing techniques ensure that electronic business documents have a single, consistent physical representation for digital signing. Removing variations in white space and character encoding allows the same document to produce the same hash on different systems. Applying ubl 2.1 canonicalization is a required step before generating or verifying a digital signature on an invoice.
Syntax Normalization
Transforming the raw data into a standard form prevents the signature from breaking due to minor formatting differences. The ubl 2.1 canonicalization process follows a set of rules that dictate how to handle namespace prefixes and empty elements. This ensures that the logical content remains identical even if the text file looks different.
Signature Stability
Reliable verification of a document depends on the hash value remaining constant as the file moves between different servers. Without ubl 2.1 canonicalization, a simple change in the line endings of a file would invalidate the cryptographic signature. This stability allows various tax authorities and trading partners to process the same electronic document without errors.
The mechanism provides the consistency needed for long term archiving of financial records.
Structural Consensus
Agreeing on a common way to represent data structures simplifies the integration of software from different vendors. Using ubl 2.1 canonicalization supports the interoperability of global supply chain systems. This consensus reduces the cost of building custom translators for every new business partner.