Scribd Logo
Upload

Welcome to Scribd!

  • 132 views

    Uri Twist99

    Uploaded by

    ahgase snxxsnxx
    The document discusses the history and design of Uniform Resource Identifiers (URIs). It describes how URIs evolved from web addresses to become a simple and extensible means of identification. A URI provides a unique identifier for a resource, which can be anything with a conceptual identity or membership, including documents, services, collections of other resources, and non-networked objects. The design principles of URIs are that they be uniform, extensible, hierarchical, and transcribable to allow identification of diverse resources in a consistent way on the web. However, some failures in the design include URIs not being easily spoken aloud and an over-reliance on the Domain Name System.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd

    Uri Twist99

    Uploaded by

    ahgase snxxsnxx
    132 views12 pages
    The document discusses the history and design of Uniform Resource Identifiers (URIs). It describes how URIs evolved from web addresses to become a simple and extensible means of identification. A URI provides a unique identifier for a resource, which can be anything with a conceptual identity or membership, including documents, services, collections of other resources, and non-networked objects. The design principles of URIs are that they be uniform, extensible, hierarchical, and transcribable to allow identification of diverse resources in a consistent way on the web. However, some failures in the design include URIs not being easily spoken aloud and an over-reliance on the Domain Name System.

    Original Description:

    Original Title

    uri_twist99.ppt

    Copyright

    © © All Rights Reserved

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the history and design of Uniform Resource Identifiers (URIs). It describes how URIs evolved from web addresses to become a simple and extensible means of identification. A URI provides a unique identifier for a resource, which can be anything with a conceptual identity or membership, including documents, services, collections of other resources, and non-networked objects. The design principles of URIs are that they be uniform, extensible, hierarchical, and transcribable to allow identification of diverse resources in a consistent way on the web. However, some failures in the design include URIs not being easily spoken aloud and an over-reliance on the Domain Name System.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    132 views12 pages

    Uri Twist99

    Uploaded by

    ahgase snxxsnxx
    The document discusses the history and design of Uniform Resource Identifiers (URIs). It describes how URIs evolved from web addresses to become a simple and extensible means of identification. A URI provides a unique identifier for a resource, which can be anything with a conceptual identity or membership, including documents, services, collections of other resources, and non-networked objects. The design principles of URIs are that they be uniform, extensible, hierarchical, and transcribable to allow identification of diverse resources in a consistent way on the web. However, some failures in the design include URIs not being easily spoken aloud and an over-reliance on the Domain Name System.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 12

    Uniform Resource Identifiers

    Roy T. Fielding
    University of California, Irvine
    http://www.ics.uci.edu/~fielding/
    URI History
    Web Addresses [Berners-Lee] 1990
    Universal Document Identifiers 1992
    Universal Resource Identifiers RFC 1630
    URL: Locators RFC 1736,1738,1808
    URN: Names RFC 1737,2141
    Uniform Resource Identifiers RFC 2396
    A simple and extensible means of identification
    http://www.ics.uci.edu/~fielding/talks/
    mailto:[email protected]

    2
    Etymology of URI … Identifier
    Establishing identity by reference
    name, handle, moniker, location, …
    global scope
    Simple
    Just a string of common characters
    Transcribable
    bar napkins, advertisements, and e-mail
    a sequence of characters, not coded character octets
    Usable
    no additional entry barrier to deployment and use
    3
    Etymology of URI … Resource
    What we want to identify: Resources
    match the semantics of a hypermedia reference
    ephemeral and persistent information
    new and existing information sources
    A resource can be anything that has identity
    a document or image
    a service, e.g., “today’s weather in Irvine”
    a collection of other resources
    non-networked objects (e.g., people)

    4
    More precisely, a resource is …
    A temporally varying membership function MR(t)
    that, for each time t, maps to some set of
    semantically equivalent values
    Values may be resource representations or
    identifiers to other resources
    Can map to the empty set, allowing references to
    be made to a concept before any realization of
    that concept exists
    The resource is the conceptual mapping, not the
    entity that corresponds to that mapping at t
    5
    Representations of a Resource
    The Web is designed to manipulate and transfer
    representations of a resource
    A single resource may be associated with
    multiple representations (content negotiation)
    A representation is in the form of a media type
    provides information for this resource
    provides potential hypermedia state transitions
    Most representations can be cached
    GET URI transfers representation, not resource

    6
    Etymology of URI … Uniform
    Uniformity allows
    different types of resource identification within
    a single protocol element
    uniform semantic interpretation of common
    syntactic elements; shared implementations
    relative syntactic interpretation
    independent of scheme
    extensibility for new identification schemes
    bounds variability along common paths, making it
    easier to extend the use of URI to new applications

    7
    Uniform Extensibility
    URI scheme allows new types to be defined
    without affecting old uses
    file, news, http, telnet, gopher, wais, ftp, …
    Naturally lends itself to table-driven
    implementations
    browser uses table to select handler
    handler can be dynamically loaded/downloaded
    Unfortunately,
    some people haven’t figured that out yet

    8
    Uniform Hierarchy
    Scheme defines interpretation and structure
    <scheme>:<scheme-specific-part>
    Hierarchical when desired [Engelbart]
    <scheme>://<authority>/<path>?<query>
    <scheme>:/<segment>/<segment>/<segment>
    <scheme>:<opaque_string>
    Name components may be meaningful
    http://www.ics.uci.edu/~fielding/talks/
    Hierarchy enables relative URI

    9
    Relative URI
    An identifier that obtains global scope when
    interpreted relative to a base URI
    Only valid when the base URI is well-defined
    Saves space
    Allows document content to be partially independent
    of its location and accessibility
    Document trees (groups of inter-related documents)
    can be moved without changing embedded URI
    Documents can be shared by multiple access schemes
    and servers

    10
    Design Failures
    Transcribable, but not easily spoken
    aitch tee tee pee colon slash slash double-you
    double-you double-you dot eye see es dot you see eye
    dot ee dee you slash tilde fielding slash
    Hierarchical path assumes only one root
    not true for FTP resources, leading to ambiguity
    gopher path isn’t layered left-to-right
    Reliance on DNS as only naming authority
    vanity hostname explosion
    flat namespace under dot com
    11
    Questions?

    Places to see for more URI design information:

    http://www.ics.uci.edu/pub/ietf/uri/
    http://www.w3.org/Addressing/Addressing.html
    http://www.w3.org/DesignIssues/

    Slides:
    http://www.ics.uci.edu/~fielding/talks/

    12

    You might also like