Skip to main content

Architecture of the World Wide Web, Volume One

Popularity Report

Total Popularity Score: 0
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...

Rank

Groups (1)

  • internet_linguistics

    Internet-Linguistics

    7 members,123 bookmarks

    explore the use of internet and webtools to help preserve and promote indigenous languages

Bookmark History

Saved by 28 people (9 private), first by anonymouse user on 2006-04-24


Public Comment

on 2006-06-26 by jamesb

Could be worth reading, mentions GUID's

Public Sticky notes

this architecture document discusses the core design components of the Web.

Highlighted by prakashswami

referred to as resources, are identified by global identifiers called Uniform Resource Identifiers (URI).

Highlighted by prakashswami

HTTP, for example, typically transmits a single octet stream plus metadata, and uses the "Content-Type" and "Content-Encoding" header fields to further identify the format of the representation

Highlighted by prakashswami

grouping bits into eight-bit units (octets)

Highlighted by prakashswami

Web makes use of a single global identification system: the URI. URIs are a cornerstone of Web architecture, providing identification that is common across the Web.

Highlighted by prakashswami

The global scope of URIs promotes large-scale "network effects": the value of an identifier increases the more it is used consistently

Highlighted by prakashswami

Social and technical solutions have been devised to help avoid URI collision

Highlighted by prakashswami

A corollary of Metcalfe's Principle (the "network effect") is that the value of a given resource can be measured by the number and value of other resources in its network neighborhood, that is, the resources that link to it.

Highlighted by prakashswami

The Web's protocols (including HTTP, FTP, SOAP, NNTP, and SMTP) are based on the exchange of messages. A message may include data as well as metadata about a resource (such as the "Alternates" and "Vary" HTTP headers), the message data, and the message itself (such as the "Transfer-encoding" HTTP header)

Highlighted by prakashswami

Error recovery means that an agent does not repair an error condition but continues processing by addressing the fact that the error has occurred.

Highlighted by prakashswami

The browser reads the headers, learns from the "Content-Type" field that the Internet media type of the representation is "image/jpeg", reads the sequence of octets that make up the representation data, and renders the image.

Highlighted by prakashswami

An application developer or specification author SHOULD NOT require networked retrieval of representations each time they are referenced.

Highlighted by prakashswami

Binary data formats are those in which portions of the data are encoded for direct use by computer processors, for example 32 bit little-endian two's-complement and 64 bit IEEE double-precision floating-point

Highlighted by prakashswami

In principle, all data can be represented using textual formats. In practice, some types of content (e.g., audio and video) are generally represented using binary formats.

Highlighted by prakashswami

Extensibility is not free. Providing hooks for extensibility is one of many requirements to be factored into the costs of language design. Experience suggests that the long term benefits of a well-designed extensibility mechanism generally outweigh the costs.

Highlighted by prakashswami

For instance, when transcribing a URI, agents should not gratuitously percent-encode characters.

Highlighted by prakashswami

Architecture of the World Wide Web, Volume One

Highlighted by akuiaku

Abstract

The World Wide Web uses relatively simple technologies with sufficient scalability, efficiency and utility that they have resulted in a remarkable information space of interrelated resources, growing across languages, cultures, and media. In an effort to preserve these properties of the information space as the technologies evolve, this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space. We relate core design components, constraints, and good practices to the principles and properties they support.

Highlighted by akuiaku

this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space.

Highlighted by praphulcs

In order to communicate internally, a community agrees (to a reasonable extent) on a set of terms and their meanings. One goal of the Web, since its inception, has been to build a global community in which any party can share information with any other party. To achieve this goal, the Web makes use of a single global identification system: the URI.

Highlighted by praphulcs

The global scope of URIs promotes large-scale "network effects": the value of an identifier increases the more it is used consistently

Highlighted by praphulcs

Global naming leads to global network effects.

Highlighted by praphulcs

The choice of syntax for global identifiers is somewhat arbitrary; it is their global scope that is important.

Highlighted by praphulcs

There are substantial benefits to participating in the existing network of URIs, including linking, bookmarking, caching, and indexing by search engines, and there are substantial costs to creating a new identification system that has the same properties as URIs.

Highlighted by praphulcs

The global scope of URIs promotes large-scale "network effects": the value of an identifier increases the more it is used consistently (for example, the more it is used in hypertext links (§4.4)).

Highlighted by marido

To benefit from and increase the value of the World Wide Web, agents should provide URIs as identifiers for resources.

Highlighted by praphulcs

A resource should have an associated URI if another party might reasonably want to create a hypertext link to it, make or refute assertions about it, retrieve or cache a representation of it, include all or part of it by reference into another representation, annotate it, or perform other operations on it.

Highlighted by praphulcs

By design a URI identifies one resource. We do not limit the scope of what might be a resource.

Highlighted by praphulcs

It is conventional on the hypertext Web to describe Web pages, images, product catalogs, etc. as “resources”.

Highlighted by praphulcs

Since the scope of a URI is global, the resource identified by a URI does not depend on the context in which the URI appears

Highlighted by praphulcs

the Web is designed so that agents communicate resource information state through representations, not identifiers. In general, one cannot determine the type of a resource representation by inspecting a URI for that resource.

Highlighted by marido

Resource state may evolve over time. Requiring a URI owner to publish a new URI for each change in resource state would lead to a significant number of broken references. For robustness, Web architecture promotes independence between an identifier and the state of the identified resource.

Highlighted by marido

define RDF properties such as sameAs to assert that two URIs identify the same resource or inverseFunctionalProperty to imply it.

Highlighted by marido

Although persistence in this case is observable as a result of representation retrieval, the term URI persistence is used to describe the desirable property that, once associated with a resource, a URI should continue indefinitely to refer to that resource.

Highlighted by marido