# multicast of URN/URL session?

Pete Deuel (deuelpm@craft.clarkson.edu)
Sun, 11 Jul 1993 11:38:21 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Michael Mealling: "Uniform Resource Modifier: a meta-information encoding scheme"
- Previous message: Larry Masinter: "multicast of URN/URL session?"

    Date: Sun, 11 Jul 1993 11:38:21 -0400

    From: deuelpm@craft.clarkson.edu (Pete Deuel)

    Message-Id: <9307111538.AA29959@craft.clarkson.edu>

    To: distribution:; (see end of body)

sadlerl@indiana.edu, samhahn@netcom.com, saw@cs.purdue.edu,
schardt@acc.vf.ge.com, schneide@divsun.unige.ch,
schwabe@exu.inf.puc-rio.br, sendall@dxcern.cern.ch, softpro@cscns.com,
softpro@world.std.com, stoughto@fnal.fna
Subject: Questions: HTML Reference Guide

Well, you had to know this was coming... this is a brief
questionairre concerning the HTML Reference Guide. If you've not had
time to write any HTML (and therefore use the guide), either save the
questionairre or trash it. You'll have another opportunity to give
feedback later!

Also, just stick a "n/a" in for the questions that don't concern
you. For example, if you didn't bother to trim the pages, don't
comment on questions where I ask about margins...

To fill out this questionairre, please use an ASCII text editor
and either:

edit a saved copy of this questionairre, putting your
answers in after each question

or:

just type your answers preceded by the appropriate
question number

and mail the completed questionairre to:

deuelpm@craft.camp.clarkson.edu

*Note: The questionairre method is what I call "moderated
feedback" and it is just as important to me as "unmoderated feedback."
I consider this moderated feedback because I have control of the kinds
of comments you make. I constrain you, in a way, to comment on the
topics on which I need feedback. (I must go with a "majority vote" on some
of the considerations that go into this book. For instance, if 99% of
the readers hate the document size, and 1% love it, I have to stick to
the 99%'s opinion and change the page size.)

Your unmoderated feedback (off-hand comments, initial
reactions, etc.) are also VERY IMPORTANT--I realize that no matter how
I might "justify" having written a certain paragraph, sentance,
heading, or whatever, it is THE READERS' reaction that either make or
break that aspect of a book. So, feel free to send me E-mail on
whatever concerns you...

I will use this feedback to edit the book and make an improved
version .2, which you will all receive. (I will send out a mailer
about a week ahead of time; if this is not a list you'd like to stay
on, you'll have the opportunity to have me yank you off the list before
I send out the new version.)

Thanks for your time!

Pete
deuelpm@craft.camp.clarkson.edu

-----cut here-----~s Questionairre: HTML v.1

DISTRIBUTION:

1. Did you receive the HTML Reference Guide okay? Were you succesful
at "undoing" the way the file was packaged? Did you easily get valid
postscript files?

2. Are you aware of other means to distribute compressed postscript?
If so, what are they? (Keep in mind that I'd like to continue to
compress the postscript to cut down on Internet traffic; you know what a
pain net-lag can be!)

FORMAT:

3. I picked a 7" x 8.5" size because I wanted to make a small book
that's easy to carry and doesn't take up too much desk space. Do you
have a better size in mind?

4. How useful was the Table of Contents? How could it be better?

5. How useful were the headers and footers? (The footers tell which
section of the book you're in; the headers tell you which section and
sub-section the page is in.) How might you change them?

6. Was it clear what each text font meant? ...that courrier was what you
would type, that italics in a command were like "variables," etc....)

7. Was there enough whitespace to make the book easy to scan?

8. Was there enough space to scribble down notes? If not, where would
you add space for this purpose?

9. Did the tag commands stick out from the text so that you could
easily trun to a page and see them at a glance? If not, how would you
fix this?

10. Did the examples stand out well? If not, how would you make them
stand out for easy scanning?

11. Did you find Appendix A (Command Quick-Reference) useful? How
could it be more useful?

12. If you used the index: How successful were you at finding
information that is in the book by looking in the index?

13. Overall, what improvements would you make to this book to make it
easier to scan and use as a reference work.

CONTENT

14. Were there any type-o's that you found? (Please specify page
number, word, and correction if possible.)

15. Were all the examples proper HTML for your WWW browser? What
examples didn't work for you?

16. Were the examples clear enough? Should they have more or less
explanation?

17. Were the commands clearly documented? That is, could you easily
look at the command and understand it's syntax? If not, what would make
this task easier for you?

18. Briefly, what other HTML commands do you know of that weren't
included in this document? (You can just name them off and quickly
tell me what they do.)

19. What other information would you like to have handy when writing
HTML? Do you think I should include it in this book? How should I
include it (a table, an appendix, a new section)?

20. What else would you like to say about the HTML Reference Guide?

