InputLab

## Description Importing an XML document leads to a crash when the`ram:AttachmentBinaryObject` element contains whitespaces. ## To reproduce [test_binary64_invoice.txt](https://github.com/user-attachments/files/19535731/test_binary64_invoice.txt) ```java ZUGFeRDInvoiceImporter importer = new ZUGFeRDInvoiceImporter("test_binary64_invoice.txt"); ``` A concrete example of...

Valid XML report despite a failed validation

2

## Description As a result of validation, the KoSIT validator produces an XML report listing the outcome (valid/invalid status) and a list of errors. However, suppose the validation process fails...

Missing rules to enforce format attribute

1

## Description Schematron rules don’t enforce valid values for `//ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime/udt:DateTimeString` elements, since their `format` attribute is not validated. Therefore, documents with the following content are claimed to be valid. ```xml...

## Description Rule **BR-CO-19** doesn't enforce the date format for `StartDateTime` and `EndDateTime` elements in `//ram:ApplicableHeaderTradeSettlement/ram:BillingSpecifiedPeriod`. The rule **BR-29** can implicitly check that, but *only* if **both** `StartDateTime` and `EndDateTime`...

## Problem Description CII XSD schemas use two namespaces for `DateTimeString` elements: ``` xmlns:qdt="urn:un:unece:uncefact:data:standard:QualifiedDataType:100" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:100" ``` However, Schematron rules consider only the `udt` namespace (see rules `CII-DT-097`, `PEPPOL-EN16931-R110`, `PEPPOL-EN16931-R111`, `BR-29`,...