You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
638 lines
25 KiB
638 lines
25 KiB
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
|
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
|
<html>
|
|
<head>
|
|
<title>Web Characterization Terminology & Definitions Sheet</title>
|
|
<link rel="stylesheet" type="text/css"
|
|
href="http://www.w3.org/StyleSheets/TR/W3C-WD">
|
|
</head>
|
|
<body lang="en">
|
|
|
|
<div class="head">
|
|
|
|
<a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home"
|
|
alt="W3C" height="48" width="72" border="0">
|
|
</a>
|
|
|
|
<h1>Web Characterization Terminology & Definitions Sheet</h1>
|
|
|
|
<h2>W3C Working Draft 24-May-1999</h2>
|
|
<dl>
|
|
<dt>This version:</dt>
|
|
<dd>
|
|
<a
|
|
href="http://www.w3.org/1999/05/WCA-terms/01">http://www.w3.org/1999/05/WCA-terms/01</a>
|
|
</dd>
|
|
<dt>Latest version:</dt>
|
|
<dd>
|
|
<a
|
|
href="http://www.w3.org/1999/05/WCA-terms/">http://www.w3.org/1999/05/WCA-terms/</a>
|
|
</dd>
|
|
<dt>Editors:</dt>
|
|
<dd>
|
|
Brian Lavoie <<a href="mailto:lavoie@oclc.org">lavoie@oclc.org</a>>,
|
|
</dd>
|
|
<dd>
|
|
Henrik Frystyk Nielsen <<a href="mailto:frystyk@w3.org">frystyk@w3.org</a>>
|
|
</dd>
|
|
</dl>
|
|
|
|
<a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
|
|
© 1999 <a href="http://www.w3.org/">W3C</a> (<a
|
|
href="http://www.lcs.mit.edu/">MIT</a>, <a
|
|
href="http://www.inria.fr/">INRIA</a>, <a
|
|
href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
|
|
<a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
|
|
<a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
|
|
use</a> and <a
|
|
href="http://www.w3.org/Consortium/Legal/copyright-software">software
|
|
licensing</a> rules apply.
|
|
<hr title="Separator for header">
|
|
|
|
</div>
|
|
|
|
<h2><a name="abstract"></a>Abstract</h2>
|
|
|
|
In characterizing the structure and content of the Web, it is necessary to
|
|
establish precise semantics for Web concepts. The Web has proceeded for a
|
|
surprisingly long time without consistent definitions for concepts which have
|
|
become part of the common vernacular, such as "Web site" or "Web page". This
|
|
can lead to a great deal of confusion when attempting to develop, interpret,
|
|
and compare Web metrics.
|
|
|
|
<p>This document represents an effort on the part of the W3C Web
|
|
Characterization Activity to establish a shared understanding of key Web
|
|
concepts. The primary goal in preparing this document was to develop a common
|
|
interpretation for terminology related to Web characterization research.
|
|
However, it is hoped that the Web community at large will also benefit from
|
|
the enumeration and definition of important Web concepts.</p>
|
|
|
|
<h2><a name="status"></a>Status of this document</h2>
|
|
|
|
This document is a working draft for review by W3C members and other
|
|
interested parties. It reflects rough consensus of the W3C Web
|
|
Characterization Activity Working Group. We do not claim the set of terms
|
|
defined in this Working Draft to be exhaustive nor (despite our efforts) that
|
|
all definitions are applicable in all situations. The purpose of this Working
|
|
Draft is to bring clarity to the terms often used when talking about the Web
|
|
as well as to encourage discussion of these and other terms. It is expected
|
|
that future changes will be elaborations on the concepts contained in this
|
|
document, rather than changes in the concepts themselves. Please send comments
|
|
to the <<a href="mailto:www-wca@w3.org">www-wca@w3.org</a>> mailing list
|
|
which is archived at "<a
|
|
href="http://lists.w3.org/Archives/Public/www-wca/">http://lists.w3.org/Archives/Public/www-wca/</a><a></a>"
|
|
|
|
<p>Information on the W3C Web Characterization Activity is located at "<a
|
|
href="http://www.w3.org/WCA/">http://www.w3.org/WCA/</a>". A list of current
|
|
W3C Recommendations and other technical documents can be found at "<a
|
|
href="http://www.w3.org/TR/">http://www.w3.org/TR/</a>".</p>
|
|
|
|
<h2><a name="contents"></a>Table of contents</h2>
|
|
<dl>
|
|
<dt><a href="#PRIMITIVE">1. Primitive Elements</a></dt>
|
|
<dt><a href="#WEBSCOPE">2. The Scope of the Web from Perspective of Web
|
|
Characterization</a></dt>
|
|
<dd><dl>
|
|
<dt><a href="#WEBCLIENTS">2.1 Web Clients</a></dt>
|
|
<dt><a href="#WEBSERVERS">2.2 Web Servers</a></dt>
|
|
<dt><a href="#RESOURCESTRUCTURE">2.3 Resource Structure</a></dt>
|
|
</dl>
|
|
</dd>
|
|
<dt><a href="#References">3. References</a></dt>
|
|
</dl>
|
|
|
|
<h2><a name="PRIMITIVE">1. Primitive Elements</a></h2>
|
|
|
|
Primitive elements are general concepts and terms that can be used to describe
|
|
an information space like the Web. These terms are not necessarily limited to
|
|
resources accessible via any particular access mechanism nor are they
|
|
guaranteed to be accessible via the Internet.
|
|
|
|
<p>In this context we use them to describe the information space known as
|
|
<em>the Web</em>. However, in addition to illustrating the scope of the Web in
|
|
general, the reason why we mention them here is that they are needed to define
|
|
a more <a href="#WEBSCOPE">restrictive set of terms used in Web
|
|
characterization research</a> which we can measure and define a set of metrics
|
|
for.</p>
|
|
|
|
<h3><a name="Resource">Resource</a></h3>
|
|
|
|
<p>The <a href="http://www.rfc-editor.org/rfc/rfc2396.txt">URI
|
|
specification</a> describes a <a
|
|
href="http://www.rfc-editor.org/rfc/rfc2396.txt">resource</a> as the common
|
|
term for "...anything that has identity. Familiar examples include an
|
|
electronic document, an image, a service (e.g., "today's weather report for
|
|
Los Angeles"), as well as a collection of other resources. Not all resources
|
|
are network "retrievable"; e.g., human beings, corporations, and bound books
|
|
in a library can also be considered resources..." (see also the term <a
|
|
href="#Resource2">Web Resource</a>).</p>
|
|
|
|
<p><em><strong>Examples:</strong> Web page, collection of Web pages, service
|
|
that provides information from a database, e-mail message, Java classes
|
|
...</em></p>
|
|
|
|
<h3><a name="URI">URI</a></h3>
|
|
|
|
<p>The <a href="http://www.rfc-editor.org/rfc/rfc2396.txt">URI
|
|
specification</a> defines a <a
|
|
href="http://www.rfc-editor.org/rfc/rfc2396.txt">Uniform Resource Identifier
|
|
(URI)</a> as a compact string of characters for identifying an abstract or
|
|
physical <a href="#Resource">resource</a>.</p>
|
|
|
|
<h3><a name="Resource1">Resource Manifestation</a></h3>
|
|
|
|
A resource manifestation is a rendition of a resource at a specific point in
|
|
time and space. A conceptual mapping exists between a resource and a resource
|
|
manifestation (or set of manifestations), in the sense that the resource has
|
|
certain properties - e.g., its URI, its intended purpose, etc. - which are
|
|
inherited by each manifestation, although the specific structure, form, and
|
|
content of the manifestation may vary according to factors such as the
|
|
environment in which it is displayed, the time it is accessed, etc. Regardless
|
|
of the form the manifestation's rendering ultimately takes, the conceptual
|
|
mapping to the resource is preserved.
|
|
|
|
<p><em><strong>Note:</strong> For historical reasons, HTTP/1.x calls a
|
|
manifestation for an "entity"</em><em>.</em></p>
|
|
|
|
<p><em><strong>Examples:</strong> real-time information accessed from a news
|
|
Web site on a particular day, up-to-the-minute stock quotes, a rendering of a
|
|
multimedia Web page accessed with a particular client ...</em></p>
|
|
|
|
<h3><a name="Link">Link</a></h3>
|
|
|
|
<p>A link expresses one or more (explicit or implicit) relationships between
|
|
two or more resources.</p>
|
|
|
|
<p><em><strong>Note:</strong> The type of the relationship can describe
|
|
relationships like "authored by", "embedded", etc. Types can themselves be
|
|
identified by URIs as for example is the case for </em><a
|
|
href="/RDF/"><em>RDF</em></a><em>.</em></p>
|
|
|
|
<p><em><strong>Examples:</strong> An HTML </em><code><em><a
|
|
href="http://www.w3.org/Protocols/#News">...</a></em></code><em> element,
|
|
an HTML <code><img src=<http://www.w3.org/icons/w3c-home"></code>
|
|
element.</em></p>
|
|
|
|
<h3><a name="Anchor">Anchor</a></h3>
|
|
|
|
<p>An area within a resource that can be the source or destination of zero,
|
|
one or more <a href="#Link">links</a>. An anchor may refer to the whole
|
|
resource, particular parts of the resource, or to particular manifestations of
|
|
the resource.</p>
|
|
|
|
<p><em><strong>Examples:</strong> An HTML </em><code><em><a
|
|
name="http://www.w3.org/Protocols/#News">...</a></em></code><em>
|
|
element.</em></p>
|
|
|
|
<h3><a name="Client">Client</a></h3>
|
|
|
|
The role adopted by an application when it is retrieving and/or rendering
|
|
resources or resource manifestations.
|
|
|
|
<p><em><strong>Examples:</strong> A Web browser, an e-mail reader, a Usenet
|
|
reader ...</em></p>
|
|
|
|
<h3><a name="Server">Server</a></h3>
|
|
|
|
The role adopted by an application when it is supplying resources or resource
|
|
manifestations.
|
|
|
|
<p><em><strong>Examples:</strong> An HTTP server, a file server, etc
|
|
...</em></p>
|
|
|
|
<h3><a name="Proxy">Proxy</a></h3>
|
|
|
|
<p>A proxy is an intermediary which acts as both a server and a client for the
|
|
purpose of retrieving resources or resource manifestations on behalf of other
|
|
clients. Clients using a proxy know the proxy is present and that it is an
|
|
intermediary.</p>
|
|
|
|
<p><em><strong>Examples:</strong> An HTTP firewall proxy ...</em></p>
|
|
|
|
<h3><a name="Gateway">Gateway</a></h3>
|
|
|
|
<p>A gateway is an intermediary which acts as a server on behalf of some other
|
|
server with the purpose of supplying resources or resource manifestations from
|
|
that other server. Clients using a gateway know the gateway is present but
|
|
does not know that it is an intermediary.</p>
|
|
|
|
<p><em><strong>Examples:</strong> An HTTP to FTP gateway</em></p>
|
|
|
|
<h3><a name="Message">Message</a></h3>
|
|
|
|
A unit of communication exchanged between equivalent network layers or
|
|
services, located at different hosts.
|
|
|
|
<p><em><strong>Examples:</strong> A datagram sent from one Internet layer to
|
|
another, an e-mail sent from one e-mail reader and received at another
|
|
...</em></p>
|
|
|
|
<h3><a name="Request">Request</a></h3>
|
|
|
|
A message describing an atomic operation to be carried out in the context of a
|
|
specified resource.
|
|
|
|
<p><em><strong>Examples:</strong> HTTP GET, POST, PUT, and HEAD requests
|
|
...</em></p>
|
|
|
|
<h3><a name="Response">Response</a></h3>
|
|
|
|
A message containing the result of an executed request.
|
|
|
|
<p><em><strong>Examples:</strong> An HTML document, a server error message
|
|
...</em></p>
|
|
|
|
<h3><a name="User">User</a></h3>
|
|
|
|
The principal using a client to interactively retrieve and render resources or
|
|
resource manifestations.
|
|
|
|
<p><em><strong>Examples:</strong> A person using a Web browser, a person using
|
|
an e-mail reader, a person using a CRT terminal emulator ...</em></p>
|
|
|
|
<h3><a name="Publisher">Publisher</a></h3>
|
|
|
|
<p>The principal responsible for the publication of a given resource and for
|
|
the mapping between the resource and any of its resource manifestations. See
|
|
also the term <a href="#site1">Web Site Publisher</a></p>
|
|
|
|
<p><em><strong>Examples:</strong> A person writing an e-mail message, a person
|
|
composing a Web page</em></p>
|
|
|
|
<h2><a name="WEBSCOPE">2. The Scope of the Web from the Perspective of Web
|
|
Characterization</a></h2>
|
|
|
|
<p>The primitive elements defined above are useful when talking about the Web
|
|
in general but are too broad in practice to enable us to characterize the Web
|
|
with the desired level of rigor. This does not mean that we do not consider
|
|
the general terms important or interesting, but that we need a mechanism for
|
|
limiting the scope of the problem of characterizing the Web.</p>
|
|
|
|
<p>Therefore, we define the following terms to address the question of "What
|
|
is the Web?" from the perspective of Web Characterization. For the purposes of
|
|
Web Characterization research, the Web may be viewed as consisting of three
|
|
components: the core, the neighborhood, and the periphery:</p>
|
|
|
|
<p style="text-align: center"><img src="Web-WCA" alt="Scope of the Web from
|
|
WCA's perspective"></p>
|
|
|
|
<p>where</p>
|
|
|
|
<h3><a name="Core">Web Core</a></h3>
|
|
|
|
The collection of resources residing on the Internet that can be accessed
|
|
using any implemented version of HTTP as part of the protocol stack (or its
|
|
equivalent), either directly or via an intermediary.
|
|
|
|
<p><em><strong>Notes:</strong> By the term "or its equivalent" we consider any
|
|
version of HTTP that is currently implemented as well as any new standards
|
|
which may replace HTTP (HTTP-NG, for example). Also, we include any protocol
|
|
stack including HTTP at any level, for example HTTP running over SSL.</em></p>
|
|
|
|
<h3><a name="Resource2">Web Resource</a></h3>
|
|
|
|
<p>A resource, identified by a URI, that is a member of the <a
|
|
href="#Core">Web Core</a>.</p>
|
|
|
|
<p><em><strong>Note:</strong> The URI identifying the Web Resource does not
|
|
itself have to be found within the Web Core. That is, a URI written on a bus
|
|
identifying a resource that is a member of the </em><a href="#Core"><em>Web
|
|
Core</em></a><em> identifies a Web Resource.</em></p>
|
|
|
|
<h3><a name="Resource3">Web Resource Manifestation</a></h3>
|
|
|
|
<p>A <a href="#Resource1">resource manifestation</a> generated by a <a
|
|
href="#Resource2">Web resource</a>.</p>
|
|
|
|
<h3><a name="Neighborho">Web Neighborhood</a></h3>
|
|
|
|
<p>The collection of <a href="#Resource">resources</a> directly <a
|
|
href="#Link">linked</a> from a <a href="#Resource2">Web resource</a>.</p>
|
|
|
|
<h3><a name="Web-access">Web Neighborhood Resource</a></h3>
|
|
|
|
A resource, identified by a URI, that is a member of the <a
|
|
href="#Neighborho">Web Neighborhood</a>.
|
|
|
|
<p><em><strong>Examples:</strong> An "<code>ftp</code>" link within an HTML
|
|
document which can be accessed via HTTP, a "<code>mailto</code>" link within
|
|
an HTML document which can be accessed via HTTP.</em></p>
|
|
|
|
<h3><a name="Periphery">Web Periphery</a></h3>
|
|
|
|
<p>The collection of resources on the Web which is <em>not</em> part of the <a
|
|
href="#Core">Web Core</a> or the <a href="#Neighborho">Web
|
|
Neighborhood</a>.</p>
|
|
|
|
<h2><a name="WEBCLIENTS">2.1 Web Clients</a></h2>
|
|
|
|
<p>Concepts relating to the process of accessing Web resources and render <a
|
|
href="#Resource3">Web resource manifestations</a>.</p>
|
|
|
|
<h3><a name="Client1">Web Client</a></h3>
|
|
|
|
A client that is capable of accessing Web resources by issuing requests and
|
|
render responses containing Web resource manifestations.
|
|
|
|
<p><em><strong>Examples:</strong> A Web browser, a harvester, a spider
|
|
...</em></p>
|
|
|
|
<h3><a name="Click">Web Request</a></h3>
|
|
|
|
<p>A Web request is a <a href="#Request">request</a> issued by a <a
|
|
href="#Client1">Web client</a>. A Web request can be described as either:</p>
|
|
<dl>
|
|
<dt>Explicit Web request:</dt>
|
|
<dd>
|
|
A request that is initiated manually by the <a href="#User">user</a>.
|
|
</dd>
|
|
<dt>Implicit Web request:</dt>
|
|
<dd>
|
|
A request that is initiated transparently by the <a href="#Client1">Web
|
|
client</a>, without manual intervention on the part of the user, as an
|
|
ancillary event corresponding to an explicit Web request.
|
|
</dd>
|
|
</dl>
|
|
|
|
<p>and as either:</p>
|
|
<dl>
|
|
<dt>Embedded Web request:</dt>
|
|
<dd>
|
|
A request for dereferencing a URI embedded within a Web resource
|
|
manifestation: e.g., following the <a href="#Link">link</a> in an HTML
|
|
document, etc.
|
|
</dd>
|
|
<dt>User-input Web request:</dt>
|
|
<dd>
|
|
A request for dereferencing a URI supplied by the user directly to the Web
|
|
client: e.g., typed into the address window, bookmarks, history, etc.
|
|
</dd>
|
|
</dl>
|
|
|
|
<p><strong><em>Examples:</em></strong><em> a) A user follows a link appearing
|
|
in a HTML document (explicit, embedded Web request). The Web client retrieves
|
|
the requested HTML document, and also makes an additional request for an image
|
|
referenced in the HTML document (implicit, embedded Web request); b) A user
|
|
reads the URI printed on a bus and feeds it to the Web client (explicit,
|
|
user-input Web request).</em></p>
|
|
|
|
<h3><a name="Client2">Web Request Header</a></h3>
|
|
|
|
<p>The request header contains information about the request, information
|
|
about the client itself, and potentially information about any resource
|
|
manifestation included in the request.</p>
|
|
|
|
<p><em><strong>Examples:</strong><a href="request.txt"> Sample HTTP request
|
|
header</a></em></p>
|
|
|
|
<h3 id="Request1">Web Request Body</h3>
|
|
|
|
<p>The request body (if any) of an HTTP request is used to carry the payload
|
|
of the HTTP message.</p>
|
|
|
|
<h3><a name="User1">User Session</a></h3>
|
|
|
|
A delimited set of user clicks across one or more Web servers.
|
|
|
|
<p><em>Example: At a library, a patron sits down at a public Internet-access
|
|
terminal, accesses one or more Web resources, then relinquishes control of the
|
|
terminal to another patron.</em></p>
|
|
|
|
<h3><a name="Episode">Episode</a></h3>
|
|
|
|
A subset of related user clicks that occur within a user session.
|
|
|
|
<p><em>Example: Continuing the previous example, the library patron accesses a
|
|
weather report (episode 1), checks stock prices (episode 2), then downloads a
|
|
patch for his operating system (episode 3).</em></p>
|
|
|
|
<h2><a name="WEBSERVERS">2.2 Web Servers</a></h2>
|
|
|
|
Concepts relating to the process of supplying Web resource manifestations.
|
|
|
|
<h3><a name="Server3">Web Server</a></h3>
|
|
|
|
A server that provides access to Web resources and which supplies Web resource
|
|
manifestations to the requestor.
|
|
|
|
<h3><a name="Response1">Web Response</a></h3>
|
|
|
|
<p>A Web response is a <a href="#Response">response</a> issued by a <a
|
|
href="#Server3">Web server</a>.</p>
|
|
|
|
<h3><a name="Server4">Web Response Header</a></h3>
|
|
|
|
The response header contains information about the response, information about
|
|
the server itself, and potentially information about any resource
|
|
manifestation which may or may not be included in the response.
|
|
|
|
<p><em><strong>Examples:</strong> <a href="response.txt">Sample HTTP Response
|
|
Header</a></em></p>
|
|
|
|
<h3><a name="Server5">Web Response Body</a></h3>
|
|
|
|
The response body (if any) of an HTTP response is used to carry the payload of
|
|
the HTTP message.
|
|
|
|
<h3><a name="Server1">Server Session</a></h3>
|
|
|
|
<p>A collection of user clicks to a single Web server during a user session.
|
|
Also called a visit.</p>
|
|
|
|
<h3><a name="Cookie">Cookie</a></h3>
|
|
|
|
Data sent by a Web server to a Web client, to be stored locally by the client
|
|
and sent back to the server on subsequent requests.
|
|
|
|
<p><em>Example: When the Web site of an online retail store is accessed for
|
|
the first time by a particular client, a unique hashcode is sent back to the
|
|
client to be stored locally. Then, when the client requests URLs from the
|
|
site, the hashcode is appended to the URL request, allowing the Web site
|
|
administrators to track the surfing pattern of the customer through the
|
|
site.</em> </p>
|
|
|
|
<h2><a name="RESOURCESTRUCTURE">2.3 Resource Structures</a></h2>
|
|
|
|
The following concepts relates to the structure of Web content.
|
|
|
|
<h3><a name="page">Web page</a></h3>
|
|
|
|
A collection of information, consisting of one or more Web resources, intended
|
|
to be rendered simultaneously, and identified by a single URI. More
|
|
specifically, a Web page consists of a <a href="#Resource2">Web resource</a>
|
|
with zero, one, or more embedded <a href="#Resource2">Web resources</a>
|
|
intended to be rendered as a single unit, and referred to by the URI of the
|
|
one Web resource which is not embedded.
|
|
|
|
<p><em><strong>Examples:</strong> An image file, an applet, and an HTML file
|
|
identified and accessed through a single URI, and rendered simultaneously by a
|
|
Web client.</em></p>
|
|
|
|
<p><em><strong>Note:</strong> The components of a Web page can reside at
|
|
different network locations. The location of the Web page, however, is
|
|
determined by the URI identifying the page.</em></p>
|
|
|
|
<p><em><strong>Note:</strong> The scope of a Web page is limited to the
|
|
collection of Web resources which are displayed simultaneously by requesting
|
|
the Web page's URI. The components of a Web page actually rendered in a page
|
|
view is client-dependent.</em></p>
|
|
|
|
<h3><a name="Page">Page View</a></h3>
|
|
|
|
Visual rendering of a Web page in a specific client environment at a specific
|
|
point in time.
|
|
|
|
<p><em><strong>Examples:</strong> Displaying a particular Web page in Internet
|
|
Explorer is a pageview; displaying the same page in Netscape Navigator is a
|
|
different page view.</em></p>
|
|
|
|
<h3><a name="Home">Host Page</a></h3>
|
|
|
|
A Web page identified by a URI containing an <code><authority></code>
|
|
component but where the <code><path></code> component is either empty or
|
|
simply consists of a single <code>"/"</code> only.
|
|
|
|
<p><em><strong>Examples:</strong> The Web pages identified by
|
|
<code>http://www.w3.org</code> and <code>http://www.cern.ch</code> are host
|
|
pages</em></p>
|
|
|
|
<h3><a name="site">Web site</a></h3>
|
|
|
|
A collection of interlinked Web pages, including a <a href="#Home">host
|
|
page</a>, residing at the same network location. "Interlinked" is understood
|
|
to mean that any of a Web site's constituent <a href="#page">Web pages</a> can
|
|
be accessed by following a sequence of references beginning at the site's <a
|
|
href="#Home">host page</a>; spanning zero, one or more <a href="#page">Web
|
|
pages</a> located at the same site; and ending at the Web page in question.
|
|
|
|
<p><strong><em>Examples:</em></strong><em> The Web page consisting of the
|
|
article "Thought Paper on Automatic Recharacterization" is part of the <a
|
|
href="http://www.w3.org">W3C Web site</a>, since it satisfies the two
|
|
properties mentioned above. First, it resides at the same network location as
|
|
the W3C </em><a href="#Home"><em>host page,</em></a><em>
|
|
</em><code><em>http://www.w3.org</em></code><em>. Second, we can begin at the
|
|
W3C host page (</em><code><em>http://www.w3.org</em></code><em>) and follow a
|
|
sequence of internal links, ending at the article: specifically:</em></p>
|
|
<ol>
|
|
<li>
|
|
<em><code>http://www.w3.org</code> to <code>http://www.w3.org/WCA/</code>,
|
|
and</em>
|
|
</li>
|
|
<li>
|
|
<em><code>http://www.w3.org/WCA/</code> to
|
|
<code>http://www.w3.org/WCA/1998/12/aut_char.html</code></em>
|
|
</li>
|
|
</ol>
|
|
|
|
<p><em><strong>Notes:</strong> It is not uncommon for Web sites to be
|
|
duplicated, or mirrored, on multiple physical host machines (e.g., for load
|
|
balancing purposes). Typically, it is immaterial to the client (or user) which
|
|
host machine is used to access the Web site.</em><em> In this case, it may be
|
|
useful to consider this collection of "physical" Web sites, located at
|
|
multiple host machines, as one "logical" Web site.</em><em> This is possible
|
|
in the case where a single domain name is mapped to each of the host machines;
|
|
the logical Web site can then be identified using the unique domain name.
|
|
</em><em>If there is no unique domain name that can be applied to the
|
|
collection of duplicate sites, we consider each physical host machine as a
|
|
separate Web site.</em></p>
|
|
|
|
<h3><a name="Independen">Independent Web Page</a></h3>
|
|
|
|
A Web page that is not part of the Web site associated with its network
|
|
location. Specifically, it is not possible to reach the Web page in question
|
|
by traversing a sequence of links internal to the Web site, beginning at the
|
|
<a href="#Home">host page</a>.
|
|
|
|
<p><em><strong>Examples:</strong> If a page is mounted on a Web server, but is
|
|
not linked to by any page on the Web site associated with the server, then the
|
|
page is like an "island" on the Web. The only way the page can be accessed is
|
|
through explicit knowledge of its URI. </em></p>
|
|
|
|
<h3><a name="site1">Web Site Publisher</a></h3>
|
|
|
|
A person or corporate body that is the primary claimant to the rewards or
|
|
benefits resulting from usage of the Web site, incurs at least part of the
|
|
costs necessary to produce and distribute the site, and exercises editorial
|
|
control over the finished form of the Web site and its content. See also the
|
|
term <a href="#Publisher">publisher</a>.
|
|
|
|
<p><em><strong>Examples:</strong> The W3C is the publisher of the site located
|
|
at http://www.w3.org/ ...</em></p>
|
|
|
|
<h3><a name="Subsite">Subsite</a></h3>
|
|
|
|
A cluster of Web pages within a Web site, that is maintained by a different
|
|
publisher than that of the parent Web site, or host site. The subsite
|
|
publisher exercises editorial control over the Web pages comprising the
|
|
subsite, perhaps restrained by some broad guidelines imposed by the host site
|
|
publisher.
|
|
|
|
<p><em><strong>Examples:</strong> An Internet service provider supplying
|
|
hosting services to its customers. All of the customers' Web sites may be
|
|
located at the same IP address, but nevertheless represent logically
|
|
independent sites (and, in the case of virtual hosting, may even have distinct
|
|
domain names).</em></p>
|
|
|
|
<h3><a name="Collection">Web Collection</a></h3>
|
|
|
|
A portion or section of a <a href="#site">Web site</a>, consisting of two or
|
|
more Web pages, that represents a non-trivial, self-contained resource, but is
|
|
still maintained by the same publisher of the overall <a href="#site">Web
|
|
site</a>.
|
|
|
|
<p><em><strong>Examples:</strong> Web journal, electronic monograph, photo
|
|
gallery ...</em></p>
|
|
|
|
<h3><a name="Supersite">Supersite</a></h3>
|
|
|
|
A single, logical <a href="#site">Web site</a> that extends over multiple
|
|
network locations, but is intended to be viewed as a single <a
|
|
href="#site">Web site</a>. It is transparent to the user that the site is
|
|
distributed over multiple locations. A single <a href="#Home">host page</a>
|
|
applies to the entire supersite.
|
|
|
|
<p><em><strong>Examples:</strong> The resources available from a particular
|
|
entity may be distributed over multiple servers, but users access the
|
|
supersite through one <a href="#Home">host page</a>, and view the distributed
|
|
resources as one logical site.</em></p>
|
|
|
|
<h2><a name="References" href="#contents">4. References</a></h2>
|
|
|
|
<p>Other useful places to look for terminology sections are</p>
|
|
<ul>
|
|
<li>
|
|
<a href="/Terms">Hypertext terms defined by Tim Berners-Lee in 1995</a>
|
|
</li>
|
|
<li>
|
|
<a href="/Architecture/Terms.html">Another set of hypertext terms defined by
|
|
Dan Connolly in 1996</a>
|
|
</li>
|
|
<li>
|
|
<a
|
|
href="http://www.w3.org/Protocols/HTTP/1.1/draft-ietf-http-v11-spec-rev-06.txt">Hypertext
|
|
Transfer Protocol 1.1 Specification</a>
|
|
</li>
|
|
<li>
|
|
<a href="http://www.w3.org/TR/REC-html40/">Hypertext Markup Language 4.0
|
|
Specification</a>
|
|
</li>
|
|
<li>
|
|
<a href="http://info.internet.isi.edu/in-notes/rfc/files/rfc2396.txt">Uniform
|
|
Resource Identifier Specification</a>
|
|
</li>
|
|
</ul>
|
|
|
|
<p></p>
|
|
<hr title="Separator from footer">
|
|
|
|
<address>
|
|
|
|
<p>@(#) $Id: 01.html,v 1.46 1999/05/24 13:58:18 frystyk Exp $</p>
|
|
</address>
|
|
|
|
<p></p>
|
|
</body>
|
|
</html>
|