Kat Street writes:
> Reins: The way we check is just by looking, but there's little we can do
> to force people to change by ourselves.
you could run a robot which walked over the pages and applied some
checks
> Carrots: We have generic, corporate templates people can (should) use. We
> will do different designs for specific cases. We maintain central style
> sheets, so that people aren't (shouldn't be) using any kind of text
> formatting etc.
the problem with this is the endemic one of HTML being so open to
poisoning...
> Apathy is your greatest enemy.
At this stage, yes. at a later stage, it is your friend. Within my
department, we have switched largely to a web site maintained in
XML. There are two layers between the author and the reader:
- a change management system where documents are stored, which checks
incoming material. Invalid XML files are not passed to the web
server
- a web server transforming XML into HTML under the control of XSLT
stylesheets
My feeling is that to force something special through this system is
too much bother for most people, so they will go with the flow (early
days yet, I may have well have a revolt!).
One answer to the problem *is* to instiutute these layers of control,
without any option to bypass them, and rely on departments not being
bothered enough to go out to private ISPs. On a University-wide scale,
it would be a tremendous undertaking, of course. Still, the alternative
is pre-millenial chaos well into the future.
Sebastian
|