veraPDF test suite 6-6-2-3-2-t01-fail-b.pdf - mixture of catalog and page level metadata

[DietrichSeggern]

The file uses Extension Schemas on document/catalog and on page level. The actual metadata properties use a value type as defined on catalog level in a property defined on the page:

== Document/Catalog Extension Schema==
Schema: "cs:Custom schema"
Property: "CustomNumber" Type: TextValue
Type: "cp:ArticleNumber"
Field: "TextNumber" Type: Text

== Page Extension Schema==
Schema: "cs:Custom schema"
Property: "CProp" Type: ArticleNumber
Value Type: "cp:CValue
"Field: "CField" Type: Text

== Metadata used on page level==
cs:CProp/cp:TextNumber = "M17"

PDF/A-2 says: "Schemas present in metadata streams other than that of the Catalog may extend or replace some or all of a schema that was inherited from the Catalog’s stream."

As far as I see the case the use of the metadata properties is correct:
A property "cs:CProp" is used on a page where it is defined in an Extension Schema.
The property "cs:CProp" uses the type "ArticleNumber" which is defined on document level.

Dietrich

[DmitryRemezow]

The following tests were moved to the directory "Undefined" - #107 :

1. veraPDF test suite 6-6-2-3-2-t01-fail-b -> veraPDF test suite 6-6-2-3-2-t01-undefined-a
   The Catalog metadata defines custom value used in a custom property in the page metadata

2. veraPDF test suite 6-6-2-3-2-t01-pass-a -> veraPDF test suite 6-6-2-3-2-t01-undefined-b
   The Catalog metadata defines custom property, which is used in the page metadata

3. veraPDF test suite 6-6-2-3-2-t01-pass-a -> veraPDF test suite 6-6-2-3-2-t01-undefined-c
   The Catalog metadata defines custom property; The page metadata replaces the definition of this property