Architecture of the World Wide Web, Volume One - The Diigo Meta page

• 24 Nov 09
  

  Arno Hollosi

  web w3c architecture webdev specification c02web uri

• 26 Jul 09
  

  Kenyth Zeng

  w3c architecture www spec toread

• 11 Jul 09
  

  Maik Schmidt

  internet architecture www

• 10 Jul 09
  

  Architecture of the World Wide Web, Volume One

  web architecture w3c standards rest reference www uri

• 11 Apr 09
  

  Mike Fruchter
• 24 Oct 08
  

  Hassan Ibraheem
• 20 Sep 08
  

  James Burke

  w3c uri standards web2.0 www

• 19 Aug 08
  

  praphul chandra

  semantic web architecture

  • 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.
  • 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.
  • 9 more annotations...
  • • The global scope of URIs promotes
      large-scale "network effects": the value of an identifier increases
      the more it is used consistently
    • Global naming
      leads to global network effects.
    • The choice of syntax for global
      identifiers is somewhat arbitrary; it is their global scope that is
      important.
    • 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.
    • To benefit from and
      increase the value of the World Wide Web, agents should provide
      URIs as identifiers for resources.
    • 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.
    • By design a URI identifies one
      resource. We do not limit the scope of what might be a resource.
    • It is conventional on the hypertext Web to
      describe Web pages, images, product catalogs, etc. as “resources”.
    • 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
• 04 Jul 08
  

  Bharath M
• 05 Apr 08
  

  akoyako :-)

  Architecture of the World Wide Web, Volume One
  W3C Recommendation 15 December 2004
  
  This version:
  http://www.w3.org/TR/2004/REC-webarch-20041215/
  Latest version:
  http://www.w3.org/TR/webarch/
  Previous version:
  http://www.w3.org/TR/2004/PR-webarch-20041105/
  
  Editors:
  Ian Jacobs, W3C
  Norman Walsh, Sun Microsystems, Inc.
  Authors:
  See acknowledgments (§8).
  
  Please refer to the errata for this document, which may include some normative corrections.
  
  See also translations.
  
  Copyright © 2002-2004 W3C ® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.
  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.
  Status of this document
  
  This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
  
  This is the 15 December 2004 Recommendation of “Architecture of the World Wide Web, Volume One.” This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and

  w3c webdev architecture

• 03 Apr 08
  

  Spencer Turner

  architecture rest specification standards volume w3c web webdev

• 

  akui :-)

  webarchitecture

  • Architecture of the
    World Wide Web, Volume One

  • 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.

• 06 Feb 08
  

  juandesant

  architecture berners-lee bray internet w3c web

• 02 Nov 07
  

  Steven Yamanaka

  web software architecture

• 25 Sep 07
  

  David Slattery

  Reference architecture

• 02 Aug 07
  

  Mats Svensson

  HTTP programming web webdev

• 15 Jul 07
  

  prakashswami
  • this architecture document
    discusses the core design components of the Web.
  • referred to as resources, are
    identified by global identifiers called Uniform Resource
    Identifiers (URI).
  • 14 more annotations...
  • • 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
    • grouping bits into eight-bit
      units (octets)
    • 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.
    • The global scope of URIs promotes
      large-scale "network effects": the value of an identifier increases
      the more it is used consistently
    • Social and technical solutions have
      been devised to help avoid URI collision
    • For instance, when transcribing a URI,
      agents should not gratuitously percent-encode characters.
    • 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.
    • 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)
    • Error recovery means that an
      agent does not repair an error condition but continues processing
      by addressing the fact that the error has occurred.
    • 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.
    • 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
    • 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.
    • An application
      developer or specification author SHOULD NOT require networked
      retrieval of representations each time they are referenced.
    • 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.
• 

  Peter Murray

  http imported oaiore specification standards web webarchitecture webdev webstandards

• 19 May 07
  

  Aaron Stockton

  design development geek network programming reference resources tech usability web2.0 webdesign webdev

• 06 Feb 07
  

  Alain Van Kerckhoven

  references standards webmastering

• 24 Oct 06
  

  Vladislav Zlobin

  ia

• 24 Aug 06
  

  toxi

  future paper rdf standards webdev

• 13 Jul 06
  

  Michael C. Harris

  web w3c

• 11 Jul 06
  

  kay

  rest standards w3c

• 09 Jul 06
  

  craig hancock

  architecture information interesting internet it recommendations reference resources rest semweb specs standard standards study technology theory to-read toread vocabulary w3c web web2.0 webdev whitepaper www

• 26 Jun 06
  

  James

  timbray uri web writing

• 07 Jun 06
  

  brian moffatt

  w3c webdesign

• 25 Apr 06
  

  Jonathan Broad

  web architecture http uri

• 10 Oct 05
  

  Hrvoje Šimić

  w3c web2.0 webeng rest

• 22 Jun 05
  

  Nick Gall

  URIs are fundamental to web architecture. Identifiers that are not URIs are "terminal nodes on the Web".

  W3C

  • 5.4. Protocol-based Interoperability
    
    The Web follows Internet tradition in that its important interfaces are defined in terms of protocols, by specifying the syntax, semantics, and sequencing constraints of the messages interchanged. Protocols designed to be resilient in the face of widely varying environments have helped the Web scale and have facilitated communication across multiple trust boundaries. Traditional application programming interfaces (APIs) do not always take these constraints into account, nor should they be required to. One effect of protocol-based design is that the technology shared among agents often lasts longer than the agents themselves.
    
    It is common for programmers working with the Web to write code that generates and parses these messages directly. It is less common, but not unusual, for end users to have direct exposure to these messages. It is often desirable to provide users with access to format and protocol details: allowing them to 01Cview source,01D whereby they may gain expertise in the workings of the underlying system.
  • When a representation of one resource contains a reference to another resource, expressed with a URI identifying that other resource, this constitutes a link between the two resources. Additional metadata may also form part of the link (see [XLink10], for example). Note: In this document, the term "link" generally means "relationship", not "physical connection".
    
    Good practice: Link identification
    
    A specification SHOULD provide ways to identify links to other resources, including to secondary resources (via fragment identifiers).
    
    Formats that allow content authors to use URIs instead of local identifiers promote the network effect: the value of these formats grows with the size of the deployed Web.
    
    Good practice: Web linking
    
    A specification SHOULD allow Web-wide linking, not just internal document linking.
    
    Good practice: Generic URIs
    
    A specification SHOULD allow content authors to use URIs without constraining them to a limited set of URI schemes.
    
    What agents do with a hypertext link is not constrained by Web architecture and may depend on application context. Users of hypertext links expect to be able to navigate among representations by following links.
    
    Good practice: Hypertext links
    
    A data format SHOULD incorporate hypertext links if hypertext is the expected user interface paradigm.
    
    Data formats that do not allow content authors to create hypertext links lead to the creation of "terminal nodes" on the Web.
• 14 Jun 05
  

  Sander van Zoest

  www world wide web architecture URI w3c

• 23 Jan 05
  

  Laurent Somers

  Programming

• 03 Jan 05
  

  Robin Millette

  standards

  • 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.
• 17 Dec 04
  

  planetoid hsu

  web_dev

• 16 Dec 04
  

  Derek Mahar

  web

Page Comments

• 
  James on 2006-06-26
  Could be worth reading, mentions GUID's

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.