<snip/>
In other words,
<map:match pattern="*.mid"> <map:read src="{1}.mid"/> <!-- without the unless-label --> <map:generate type="midi" src="{1}.mid"/> <map:transform src="xmidi2xdoc.xsl" label="content-label"/> <!-- should never come here --> <map:serialize type="xml"/> </map:match>
must become valid for consistency. A reader becomes an exit point and the rest of a pipeline is, by default, ignored. Is this an intended consequence?
No consequence : this is how the sitemap works today, and the above is valid,
No, that's not valid today. And if current sitemap implementation does not passes the conformance test, it does not indicate that invalid syntax has become valid. It just indicates that current sitemap implementation is not conformant.
PS Absense of the official conformance test suite does not make point above invalid. Here is an attempt at the test:
http://cvs.apache.org/viewcvs.cgi/cocoon-2.0/src/webapp/mount/lint/sitemap.xmap?rev=1.1&content-type=text/vnd.viewcvs-markup
Vadim
