ValidatePdfE method

ValidatePdfE walks the open document looking for the PDF/E-1 file-format markers defined by ISO 24517-1:2008:

• An XMP metadata stream containing pdfe:ISO_PDFEVersion (§5 + §13.3).
• The matching pdfaExtension:schemas description for the pdfe namespace (XMP Specification 2004 extension-schema requirement, inherited via §13.1).
• A Document Information Dictionary entry /ISO_PDFEVersion with a literal-string value (§5 SHALL).
• Equality between the Info-dictionary value and the XMP value (§6.5 / §13.1).
• A trailer /ID array (§6.2).
• xmp:CreateDate and xmp:ModifyDate entries in XMP (inherited from ISO 19005-1 §6.7 via §13.1).

The result is a TPdfEValidationResult record:

• Conformance — the detected level: pec1 (PDF/E-1 identifier found and non-empty), pecNone (no PDF/E marker), or pecUnknown (parse failed or marker present but value missing).
• Issues — a TPdfEValidationIssues set containing zero or more values: pveiMissingXmpMetadata, pveiMissingPdfEIdentifier, pveiMissingExtensionSchema, pveiMissingInfoVersionEntry, pveiInfoVersionMismatch, pveiMissingTrailerId, pveiMissingXmpDates.
• IsCompliant — returns True when Conformance is a real PDF/E level and Issues is empty

ValidatePdfE is a read-only inspection — it does not modify the document and is safe to call repeatedly. Use it before pushing a PDF/E payload into an engineering archive to surface the file-format-level non-conformances this library can detect. For the common "is this PDF/E-1?" check that doesn't need the issue list, prefer the lighter-weight PdfEConformance property.

• ValidatePdfE is a file-format-level inspection — it does not enforce content-level PDF/E rules (font embedding completeness, ToUnicode CMaps, prohibited Reference XObjects / PostScript XObjects / TR / TR2 != Default / XFA forms / JavaScript actions, etc.). For a full validator pair this method with an external tool such as callas pdfaPilot or axesPDF.
• The validator reports pveiInfoVersionMismatch only when both Info /ISO_PDFEVersion and XMP pdfe:ISO_PDFEVersion are present and disagree. When the Info entry is absent the validator reports pveiMissingInfoVersionEntry only (no spurious mismatch).
• Calling ValidatePdfE on an inactive document returns a record with Conformance = pecUnknown and an empty Issues set.
• PDF/E-1 permits encryption (§6.3) provided trailer /ID strings remain direct objects. The validator therefore does NOT flag encryption as a non-conformance.