LISTSERV mailing list manager LISTSERV 15.5

Help for HTML-WG Archives

HTML-WG Archives

HTML-WG Archives


Next Message | Previous Message
Next in Topic | Previous in Topic
Next by Same Author | Previous by Same Author
Chronologically | Most Recent First
Proportional Font | Monospaced Font


Join or Leave HTML-WG
Reply | Post New Message
Search Archives

Subject: Scope, other edits ready to go in HTML 2.0 draft
From: "Daniel W. Connolly" <[log in to unmask]>
Reply-To:[log in to unmask]
Date:Thu, 21 Sep 95 20:13:33 EDT

text/plain (644 lines)

I added Larry's text regarding past/future to the scope section.
I also fixed a bunch of typos that folks have sent me since
draft 5 went out (thanks folks!).

Hypertext Markup Language - 2.0 - Table of Contents
Fri Sep 22 00:24:28 1995

TeXinfo and a postscript rendering derived from it are also available:
(Joe's tools make better postscript... stay tuned...)

As soon as I hear that the IESG member who asked for the scope changes
is satisfied (and Joe sends me text/plain), I'll send the draft to the
IETF editor.



* Added prose about past/future to scope

* BASE explanation made more conservative

* prose about anchor addresses made more conservative 

* Added a little blurb in definition of hyperlink defining

* Incoroporated suggestion to explain LINK a little more

* fixed <DD> -> </DD> in explanation of end-tag omission

* typos: may may, poem/play, Use the -> use of the, fields->field
* changed date

* Under <A>, added "The semantics of link relationships are not
 specified in this document."

Public text:

* added exception -(META|LINK) to TITLE

* typos (an->and, emphais, substituable metainfo->meta-inf)

* catalog: no more level 0

* catalog: 72 char line limit

Joe: would you spin another text and postscript rendition?
Here's the tarball:
-rw-r--r--   1 connolly www  7534 Sep 21 19:56 html-pubtext-19950922.tar.gz

Good night.


p.s. Here are the changes since August 8 in gory detail, for those
who want to know exactly what's changed since the last I-D was issued.

RCS file: /afs/,v
retrieving revision 1.26
diff -b -w -u -r1.26 Makefile
--- 1.26	1995/08/04 17:50:10
+++ Makefile	1995/09/21 23:46:22
@@ -1,8 +1,8 @@
 # Makefile for HTML specification
-# $Id: Makefile,v 1.26 1995/08/04 17:50:10 connolly Exp $
+# $Id: Makefile,v 1.28 1995/09/21 23:46:22 connolly Exp $
-RELEASE = 19950804
+RELEASE = 19950922
 PACKAGE = html-spec-$(RELEASE)
 PUBTEXT = html-pubtext-$(RELEASE)
RCS file: /afs/,v
retrieving revision 1.3
diff -b -w -u -r1.3 acknowledgements.sgm
--- 1.3	1995/06/02 07:59:53
+++ acknowledgements.sgm	1995/09/21 23:46:24
@@ -8,7 +8,7 @@
 <p>Since 1993, a wide variety of Internet participants have
 contributed to the evolution of HTML, which has included the addition
 of in-line images introduced by the NCSA Mosaic software for WWW. Dave
-Raggett played an important role in deriving the FORMS material from
+Raggett played an important role in deriving the forms material from
 the HTML+ specification.
 <p>Dan Connolly and Karen Olson Muldrow rewrote the HTML Specification
RCS file: /afs/,v
retrieving revision 1.9
diff -b -w -u -r1.9 blocks.sgm
--- 1.9	1995/06/15 20:16:38
+++ blocks.sgm	1995/09/21 23:46:26
@@ -1,4 +1,4 @@
-<!-- $Id: blocks.sgm,v 1.9 1995/06/15 20:16:38 connolly Exp $ -->
+<!-- $Id: blocks.sgm,v 1.10 1995/09/21 23:46:26 connolly Exp $ -->
 <h2>Block Structuring Elements
 <p>Block structuring elements include paragraphs, lists, and block
@@ -48,7 +48,7 @@
 <li>Anchor elements and phrase markup may be used.
-<NOTE>Constraints on the processing of <tag/PRE/ content may may limit or
+<NOTE>Constraints on the processing of <tag/PRE/ content may limit or
 prevent the ability of the HTML user agent to faithfully render
 phrase markup.
@@ -144,7 +144,7 @@
 <p>Example of use:
-I think the poem ends
+I think the play ends
 <P>Soft you now, the fair Ophelia. Nymph, in thy orisons, be all 
 my sins remembered.
RCS file: /afs/,v
retrieving revision 1.2
diff -b -w -u -r1.2 catalog
--- 1.2	1994/11/30 23:45:18
+++ catalog	1995/09/21 23:30:23
@@ -1,5 +1,5 @@
 	-- catalog: SGML Open style entity catalog for HTML --
-	-- $Id: catalog,v 1.2 1994/11/30 23:45:18 connolly Exp $ --
+	-- $Id: catalog,v 1.3 1995/09/21 23:30:23 connolly Exp $ --
 	-- Ways to refer to Level 2: most general to most specific --
 PUBLIC  "-//IETF//DTD HTML//EN"			html.dtd
@@ -11,24 +11,17 @@
 PUBLIC  "-//IETF//DTD HTML Level 1//EN"		html-1.dtd
 PUBLIC  "-//IETF//DTD HTML 2.0 Level 1//EN"	html-1.dtd
-	-- Ways to refer to Level 0: most general to most specific --
-PUBLIC  "-//IETF//DTD HTML Level 0//EN"		html-0.dtd
-PUBLIC  "-//IETF//DTD HTML 2.0 Level 0//EN"	html-0.dtd
-	-- Ways to refer to Strict Level 2: most general to most specific --
+	-- Ways to refer to
+		 Strict Level 2: most general to most specific --
 PUBLIC  "-//IETF//DTD HTML Strict//EN"			html-s.dtd
 PUBLIC  "-//IETF//DTD HTML 2.0 Strict//EN"		html-s.dtd
 PUBLIC  "-//IETF//DTD HTML Strict Level 2//EN"		html-s.dtd
 PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 2//EN"	html-s.dtd
-	-- Ways to refer to Strict Level 1: most general to most specific --
+	-- Ways to refer to
+		 Strict Level 1: most general to most specific --
 PUBLIC  "-//IETF//DTD HTML Strict Level 1//EN"		html-1s.dtd
 PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 1//EN"	html-1s.dtd
-	-- Ways to refer to Strict Level 0: most general to most specific --
-PUBLIC  "-//IETF//DTD HTML Strict Level 0//EN"		html-0s.dtd
-PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 0//EN"	html-0s.dtd
 	-- ISO latin 1 entity set for HTML -- 
 PUBLIC	"ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"	ISOlat1.sgml
RCS file: /afs/,v
retrieving revision 1.10
diff -b -w -u -r1.10 doc-charset.sgm
--- 1.10	1995/06/15 20:16:40
+++ doc-charset.sgm	1995/09/21 23:46:27
@@ -1,4 +1,4 @@
-<!-- $Id: doc-charset.sgm,v 1.10 1995/06/15 20:16:40 connolly Exp $ -->
+<!-- $Id: doc-charset.sgm,v 1.11 1995/09/21 23:46:27 connolly Exp $ -->
 <h1 id=datachrs>Characters, Words, and Paragraphs
 An HTML user agent should present the body of an HTML document as a
@@ -18,7 +18,7 @@
 Latin Alphabet No. 1, or simply Latin-1.  Latin-1 comprises 191
 graphic characters, including the alphabets of most Western European
-<note>Use the non-breaking space and soft hyphen indicator characters is 
+<note>Use of the non-breaking space and soft hyphen indicator characters is 
 discouraged because support for them is not widely deployed.
RCS file: /afs/,v
retrieving revision 1.12
diff -b -w -u -r1.12 forms.sgm
--- 1.12	1995/08/04 17:50:13
+++ forms.sgm	1995/09/21 23:46:28
@@ -52,7 +52,7 @@
 <h4>Text Field: INPUT TYPE=TEXT
 <p>The default vaule of the <attr/TYPE/ attribute is <code/TEXT/,
-indicating a single line text entry fields. (Use the <tag/TEXTAREA/
+indicating a single line text entry field. (Use the <tag/TEXTAREA/
 element for multi-line text fields.)
 <p>Required attributes are:
@@ -62,7 +62,7 @@
-The optional attriubtes are:
+The optional attributes are:
 <tli>MAXLENGTH: constrains the number of characters that can be
RCS file: /afs/,v
retrieving revision 1.9
diff -b -w -u -r1.9 glossary.sgm
--- 1.9	1995/08/04 17:50:14
+++ glossary.sgm	1995/09/21 23:46:30
@@ -69,8 +69,9 @@
 <tli>HTML document: An SGML document conforming to this document type
-<tli>hyperlink: a relationship between two anchors, called the tail
-and the head.
+<tli>hyperlink: a relationship between two anchors, called the head
+and the tail. The link goes from the tail to the head. The head
+and tail are also known as destination and source, respectively.
 <tli>markup: Syntactically delimited characters added to the data of a
 document to represent its structure. There are four different kinds of
RCS file: /afs/,v
retrieving revision 1.8
diff -b -w -u -r1.8 head-elts.sgm
--- 1.8	1995/08/04 17:50:15
+++ head-elts.sgm	1995/09/21 23:53:03
@@ -17,12 +17,10 @@
 <h3 id=base>Base Address: BASE
-<p>The optional <tag/BASE/ element allows the address a document to be
-recorded in situations in which the document may be read out of
-context. The required <attr/HREF/ attribute specifies specifies the
-base URI (see <hdref refid=hyperlink>) for navigating the document,
-overriding any context otherwise known to the user agent. The value of
-the <attr/HREF/ attribute must be an absolute URI.
+<p>The optional <tag/BASE/ element provides a base address for
+interpreting relative URLs when the document is read out of context
+(see <hdref refid=hyperlink>). The value of the <attr/HREF/ attribute
+must be an absolute URI.
 <h3>Keyword Index: ISINDEX
@@ -33,12 +31,13 @@
 <h3>Link: LINK
 <p>The <tag/LINK/ element represents a hyperlink (see <hdref
-refid=hyperlink>). It has the same attributes as the <tag/A/ element
-(see <hdref refid=a>).
+refid=hyperlink>).  Any number of LINK elements may occur in the
+<tag/HEAD/ element of an HTML document.  It has the same attributes as
+the <tag/A/ element (see <hdref refid=a>).
 <p>The <tag/LINK/ element is typically used to indicate authorship,
 related indexes and glossaries, older or more recent versions,
-style sheets, document hierarchy etc.
+document hierarchy, associated resources such as style sheets, etc.
 <h3>Associated Meta-information: META
@@ -59,7 +58,9 @@
 contents&mdash;concatenated as a comma-separated list&mdash;is the value
 associated with that name.
 <note>The <tag/META/ element should not be used where a specific
-element, such as <tag/TITLE/, would be more appropriate.
+element, such as <tag/TITLE/, would be more appropriate. Rather
+than a <tag/META/ element with a URI as the value of the <attr/CONTENT/
+attribute, use a <tag/LINK/ element.
 <p>HTTP servers may read the content of the document <tag/HEAD/ to
@@ -124,7 +125,7 @@
 <h3>Next Id: NEXTID
 <p> The <tag/NEXTID/ element is included for historical reasons only.
-HTML document should not contain <tag/NEXTID/ elements.
+HTML documents should not contain <tag/NEXTID/ elements.
 <p> The <tag/NEXTID/ element gives a hint for the name to use for a
 new <tag/A/ element when editing an HTML document. It should be
RCS file: /afs/,v
retrieving revision 1.11
diff -b -w -u -r1.11 html-mime.sgm
--- 1.11	1995/06/15 20:16:56
+++ html-mime.sgm	1995/09/21 23:46:32
@@ -1,4 +1,4 @@
-<!-- $Id: html-mime.sgm,v 1.11 1995/06/15 20:16:56 connolly Exp $ -->
+<!-- $Id: html-mime.sgm,v 1.12 1995/09/21 23:46:32 connolly Exp $ -->
 <h1>HTML as an Internet Media Type
 An HTML user agent allows users to interact with resources which have
@@ -46,7 +46,7 @@
 used to represent the HTML document as a sequence of octets. The
 default value is outside the scope of this specification; but for
 example, the default is <code/US-ASCII/ in the context of MIME mail,
-and <code/ISO-8859-1/ in the context of HTTP.
+and <code/ISO-8859-1/ in the context of HTTP [HTTP].
RCS file: /afs/,v
retrieving revision 1.12
diff -b -w -u -r1.12 html-sgml.sgm
--- 1.12	1995/08/04 17:50:18
+++ html-sgml.sgm	1995/09/21 23:46:33
@@ -1,4 +1,4 @@
-<!-- $Id: html-sgml.sgm,v 1.12 1995/08/04 17:50:18 connolly Exp $ -->
+<!-- $Id: html-sgml.sgm,v 1.13 1995/09/21 23:46:33 connolly Exp $ -->
 <h1>HTML as an Application of SGML
 <p>HTML is an application of ISO 8879:1986 &mdash; Standard
@@ -101,7 +101,7 @@
-Some of the elements are delimited explicity by tags, while the
+Some of the elements are delimited explicitly by tags, while the
 boundaries of others are inferred. The <tag/HTML/ element contains a
 <tag/HEAD/ element and a <tag/BODY/ element. The <tag/HEAD/ contains
 <tag/TITLE/, which is explicitly delimited by start- and end-tags.
@@ -190,10 +190,10 @@
 Some elements only have a start-tag without an end-tag. For example,
-to create a line break, you use the <code/&lt;BR>/ tag.  Additionally,
+to create a line break, use the <code/&lt;BR>/ tag.  Additionally,
 the end tags of some other elements, such as Paragraph
 (<code>&lt;/P></>), List Item (<code>&lt;/LI></>), Definition Term
-(<code>&lt;/DT></>), and Definition Description (<code>&lt;DD></>)
+(<code>&lt;/DT></>), and Definition Description (<code>&lt;/DD></>)
 elements, may be omitted.
 The content of an element is a sequence of data character strings and nested 
@@ -211,7 +211,7 @@
 A name consists of a letter followed by letters, digits, periods, or
 hyphens. The length of a name is limited to 72 characters by the
-<code/NAMELEN/ parameter in the SGML delcaration for HTML, <hdref
+<code/NAMELEN/ parameter in the SGML declaration for HTML, <hdref
 refid=decl>.  Element and attribute names are not case sensitive, but
 entity names are. For example, <code>&lt;BLOCKQUOTE></>,
 <code>&lt;BlockQuote></>, and <code>&lt;blockquote></> are equivalent,
RCS file: /afs/,v
retrieving revision 1.13
diff -b -w -u -r1.13 html-spec.sgm
--- 1.13	1995/08/04 17:50:20
+++ html-spec.sgm	1995/09/21 23:53:08
@@ -1,13 +1,13 @@
 <!doctype spaper public "-//Houston//DTD snafu5//EN" [
-<!-- $Id: html-spec.sgm,v 1.13 1995/08/04 17:50:20 connolly Exp $ -->
+<!-- $Id: html-spec.sgm,v 1.16 1995/09/21 23:53:08 connolly Exp $ -->
 <!entity % u.phrases "file|dns|tag|attr|uri|mbox">
 <!entity status SYSTEM "draft-status.sgm">
 <!entity stat "Internet Draft">
-<!entity date "August 4, 1995">
-<!entity filename CDATA "&#60;draft-ietf-html-spec-05.txt&#62;">
+<!entity date "September 22, 1995">
+<!entity filename CDATA "&#60;draft-ietf-html-spec-06.txt&#62;">
 <!entity intro system "intro.sgm">
RCS file: /afs/,v
retrieving revision 1.29
diff -b -w -u -r1.29 html.dtd
--- 1.29	1995/08/04 17:50:22
+++ html.dtd	1995/09/21 23:30:19
@@ -3,7 +3,7 @@
         Document Type Definition for the HyperText Markup Language
 		 (HTML DTD)
-	$Id: html.dtd,v 1.29 1995/08/04 17:50:22 connolly Exp $
+	$Id: html.dtd,v 1.30 1995/09/21 23:30:19 connolly Exp $
 	Author: Daniel W. Connolly <[log in to unmask]>
 	See Also: html.decl, html-1.dtd
@@ -41,7 +41,7 @@
 <!ENTITY % HTML.Deprecated "INCLUDE"
 	-- Certain features of the language are necessary for
 	   compatibility with earlier versions of the specification,
-	   but they tend to be used an implemented inconsistently,
+	   but they tend to be used and implemented inconsistently,
 	   and their use is deprecated. This feature test entity
 	   enables a document type definition that eliminates
 	   these features.
@@ -145,11 +145,11 @@
 <!-- <I>        Italic text                             -->
 <!-- <EM>       Emphasized phrase                       -->
-<!-- <STRONG>   Strong emphais                          -->
+<!-- <STRONG>   Strong emphasis                         -->
 <!-- <CODE>     Source code phrase                      -->
 <!-- <SAMP>     Sample text or characters               -->
 <!-- <KBD>      Keyboard phrase, e.g. user input        -->
-<!-- <VAR>      Variable phrase or substituable         -->
+<!-- <VAR>      Variable phrase or substitutable        -->
 <!-- <CITE>     Name or title of cited work             -->
 <!ENTITY % pre.content "#PCDATA | A | HR | BR | %font | %phrase">
@@ -529,7 +529,7 @@
 <!-- <HEAD>     Document head   -->
         %SDAFORM; "Ti"    >
@@ -576,9 +576,9 @@
         NAME        NAME    #IMPLIED
         CONTENT     CDATA   #REQUIRED    >
-<!-- <META>                     Generic Metainformation         -->
+<!-- <META>                     Generic Meta-information        -->
 <!-- <META HTTP-EQUIV=...>      HTTP response header name       -->
-<!-- <META NAME=...>      	Metainformation name            -->
+<!-- <META NAME=...>      	Meta-information name           -->
 <!-- <META CONTENT="...">       Associated information          -->
 <!--======= Document Structure =================-->
RCS file: /afs/,v
retrieving revision 1.9
diff -b -w -u -r1.9 hyperlink.sgm
--- 1.9	1995/08/04 17:50:24
+++ hyperlink.sgm	1995/09/21 23:53:09
@@ -5,10 +5,10 @@
 allows the user to navigate these hyperlinks.
 <p> A hyperlink is a relationship between two anchors, called the head
-and the tail of the hyperlink[DEXTER]. Each anchor is addressed, or
-uniquely identified, by an absolute Uniform Resource Identifier (URI),
+and the tail of the hyperlink[DEXTER]. Anchors are identified
+by an anchor address: an absolute Uniform Resource Identifier (URI),
 optionally followed by a '#' and a sequence of characters called a
-fragment identifier, as per [RELURL]. For example:
+fragment identifier. For example:
@@ -22,10 +22,6 @@
 identifier, if present, refers to some view on, or portion of the
-<p>An HTML user agent begins navigation with an absolute URI, called
-the base URI, and an HTML document that is a representation of the
-resource identified by the base URI.
 <p> Each of the following markup constructs indicates the tail anchor
 of a hyperlink or set of hyperlinks:
@@ -38,16 +34,19 @@
 <li> <tag/FORM/ elements with <code/METHOD=GET/.
-<p>These markup constructs refer to head anchors either directly by
-means of an absolute URI, or indirectly by means of a relative URI,
-which must be combined with the base URI as in [RELURL] to determine
-the address of the head anchor. The markup may also include fragment
-identifiers, separeted from the URI by a '#' character.
+<p>These markup constructs refer to head anchors by a URI, either
+absolute or relative, or a fragment identifier, or both.
+<p>In the case of a relative URI, the absolute URI in the address of
+the head anchor is the result of combining the relative URI with a
+base absolute URI as in [RELURL]. The base document is taken from the
+document's <tag/BASE/ element, if present; else, it is determined as
+in [RELURL].
 <h2>Accessing Resources
 <p>Once the address of the head anchor is determined, the user agent
-may obtain a representation of the resource, for example as in [URL].
+may obtain a representation of the resource.
 <p>For example, if the base URI is <code>http://host/x/y.html</> and
 the document contains:
@@ -58,14 +57,9 @@
 <p> then the user agent uses the URI
-<code>http://host/icons/abc.gif</> to access the resource linked from
-the <tag/IMG/ element.
+<code>http://host/icons/abc.gif</> to access the resource, as in
-<p>If the URI in the address of the head anchor is the same as the
-base URI, then the base document is sufficient as a representation of
-the resource. A user agent must <emph/not/, for example, use any network
-information retrieval protocols to obtain a new representation of the
 <h2 id=traverse>Activation of Hyperlinks
@@ -77,11 +71,7 @@
 <p> To activate a link, the user agent obtains a representation of the
 resource identified in the address of the head anchor. If the
 representation is another HTML document, navigation may begin again
-with this new document. The base URI for navigation is taken from the
-head anchor by default; however, any <tag/BASE/ tag in the destination
-document overrides this default. The process of obtaining the
-destination document may also override the base URI, as in the case of
-an HTTP <code/URI:/ header or redirection transaction.
+with this new document.
 <h2 id=image-present>Simultaneous Presentation of Image Resources
@@ -98,7 +88,7 @@
 <h2>Fragment Identifiers
 Any characters following a <code/#/ character in a hypertext address
-constitute a fragment identifier. As a degenerate case, an address of
+constitute a fragment identifier. In particular, an address of
 the form <code/#fragment/ refers to an anchor in the same document.
 The meaning of fragment identifiers depends on the media type of the
RCS file: /afs/,v
retrieving revision 1.12
diff -b -w -u -r1.12 intro.sgm
--- 1.12	1995/06/15 20:17:08
+++ intro.sgm	1995/09/21 23:46:38
@@ -1,4 +1,4 @@
-<!-- $Id: intro.sgm,v 1.12 1995/06/15 20:17:08 connolly Exp $ -->
+<!-- $Id: intro.sgm,v 1.13 1995/09/21 23:46:38 connolly Exp $ -->
 The HyperText Markup Language (HTML) is a simple data format
@@ -13,9 +13,17 @@
 HTML has been in use by the World-Wide Web (WWW) global information
-initiative since 1990. This specification corresponds to the
-capabilities of HTML in common use prior to June 1994 and referred to
-as "HTML 2.0".
+initiative since 1990. Previously, informal documentation on HTML has
+been available from a number of sources on the Internet.  This
+specification brings together, clarifies, and formalizes a set of
+features that roughly corresponds to the capabilities of HTML in
+common use prior to June 1994. A number of new features to HTML are
+being proposed and experimented in the Internet community.
+This document thus defines a HTML 2.0 (to distinguish it from the
+previous informal specifications). Future (generally upwardly
+compatible) versions of HTML with new features will be released with
+higher version numbers.
 HTML is an application of ISO Standard 8879:1986 <emph>Information
 Processing Text and Office Systems; Standard Generalized Markup
RCS file: /afs/,v
retrieving revision 1.5
diff -b -w -u -r1.5 lists.sgm
--- 1.5	1995/06/15 20:17:10
+++ lists.sgm	1995/09/21 23:46:39
@@ -9,8 +9,8 @@
 <h3>Unordered List: UL, LI
-<p>The <tag/UL/ represents a list of items &mdash; typically a
-bulleted list.
+<p>The <tag/UL/ represents a list of items &mdash; typically rendered
+as a bulleted list.
 <p>The content of a <tag/UL/ element is a sequence of <tag/LI/
 elements. For example:
RCS file: /afs/,v
retrieving revision 1.8
diff -b -w -u -r1.8 phrase.sgm
--- 1.8	1995/06/15 20:17:11
+++ phrase.sgm	1995/09/21 23:46:42
@@ -41,7 +41,7 @@
 <p>The <tag/CODE/ element indicates an example of code, typically
 rendered in a mono-spaced font. The <tag/CODE/ element is intended
 for short words or phrases of code; the <tag/PRE/ block
-structuring element (<hdref refid=pre>) is more apropriate for
+structuring element (<hdref refid=pre>) is more appropriate for
 multiple-line listings. For example:
@@ -83,7 +83,7 @@
 typically rendered in bold. For example:
-<strong>STOP</strong>, or I'll say "<strong>STOP</strong>" again!.
+<strong>STOP</strong>, or I'll say "<strong>STOP</strong>" again!
 <h4>Variable: VAR
@@ -155,7 +155,8 @@
 <tli>REL: The <attr/REL/ attribute gives the relationship(s) described
 by the hyperlink. The value is a whitespace separated list of
-relationship names.
+relationship names. The semantics of link relationships are not
+specified in this document.
 <tli>REV: same as the REL attribute, but the semantics of the
 relationship are in the reverse direction. A link from A to B with
RCS file: /afs/,v
retrieving revision 1.4
diff -b -w -u -r1.4 pubtext.sgm
RCS file: /afs/,v
retrieving revision 1.10
diff -b -w -u -r1.10 references.sgm
--- 1.10	1995/08/04 17:50:27
+++ references.sgm	1995/09/21 23:46:45
@@ -8,7 +8,7 @@
 <tli>[URL]: T. Berners-Lee, L. Masinter, and M. McCahill. "Uniform
 Resource Locators (URL)."  RFC 1738, CERN,
-Xerox PARC, University of Minnesota, October 1994.
+Xerox PARC, University of Minnesota, December 1994.
 <tli>[HTTP]: T. Berners-Lee, R. T. Fielding, and H. Frystyk

Back to: Top of Message | Previous Page | Main HTML-WG Page



CataList Email List Search Powered by the LISTSERV Email List Manager