Re: why TITLE, not TITLE?

At 04:24 PM 5/9/97 -0400, you wrote:
>John Udall wrote:
>>         But then you have to have modified versions of all of those DTDs
>> available, so that people can check against them.  
>
>So? DTDs are small and the code to process them is freely available.
>DTDs can be downloaded and updated easily without changes to binary
>code.
>
	Good point.  It really is just a design decision that Chad Owen Yoshikawa
<chad@CS.Berkeley.EDU> is going to have to make.  He'll have to balance out
cost, effort, and maintainablity.  Your point about DTDs is well made. I'm
not sure which way I would go, if I were in his shoes. 

	Just thinking out loud here. Wouldn't it be cool if you had a browser that
would download the appropriate DTD automatically from a public location and
download the accompanying code necessary to parse the markup associated
with that DTD, and then dynamically link in that new code, so that you
could view the document.  This sort of scenario would require a lot more
bandwidth than is currently available to most users today, but I could
imagine it happening somewhere down the road. The base technolgies are
there. It's just a matter of putting the pieces together and waiting for
the core infrastructure to be in place. (which is of course the hard part)
:-(  Oh well, maybe I'll see it in my lifetime. :-)

-John

> Paul Prescod
>
>

John Udall,
      Programmer/Sys. Admin.
Extension Electronic Technologies Group (EETG),
Cornell Cooperative Extension,
40 Warren Hall
Cornell University,
Ithaca, New York 14853
(607) 255-8127
jsu1@cornell.edu

Received on Monday, 12 May 1997 10:11:25 UTC