> Now HTML 3 is no more, and HTML 3.2 has been adopted by industry
> leaders, should we be validating using HTML 2 or HTML 3.2?
> Has this been discussed within eLib?
FIGIT hasn't discussed it, and you lot _are_ eLib...
Personally, I suspect the answer might depend on your market position and
your user-base. Assuming that HTML 3.2 might leave older browsers a
little confused, some might deliberately wish to err on the cautious
side. Others, needing the additional features of 3.2, might wish to drag
their user-base to the latest versions.
Is my assumption reasonable?
Remember we _did_ discuss that there is a long term problem in storing in
HTML, as it is so dynamic and not necessarily backwards compatible. This
probably doesn't matter so much for your 'navigation' pages, but does for
your 'content' pages, with many pages not falling into either camp. SGML
is a safer long term bet, although more of a problem in the short term.
CLIC have done some good work on SGML-to-HTML conversion on the fly, and
of course it could be done in batch as well.
The solution might be a deliberate short term decision to store in HTML,
recognising the need to migrate forward to later versions as appropriate,
with perhaps a medium term aim of migrating to SGML and a suitable DTD.
--
Chris Rusbridge
Programme Director, Electronic Libraries Programme
The Library, University of Warwick, Coventry CV4 7AL, UK
Phone 01203 524979 Fax 01203 524981
Email [log in to unmask]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|