Browse Prior Art Database

URI Design and Ownership (RFC7320)

IP.com Disclosure Number: IPCOM000237791D
Original Publication Date: 2014-Jul-01
Included in the Prior Art Database: 2014-Jul-11
Document File: 18 page(s) / 18K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Nottingham: AUTHOR

Abstract

URIs [RFC3986] very often include structured application data. This might include artifacts from filesystems (often occurring in the path component) and user information (often in the query component). In some cases, there can even be application-specific data in the authority component (e.g., some applications are spread across several hostnames to enable a form of partitioning or dispatch).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 15% of the total text.

Internet Engineering Task Force (IETF)                     M. Nottingham Request for Comments: 7320 BCP: 190                                                       July 2014 Updates: 3986 Category: Best Current Practice ISSN: 2070-1721

                         URI Design and Ownership

Abstract

   Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and    extensible naming system wherein each scheme's specification may    further restrict the syntax and semantics of identifiers using that    scheme."  In other words, the structure of a URI is defined by its    scheme.  While it is common for schemes to further delegate their    substructure to the URI's owner, publishing independent standards    that mandate particular forms of URI substructure is inappropriate,    because that essentially usurps ownership.  This document further    describes this problematic practice and provides some acceptable    alternatives for use in standards.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7320.

Nottingham                Best Current Practice                 [Page 1]
 RFC 7320                  URI Design Ownership                 July 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

     1.1.  Intended Audience . . . . . . . . . . . . . . . . . . . .   4

     1.2.  Notational Conventions  . . . . . . . . . . . . . . . . .   4

   2.  Best Current Practices for Standardizing Structured URIs  . .   4

     2.1.  URI Schemes . . ....