It is not entirely clear to me that I matter -- except that
my wife and kids tell me so fairly often -- but I can report
to you on some recent discussions on the html-wg mailing list.
While I was traveling recently a discussion about <INCLUDE>
erupted and just as suddenly ended. I have to admit that
I did not follow the discussion, so I cannot report on whether
it reached a resolution.
A week or so ago, I posted a proposal which includes an
attempt to describe the meaning of <LINK> and <A> elements,
especially with respect to the use of the REL and REV attributes.
In it, I suggested <A REL=INCLUDE HREF=...> for an inclusion
link. The response was mixed, but I will be re-issuing that
proposal with some edits and further details some time real
soon now.
I expect that we will see some form of inclusion capability
in HTML in the not-too-distant future. Without such a
capability it will be impossible (or at least unethical)
to include copyrighted material from publishers who expect
a royalty payment for use of their material. With a formal
mechanism, it is assumed that derivative works could be
built and published in a commercially viable manner.
In short: be patient, we'll get there.
Murray
===========================================================================
---------------------------------------------------------------------------
Murray C. Maloney Internet: [email protected]
Technical Publications Writer/Architect Uucp: ...uunet!sco!murray
SCO Canada, Inc. My Phone: (416) 960-4031
130 Bloor Street West, 10th Floor Fax: (416) 922-2704
Toronto, Ontario, Canada M5S 1N5 SCO Phone: (416) 922-1937
===========================================================================
Disclaimer: I'm speaking for myself. 'T ain't nobody else to blame but me.
---------------------------------------------------------------------------
Sponsor member of Davenport Group Member of IETF HTML Working Group
===========================================================================