I wrote an appendix explaining these attributes for ISO 12083 and
will check to see whether there is any reason why I can't simply pare
that down into an appendix for HTML 2.0 (that is, whether the ISO
copyright might force me to rewrite rather than self-plagiarize).
That is to say, I'm volunteering to write an appendix.
As various people have mentioned, ICADD transformation is common practice
now and I agree with all the arguments for keeping it in.
Just for the record: There
are several good reasons why #FIXED attributes were used instead of
all the options -- and yes, we seriously considered LINK and DSSSL;
the location model in ICADD owes a little to each -- and it seems
that the overwhelming reason, the political one, worked: By making
ICADD attributes "part" of a DTD/application, several people have
found that it is considerably easier to get funding to include them
as part of DTD development. Our concern in the ICADD committee was
to not give DTD owners as easy way to say "Oh we'll just deal with
the SDA transformation later in this separate file/converter/filter,
etc."
I agree with everyone who thinks it would have been more efficient/cleaner/
whatever to not have one fixed Braille/largeprint/voice transformation
built into the DTD. However, in practice, this turns out to have been
one of our wisest decisions.
Yuri
---------------------------------------------------------------------
Yuri Rubinsky +1 416 239-4801
Member, ICADD (800) 387-2777 (from US only)
President, SoftQuad Inc. uucp: {uunet,utzoo}!sq!yuri
Suite 810 56 Aberfoyle Crescent Internet: yuri@sq.com
Toronto, Ontario, Canada M8X 2W4 Fax: +1 416 239-7105