Steve wrote:
You can actually get rid of this error without
documentFinalTerminatorCanBeMissing by removing the ambiguity of the sequences
in a choice. For example, we could replace the choice with the
following:
Wow! That is fantastic!
I went a step further and made that EOL
The difference here is that this warning only appears when *compiling*
the schema, just to alert you that the schema might not give you the
expected behavior. In this case, it's relatively easy to know that that
the schema is doing what we expect and that the warning can be ignored.
However, the
Steve wrote:
> I think it would be reasonable to
> ignore this warning.
But, but, but, ...
Mike said (paraphrasing) that it is unwise to officially publish a DFDL schema
that produces warnings on valid data.
It appears that it is impossible to avoid getting a warning message (for the
CSV
When unparsing a choice, we use the infoset to determine which branch of
the choice to unparse. For example, say we had this choice:
If the infoset contained the "A" element, then we would unparse the
first branch of the choice. If the infoset contained the "B" element,
then we
Hi Folks,
Suppose you are creating the official, standard DFDL schema for a data format.
Would you be okay with officially releasing a schema that generates warnings on
data that is valid?
Here's an example. The RFC for CSV (RFC 4180) says that CSV files consist of
records separated by
