So this is not looking to see if initiatedContent is yes/no because there is no point of uncertainty here, so there is nothing for the initiatedContent to be discriminating.
Whether that's correct or not w.r.t the spec, I'm not sure. You may be correct that the spec requires checking for this case even when there is no point of uncertainty. ________________________________ From: Costello, Roger L. <[email protected]> Sent: Monday, September 9, 2019 7:50 AM To: [email protected] <[email protected]> Subject: Bug in Daffodil? No error with dfdl:initiatedContent="yes" and dfdl:initiator="%ES;" The specification says this: If the ES entity or the WSP* entity appear alone as one of the string literals in the list, then dfdl:initiatedContent must be "no" . Below is a DFDL schema with dfdl:initiatedContent="yes" and dfdl:initiator="%ES;". No error is generated on parsing. Is this a bug? /Roger <xs:element name="input"> <xs:complexType> <xs:sequence dfdl:initiatedContent="yes"> <xs:element name="A" type="xs:string" dfdl:initiator="%ES;" /> </xs:sequence> </xs:complexType> </xs:element>
