Re: "Mailto" Command

Dr. Clue (drclue@mail1.abac.com)
Sun, 06 Apr 1997 17:23:35 -0700


Message-ID: <33483E87.3D41@mail1.abac.com>
Date: Sun, 06 Apr 1997 17:23:35 -0700
From: "Dr. Clue" <drclue@mail1.abac.com>
To: Ingo Macherius <Ingo.Macherius@tu-clausthal.de>
CC: Dan Connolly <connolly@w3.org>, www-html@w3.org
Subject: Re: "Mailto" Command

The quoted at the end of the page outlines a long standing issue=20
regarding mailto in particular, but client-side parameter passing in
general. I will paste here a generic responce and proposal I have been
suggesting for a long time now.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Standard =
responce to email problem =3D=3D=3D=3D=3D=3D=3D
 Today I figure to keep from breaking older software we would have to
add
 something, but as long as we are pretending to be standard gods for a
 moment perchance one should consider parameter passing to local
 applications in general.
=20
 In the future parameter passing to local utilities beyond email such as
 video conferencing will also become an issue, so some off the cuff =20
 syntax not to be take too literally might be=20
=20
 <A HREF=3Dmailto:user@server.com USERAPP=3D"#sendmail">email me</A>
 <USERAPP NAME=3D"SENDMAIL">
 <PARAM NAME=3D"TO" VALUE=3D"user@server.com">
 <PARAM NAME=3D"SUBJECT" VALUE=3D"My subject">
 <PARAM NAME=3D"CC" VALUE=3D"someone@otherserver.com">
 </USERAPP>
=20
 The value assigned to the USERAPP attribute would refer some generic=20
 functionality such as sendmail, videoconference, chat or whatever.
 The HREF would only apply to those situations in which support for
 USERAPP was not avaiable or was disabled, and would do whatever
 HREF does now.
=20
 Each <PARAM> tag between <USERAPP> and </USERAPP> would represent a =20
 name value pair and the client could use whatever it understood and
 ignore the rest. Nothing would be encoded in a manner that could not be
 freely entered from the keyboard and the application would also receive
 the HREF value when called.
=20
 This syntax is very similar in nature to the client side imagemap hack
 and would provide a great deal of flexibility.
=20
 The <A HREF> entry point to this mechanism would also have cousins in
 client side imagemaps, <FORMS> and per-chance some link to a
 content-type mechanism for good measure.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D End Stand=
ard responce to email problem =3D=3D=3D=3D=3D=3D=3D

Ingo Macherius wrote:
> Dan Connolly said:
> | It's important to keep the HTML spec independent of the URL specs.
> | Note that the HTML spec doesn't mandate any list of graphics formats
> | either.
> So if this is a FAQ and an frequently requested feature, why it is not
> added to HTML in a clean way ? This can not be done following the same
> mechanism as used with <applet>:
>         <applet ...>
>                 <param ...>
>                 Text for non Java Browsers
>         </applet>
>=20
> This is defining a semantic for the <applet> mixed content model, where
> element content is used by an aware application and discarded by=20
> others. Character content is discarded by the aware and displayed by=20
> the unaware application. The trick is having all elements EMPTY.
>=20
> Similarily one could try something like this to enhance mailto: anchors
>         <a href=3D"mailto:...">
>                 <mailheader key=3D"Subject" VALUE=3D"Re: ACME=20
> advertisement">
>                 <mailheader key=3D"CC"      VALUE=3D"big@brother.com">
>                 Click here for free demo
>         </a>
>=20
> But in this case the decision whether to process or discard the=20
> <mailheader>
> tags *are* dependant on the URL=B4s protocol part. The role of mailto i=
s
> to make <a> a *typed* anchor, something like
>=20
>         <a class=3D"mailto" href=3D"joe@user.org">
>=20
> So is it really possible to give the requested functionality without
> a dependence of URL and HTML ? A cheap way out is to add tons of new
> attributes to <a>, but is this desireable ?


--=20
   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Unix,C++,TCP/IP,Dynamic HTML,Servers,Proxies,Agents
__ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D __
\/  =3D      Dr. Clue (A.K.A. Ian A. Storms)     =3D  \/
   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
\/ HTML/CGI Guide W/ C++ Source code
http://users.abac.com/cgi-bin/drclue/F1.cgi/HTML/HTML.html