%%% overflow headers %%%
To: BENMRAD@ELDI.EPFL.CH, Cardeci@Lysator.LiU.SE, Colin.Walls@barclays.co.uk,
D.M.Anthony@csv.warwick.ac.uk, David.Martland@brunel.ac.uk,
Erwin.Bolwidt@loesje.org, Graham.Reynolds@cwi.nl,
Ian_MacPhedran@engr.usask.ca, Paul.Wilson@barclays.co.uk,
adreyer@uni-paderborn.de, adrian@cs.wm.edu,
adrian@medlan.med.monash.edu.au, alien%uk.ac.essex@nsfnet-relay.ac.uk,
andreas@iguwnext.tuwien.ac.at, andrew@gid.co.uk, andrewc@aiai.ed.ac.uk,
as.mjp@forsythe.stanford.edu, ballav@caen.engin.umich.edu,
bandeira@inf.ufrgs.br, barta@infosys.tuwien.ac.at,
bebo@slac.stanford.edu, bene@cs.tu-berlin.de, bert@mit.edu,
bjordan@u.washington.edu, bloemer@tnt.uni-hannover.de,
borovoy@apple.com, bower@is.morgan.com, brennan@hal.com,
brown@cme.nist.gov, brw@hertz.njit.edu, budi_rahardjo@umanitoba.ca,
burger@ffg.com, bwhite@inmet.com, cdr@stolaf.edu, cherhal@grenet.fr,
chumphre@vm.ucs.ualberta.ca, ckaul@cs.sandia.gov, clv2m@virginia.edu,
comte@sophia.inria.fr, costello@vnet.ibm.com, coyne@beno.css.gov,
cricket@hp.com, dale@ora.com, dan@chem.bu.edu, dane@fnal.gov,
dave@cs.strath.ac.uk, debra@win.tue.nl, dhancock@arinc.com,
dianew@sco.com, dig@boxhill.com, dlee@cis.ohio-state.edu,
dneal@neosoft.com, ec@pms240.pms.ford.com, edgar@ms.washington.edu,
edwardc@aisb.ed.ac.uk, efeustel@ida.org, ejohnson@enuxha.eas.asu.edu,
ekatz@ncsa.uiuc.edu, ekki@prakinf.tu-ilmenau.de,
erick@sunee.uwaterloo.ca, evans@phebos.aps.anl.gov,
ezcrues@gothamcity.jsc.nasa.gov, f87-sir@nada.kth.se,
fabio@cirfid.unibo.it, fbignone@alchemy.chem.utoronto.ca,
fin@unet.umn.edu, fine@cis.ohio-state.edu, francis@engr.umbc.edu,
frankt@cwi.nl, fred@bradley.bradley.edu, fsp@thp.uni-koeln.de,
gdale@apple.com, gis80534@eicsun2.eic.nctu.edu.tw, gopher@ifi.unizh.ch,
gw@cs.strath.ac.uk, hanusj@bcc.orst.edu, harmo@kruuna.Helsinki.FI,
harvey@oasys.dt.navy.mil, harward@convex.com,
heffron@falstaff.css.beckman.com, hoesel@chem.rug.nl,
houghton@cs.cmu.edu, hoymand@joe.uwex.edu,
huangp@hpwcsvp.mayfield.hp.com, j-germuska@nwu.edu,
j.williams@aston.ac.uk, jal@plaza.ds.adp.com, jamie@csd.uwo.ca,
jansen@syd.dit.csiro.au, jasper@molbiol.ox.ac.uk,
jbotz@orixa.mtholyoke.edu, jcorn@cudnvr.denver.colorado.edu,
jel@corp.portal.com, jgraves@eng.auburn.edu,
jiliu@silver.ucs.indiana.edu, jim@ml.com, jlbeug@calPoly.edu,
jmr@austin.ibm.com, johni@ee.ubc.ca, johnston@turing.scs.carlton.ca,
joslyn@kong.gsfc.nasa.gov, jst@lauri.oulu.fi, julien@scs.leeds.ac.uk,
jw4@bcstec.boeing.com, jz27@columbia.edu, kchang@ncsa.uiuc.edu,
ken@odin.stockton.edu, ketlux@ketlux.demon.co.uk,
kevinh@pulua.hcc.hawaii.edu, khm@daimi.aau.dk, khushro@eecs.umich.edu,
kwp@avalanche.com, lambert@psc.edu, lane@selway.umt.edu, lark@ora.com,
m.koster@nexor.co.uk, maartenb@na47sun05.cern.ch, mah@ic.co.at,
maier@edvz.sbg.ac.at, maler@zk3.dec.com, mau@ipifidpt.difi.unipi.it,
mbell@compsci.liverpool.ac.uk, mcclanah@edcserver1.cr.usgs.gov,
mengtat@iti.gov.sg, mf@ircam.fr, michael@cygnus.uni-muenster.de,
mitch@vesheu.sar.usf.edu, mkrause@mitre.org, mma@creare.com,
mowgli@magnus.acs.ohio-state.edu, mswain2@baboon.cv.nrao.edu,
nanda@pgate.boeing.com, ngps@np.ac.sg, nikos@cbl.leeds.ac.uk,
norman@giardia.pdb.cdc.gov, nystrom@psc.edu,
olson%mydual.uucp@necis.ma.nec.com, p00327@psilink.com,
phillips@cs.ubc.ca, pjb@frame.com, plord@uspto.gov, pshannon@nrao.edu,
r_clark@edrc.ac.uk, raisch@ora.com, ray@cme.nist.gov,
rer@sun1x.clarkson.edu, rhc52134@uxa.cso.uiuc.edu,
rhca80@melton.sps.mot.com, rick@sq.com, rjones@pa.dec.com,
robert.bagwill@nist.gov, rodgers@nlm.nih.gov, ross@cs.rmit.edu.au,
rriley@fisher.com, rsmith@proteus.arc.nasa.gov,
rstepno@eagle.wesleyan.edu, rtgrc@rc.rit.edu, ryanw@microsoft.com
%%% end overflow headers %%%

- Next message: Michael Mealling: "Uniform Resource Modifier: a meta-information encoding scheme"
- Previous message: Larry Masinter: "multicast of URN/URL session?"