cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colin Paul Adams <>
Subject Invalid sitemap contents in lint/sitemap.xmap
Date Wed, 23 Oct 2002 15:13:16 GMT
Whilst I now have a sitemap DTD that validates all the existing
sitemaps, it doesn't fail all the examples of invalid pipelines in the
lint sitemap:

    <!-- Pipeline with no map:generate|read|mount|redirect-to|call is illegal
      <map:transform src="../../stylesheets/simple-xml2html.xsl"/>

But I am using a rather generous grammar for pipeline contents:
<!ENTITY % pipe.contents

which clearly does not fail this case. It would be good to establish
exactly what the rules are, but I'm finding it rather difficult to

For instance a pipeline must start with: ??
 map:generate|read|mount|redirect-to|call|match|act ?

Is it worth trying to establish this? I think the rule must be rather
complex. For instance, if a pipeline starts with a match, then each
branch of the match must have the same start requirements as a
pipeline, yes? But if a pipeline starts with a generate, and the next
stage is a match (is this allowed) then the map branches could start
with a transform.


    <!-- Pipeline with map:generate|transform must have serialize
      <map:generate src="sitemap.xmap"/>
      <map:transform src="../../stylesheets/simple-xml2html.xsl"/>

validates, incorrectly. But is this necessarily invalid, in the
presence of views?


    <!-- Pipeline with component after map:serialize|read|mount|redirect-to|call is illegal
      <map:read mime-type="text/test" src="sitemap.xmap"/>
      <map:act type="request"/>

validates incorrectly. I think it will be much easier to express these
sort of restrictions in schematron than WXS or RelaxNG. DTD has no

In fact, nearly all of the invalid pipelines in lint are validated ok
by the DTD.
Colin Paul Adams
Preston Lancashire

To unsubscribe, e-mail:
For additional commands, email:

View raw message