XRechnung validations on Basic Profile?

[kaikuchn]

Hey,

I've noticed some notice severity validation failures when checking a valid ZUGFeRD PDF with a Basic-Profile XML. Looking at the code I found this default case in validateXR:

mustangproject/validator/src/main/java/org/mustangproject/validator/XMLValidator.java

Lines 409 to 411 in 4a410bc

	} else { // This is the default check which is also run on en16931 files to generate notices.
	validateSchematron(xml, "/xslt/XR_30/XRechnung-CII-validation.xslt", 27, errorImpact);
	}

That is called from this code block:

mustangproject/validator/src/main/java/org/mustangproject/validator/XMLValidator.java

Lines 361 to 371 in 4a410bc

	if (context.getFormat().equals("CII")) {
	if (context.getGeneration().equals("2")
	&& (isBasic || isEN16931 || isXRechnung)) {
	//additionally validate against CEN
	validateSchematron(zfXML, "/xslt/en16931schematron/EN16931-CII-validation.xslt", 24, ESeverity.error);
	if (!disableNotices || XrechnungSeverity != ESeverity.notice) {
	validateXR(zfXML, XrechnungSeverity);
	}
	}
	}

Is there a reason why /xslt/XR_30/XRechnung-CII-validation.xslt is used to validate a Basic-Profile XML?

Best regards,
Kai

[jstaerk]

It only creates notices, the idea is that if you enter something en16931-ish you get notices "if you did that you would also get a valid XRechnung". You can switch off notices e.g. with --no-notices