[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: SAX Test suite

• To: "'Alaric B Snell'" <alaric@a...>, "'Elliotte Rusty Harold'" <elharo@m...>
• Subject: RE: SAX Test suite
• From: "Bob Wyman" <bob@w...>
• Date: Mon, 10 Nov 2003 19:58:39 -0500
• Cc: <xml-dev@l...>, <sax-devel@l...>
• Importance: Normal
• In-reply-to: <3FB030D2.1060400@a...>
• Reply-to: <bob@w...>

Alaric B Snell wrote:
> Its output might be something like:
	I suggest that the trace would be more useful if the various
steps were explicitly flagged as to their type. For instance, you
should be able to easily distinguish between lines which are the
result of inspecting features, properties or other state and lines
which record the occurrence of and parameters of callbacks. It
probably also makes sense to do all this in XML... Thus, I would have
something like:

<test name="first test" system-under-test="asn2sax" runby="bobwyman">
  <features>http://xml.org/sax/features/namespaces = true</features>
  <callback>startDocument()</callback>
 
<callback>startPrefixMapping("foo","http://www.example.com/")</callbac
k>
  <callback>startElement("http://www.example.com/","test","foo:test",
 
[("attr1","foo:attr1","CDATA","http://www.example.com/","hello")])</ca
llback>
  <features>http://xml.org/sax/features/namespaces = true</features>
  ...
</test>

		bob wyman

• References:
  • Re: SAX Test suite
    • From: Alaric B Snell <alaric@a...>

• Prev by Date: Re: SAX Test suite
• Next by Date: Re: Re: Production 78 / Process failure in XML 1.1
• Previous by thread: Re: SAX Test suite
• Next by thread: Formating XML data in XSLT
• Index(es):
  • Date
  • Thread