Re: Error states in the spec

Thanks Norm.
> For example, an opening quote mark that doesn’t have a matching closing
> quote mark is obviously an “unterminated string” error. But the spec
> doesn’t actually say that, I don’t think.

Well, that falls under the general case of "syntax error". A missing closing bracket would be a similar example. So the syntax says that a missing close quote is a syntax error.

Steven

> I expect that a little implementation experience will bring more kinds
> of errors to light. In the meantime, there are some in the
> specification:
>
> 1. An encoded character that is outside of the Unicode code-point range
> 2. An encoded character that is a noncharacter or surrogate code point
> 3. Names that must be serialized but are not XML names
> 4. Non-conforming grammars must be rejected
> 5. There must be exactly one rule for every non-terminal
> 6. Terminal symbols must not be marked as attributes
> 7. In a character class, the class must be defined in Unicode
> 8. Unterminated strings
> 9. Other syntax errors in the grammar
> 10. It is possible for an implementation to run out of memory or
> otherwise be unable to complete a parse
>
> Be seeing you,
> norm
>
> --
> Norm Tovey-Walsh
> Saxonica
>

Received on Thursday, 11 November 2021 13:29:26 UTC