[Home] [By Thread] [By Date] [Recent Entries]
A 'sanity check' seems clearly to be in order here. I hear the industry way to solve spec interpretation problems (re conformance) is to use test assertions, whether it be XML, C, C# or java. What would be
test assertions for those spec statements I just highlighted as possible culprits? Maybe producing these will help clarify the spec. "In order to support correction of errors, the processor MAY make unprocessed data from the document (with intermingled character data and markup) available to the application." "Once a fatal error is detected, however, the processor MUST NOT continue normal processing (i.e., it MUST NOT continue to pass character data and information about the document's logical structure to the application in the normal way)." ---- Stephen D Green On 17 July 2011 10:39, David Carlisle <davidc@n...> wrote:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



