You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<Error>: a URI representing an error-tracking pixel; this element can occur multiple times. Errors are defined in section 2.4.2.3.
If I'm interpreting this correctly, this would seem to indicate that the maxOccurs should be "unbounded" in the xsd, not "1" -- similar to the <Impression> element.
Also, while not explicit in the spec, I would imagine, the <Error> inside the <Wrapper> would match:
There should be an <Error> element defined at the root element. See section "6 Human Readable VAST XML Schema" in the spec as well as "2.2.5.1 Summary of VAST Tracking Elements".
The text was updated successfully, but these errors were encountered:
Thank you for identifying this issue. We are not currently making edits to VAST 3 any longer as it is more in long term maintenance mode. I will leave this issue open for now, but I don't expect any changes to occur. If you identify similar issues with the VAST 4.x xsd files please open a new issue and we will review.
Issue 1
vast/vast3_draft.xsd
Line 80 in dac1274
Please clarify:
Vast 3 final spec (https://www.iab.com/wp-content/uploads/2015/06/VASTv3_0.pdf), section "2.2.4.2 Optional InLine Elements" states:
If I'm interpreting this correctly, this would seem to indicate that the maxOccurs should be "unbounded" in the xsd, not "1" -- similar to the <Impression> element.
Also, while not explicit in the spec, I would imagine, the <Error> inside the <Wrapper> would match:
vast/vast3_draft.xsd
Line 293 in dac1274
Issue 2
There should be an <Error> element defined at the root element. See section "6 Human Readable VAST XML Schema" in the spec as well as "2.2.5.1 Summary of VAST Tracking Elements".
The text was updated successfully, but these errors were encountered: