Closed bseddon closed 3 years ago
As for this error, the actual truth is that in my local copy, it does not appear.
This error was reported by some other user and fixed. Again, when I deploy the new version on the server it should not appear
Thanks again.
Because I'm new to the tool, I'm reading every word carefully and spotted this small typo in the Errors and warnings and Full report pages. In a few days it will seem familiar and I will not notice it so this note is to flag it while I still do.
Hi again, Thank you very much indeed for pointing this out. Fixed in my local copy.
Regards Juan Carlos
Hi
This post is about the second of two errors reported against the signature file attached. Again, I've only just begun using the checker tool so I not be interpreting the information supplied in the error messages correctly and I apologize if this is the case.
signature.zip
The error reported is shown in the screenshot. The Xml fragment from the signature that causes the error is:
The error reports that something is wrong after the <ObjectReference> (this is where the carat character appears in the output). However <ObjectReference> is the last used element and the only element that can appear after <ObjectReference> is the optional <CommitmentTypeQualifiers>.
The CommitmentTypeIndicationType is described in section 5.2.3 of ETSI 319 132-1 V1.1.1 (2016-04). This type is reproduced here. In it the CommitmentTypeQualifiersListType is defined with a minOccurs facet value of zero. This is reflected in the error message as <CommitmentTypeQualifiers> is shown with a '?' suffix. As a result, surely there should be no error.