As of:  Thu 2017-12-14 17:02:17 UTC  [=1513270937. 12:02:17-05:00]

>> gkwtags.html  L: 13,394. A: 100644. M: 2009-01-17 19:51:47 UTC [=1232221907] -3252.88d >> 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "">
<title>Unknown HTML tag test page</title>
<META NAME="description" CONTENT="HTML page with extra markup tags not defined in HTML spec.
I wrote this before I found out some big commercial websites use this trick already.">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

<!-- Obviously, SGML comments could be used as processing directives here... -->

<!-- Also note that, when I process this file through a CGI script that      -->
<!-- sends a HTTP "Content-type: text/plain" header, Microsoft Internet      -->
<!-- Explorer 4 *still* treats the tags in the text *as* tags!               -->
<body bgcolor="#D3D3D3">
<h1>Unknown <protocol>HTML</protocol> tag test page</h1>
<center><table width="75%">
<tr><td align=center><font color="navy"><i>Motion, even in the direction of the horizon
which presents itself to
a person standing erect with open eyes facing forward, is not
necessarily progress.</i></font></td>
<hr><p><big><img src="gif/b.gif" height=34 width=33 border=0 align=left alt="B">elow are some thoughts I had about <b>XML</b> during the summer of 1998.
I still think they may be worth reading and express valid concerns. After attending the
Graphic Communication Association's <b>XML 98</b> conference (Chicago, 14-20 November 1998), however,
I feel that the issues are much bigger, and that my earlier concerns and thoughts
do not point in the direction(s) where limited energy
will likely be most productively expended -- although I still do believe it is important for
grandmothers to be able to author their own web pages.</big></p>
<p><big><big>A</big>fter the conference, I no longer see <b>XML</b> simply as
"dumbed down" <b><a href="WhatIsSGML.html">SGML</a></b>.
I now see <b>XML</b> itself more as a "hook" on which a lot of powerful and complex
supporting technologies will be hung -- like a pile of garments way
overloading a wobbly coat rack (could these technologies have been hung on the <b>SGML</b>
hook? For "political" reasons, that now seems an idle question).  I now anticipate that
<b>XML</b> will likely become far more <i>complex and difficult</i> than <b>SGML</b>, when considered in the
light all the adjunctive technologies and standards surrounding it (e-commerce technologies,
XSL, Namespaces, Xlink, Schemas of whatever kind, Link maps, XIML(?), GKW(?) etc.).</big></p>
<p><big><big>T</big>hese developments (e.g., schemas replacing
DTDs) may result in <b>XML</b> becoming far <i>more</i> powerful than <b>SGML</b> ever was in practice.
Some of the challenges <b>XML</b> is tackling (even such seeming details as
handling non-Latin character sets, e.g., Kanji) may immensely add complexity. There
may be "consequences" (as in, e.g., "unanticipated side effects"). Beyond observing the
truism that complexification should itself be cause for concern, I have no idea where <b>XML</b> is
headed in its impacts on society, technology or technological workers. I am, however,
now pretty sure that the things about which I wrote below are not, as I thought when I wrote them
(except for that concern about grandmothers!), "key issues" even in the "regional ontology(ies)"
directly involved, not to mention more inclusive humasn[e] perspectives.</big></p>
<p><big>A</big>lso, I would like to respond to a snide remark about HTML, made by one of the
<b>XML 98</b> conference presenters.  This person denigrated HTML as "just anything
Netscape or Microsoft decided to support in their browsers, and that HTML web pages were
never validated in any way".  I agree that HTML is only formatting markup, and it
is obvious that even major corporations' and academic institutions'
websites are generally composed of pages which don't even have
"doctype" declarations. However: almost all the HTML pages on <i>this</i> web site
(<a href="welcome.html"></a>)
<i>are</i> validated, and the pages that are <b>not</b>
generally have good reasons for being that way, along the lines of another conference
speaker's "defense of invalid SGML" in situations where the
invalidity of the marked up text -- as in <a href="gkwtags.html">the present page</a> --
is part of a point made by and/or the use to be made of the text.</p>
<hr size="7">
<a href=""><img src="MSIE4.gif"
width=88 height=31 vspace=1 hspace=2 align=right alt="[ Get Internet Explorer 5! ]" border=0></a><font color="maroon"><big><big>M</big>ay 1999:
New development. Microsoft's Internet Explorer 5.0
supports XML pages.  I have some sample pages which you can check out if you have IE5:
<a href="xmlcsst.xml">xmlcsst.xml</a> (uses CSS), <a href="xmlxslt.xml">xmlxslt.xml</a> (uses XSL), and
<a href="xmlisland.html">xmlisland.html</a> (uses an XML "data island").</big></font>
<hr size="7">
<p><big><big>T</big>his page tests what <browser>Netscape
<b.version>3.04</b.version></browser> (and other web browsers...) do with <b><object>
markup</object></b> (e.g.: <font color=purple>&lt;gkw>?&lt;/gkw></font>). It suggests a
way that <protocol>HTML</protocol> could be extended with
content-describing (<protocol>SGML</protocol>-type) tags, that would grow out of
existing <protocol>HTML</protocol> coding, rather than replacing
it with something else (esp.: <protocol>XML</protocol>/<protocol>XSL</protocol>).</big>
<p><big><big>T</big>his would allow grandmothers and others to continue to produce their
own web pages without needing to use web-page construction programs (e.g.,
<product>Microsoft FrontPage</product>), while
still permitting enhancements to the structural articulation of the text.
<emphasize><i><b>Both</b></i></emphasize> format and structure describing tags would
<emphasize><i><b>coexist</b></i></emphasize>, instead of formatting being split off
from content descriptors in a separate stylesheet that uses a new arcane syntax.</big>
<p><big><big>I</big> would urge: Where
there is serious concern for structural markup,
use <emphasize><i><b>real</b></i></emphasize>
<protocol>SGML</protocol> (<product><a href="panorama-1.html">SoftQuad Panorama</a></product>, e.g.,
can be used to format it).  <protocol>XML</protocol> is
neither grandmother-friendly (like simple <protocol>HTML</protocol>),
nor "industrial strength" (like
real <protocol>SGML</protocol>).  Why introduce new compromised clutter that
doesn't really satisfy anyone's needs but forces everyone
to learn and do something other than what they're
accustomed to, into an already messed up world that
has serviceable ways of accomplishing all the relevant purposes?</big>
<blockquote><font color=maroon><big>[Vice-president of marketing, P.G.] Bartlett
at ArborText [a key supplier of
SGML and XML software] has no doubts about what's going on. "XML," he says, "will prove to be one of the
top ten technological innovations of the first century of computing." (<i>New Scientist</i>,
30 May 98, p. 37)</big></font></blockquote>
<p><big><big>I</big>f a "dumbed down" form of
<protocol>SGML</protocol> is really needed, it is already available
in the form of a person using only a limited
subset of <protocol>SGML</protocol>'s existing functionality.  If this
is "too difficult" for people, maybe the
problem is not the difficulty of the <protocol>SGML</protocol> itself,
but the inadequacy of documentation how to use it.
(The inventor of <product><a href="panorama-1.html">SoftQuad Panorama</a></product>,
<a href="yuriObit1.html">Yuri Rubinsky</a>, had a vision of "<a href="WhatIsSGML.html">SGML on the WEB</a>", which,
alas, died along with his own premature decease.)</big>
<p><big><big>T</big>o see the source code for this file, with its undefined markup, please
<a href="">click
here</a>. If anyone wants to go
beyond <protocol>HTML</protocol> in substantively empowering ways,
I would suggest they start with:</big>
<li><big><big>F</big>igure out a way to implement <protocol>CGI</protocol> scripting
that would enable it to be
a normal part of everybody's website (e.g., <i><b>GeoCities</b></i>
and <i><b>AOL</b></i> homepages). <protocol>CGI</protocol> is a lot more powerful
than a lot of more confusing and browser-dependent workarounds, like <workaround>Javascript</workaround>
and <workaround>Java</workaround>.  (Do
<honorific>computer science wizards</honorific> shy
away from this challenge because it is too difficult? Or is such a service to the
user community beneath their self-image of suitable employment of their skills?)</big>
<li><big><big>I</big>mplement a multiple-target hyperlink construct.
E.g., clicking on: <font color=purple>&lt;a href<b>s</b>="
'The New York Times', target2.html 'Some web page of mine' ...,
ftp://more.blahblah/targetn.ftp 'Somebody else\'s ftp site'"></font><u>let me
choose where I want to go</u><font color=purple>&lt;/a></font>, would
popup an annotated menu of destinations from among which the user could
choose which one they wanted to link to. (Note that SGML HyTime implemented this multi-target linking facility; I
once maintained an HTML application that implemented multi-targeted links thru JavaScript --
see screenshot of <a href="#multi">example multilink</a>, <i><a href="#multi">below</a></i>.)</big>
<p><big><appreciation><big>T</big>hank you for considering my thoughts.
<I><a href="signgb.html">Your thoughts?</a></I></appreciation>
<a href="signgb.html"><img src="emailme.gif" align=bottom
border=0 hspace=2 width=20 height=12 alt="[ Email me! ]"></a></big>
<p><hr size="7">
<table cellspacing=0 cellpadding=0 border=0 width="100%">
<tr><td align=left><big><a href="WhatIsSGML.html">Go</a>/<a href="WhatIsSGML.html">Return</a> to
SGML document introducing you to SGML.</big>
<table cellspacing=0 cellpadding=0 border=0>
<tr><td valign=top><big><a href="sgmlnote.html">Go</a>/<a href="sgmlnote.html">Return</a></big></td>
<td><big>&nbsp; to another intro to SGML: <i>*Darwin Among the Machines*</i> (<i>Susanne Langer and SGML</i>).</big></td>
<a href="xmlstuff.html">Read</a> Laurent Sabarthez' notes about XML (SGML's "replacement").</big></td>
<td><img src="sp.gif" height=2 width=2 border=0 alt="[ ]" hspace=6></td>
<td valign=top align=right><a href="WhatIsSGML.html"><img src="gif/sgml.gif" height=32 width=32 vspace=3 hspace=3 alt="[ Learn about SGML! ]" border=0></a></td></tr>
<table cellspacing=0 cellpadding=0 border=0 width="100%">
<tr><td valign=bottom><big>&nbsp;<br>
<a href="changelog.html">What's new</a> on this website?<br>
<a href="sitetoc.html">Go</a> to website <i>Table of Contents</i>.<br>
<a href="welcome.html">Return</a> to Brad McCormick's home page.<br>
<a href="Bradsmap.html">Return</a> to site map.</big></td>
<td align=right valign=bottom><table cellspacing=0 cellpadding=0 border=0>
<tr><td rowspan=2><img src="sp.gif" height=2 width=2 hspace=3 alt="[ ]" border=0></td>
<td valign=bottom><a href="Bradsmap.html"><img src="signpost.gif" height=32 width=33 border=0 alt="[ Go to Site Map! ]"></a></td>
<td><img src="sp.gif" height=2 width=2 hspace=11 alt="[ ]" border=0></td>
<td valign=bottom><a href="sitetoc.html"><img src="gif/up_black.gif" vspace=1 height=16
width=16 border=1 alt="[ Go to website Table of Contents! ]"></a></td>
<td><img src="sp.gif" height=2 width=2 border=0 alt="[ ]" hspace=20></td>
<td rowspan=2 valign=bottom><a href="welcome.html"><img src="gif/home.gif" height=32 width=32 vspace=1 border=0 alt="[ Go home! (BMcC website Home page!) ]"></a></td>
<td rowspan=2><img src="sp.gif" height=2 width=2 border=0 alt="[ ]" hspace=3></td></tr>
<tr><td colspan=4><img src="sp.gif" height=2 width=2 border=0 alt="[ ]" vspace=1></td></tr>
<table width="100%" cellspacing=0 cellpadding=0 border=0><tr>
<td nowrap align=left><address><font color=green>
<author>Brad McCormick, Ed.D.</author><br>
<version><vdate><d>10</d> <m>April</m> <y>2006</y></vdate> (v01.29)</version>
</font><!--#exec cgi="cgi-bin/"--></address></td>
<td valign=top align=right><b><font face="Arial" color=red>[&nbsp;<a href="">This
page is not<br>valid HTML 3.2, 4.0<br>or anything else!</a>&nbsp;]</font></b></td></tr>
<tr><td colspan=2><a name="multi"><img src="sp.gif" height=2 width=2 vspace=12 border=0 alt="[ ]"></a></td></tr>
<tr><td colspan=2 align=center><table cellspacing=0 cellpadding=0 border=0><tr>
<td><a href="$gkwtags.html%23multi$"><img src="gif/multilink.gif" height=270 width=374 alt="[ Multilink example: Clicking link pops up menu of URLs to go to ]" border=1></a></td></tr>
<tr><td><img src="sp.gif" height=2 width=2 border=0 alt="[ ]" vspace=2></td></tr>
<tr><td width=376><font color=purple><small><big>E</big>xample multilink. When you click on "Native American Indians",
a window pops up with a list of places to go to.</small></font></td></tr></table></td></tr>
<tr><td colspan=2><img src="sp.gif" height=2 width=2 vspace=3 border=0 alt="[ ]"></td></tr></table>

<< gkwtags.html  L: 13,394. A: 100644. M: 2009-01-17 19:51:47 UTC [=1232221907] -3252.88d <<

[ Please note: ]  Some systems do not provide this script with a return address (the HTTP_REFERER cgi environment variable). In those cases, the "Return" icon at right is disabled, but you can still use your web browser's BACK button to return to the page from which you came to here. I apologize. Thank you for your understanding.

Page generated by:
Copyright © 2001-2005 Brad McCormick, Ed.D. [ Email me! ]
26 April 2008CE
[ ]
[ ]
[ Notice what's hiding in plain sight! ] [ ]
[ ] [ ]
[ Go home! (BMcC website Home page!) ] [ ] [ Use your web browser's BACK button to return to page from which you linked to here! ] [ ]
[ ]
[ Go to Site Map! ] [ ] [ HTML 3.2 Checked! Test me! ] [ ]
[ ]
[ ]
[ Go to website Table of Contents! ] [ ] [ Welcome to my website! Please come in! ]
[ ]
[ ]