Re: ICADD elements in HTML (Jeff Suttor)
Date: Tue, 13 Sep 94 08:39:53 EDT
Message-id: <>
Precedence: bulk
From: (Jeff Suttor)
To: Multiple recipients of list <>
Subject: Re: ICADD elements in HTML
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Working Group (Private)
Yuri Rubinsky writes ...
> Jeff: Your recent posting has made me wonder whether you saw the first
> posting about there being a need for two approaches: The one you describe,
> which gets us  anyDTD -> ICADD markup, works to go, of course, from HTML -> 
> ICADD, since HTML simply has more tagnames than ICADD. 

I re-read the posting(s) ... let's go ahead and make the changes to
HTML that were suggested.

> But I'm concerned about the other direction too. And that's to deal with
> the simpler case where you have an ICADD file, are using it to generate
> Braille or whatever, but want also to make that file (with its added 
> capabilites such as source page number) available to a blind WWW borwser
> user.

I was also trying to lay the foundation that HTML 3+ should be an
architecture based an architectural forms so we could do anyDTD ->
browsable HTML :)

> But as long as there are free WWW browsers, I'd like for print-disabled
> people to have access to them. Most hardware and software for these people
> is very very expensive. There are techinques for making software work 
> readily, for example, with screen-reading voice software; in fact I 
> believe that ASCII WWW browsers probably will "automatically" work with
> such software. For me having any ICADD file be readable by any WWW browser
> means that half the work is done: The other half is ensuring that those
> browsers work well with screen-readers.

I agree the point is access.  Let's make the modifications you suggest
to HTML 2.0 and go on from there.  Let me know if you want any help
with adding the SDA simple architectural forms to HTML 2.0.

P.S. Yuri has really helped us at UCLA by introducing us to the SDA
simple arch forms to drive transformations.  Once we had them working
for our print impaired community, it was easy to make the leap to
using other simple arch forms for other target platforms and other
communities.  E.G. HTML/WWW