>>>>> "David" == David Crossley <[EMAIL PROTECTED]> writes:
David> There is also a draft WXS (W3C XML Schema) at
David> src/documentation/xdocs/drafts/sitemap-2.1-draft.xsd I do
David> not know its status, but see
David> http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=102338126329025
I've gone through the entire thread. Nothing said since late
June. Does this schema still validate all sitemaps?
I was actually thinking of a more modular approach, with possibly several
namespaces. Then if something new is needed in the sitemap, whoever is
writing the stuff writes a new .xsd file, which gets imported into the
main file.
I also note that there is additional benefit to be gained by from the
validated process. For instance, LinkSerializer has a hard-coded (in Java)
mime-type. This may be all very well, but if someone creates a
pipeline involving a LinkSerializer, and codes the mime-type, it will
be ignored, and the innocent pipeline-coder might spend a lot of time
scratching their head to work out why.
If LinkSerializer was a substitutable type for Serializer in the
schema, then it could specify a fixed value for mime-type there, and
so the pipeline coder would see a validation error.
The mime-type would still have to be hard-coded in Java, though,
unless validation was also done at run time (hm. Cocoon is slow enough
already on my machine!).
When I finish the dtd (I just need to discuss matters with the author
of sitebuilder, then I can finish in 5 minutes), I would suggest
immediately turning on validate of sitemaps in the build process
against the dtd, so as to ensure it's kept up to date. Then gradually
converting to using WXS.
--
Colin Paul Adams
Preston Lancashire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
