kinlane
8/31/2016 - 7:17 AM

Web Specs

Web Specs

{
  "Internet Engineering Task Force (IETF)": {
    "Request for Comments (RFC)": {
      "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content": {
        "document_name": "RFC 7231",
        "document_uri": "urn:ietf:rfc:7231",
        "online_version": "`http://tools.ietf.org/html/rfc7231`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7231"
      },
      "The telnet URI Scheme": {
        "document_name": "RFC 4248",
        "document_uri": "urn:ietf:rfc:4248",
        "online_version": "`http://tools.ietf.org/html/rfc4248`",
        "abstract": "This document specifies the telnet Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track.",
        "url": "http://webconcepts.info/specs/IETF/RFC/4248"
      },
      "Scheduling Extensions to CalDAV": {
        "document_name": "RFC 6638",
        "document_uri": "urn:ietf:rfc:6638",
        "online_version": "`http://tools.ietf.org/html/rfc6638`",
        "abstract": "This document defines extensions to the Calendaring Extensions to WebDAV (CalDAV) calendar-access feature to specify a standard way of performing scheduling operations with iCalendar-based calendar components. This document defines the calendar-auto-schedule feature of CalDAV.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6638"
      },
      "vCard Format Specification": {
        "document_name": "RFC 6350",
        "document_uri": "urn:ietf:rfc:6350",
        "online_version": "`http://tools.ietf.org/html/rfc6350`",
        "abstract": "This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6350"
      },
      "A Uniform Resource Identifier for Geographic Locations ('geo' URI)": {
        "document_name": "RFC 5870",
        "document_uri": "urn:ietf:rfc:5870",
        "online_version": "`http://tools.ietf.org/html/rfc5870`",
        "abstract": "This document specifies a Uniform Resource Identifier (URI) for geographic locations using the 'geo' scheme name. A 'geo' URI identifies a physical location in a two- or three-dimensional coordinate reference system in a compact, simple, human-readable, and protocol-independent way. The default coordinate reference system used is the World Geodetic System 1984 (WGS-84).",
        "url": "http://webconcepts.info/specs/IETF/RFC/5870"
      },
      "REsource LOcation And Discovery (RELOAD) Base Protocol": {
        "document_name": "RFC 6940",
        "document_uri": "urn:ietf:rfc:6940",
        "online_version": "`http://tools.ietf.org/html/rfc6940`",
        "abstract": "This specification defines REsource LOcation And Discovery (RELOAD), a peer-to-peer (P2P) signaling protocol for use on the Internet. A P2P signaling protocol provides its clients with an abstract storage and messaging service between a set of cooperating peers that form the overlay network. RELOAD is designed to support a P2P Session Initiation Protocol (P2PSIP) network, but can be utilized by other applications with similar requirements by defining new usages that specify the Kinds of data that need to be stored for a particular application. RELOAD defines a security model based on a certificate enrollment service that provides unique identities. NAT traversal is a fundamental service of the protocol. RELOAD also allows access from client nodes that do not need to route traffic or store data for others.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6940"
      },
      "Returning Values from Forms: multipart/form-data": {
        "document_name": "RFC 2388",
        "document_uri": "urn:ietf:rfc:2388",
        "online_version": "`http://tools.ietf.org/html/rfc2388`",
        "abstract": "This specification defines an Internet Media Type, multipart/form-data, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2388"
      },
      "An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors": {
        "document_name": "RFC 5261",
        "document_uri": "urn:ietf:rfc:5261",
        "online_version": "`http://tools.ietf.org/html/rfc5261`",
        "abstract": "Extensible Markup Language (XML) documents are widely used as containers for the exchange and storage of arbitrary data in today's systems. In order to send changes to an XML document, an entire copy of the new version must be sent, unless there is a means of indicating only the portions that have changed. This document describes an XML patch framework utilizing XML Path language (XPath) selectors. These selector values and updated new data content constitute the basis of patch operations described in this document. In addition to them, with basic <add>, <replace>, and <remove> directives a set of patches can then be applied to update an existing XML document.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5261"
      },
      "Constrained RESTful Environments (CoRE) Link Format": {
        "document_name": "RFC 6690",
        "document_uri": "urn:ietf:rfc:6690",
        "online_version": "`http://tools.ietf.org/html/rfc6690`",
        "abstract": "This specification defines Web Linking using a link format for use by constrained web servers to describe hosted resources, their attributes, and other relationships between links. Based on the HTTP Link Header field defined in RFC 5988, the Constrained RESTful Environments (CoRE) Link Format is carried as a payload and is assigned an Internet media type. RESTful refers to the Representational State Transfer (REST) architecture. A well-known URI is defined as a default entry point for requesting the links hosted by a server.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6690"
      },
      "Calendaring Extensions to WebDAV (CalDAV)": {
        "document_name": "RFC 4791",
        "document_uri": "urn:ietf:rfc:4791",
        "online_version": "`http://tools.ietf.org/html/rfc4791`",
        "abstract": "This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format. This document defines the calendar-access feature of CalDAV.",
        "url": "http://webconcepts.info/specs/IETF/RFC/4791"
      },
      "The text/markdown Media Type": {
        "document_name": "RFC 7763",
        "document_uri": "urn:ietf:rfc:7763",
        "online_version": "`http://tools.ietf.org/html/rfc7763`",
        "abstract": "This document registers the text/markdown media type for use with Markdown, a family of plain-text formatting syntaxes that optionally can be converted to formal markup languages such as HTML.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7763"
      },
      "Hypertext Transfer Protocol - HTTP/1.1": {
        "document_name": "RFC 2068",
        "document_uri": "urn:ietf:rfc:2068",
        "online_version": "`http://tools.ietf.org/html/rfc2068`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, object-oriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as HTTP/1.1.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2068"
      },
      "Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)": {
        "document_name": "RFC 5842",
        "document_uri": "urn:ietf:rfc:5842",
        "online_version": "`http://tools.ietf.org/html/rfc5842`",
        "abstract": "This specification defines bindings, and the BIND method for creating multiple bindings to the same resource. Creating a new binding to a resource causes at least one new URI to be mapped to that resource. Servers are required to ensure the integrity of any bindings that they allow to be created.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5842"
      },
      "Hypertext Transfer Protocol (HTTP/1.1): Caching": {
        "document_name": "RFC 7234",
        "document_uri": "urn:ietf:rfc:7234",
        "online_version": "`http://tools.ietf.org/html/rfc7234`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7234"
      },
      "HTTP framework for time-based access to resource states - Memento": {
        "document_name": "RFC 7089",
        "document_uri": "urn:ietf:rfc:7089",
        "online_version": "`http://tools.ietf.org/html/rfc7089`",
        "abstract": "The HTTP-based Memento framework bridges the present and past Web. It facilitates obtaining representations of prior states of a given resource by introducing datetime negotiation and TimeMaps. Datetime negotiation is a variation on content negotiation that leverages the given resource's URI and a user agent's preferred datetime. TimeMaps are lists that enumerate URIs of resources that encapsulate prior states of the given resource. The framework also facilitates recognizing a resource that encapsulates a frozen prior state of another resource.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7089"
      },
      "An HTTP Status Code to Report Legal Obstacles": {
        "document_name": "RFC 7725",
        "document_uri": "urn:ietf:rfc:7725",
        "online_version": "`http://tools.ietf.org/html/rfc7725`",
        "abstract": "This document specifies a Hypertext Transfer Protocol (HTTP) status code for use when resource access is denied as a consequence of legal demands.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7725"
      },
      "Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)": {
        "document_name": "RFC 6764",
        "document_uri": "urn:ietf:rfc:6764",
        "online_version": "`http://tools.ietf.org/html/rfc6764`",
        "abstract": "This specification describes how DNS SRV records, DNS TXT records, and well-known URIs can be used together or separately to locate CalDAV (Calendaring Extensions to Web Distributed Authoring and Versioning (WebDAV)) or CardDAV (vCard Extensions to WebDAV) services.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6764"
      },
      "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing": {
        "document_name": "RFC 7230",
        "document_uri": "urn:ietf:rfc:7230",
        "online_version": "`http://tools.ietf.org/html/rfc7230`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document provides an overview of HTTP architecture and its associated terminology, defines the http and https Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes general security concerns for implementations.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7230"
      },
      "Web Distributed Authoring and Versioning (WebDAV): Redirect Reference Resources": {
        "document_name": "RFC 4437",
        "document_uri": "urn:ietf:rfc:4437",
        "online_version": "`http://tools.ietf.org/html/rfc4437`",
        "abstract": "This specification defines an extension to Web Distributed Authoring and Versioning (WebDAV) to allow clients to author HTTP redirect reference resources whose default response is an HTTP/1.1 3xx (Redirection) status code. A redirect reference makes it possible to access the target resourced indirectly through any URI mapped to the redirect reference resource. This specification does not address remapping of trees of resources or regular expression based redirections. There are no integrity guarantees associated with redirect reference resources. Other mechanisms can also be used to achieve the same functionality as this specification. This specification allows operators to experiment with this mechanism and develop experience on what is the best approach to the problem.",
        "url": "http://webconcepts.info/specs/IETF/RFC/4437"
      },
      "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests": {
        "document_name": "RFC 7232",
        "document_uri": "urn:ietf:rfc:7232",
        "online_version": "`http://tools.ietf.org/html/rfc7232`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7232"
      },
      "Link Relation Types for Simple Version Navigation between Web Resources": {
        "document_name": "RFC 5829",
        "document_uri": "urn:ietf:rfc:5829",
        "online_version": "`http://tools.ietf.org/html/rfc5829`",
        "abstract": "This specification defines a set of link relation types that may be used on Web resources for navigation between a resource and other resources related to version control, such as past versions and working copies.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5829"
      },
      "HTTP Alternate Services": {
        "document_name": "RFC 7838",
        "document_uri": "urn:ietf:rfc:7838",
        "online_version": "`http://tools.ietf.org/html/rfc7838`",
        "abstract": "This document specifies alternative services for HTTP, which allow an origin's resources to be authoritatively available at a separate network location, possibly accessed with a different protocol configuration.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7838"
      },
      "The ALPN HTTP Header Field": {
        "document_name": "RFC 7639",
        "document_uri": "urn:ietf:rfc:7639",
        "online_version": "`http://tools.ietf.org/html/rfc7639`",
        "abstract": "This specification allows HTTP CONNECT requests to indicate what protocol is intended to be used within the tunnel once established, using the ALPN header field.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7639"
      },
      "Atom Syndication Format": {
        "document_name": "RFC 4287",
        "document_uri": "urn:ietf:rfc:4287",
        "online_version": "`http://tools.ietf.org/html/rfc4287`",
        "abstract": "Atom is an XML-based document format that describes lists of related information known as feeds. Feeds are composed of a number of items, known as entries, each with an extensible set of attached metadata. For example, each entry has a title.",
        "url": "http://webconcepts.info/specs/IETF/RFC/4287"
      },
      "HTTP Digest Access Authentication": {
        "document_name": "RFC 7616",
        "document_uri": "urn:ietf:rfc:7616",
        "online_version": "`http://tools.ietf.org/html/rfc7616`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) provides a simple challenge-response authentication mechanism that may be used by a server to challenge a client request and by a client to provide authentication information. This document defines the HTTP Digest Authentication scheme that can be used with the HTTP authentication mechanism.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7616"
      },
      "Atom Publishing Protocol (AtomPub)": {
        "document_name": "RFC 5023",
        "document_uri": "urn:ietf:rfc:5023",
        "online_version": "`http://tools.ietf.org/html/rfc5023`",
        "abstract": "The Atom Publishing Protocol (AtomPub) is an application-level protocol for publishing and editing Web resources. The protocol is based on HTTP transfer of Atom-formatted representations. The Atom format is documented in the Atom Syndication Format.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5023"
      },
      "Uniform Resource Locators (URL)": {
        "document_name": "RFC 1738",
        "document_uri": "urn:ietf:rfc:1738",
        "online_version": "`http://tools.ietf.org/html/rfc1738`",
        "abstract": "This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet.",
        "url": "http://webconcepts.info/specs/IETF/RFC/1738"
      },
      "Hypertext Transfer Protocol (HTTP/1.1): Authentication": {
        "document_name": "RFC 7235",
        "document_uri": "urn:ietf:rfc:7235",
        "online_version": "`http://tools.ietf.org/html/rfc7235`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7235"
      },
      "Naming Things with Hashes": {
        "document_name": "RFC 6920",
        "document_uri": "urn:ietf:rfc:6920",
        "online_version": "`http://tools.ietf.org/html/rfc6920`",
        "abstract": "This document defines a set of ways to identify a thing (a digital object in this case) using the output from a hash function. It specifies a new URI scheme for this purpose, a way to map these to HTTP URLs, and binary and human-speakable formats for these names. The various formats are designed to support, but not require, a strong link to the referenced object, such that the referenced object may be authenticated to the same degree as the reference to it. The reason for this work is to standardise current uses of hash outputs in URLs and to support new information-centric applications and other uses of hash outputs in protocols.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6920"
      },
      "Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol": {
        "document_name": "RFC 3744",
        "document_uri": "urn:ietf:rfc:3744",
        "online_version": "`http://tools.ietf.org/html/rfc3744`",
        "abstract": "This document specifies a set of methods, headers, message bodies, properties, and reports that define Access Control extensions to the WebDAV Distributed Authoring Protocol. This protocol permits a client to read and modify access control lists that instruct a server whether to allow or deny operations upon a resource (such as HyperText Transfer Protocol (HTTP) method invocations) by a given principal. A lightweight representation of principals as Web resources supports integration of a wide range of user management repositories. Search operations allow discovery and manipulation of principals using human names.",
        "url": "http://webconcepts.info/specs/IETF/RFC/3744"
      },
      "Concise Binary Object Representation (CBOR)": {
        "document_name": "RFC 7049",
        "document_uri": "urn:ietf:rfc:7049",
        "online_version": "`http://tools.ietf.org/html/rfc7049`",
        "abstract": "The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7049"
      },
      "Hypertext Transfer Protocol -- HTTP/1.1": {
        "document_name": "RFC 2616",
        "document_uri": "urn:ietf:rfc:2616",
        "online_version": "`http://tools.ietf.org/html/rfc2616`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as HTTP/1.1, and is an update to RFC 2068.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2616"
      },
      "The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)": {
        "document_name": "RFC 7168",
        "document_uri": "urn:ietf:rfc:7168",
        "online_version": "`http://tools.ietf.org/html/rfc7168`",
        "abstract": "The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification does not allow for the brewing of tea, in all its variety and complexity. This paper outlines an extension to HTCPCP to allow for pots to provide networked tea-brewing facilities.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7168"
      },
      "HTTP Origin-Bound Authentication (HOBA)": {
        "document_name": "RFC 7486",
        "document_uri": "urn:ietf:rfc:7486",
        "online_version": "`http://tools.ietf.org/html/rfc7486`",
        "abstract": "HTTP Origin-Bound Authentication (HOBA) is a digital-signature-based design for an HTTP authentication method. The design can also be used in JavaScript-based authentication embedded in HTML. HOBA is an alternative to HTTP authentication schemes that require passwords and therefore avoids all problems related to passwords, such as leakage of server-side password databases.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7486"
      },
      "Session Traversal Utilities for NAT (STUN) Extension": {
        "document_name": "RFC 7635",
        "document_uri": "urn:ietf:rfc:7635",
        "online_version": "`http://tools.ietf.org/html/rfc7635`",
        "abstract": "This document proposes the use of OAuth 2.0 to obtain and validate ephemeral tokens that can be used for Session Traversal Utilities for NAT (STUN) authentication. The usage of ephemeral tokens ensures that access to a STUN server can be controlled even if the tokens are compromised.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7635"
      },
      "xCard: vCard XML Representation": {
        "document_name": "RFC 6351",
        "document_uri": "urn:ietf:rfc:6351",
        "online_version": "`http://tools.ietf.org/html/rfc6351`",
        "abstract": "This document defines the XML schema of the vCard data format.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6351"
      },
      "The 'mailto' URI Scheme": {
        "document_name": "RFC 6068",
        "document_uri": "urn:ietf:rfc:6068",
        "online_version": "`http://tools.ietf.org/html/rfc6068`",
        "abstract": "This document defines the format of Uniform Resource Identifiers (URIs) to identify resources that are reached using Internet mail. It adds better internationalization and compatibility with Internationalized Resource Identifiers to the previous syntax of 'mailto' URIs.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6068"
      },
      "JSON Web Token (JWT)": {
        "document_name": "RFC 7519",
        "document_uri": "urn:ietf:rfc:7519",
        "online_version": "`http://tools.ietf.org/html/rfc7519`",
        "abstract": "JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7519"
      },
      "Additional Link Relation Types": {
        "document_name": "RFC 6903",
        "document_uri": "urn:ietf:rfc:6903",
        "online_version": "`http://tools.ietf.org/html/rfc6903`",
        "abstract": "This specification defines a number of additional link relation types that can be used for a range of purposes in a variety of applications types.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6903"
      },
      "The 'describes' Link Relation Type": {
        "document_name": "RFC 6892",
        "document_uri": "urn:ietf:rfc:6892",
        "online_version": "`http://tools.ietf.org/html/rfc6892`",
        "abstract": "This specification defines the 'describes' link relation type that allows resource representations to indicate that they are describing another resource. In contexts where applications want to associate described resources and description resources, and want to build services based on these associations, the 'describes' link relation type provides the opposite direction of the 'describedby' link relation type, which already is a registered link relation type.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6892"
      },
      "Hypertext Transfer Protocol Version 2": {
        "document_name": "RFC 7540",
        "document_uri": "urn:ietf:rfc:7540",
        "online_version": "`http://tools.ietf.org/html/rfc7540`",
        "abstract": "This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients. This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7540"
      },
      "Transparent Content Negotiation in HTTP": {
        "document_name": "RFC 2295",
        "document_uri": "urn:ietf:rfc:2295",
        "online_version": "`http://tools.ietf.org/html/rfc2295`",
        "abstract": "HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is an extensible negotiation mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2295"
      },
      "WebFinger": {
        "document_name": "RFC 7033",
        "document_uri": "urn:ietf:rfc:7033",
        "online_version": "`http://tools.ietf.org/html/rfc7033`",
        "abstract": "This specification defines the WebFinger protocol, which can be used to discover information about people or other entities on the Internet using standard HTTP methods. WebFinger discovers information for a URI that might not be usable as a locator otherwise, such as account or email URIs.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7033"
      },
      "URI Fragment Identifiers for the text/plain Media Type": {
        "document_name": "RFC 5174",
        "document_uri": "urn:ietf:rfc:5174",
        "online_version": "`http://tools.ietf.org/html/rfc5174`",
        "abstract": "This memo defines URI fragment identifiers for text/plain MIME entities. These fragment identifiers make it possible to refer to parts of a text/plain MIME entity, either identified by character position or range, or by line position or range. Fragment identifiers may also contain information for integrity checks to make them more robust.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5174"
      },
      "Public Key Pinning Extension for HTTP": {
        "document_name": "RFC 7469",
        "document_uri": "urn:ietf:rfc:7469",
        "online_version": "`http://tools.ietf.org/html/rfc7469`",
        "abstract": "This document defines a new HTTP header that allows web host operators to instruct user agents to remember (pin) the hosts' cryptographic identities over a period of time. During that time, user agents (UAs) will require that the host presents a certificate chain including at least one Subject Public Key Info structure whose fingerprint matches one of the pinned fingerprints for that host. By effectively reducing the number of trusted authorities who can authenticate the domain during the lifetime of the pin, pinning may reduce the incidence of man-in-the-middle attacks due to compromised Certification Authorities.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7469"
      },
      "Prefer Header for HTTP": {
        "document_name": "RFC 7240",
        "document_uri": "urn:ietf:rfc:7240",
        "online_version": "`http://tools.ietf.org/html/rfc7240`",
        "abstract": "This specification defines an HTTP header field that can be used by a client to request that certain behaviors be employed by a server while processing a request.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7240"
      },
      "Web Host Metadata": {
        "document_name": "RFC 6415",
        "document_uri": "urn:ietf:rfc:6415",
        "online_version": "`http://tools.ietf.org/html/rfc6415`",
        "abstract": "This specification describes a method for locating host metadata as well as information about individual resources controlled by the host.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6415"
      },
      "Web Linking": {
        "document_name": "RFC 5988",
        "document_uri": "urn:ietf:rfc:5988",
        "online_version": "`http://tools.ietf.org/html/rfc5988`",
        "abstract": "This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5988"
      },
      "Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)": {
        "document_name": "RFC 2324",
        "document_uri": "urn:ietf:rfc:2324",
        "online_version": "`http://tools.ietf.org/html/rfc2324`",
        "abstract": "This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2324"
      },
      "HTTP State Management Mechanism": {
        "document_name": "RFC 2965",
        "document_uri": "urn:ietf:rfc:2965",
        "online_version": "`http://tools.ietf.org/html/rfc2965`",
        "abstract": "This document specifies a way to create a stateful session with Hypertext Transfer Protocol (HTTP) requests and responses. It describes three new headers, Cookie, Cookie2, and Set-Cookie2, which carry state information between participating origin servers and user agents. The method described here differs from Netscape's Cookie proposal [Netscape], but it can interoperate with HTTP/1.0 user agents that use Netscape's method.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2965"
      },
      "Media Resource Control Protocol Version 2 (MRCPv2)": {
        "document_name": "RFC 6768",
        "document_uri": "urn:ietf:rfc:6768",
        "online_version": "`http://tools.ietf.org/html/rfc6768`",
        "abstract": "The Media Resource Control Protocol Version 2 (MRCPv2) allows client hosts to control media service resources such as speech synthesizers, recognizers, verifiers, and identifiers residing in servers on the network. MRCPv2 is not a stand-alone protocol -- it relies on other protocols, such as the Session Initiation Protocol (SIP), to coordinate MRCPv2 clients and servers and manage sessions between them, and the Session Description Protocol (SDP) to describe, discover, and exchange capabilities. It also depends on SIP and SDP to establish the media sessions and associated parameters between the media source or sink and the media server. Once this is done, the MRCPv2 exchange operates over the control session established above, allowing the client to control the media processing resources on the speech resource server.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6768"
      },
      "The 'application/zlib' and 'application/gzip' Media Types": {
        "document_name": "RFC 6713",
        "document_uri": "urn:ietf:rfc:6713",
        "online_version": "`http://tools.ietf.org/html/rfc6713`",
        "abstract": "This document defines the 'application/gzip' and 'application/zlib' media types for compressed data using the gzip and zlib compression formats.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6713"
      },
      "The 'disclosure' Link Relation Type": {
        "document_name": "RFC 6579",
        "document_uri": "urn:ietf:rfc:6579",
        "online_version": "`http://tools.ietf.org/html/rfc6579`",
        "abstract": "This document specifies the 'disclosure' link relation type. It designates a list of IPR disclosures made with respect to the material for which such a relation type is specified.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6579"
      },
      "The GeoJSON Format": {
        "document_name": "RFC 7946",
        "document_uri": "urn:ietf:rfc:7946",
        "online_version": "`http://tools.ietf.org/html/rfc7946`",
        "abstract": "GeoJSON is a geospatial data interchange format based on JavaScript Object Notation (JSON). It defines several types of JSON objects and the manner in which they are combined to represent data about geographic features, their properties, and their spatial extents. GeoJSON uses a geographic coordinate reference system, World Geodetic System 1984, and units of decimal degrees.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7946"
      },
      "The \\data\\ URL scheme": {
        "document_name": "RFC 2397",
        "document_uri": "urn:ietf:rfc:2397",
        "online_version": "`http://tools.ietf.org/html/rfc2397`",
        "abstract": "A new URL scheme, data, is defined. It allows inclusion of small data items as immediate data, as if it had been included externally.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2397"
      },
      "Guidelines and Registration Procedures for URI Schemes": {
        "document_name": "RFC 7595",
        "document_uri": "urn:ietf:rfc:7595",
        "online_version": "`http://tools.ietf.org/html/rfc7595`",
        "abstract": "This document updates the guidelines and recommendations, as well as the IANA registration processes, for the definition of Uniform Resource Identifier (URI) schemes.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7595"
      },
      "The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)": {
        "document_name": "RFC 7538",
        "document_uri": "urn:ietf:rfc:7538",
        "online_version": "`http://tools.ietf.org/html/rfc7538`",
        "abstract": "This document specifies the additional Hypertext Transfer Protocol (HTTP) status code 308 (Permanent Redirect).",
        "url": "http://webconcepts.info/specs/IETF/RFC/7538"
      },
      "HTTP Strict Transport Security (HSTS)": {
        "document_name": "RFC 6797",
        "document_uri": "urn:ietf:rfc:6797",
        "online_version": "`http://tools.ietf.org/html/rfc6797`",
        "abstract": "This specification defines a mechanism enabling web sites to declare themselves accessible only via secure connections and/or for users to be able to direct their user agent(s) to interact with given sites only over secure connections. This overall policy is referred to as HTTP Strict Transport Security (HSTS). The policy is declared by web sites via the Strict-Transport-Security HTTP response header field and/or by other means, such as user agent configuration, for example.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6797"
      },
      "The Secure HyperText Transfer Protocol (S-HTTP)": {
        "document_name": "RFC 2660",
        "document_uri": "urn:ietf:rfc:2660",
        "online_version": "`http://tools.ietf.org/html/rfc2660`",
        "abstract": "This memo describes a syntax for securing messages sent using the Hypertext Transfer Protocol (HTTP), which forms the basis for the World Wide Web. Secure HTTP (S-HTTP) provides independently applicable security services for transaction confidentiality, authenticity/integrity and non-repudiability of origin. The protocol emphasizes maximum flexibility in choice of key management mechanisms, security policies and cryptographic algorithms by supporting option negotiation between parties for each transaction.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2660"
      },
      "Instance Digests in HTTP": {
        "document_name": "RFC 3230",
        "document_uri": "urn:ietf:rfc:3230",
        "online_version": "`http://tools.ietf.org/html/rfc3230`",
        "abstract": "HTTP/1.1 defines a Content-MD5 header that allows a server to include a digest of the response body. However, this is specifically defined to cover the body of the actual message, not the contents of the full file (which might be quite different, if the response is a Content-Range, or uses a delta encoding). Also, the Content-MD5 is limited to one specific digest algorithm; other algorithms, such as SHA-1 (Secure Hash Standard), may be more appropriate in some circumstances. Finally, HTTP/1.1 provides no explicit mechanism by which a client may request a digest. This document proposes HTTP extensions that solve these problems.",
        "url": "http://webconcepts.info/specs/IETF/RFC/3230"
      },
      "The OAuth 1.0 Protocol": {
        "document_name": "RFC 5849",
        "document_uri": "urn:ietf:rfc:5849",
        "online_version": "`http://tools.ietf.org/html/rfc5849`",
        "abstract": "OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5849"
      },
      "Forwarded HTTP Extension": {
        "document_name": "RFC 7239",
        "document_uri": "urn:ietf:rfc:7239",
        "online_version": "`http://tools.ietf.org/html/rfc7239`",
        "abstract": "This document defines an HTTP extension header field that allows proxy components to disclose information lost in the proxying process, for example, the originating IP address of a request or IP address of the proxy on the user-agent-facing interface. In a path of proxying components, this makes it possible to arrange it so that each subsequent component will have access to, for example, all IP addresses used in the chain of proxied HTTP requests. This document also specifies guidelines for a proxy administrator to anonymize the origin of a request.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7239"
      },
      "Time Zone Data Distribution Service": {
        "document_name": "RFC 7808",
        "document_uri": "urn:ietf:rfc:7808",
        "online_version": "`http://tools.ietf.org/html/rfc7808`",
        "abstract": "This document defines a time zone data distribution service that allows reliable, secure, and fast delivery of time zone data and leap-second rules to client systems such as calendaring and scheduling applications or operating systems.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7808"
      },
      "The Atom \\deleted-entry\\ Element": {
        "document_name": "RFC 6271",
        "document_uri": "urn:ietf:rfc:6271",
        "online_version": "`http://tools.ietf.org/html/rfc6271`",
        "abstract": "This specification adds mechanisms to the Atom Syndication Format that publishers of Atom Feed and Entry documents can use to explicitly identify Atom entries that have been removed.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6271"
      },
      "The \\create-form\\ and \\edit-form\\ Link Relations": {
        "document_name": "RFC 6861",
        "document_uri": "urn:ietf:rfc:6861",
        "online_version": "`http://tools.ietf.org/html/rfc6861`",
        "abstract": "RFC 5988 standardized a means of indicating the relationships between resources on the Web. This specification defines link relation types that may be used to express the relationships between a resource and an input form for constructing data submissions.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6861"
      },
      "Feed Paging and Archiving": {
        "document_name": "RFC 5005",
        "document_uri": "urn:ietf:rfc:5005",
        "online_version": "`http://tools.ietf.org/html/rfc5005`",
        "abstract": "Syndicated Web feeds (using formats such as Atom) are often split into multiple documents to save bandwidth, allow sliding window access, or for other purposes. This specification formalizes two types of feeds that can span one or more feed documents; paged feeds and archived feeds. Additionally, it defines complete feeds to cover the case when a single feed document explicitly represents all of the feed's entries.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5005"
      },
      "HTTP Cache-Control Extensions for Stale Content": {
        "document_name": "RFC 5861",
        "document_uri": "urn:ietf:rfc:5861",
        "online_version": "`http://tools.ietf.org/html/rfc5861`",
        "abstract": "This document defines two independent HTTP Cache-Control extensions that allow control over the use of stale responses by caches.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5861"
      },
      "HTTP Extensions for Distributed Authoring - WEBDAV": {
        "document_name": "RFC 2518",
        "document_uri": "urn:ietf:rfc:2518",
        "online_version": "`http://tools.ietf.org/html/rfc2518`",
        "abstract": "This document specifies a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, namespace manipulation, and resource locking (collision avoidance).",
        "url": "http://webconcepts.info/specs/IETF/RFC/2518"
      },
      "JavaScript Object Notation (JSON)": {
        "document_name": "RFC 7159",
        "document_uri": "urn:ietf:rfc:7159",
        "online_version": "`http://tools.ietf.org/html/rfc7159`",
        "abstract": "JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7159"
      },
      "HTTP Header Field X-Frame-Options": {
        "document_name": "RFC 7034",
        "document_uri": "urn:ietf:rfc:7034",
        "online_version": "`http://tools.ietf.org/html/rfc7034`",
        "abstract": "To improve the protection of web applications against clickjacking, this document describes the X-Frame-Options HTTP header field, which declares a policy, communicated from the server to the client browser, regarding whether the browser may display the transmitted content in frames that are part of other web pages.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7034"
      },
      "JSON Web Signature (JWS)": {
        "document_name": "RFC 7515",
        "document_uri": "urn:ietf:rfc:7515",
        "online_version": "`http://tools.ietf.org/html/rfc7515`",
        "abstract": "JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and an IANA registry defined by that specification. Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7515"
      },
      "Problem Details for HTTP APIs": {
        "document_name": "RFC 7807",
        "document_uri": "urn:ietf:rfc:7807",
        "online_version": "`http://tools.ietf.org/html/rfc7807`",
        "abstract": "This document defines a problem detail as a way to carry machine-readable details of errors in a HTTP response, to avoid the need to invent new error response formats for HTTP APIs.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7807"
      },
      "The Hypertext Transfer Protocol (HTTP) Authentication-Info and Proxy-Authentication-Info Response Header Fields": {
        "document_name": "RFC 7615",
        "document_uri": "urn:ietf:rfc:7615",
        "online_version": "`http://tools.ietf.org/html/rfc7615`",
        "abstract": "This specification defines the Authentication-Info and Proxy-Authentication-Info response header fields for use in HTTP authentication schemes which need to return information once the client's authentication credentials have been accepted.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7615"
      },
      "Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)": {
        "document_name": "RFC 3253",
        "document_uri": "urn:ietf:rfc:3253",
        "online_version": "`http://tools.ietf.org/html/rfc3253`",
        "abstract": "This document specifies a set of methods, headers, and resource types that define the WebDAV (Web Distributed Authoring and Versioning) versioning extensions to the HTTP/1.1 protocol. WebDAV versioning will minimize the complexity of clients that are capable of interoperating with a variety of versioning repository managers, to facilitate widespread deployment of applications capable of utilizing the WebDAV Versioning services. WebDAV versioning includes automatic versioning for versioning-unaware clients, version history management, workspace management, baseline management, activity management, and URL namespace versioning.",
        "url": "http://webconcepts.info/specs/IETF/RFC/3253"
      },
      "PKIX over Secure HTTP (POSH)": {
        "document_name": "RFC 7711",
        "document_uri": "urn:ietf:rfc:7711",
        "online_version": "`http://tools.ietf.org/html/rfc7711`",
        "abstract": "Experience has shown that it is difficult to deploy proper PKIX certificates for Transport Layer Security (TLS) in multi-tenanted environments. As a result, domains hosted in such environments often deploy applications using certificates that identify the hosting service, not the hosted domain. Such deployments force end users and peer services to accept a certificate with an improper identifier, resulting in degraded security. This document defines methods that make it easier to deploy certificates for proper server identity checking in non-HTTP application protocols. Although these methods were developed for use in the Extensible Messaging and Presence Protocol (XMPP) as a Domain Name Association (DNA) prooftype, they might also be usable in other non-HTTP application protocols.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7711"
      },
      "HTTP-Enabled Location Delivery (HELD)": {
        "document_name": "RFC 5985",
        "document_uri": "urn:ietf:rfc:5985",
        "online_version": "`http://tools.ietf.org/html/rfc5985`",
        "abstract": "This document defines a Layer 7 Location Configuration Protocol (L7 LCP) and describes the use of HTTP and HTTP/TLS as transports for the L7 LCP. The L7 LCP is used for retrieving location information from a server within an access network. It includes options for retrieving location information in two forms: by value and by reference. The protocol is an extensible application-layer protocol that is independent of the session layer.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5985"
      },
      "A Media Type for XML Patch Operations": {
        "document_name": "RFC 7351",
        "document_uri": "urn:ietf:rfc:7351",
        "online_version": "`http://tools.ietf.org/html/rfc7351`",
        "abstract": "The XML Patch media type application/xml-patch+xml defines an XML document structure for expressing a sequence of patch operations that are applied to an XML document. The XML Patch document format's foundations are defined in RFC 5261, this specification defines a document format and a media type registration, so that XML Patch documents can be labeled with a media type, for example in HTTP conversations. In addition to the media type registration, this specification also updates RFC 5261 in some aspects, limiting these updates to cases where RFC 5261 needed to be fixed, or was hard to understand.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7351"
      },
      "Additional HTTP Status Codes": {
        "document_name": "RFC 6585",
        "document_uri": "urn:ietf:rfc:6585",
        "online_version": "`http://tools.ietf.org/html/rfc6585`",
        "abstract": "This document specifies additional HyperText Transfer Protocol (HTTP) status codes for a variety of common situations.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6585"
      },
      "The Canonical Link Relation": {
        "document_name": "RFC 6596",
        "document_uri": "urn:ietf:rfc:6596",
        "online_version": "`http://tools.ietf.org/html/rfc6596`",
        "abstract": "RFC 5988 specifies a way to define relationships between links on the web. This document describes a new type of such a relationship, canonical, to designate an Internationalized Resource Identifier (IRI) as preferred over resources with duplicative content.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6596"
      },
      "Web Distributed Authoring and Versioning (WebDAV) SEARCH": {
        "document_name": "RFC 5323",
        "document_uri": "urn:ietf:rfc:5323",
        "online_version": "`http://tools.ietf.org/html/rfc5323`",
        "abstract": "This document specifies a set of methods, headers, and properties composing Web Distributed Authoring and Versioning (WebDAV) SEARCH, an application of the HTTP/1.1 protocol to efficiently search for DAV resources based upon a set of client-supplied criteria.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5323"
      },
      "Delta encoding in HTTP": {
        "document_name": "RFC 3229",
        "document_uri": "urn:ietf:rfc:3229",
        "online_version": "`http://tools.ietf.org/html/rfc3229`",
        "abstract": "This document describes how delta encoding can be supported as a compatible extension to HTTP/1.1. Many HTTP (Hypertext Transport Protocol) requests cause the retrieval of slightly modified instances of resources for which the client already has a cache entry. Research has shown that such modifying updates are frequent, and that the modifications are typically much smaller than the actual entity. In such cases, HTTP would make more efficient use of network bandwidth if it could transfer a minimal description of the changes, rather than the entire new instance of the resource. This is called delta encoding.",
        "url": "http://webconcepts.info/specs/IETF/RFC/3229"
      },
      "XML Media Types": {
        "document_name": "RFC 3023",
        "document_uri": "urn:ietf:rfc:3023",
        "online_version": "`http://tools.ietf.org/html/rfc3023`",
        "abstract": "This document standardizes five new media types - text/xml, application/xml, text/xml-external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd - for use in exchanging network entities that are related to the Extensible Markup Language (XML). This document also standardizes a convention (using the suffix '+xml') for naming media types outside of these five types when those media types represent XML MIME (Multipurpose Internet Mail Extensions) entities. XML MIME entities are currently exchanged via the HyperText Transfer Protocol on the World Wide Web, are an integral part of the WebDAV protocol for remote web authoring, and are expected to have utility in many domains.",
        "url": "http://webconcepts.info/specs/IETF/RFC/3023"
      },
      "The Item and Collection Link Relations": {
        "document_name": "RFC 6573",
        "document_uri": "urn:ietf:rfc:6573",
        "online_version": "`http://tools.ietf.org/html/rfc6573`",
        "abstract": "RFC 5988 standardized a means of indicating the relationships between resources on the Web. This specification defines a pair of reciprocal link relation types that may be used to express the relationship between a collection and its members.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6573"
      },
      "PATCH Method for HTTP": {
        "document_name": "RFC 5789",
        "document_uri": "urn:ietf:rfc:5789",
        "online_version": "`http://tools.ietf.org/html/rfc5789`",
        "abstract": "Several applications extending the Hypertext Transfer Protocol (HTTP) require a feature to do partial resource modification. The existing HTTP PUT method only allows a complete replacement of a document. This proposal adds a new HTTP method, PATCH, to modify an existing HTTP resource.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5789"
      },
      "Group Communication for the Constrained Application Protocol (CoAP)": {
        "document_name": "RFC 7390",
        "document_uri": "urn:ietf:rfc:7390",
        "online_version": "`http://tools.ietf.org/html/rfc7390`",
        "abstract": "The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for constrained devices and constrained networks. It is anticipated that constrained devices will often naturally operate in groups (e.g., in a building automation scenario, all lights in a given room may need to be switched on/off as a group). This specification defines how CoAP should be used in a group communication context. An approach for using CoAP on top of IP multicast is detailed based on existing CoAP functionality as well as new features introduced in this specification. Also, various use cases and corresponding protocol flows are provided to illustrate important concepts. Finally, guidance is provided for deployment in various network topologies.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7390"
      },
      "Hypertext Transfer Protocol (HTTP/1.1): Range Requests": {
        "document_name": "RFC 7233",
        "document_uri": "urn:ietf:rfc:7233",
        "online_version": "`http://tools.ietf.org/html/rfc7233`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7233"
      },
      "URI Scheme for Global System for Mobile Communications (GSM) Short Message Service (SMS)": {
        "document_name": "RFC 5724",
        "document_uri": "urn:ietf:rfc:5724",
        "online_version": "`http://tools.ietf.org/html/rfc5724`",
        "abstract": "This memo specifies the Uniform Resource Identifier (URI) scheme sms for specifying one or more recipients for an SMS message. SMS messages are two-way paging messages that can be sent from and received by a mobile phone or a suitably equipped networked device.",
        "url": "http://webconcepts.info/specs/IETF/RFC/5724"
      },
      "An HTTP Extension Framework": {
        "document_name": "RFC 2774",
        "document_uri": "urn:ietf:rfc:2774",
        "online_version": "`http://tools.ietf.org/html/rfc2774`",
        "abstract": "A wide range of applications have proposed various extensions of the HTTP protocol. Current efforts span an enormous range, including distributed authoring, collaboration, printing, and remote procedure call mechanisms. These HTTP extensions are not coordinated, since there has been no standard framework for defining extensions and thus, separation of concerns. This document describes a generic extension mechanism for HTTP, which is designed to address the tension between private agreement and public specification and to accommodate extension of applications using HTTP clients, servers, and proxies. The proposal associates each extension with a globally unique identifier, and uses HTTP header fields to carry the extension identifier and related information between the parties involved in the extended communication.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2774"
      },
      "Atom License Extension": {
        "document_name": "RFC 4946",
        "document_uri": "urn:ietf:rfc:4946",
        "online_version": "`http://tools.ietf.org/html/rfc4946`",
        "abstract": "This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.",
        "url": "http://webconcepts.info/specs/IETF/RFC/4946"
      },
      "Calendar Access Protocol (CAP)": {
        "document_name": "RFC 4324",
        "document_uri": "urn:ietf:rfc:4324",
        "online_version": "`http://tools.ietf.org/html/rfc4324`",
        "abstract": "The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS). At the time of this writing, three vendors are implementing CAP, but it has already been determined that some changes are needed. In order to get implementation experience, the participants felt that a CAP specification is needed to preserve many years of work. Many properties in CAP which have had many years of debate, can be used by other iCalendar protocols.",
        "url": "http://webconcepts.info/specs/IETF/RFC/4324"
      },
      "The WebSocket Protocol": {
        "document_name": "RFC 6455",
        "document_uri": "urn:ietf:rfc:6455",
        "online_version": "`http://tools.ietf.org/html/rfc6455`",
        "abstract": "The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling).",
        "url": "http://webconcepts.info/specs/IETF/RFC/6455"
      },
      "Enrollment over Secure Transport": {
        "document_name": "RFC 7030",
        "document_uri": "urn:ietf:rfc:7030",
        "online_version": "`http://tools.ietf.org/html/rfc7030`",
        "abstract": "This document profiles certificate enrollment for clients using Certificate Management over CMS (CMC) messages over a secure transport. This profile, called Enrollment over Secure Transport (EST), describes a simple, yet functional, certificate management protocol targeting Public Key Infrastructure (PKI) clients that need to acquire client certificates and associated Certification Authority (CA) certificates. It also supports client-generated public/private key pairs as well as key pairs generated by the CA.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7030"
      },
      "Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding": {
        "document_name": "RFC 7694",
        "document_uri": "urn:ietf:rfc:7694",
        "online_version": "`http://tools.ietf.org/html/rfc7694`",
        "abstract": "In HTTP, content codings allow for payload encodings such as for compression or integrity checks. In particular, the gzip content coding is widely used for payload data sent in response messages. Content codings can be used in request messages as well, however discoverability is not on par with response messages. This document extends the HTTP Accept-Encoding header field for use in responses, to indicate that content codings are supported in requests.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7694"
      },
      "The Safe Response Header Field": {
        "document_name": "RFC 2310",
        "document_uri": "urn:ietf:rfc:2310",
        "online_version": "`http://tools.ietf.org/html/rfc2310`",
        "abstract": "This document defines a HTTP response header field called Safe, which can be used to indicate that repeating a HTTP request is safe. Such an indication will allow user agents to handle retries of some safe requests, in particular safe POST requests, in a more user-friendly way.",
        "url": "http://webconcepts.info/specs/IETF/RFC/2310"
      },
      "A Reputation Query Protocol": {
        "document_name": "RFC 7072",
        "document_uri": "urn:ietf:rfc:7072",
        "online_version": "`http://tools.ietf.org/html/rfc7072`",
        "abstract": "This document defines a mechanism to conduct queries for reputation information over the HyperText Transfer Protocol (HTTP) using JavaScript Object Notation (JSON) as the payload meta-format.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7072"
      },
      "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol": {
        "document_name": "RFC 3648",
        "document_uri": "urn:ietf:rfc:3648",
        "online_version": "`http://tools.ietf.org/html/rfc3648`",
        "abstract": "This specification extends the Web Distributed Authoring and Versioning (WebDAV) Protocol to support the server-side ordering of collection members. Of particular interest are orderings that are not based on property values, and so cannot be achieved using a search protocol's ordering option and cannot be maintained automatically by the server. Protocol elements are defined to let clients specify the position in the ordering of each collection member, as well as the semantics governing the ordering.",
        "url": "http://webconcepts.info/specs/IETF/RFC/3648"
      },
      "Electronic Data Interchange - Internet Integration (EDIINT) Features Header Field": {
        "document_name": "RFC 6017",
        "document_uri": "urn:ietf:rfc:6017",
        "online_version": "`http://tools.ietf.org/html/rfc6017`",
        "abstract": "With the maturity of the Electronic Data Interchange - Internet Integration (EDIINT) standards of AS1, AS2, and AS3, applications and additional features are being built upon the basic secure transport functionality. These features are not necessarily supported by all EDIINT applications and could cause potential problems with implementations. The EDIINT-Features header field provides a means to resolve these problems and support new functionality.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6017"
      },
      "Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)": {
        "document_name": "RFC 6266",
        "document_uri": "urn:ietf:rfc:6266",
        "online_version": "`http://tools.ietf.org/html/rfc6266`",
        "abstract": "RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.",
        "url": "http://webconcepts.info/specs/IETF/RFC/6266"
      },
      "HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)": {
        "document_name": "RFC 4918",
        "document_uri": "urn:ietf:rfc:4918",
        "online_version": "`http://tools.ietf.org/html/rfc4918`",
        "abstract": "Web Distributed Authoring and Versioning (WebDAV) consists of a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance).",
        "url": "http://webconcepts.info/specs/IETF/RFC/4918"
      },
      "Brotli Compressed Data Format": {
        "document_name": "RFC 7932",
        "document_uri": "urn:ietf:rfc:7932",
        "online_version": "`http://tools.ietf.org/html/rfc7932`",
        "abstract": "This specification defines a lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding, with efficiency comparable to the best currently available general-purpose compression methods.",
        "url": "http://webconcepts.info/specs/IETF/RFC/7932"
      },
      "JavaScript Object Notation (JSON) Text Sequences": {
        "document_name": "RFC 7464",
        "document_uri": "urn:ietf:rfc:7464",
        "online_version": "`http://tools.ietf.org/html/rfc7464`",
        "abstract": "This document describes the JavaScript Object Notation (JSON) text sequence format and associated media type application/json-seq. A JSON text sequence consists of any number of JSON texts, all encoded in UTF-8, each prefixed by an ASCII Record Separator (0x1E), and each ending with an ASCII Line Feed character (0x0A).",
        "url": "http://webconcepts.info/specs/IETF/RFC/7464"
      }
    },
    "Internet Draft (I-D)": {
      "Additional Link Relations and the urn:social Namespace": {
        "document_name": "Internet Draft snell-more-link-relations",
        "document_uri": "urn:ietf:id:snell-more-link-relations",
        "online_version": "`http://tools.ietf.org/html/draft-snell-more-link-relations`",
        "abstract": "This specification defines a number of additional Link Relation Types that can used for a variety of purposes.",
        "url": "http://webconcepts.info/specs/IETF/I-D/snell-more-link-relations"
      },
      "HTTP Client Hints": {
        "document_name": "Internet Draft ietf-httpbis-client-hints",
        "document_uri": "urn:ietf:id:ietf-httpbis-client-hints",
        "online_version": "`http://tools.ietf.org/html/draft-ietf-httpbis-client-hints`",
        "abstract": "An increasing diversity of Web-connected devices and software capabilities has created a need to deliver optimized content for each device. This specification defines a set of HTTP request header fields, colloquially known as Client Hints, to address this. They are intended to be used as input to proactive content negotiation; just as the Accept header allows clients to indicate what formats they prefer, Client Hints allow clients to indicate a list of device and agent specific preferences.",
        "url": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-client-hints"
      },
      "Encrypted Content-Encoding for HTTP": {
        "document_name": "Internet Draft ietf-httpbis-encryption-encoding",
        "document_uri": "urn:ietf:id:ietf-httpbis-encryption-encoding",
        "online_version": "`http://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding`",
        "abstract": "This memo introduces a content coding for HTTP that allows message payloads to be encrypted.",
        "url": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-encryption-encoding"
      },
      "Marking HTTP Requests as Unimportant": {
        "document_name": "Internet Draft thomson-http-nice",
        "document_uri": "urn:ietf:id:thomson-http-nice",
        "online_version": "`http://tools.ietf.org/html/draft-thomson-http-nice`",
        "abstract": "An HTTP Nice header field is defined that marks a request as low priority. Intermediaries can choose to discard the request or serve it from cache rather than forwarding it to an origin server. This enables constrained origin servers, such as those that rely on battery power, to avoid expending limited resources on serving requests.",
        "url": "http://webconcepts.info/specs/IETF/I-D/thomson-http-nice"
      },
      "Application-Level Profile Semantics (ALPS)": {
        "document_name": "Internet Draft amundsen-richardson-foster-alps",
        "document_uri": "urn:ietf:id:amundsen-richardson-foster-alps",
        "online_version": "`http://tools.ietf.org/html/draft-amundsen-richardson-foster-alps`",
        "abstract": "This document describes ALPS, a data format for defining simple descriptions of application-level semantics, similar in complexity to HTML microformats. An ALPS document can be used as a profile to explain the application semantics of a document with an application-agnostic media type (such as HTML, HAL, Collection+JSON, Siren, etc.). This increases the reusability of profile documents across media types.",
        "url": "http://webconcepts.info/specs/IETF/I-D/amundsen-richardson-foster-alps"
      },
      "Duplicate Suppression in HTTP": {
        "document_name": "Internet Draft mogul-http-dupsup",
        "document_uri": "urn:ietf:id:mogul-http-dupsup",
        "online_version": "`http://tools.ietf.org/html/draft-mogul-http-dupsup`",
        "abstract": "A significant fraction of Web content is often exactly duplicated under several different URIs. This duplication can lead to suboptimal use of network bandwidth, and unnecessary latency for users. Much of this duplication can be avoided through the use of a simple mechanism, described here, which allows a cache to efficiently substitute one byte-for-byte identical value for another. By doing so, the cache avoids some or all of the network costs associated with retrieving the duplicate value.",
        "url": "http://webconcepts.info/specs/IETF/I-D/mogul-http-dupsup"
      },
      "The Key HTTP Response Header Field": {
        "document_name": "Internet Draft ietf-httpbis-key",
        "document_uri": "urn:ietf:id:ietf-httpbis-key",
        "online_version": "`http://tools.ietf.org/html/draft-ietf-httpbis-key`",
        "abstract": "The 'Key' header field for HTTP responses allows an origin server to describe the cache key for a negotiated response: a short algorithm that can be used upon later requests to determine if the same response is reusable. Key has the advantage of avoiding an additional round trip for validation whenever a new request differs slightly, but not significantly, from prior requests. Key also informs user agents of the request characteristics that might result in different content, which can be useful if the user agent is not sending Accept* fields in order to reduce the risk of fingerprinting.",
        "url": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-key"
      },
      "POST Once Exactly (POE)": {
        "document_name": "Internet Draft nottingham-http-poe",
        "document_uri": "urn:ietf:id:nottingham-http-poe",
        "online_version": "`http://tools.ietf.org/html/draft-nottingham-http-poe`",
        "abstract": "This specification describes a pattern of use that allows HTTP clients to automatically retry POST requests in a manner that assures no unintended side effects will take place, and defines mechanisms to allow implementations to automatically determine when such patterns are supported.",
        "url": "http://webconcepts.info/specs/IETF/I-D/nottingham-http-poe"
      },
      "Home Documents for HTTP APIs": {
        "document_name": "Internet Draft nottingham-json-home",
        "document_uri": "urn:ietf:id:nottingham-json-home",
        "online_version": "`http://tools.ietf.org/html/draft-nottingham-json-home`",
        "abstract": "This document proposes a home document format for non-browser HTTP clients.",
        "url": "http://webconcepts.info/specs/IETF/I-D/nottingham-json-home"
      },
      "Hierarchy Relations for Atom": {
        "document_name": "Internet Draft divilly-atom-hierarchy",
        "document_uri": "urn:ietf:id:divilly-atom-hierarchy",
        "online_version": "`http://tools.ietf.org/html/draft-divilly-atom-hierarchy`",
        "abstract": "Many applications, besides blogs, provide their data in the form of syndicated Web feeds using formats such as Atom. Some such applications organize Atom Entries in a hierarchical fashion similar to a file system. This specification describes a means of communicating about Atom Entries that are hierarchically related to each other since resource identifiers are opaque to clients and cannot be directly manipulated for the purposes of representation exchange, i.e., navigation. This specification proposes new link relations for hierarchically related Atom resources.",
        "url": "http://webconcepts.info/specs/IETF/I-D/divilly-atom-hierarchy"
      },
      "A JSON Media Type for Describing the Structure and Meaning of JSON Documents": {
        "document_name": "Internet Draft zyp-json-schema",
        "document_uri": "urn:ietf:id:zyp-json-schema",
        "online_version": "`http://tools.ietf.org/html/draft-zyp-json-schema`",
        "abstract": "JSON (JavaScript Object Notation) Schema defines the media type application/schema+json, a JSON based format for defining the structure of JSON data. JSON Schema provides a contract for what JSON data is required for a given application and how to interact with it. JSON Schema is intended to define validation, documentation, hyperlink navigation, and interaction control of JSON data.",
        "url": "http://webconcepts.info/specs/IETF/I-D/zyp-json-schema"
      },
      "The Tunnel-Protocol HTTP Header Field": {
        "document_name": "Internet Draft ietf-httpbis-tunnel-protocol",
        "document_uri": "urn:ietf:id:ietf-httpbis-tunnel-protocol",
        "online_version": "`http://tools.ietf.org/html/draft-ietf-httpbis-tunnel-protocol`",
        "abstract": "This specification allows HTTP CONNECT requests to indicate what protocol will be used within the tunnel once established, using the Tunnel-Protocol header field.",
        "url": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-tunnel-protocol"
      },
      "The Link-Template HTTP Header Field": {
        "document_name": "Internet Draft nottingham-link-template",
        "document_uri": "urn:ietf:id:nottingham-link-template",
        "online_version": "`http://tools.ietf.org/html/draft-nottingham-link-template`",
        "abstract": "This specification defines the Link-Template HTTP header field, providing a means for describing the structure of a link between two resources, so that new links can be generated.",
        "url": "http://webconcepts.info/specs/IETF/I-D/nottingham-link-template"
      },
      "Origin Cookies": {
        "document_name": "Internet Draft west-origin-cookies",
        "document_uri": "urn:ietf:id:west-origin-cookies",
        "online_version": "`http://tools.ietf.org/html/draft-west-origin-cookies`",
        "abstract": "This document updates RFC 6265, defining the origin attribute for cookies and the Origin-Cookie header field, which together allow servers to choose to harmonize the security policy of their cookies with the same-origin policy which governs other available client-side storage mechanisms.",
        "url": "http://webconcepts.info/specs/IETF/I-D/west-origin-cookies"
      },
      "The Sunset HTTP Header": {
        "document_name": "Internet Draft wilde-sunset-header",
        "document_uri": "urn:ietf:id:wilde-sunset-header",
        "online_version": "`http://tools.ietf.org/html/draft-wilde-sunset-header`",
        "abstract": "This specification defines the Sunset HTTP response header field, which indicates that a URI is likely to become unresponsive at a specified point in the future.",
        "url": "http://webconcepts.info/specs/IETF/I-D/wilde-sunset-header"
      },
      "The 'XML2RFC' version 3 Vocabulary": {
        "document_name": "Internet Draft hoffman-xml2rfc",
        "document_uri": "urn:ietf:id:hoffman-xml2rfc",
        "online_version": "`http://tools.ietf.org/html/draft-hoffman-xml2rfc`",
        "abstract": "This document defines the XML2RFC version 3 vocabulary; an XML-based language used for writing RFCs and Internet-Drafts. It is heavily derived from the version 2 vocabulary that is also under discussion. This document obsoletes the v2 grammar described in RFC 2629 and its expected followup, draft-reschke-xml2rfc.",
        "url": "http://webconcepts.info/specs/IETF/I-D/hoffman-xml2rfc"
      },
      "Link Relation Types for Web Services": {
        "document_name": "Internet Draft wilde-service-link-rel",
        "document_uri": "urn:ietf:id:wilde-service-link-rel",
        "online_version": "`http://tools.ietf.org/html/draft-wilde-service-link-rel`",
        "abstract": "Many resources provided on the Web are part of sets of resources that are provided in a context that is managed by one particular service provider. Often, these sets of resources are referred to as Web Services or Web APIs. This specification defines link relations for representing relationships from those resources to ones that provide documentation or descriptions of the Web services. The difference between these concepts is that documentation is primarily intended for human consumers, whereas descriptions are primarily intended for automated consumers. It also defines a link relation to identify a status resource that is used to represent operational information about a service's status.",
        "url": "http://webconcepts.info/specs/IETF/I-D/wilde-service-link-rel"
      },
      "Home Documents for HTTP Services: XML Syntax": {
        "document_name": "Internet Draft wilde-home-xml",
        "document_uri": "urn:ietf:id:wilde-home-xml",
        "online_version": "`http://tools.ietf.org/html/draft-wilde-home-xml`",
        "abstract": "The specification for HTTP API Home Documents provides a JSON syntax only. This specification provides an XML syntax for the same data model, so that the concept of Home Documents can be consistently exposed in both JSON- and XML-based HTTP APIs. It also defines the link relation type home so that applications can identify links to home documents.",
        "url": "http://webconcepts.info/specs/IETF/I-D/wilde-home-xml"
      },
      "Accept-Push-Policy Header Field": {
        "document_name": "Internet Draft ruellan-http-accept-push-policy",
        "document_uri": "urn:ietf:id:ruellan-http-accept-push-policy",
        "online_version": "`http://tools.ietf.org/html/draft-ruellan-http-accept-push-policy`",
        "abstract": "The Accept-Push-Policy and Push-Policy header fields enable a client and a server to negotiate the behaviour of the server regarding the usage of push on a per-request basis.",
        "url": "http://webconcepts.info/specs/IETF/I-D/ruellan-http-accept-push-policy"
      },
      "HTTP bytes-live Range Unit for Live Content": {
        "document_name": "Internet Draft pratt-httpbis-bytes-live-range-unit",
        "document_uri": "urn:ietf:id:pratt-httpbis-bytes-live-range-unit",
        "online_version": "`http://tools.ietf.org/html/draft-pratt-httpbis-bytes-live-range-unit`",
        "abstract": "To accommodate byte range requests for content that has data appended over time, this document defines a new HTTP range unit named bytes-live. The bytes-live range unit provides the ability for a client to specify a byte range in a GET or HEAD request which starts at an arbitrary byte offset within the representation and ends at an indeterminate offset, represented by *.",
        "url": "http://webconcepts.info/specs/IETF/I-D/pratt-httpbis-bytes-live-range-unit"
      },
      "Signing HTTP Messages": {
        "document_name": "Internet Draft cavage-http-signatures",
        "document_uri": "urn:ietf:id:cavage-http-signatures",
        "online_version": "`http://tools.ietf.org/html/draft-cavage-http-signatures`",
        "abstract": "When communicating over the Internet using the HTTP protocol, it can be desirable for a server or client to authenticate the sender of a particular message. It can also be desirable to ensure that the message was not tampered with during transit. This document describes a way for servers and clients to simultaneously add authentication and message integrity to HTTP messages by using a digital signature.",
        "url": "http://webconcepts.info/specs/IETF/I-D/cavage-http-signatures"
      },
      "HTTP/1.1: Range Responses of Indeterminate Length": {
        "document_name": "Internet Draft combs-http-indeterminate-range",
        "document_uri": "urn:ietf:id:combs-http-indeterminate-range",
        "online_version": "`http://tools.ietf.org/html/draft-combs-http-indeterminate-range`",
        "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document updates RFC 7233 Part 5 of the eight-part specification that defines the protocol referred to as HTTP/1.1. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests. This document improves support for responding to range requests for resources of indeterminate size.",
        "url": "http://webconcepts.info/specs/IETF/I-D/combs-http-indeterminate-range"
      },
      "Hypertext Transfer Protocol: Improved HTTP Caching": {
        "document_name": "Internet Draft drechsler-httpbis-improved-caching",
        "document_uri": "urn:ietf:id:drechsler-httpbis-improved-caching",
        "online_version": "`http://tools.ietf.org/html/draft-drechsler-httpbis-improved-caching`",
        "abstract": "This document describes an improved HTTP caching method which can be applied in addition to the standard caching behavior for HTTP. It defines the associated header field that controls this improved caching mechanism and a modified caching operation which is slightly different to standard caching operation for HTTP.",
        "url": "http://webconcepts.info/specs/IETF/I-D/drechsler-httpbis-improved-caching"
      },
      "Content-Signature Header Field for HTTP": {
        "document_name": "Internet Draft thomson-http-content-signature",
        "document_uri": "urn:ietf:id:thomson-http-content-signature",
        "online_version": "`http://tools.ietf.org/html/draft-thomson-http-content-signature`",
        "abstract": "A Content-Signature header field is defined for use in HTTP. This header field carries a signature of the payload body of a message.",
        "url": "http://webconcepts.info/specs/IETF/I-D/thomson-http-content-signature"
      }
    }
  },
  "Java Community Process (JCP)": {
    "Java Specification Request (JSR)": {
      "Pack200: A Packed Class Deployment Format For Java Applications": {
        "document_name": "JSR 200",
        "document_uri": "Packed Class Deployment Format For Java Applications",
        "online_version": "`http://www.jcp.org/en/jsr/detail?id=200`",
        "abstract": "This document specifies an archive format called Pack200. It is optimized for applications written in the Javatm programming language. Such applications are usually delivered as collections of classes, sometimes with associated resource files. This format allows any number (from one to hundreds of thousands) of Java classes to be encoded by a compressor, transmitted compactly in a single block of bytes, and decoded by a decompressor into equivalent Java class files. Because it can also represent class resources and other side files, it can serve as an alternative to the JAR archive for some deployment tasks, notably downloading Java applications.",
        "url": "http://webconcepts.info/specs/JCP/JSR/200"
      }
    }
  },
  "International Organization for Standardization (ISO)": {
    "International Electrotechnical Commission (IEC)": {
      "Information technology — Coding of audio-visual objects — Part 22: Open Font Format": {
        "document_name": "ISO/IEC 14496-22",
        "document_uri": "urn:iso:std:iso-iec:14496:-22",
        "online_version": "`http://www.iso.org/obp/ui/#iso:std:iso-iec:14496:-22`",
        "abstract": "ISO/IEC 14496-22:2015 specifies the Open Font Format (OFF) specification, the TrueType and Compact Font Format (CFF) outline formats, and the TrueType hinting language. Many references to both TrueType and PostScript exist throughout this document, as Open Font Format fonts combine the two technologies.",
        "url": "http://webconcepts.info/specs/ISO/IEC/14496-22"
      },
      "Information technology — Dynamic adaptive streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats": {
        "document_name": "ISO/IEC 23009-1",
        "document_uri": "urn:iso:std:iso-iec:23009:-1",
        "online_version": "`http://www.iso.org/obp/ui/#iso:std:iso-iec:23009:-1`",
        "abstract": "ISO/IEC 23009-1:2014 primarily specifies formats for the Media Presentation Description and Segments for dynamic adaptive streaming delivery of MPEG media over HTTP. It is applicable to streaming services over the Internet.",
        "url": "http://webconcepts.info/specs/ISO/IEC/23009-1"
      }
    }
  },
  "World Wide Web Consortium (W3C)": {
    "Technical Report (TR)": {
      "Upgrade Insecure Requests": {
        "document_name": "W3C TR http://www.w3.org/TR/upgrade-insecure-requests",
        "document_uri": "http://www.w3.org/TR/upgrade-insecure-requests",
        "online_version": "`http://www.w3.org/TR/upgrade-insecure-requests`",
        "abstract": "This document defines a mechanism which allows authors to instruct a user agent to upgrade a priori insecure resource requests to secure transport before fetching them.",
        "url": "http://webconcepts.info/specs/W3C/TR/upgrade-insecure-requests"
      },
      "Confinement with Origin Web Labels": {
        "document_name": "W3C TR http://www.w3.org/TR/COWL",
        "document_uri": "http://www.w3.org/TR/COWL",
        "online_version": "`http://www.w3.org/TR/COWL`",
        "abstract": "This specification defines an API for specifying privacy and integrity policies on data, in the form of origin labels, and a mechanism for confining code according to such policies. This allows Web application authors and server operators to share data with untrusted—buggy but not malicious—code (e.g., in a mashup scenario) yet impose restrictions on how the code can share the data further.",
        "url": "http://webconcepts.info/specs/W3C/TR/COWL"
      },
      "Manifest for Web Application": {
        "document_name": "W3C TR http://www.w3.org/TR/appmanifest",
        "document_uri": "http://www.w3.org/TR/appmanifest",
        "online_version": "`http://www.w3.org/TR/appmanifest`",
        "abstract": "This specification defines a JSON-based manifest that provides developers with a centralized place to put metadata associated with a web application. This includes, but is not limited to, the web application's name, links to icons, as well as the preferred URL to open when a user launches the web application. The manifest also allows developers to declare a default orientation for their web application, as well as providing the ability to set the display mode for the application (e.g., in fullscreen). Additionally, the manifest allows a developer to scope a web application to a URL. This restricts the URLs to which the application can be navigated and provides a means to deep link into a web application from other applications. Using this metadata, user agents can provide developers with means to create user experiences that are more comparable to that of a native application. In addition, this specification defines the manifest link type, which provides a declarative means for a document to be associated with a manifest.",
        "url": "http://webconcepts.info/specs/W3C/TR/appmanifest"
      },
      "Notification for Proxy Caches": {
        "document_name": "W3C TR http://www.w3.org/TR/WD-proxy",
        "document_uri": "http://www.w3.org/TR/WD-proxy",
        "online_version": "`http://www.w3.org/TR/WD-proxy`",
        "abstract": "A mechanism to enable better functioning of proxies is proposed. This mechanism allows proxies to inform a remote server about transactions performed using the cache and for servers to inform proxies when data becomes stale.",
        "url": "http://webconcepts.info/specs/W3C/TR/WD-proxy"
      },
      "Preload": {
        "document_name": "W3C TR http://www.w3.org/TR/preload",
        "document_uri": "http://www.w3.org/TR/preload",
        "online_version": "`http://www.w3.org/TR/preload`",
        "abstract": "This specification defines the preload keyword that may be used with link elements. This keyword provides a declarative fetch primitive that initiates an early fetch and separates fetching from resource execution.",
        "url": "http://webconcepts.info/specs/W3C/TR/preload"
      },
      "Cross-Origin Resource Sharing (CORS)": {
        "document_name": "W3C TR http://www.w3.org/TR/cors",
        "document_uri": "http://www.w3.org/TR/cors",
        "online_version": "`http://www.w3.org/TR/cors`",
        "abstract": "This document defines a mechanism to enable client-side cross-origin requests. Specifications that enable an API to make cross-origin requests to resources can use the algorithms defined by this specification. If such an API is used on http://example.org resources, a resource on http://hello-world.example can opt in using the mechanism described by this specification (e.g., specifying Access-Control-Allow-Origin: http://example.org as response header), which would allow that resource to be fetched cross-origin from http://example.org.",
        "url": "http://webconcepts.info/specs/W3C/TR/cors"
      },
      "Reporting API 1": {
        "document_name": "W3C TR http://www.w3.org/TR/reporting-1",
        "document_uri": "http://www.w3.org/TR/reporting-1",
        "online_version": "`http://www.w3.org/TR/reporting-1`",
        "abstract": "This document defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.",
        "url": "http://webconcepts.info/specs/W3C/TR/reporting-1"
      },
      "Simple Object Access Protocol (SOAP) 1.1": {
        "document_name": "W3C TR http://www.w3.org/TR/SOAP",
        "document_uri": "http://www.w3.org/TR/SOAP",
        "online_version": "`http://www.w3.org/TR/SOAP`",
        "abstract": "SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework.",
        "url": "http://webconcepts.info/specs/W3C/TR/SOAP"
      },
      "Portable Network Graphics": {
        "document_name": "W3C TR http://www.w3.org/TR/PNG",
        "document_uri": "http://www.w3.org/TR/PNG",
        "online_version": "`http://www.w3.org/TR/PNG`",
        "abstract": "This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. Indexed-color, grayscale, and truecolor images are supported, plus an optional alpha channel. Sample depths range from 1 to 16 bits. PNG is designed to work well in online viewing applications, such as the World Wide Web, so it is fully streamable with a progressive display option. PNG is robust, providing both full file integrity checking and simple detection of common transmission errors. Also, PNG can store gamma and chromaticity data for improved color matching on heterogeneous platforms.",
        "url": "http://webconcepts.info/specs/W3C/TR/PNG"
      },
      "JSON-LD 1.0": {
        "document_name": "W3C TR http://www.w3.org/TR/json-ld",
        "document_uri": "http://www.w3.org/TR/json-ld",
        "online_version": "`http://www.w3.org/TR/json-ld`",
        "abstract": "JSON is a useful data serialization and messaging format. This specification defines JSON-LD, a JSON-based format to serialize Linked Data. The syntax is designed to easily integrate into deployed systems that already use JSON, and provides a smooth upgrade path from JSON to JSON-LD. It is primarily intended to be a way to use Linked Data in Web-based programming environments, to build interoperable Web services, and to store Linked Data in JSON-based storage engines.",
        "url": "http://webconcepts.info/specs/W3C/TR/json-ld"
      },
      "Model for Tabular Data and Metadata on the Web": {
        "document_name": "W3C TR http://www.w3.org/TR/tabular-data-model",
        "document_uri": "http://www.w3.org/TR/tabular-data-model",
        "online_version": "`http://www.w3.org/TR/tabular-data-model`",
        "abstract": "Tabular data is routinely transferred on the web in a variety of formats, including variants on CSV, tab-delimited files, fixed field formats, spreadsheets, HTML tables, and SQL dumps. This document outlines a data model, or infoset, for tabular data and metadata about that tabular data that can be used as a basis for validation, display, or creating other formats. It also contains some non-normative guidance for publishing tabular data as CSV and how that maps into the tabular data model. An annotated model of tabular data can be supplemented by separate metadata about the table. This specification defines how implementations should locate that metadata, given a file containing tabular data. The standard syntax for that metadata is defined in tabular metadata. Note, however, that applications may have other means to create annotated tables, e.g., through some application specific APIs; this model does not depend on the specificities described in tabular-metadata.",
        "url": "http://webconcepts.info/specs/W3C/TR/tabular-data-model"
      },
      "Describing Linked Datasets with the VoID Vocabulary": {
        "document_name": "W3C TR http://www.w3.org/TR/void",
        "document_uri": "http://www.w3.org/TR/void",
        "online_version": "`http://www.w3.org/TR/void`",
        "abstract": "VoID is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document is a detailed guide to the VoID vocabulary. It describes how VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. It also provides deployment advice and discusses the discovery of VoID descriptions.",
        "url": "http://webconcepts.info/specs/W3C/TR/void"
      },
      "Web Video Text Tracks (WebVTT)": {
        "document_name": "W3C TR http://www.w3.org/TR/webvtt",
        "document_uri": "http://www.w3.org/TR/webvtt",
        "online_version": "`http://www.w3.org/TR/webvtt`",
        "abstract": "This specification defines WebVTT, the Web Video Text Tracks format. Its main use is for marking up external text track resources in connection with the HTML <track> element. WebVTT files provide captions or subtitles for video content, and also text video descriptions, chapters for content navigation, and more generally any form of metadata that is time-aligned with audio or video content.",
        "url": "http://webconcepts.info/specs/W3C/TR/webvtt"
      },
      "TriG": {
        "document_name": "W3C TR http://www.w3.org/TR/trig",
        "document_uri": "http://www.w3.org/TR/trig",
        "online_version": "`http://www.w3.org/TR/trig`",
        "abstract": "The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. This document defines a textual syntax for RDF called TriG that allows an RDF dataset to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. TriG is an extension of the Turtle [turtle] format.",
        "url": "http://webconcepts.info/specs/W3C/TR/trig"
      },
      "Content Security Policy Pinning": {
        "document_name": "W3C TR http://www.w3.org/TR/csp-pinning",
        "document_uri": "http://www.w3.org/TR/csp-pinning",
        "online_version": "`http://www.w3.org/TR/csp-pinning`",
        "abstract": "This document defines a new HTTP header that allows authors to instruct user agents to remember (pin) and enforce a Content Security Policy for a set of hosts for a period of time.",
        "url": "http://webconcepts.info/specs/W3C/TR/csp-pinning"
      },
      "Activity Streams 2.0": {
        "document_name": "W3C TR http://www.w3.org/TR/activitystreams-core",
        "document_uri": "http://www.w3.org/TR/activitystreams-core",
        "online_version": "`http://www.w3.org/TR/activitystreams-core`",
        "abstract": "This specification details a model for representing potential and completed activities using the JSON format.",
        "url": "http://webconcepts.info/specs/W3C/TR/activitystreams-core"
      },
      "Clear Site Data": {
        "document_name": "W3C TR http://www.w3.org/TR/clear-site-data",
        "document_uri": "http://www.w3.org/TR/clear-site-data",
        "online_version": "`http://www.w3.org/TR/clear-site-data`",
        "abstract": "This document defines an imperative mechanism which allows web developers to instruct a user agent to clear a user's locally stored data related to a host and its subdomains.",
        "url": "http://webconcepts.info/specs/W3C/TR/clear-site-data"
      },
      "Resource Hints": {
        "document_name": "W3C TR http://www.w3.org/TR/resource-hints",
        "document_uri": "http://www.w3.org/TR/resource-hints",
        "online_version": "`http://www.w3.org/TR/resource-hints`",
        "abstract": "This specification defines the dns-prefetch, preconnect, prefetch, and prerender relationships of the HTML Link Element (<link>). These primitives enable the developer, and the server generating or delivering the resources, to assist the user agent in the decision process of which origins it should connect to, and which resources it should fetch and preprocess to improve page performance.",
        "url": "http://webconcepts.info/specs/W3C/TR/resource-hints"
      },
      "Linked Data Platform 1.0 (LDP)": {
        "document_name": "W3C TR http://www.w3.org/TR/ldp",
        "document_uri": "http://www.w3.org/TR/ldp",
        "online_version": "`http://www.w3.org/TR/ldp`",
        "abstract": "Linked Data Platform (LDP) defines a set of rules for HTTP operations on web resources, some based on RDF, to provide an architecture for read-write Linked Data on the web.",
        "url": "http://webconcepts.info/specs/W3C/TR/ldp"
      },
      "PEP - An Extension Mechanism for HTTP": {
        "document_name": "W3C TR http://www.w3.org/TR/WD-http-pep",
        "document_uri": "http://www.w3.org/TR/WD-http-pep",
        "online_version": "`http://www.w3.org/TR/WD-http-pep`",
        "abstract": "HTTP is used increasingly in applications that need more facilities than the standard version of the protocol provides, ranging from distributed authoring, collaboration, and printing, to various remote procedure call mechanisms. The Protocol Extension Protocol (PEP) is an extension mechanism designed to address the tension between private agreement and public specification and to accommodate extension of applications such as HTTP clients, servers, and proxies. The PEP mechanism is designed to associate each extension with a URI, and use a few new RFC 822 derived header fields to carry the extension identifier and related information between the parties involved in an extended transaction. This document defines PEP and describes the interactions between PEP and HTTP/1.1. PEP is intended to be compatible with HTTP/1.0 inasmuch as HTTP/1.1 is compatible with HTTP/1.0. It is proposed that the PEP extension mechanism be included in future versions of HTTP. The PEP extension mechanism may be applicable to other information exchange not mentioned in this document. It is recommended that readers get acquainted with section 1.4 for a suggested reading of this specification and a list of sections specific for HTTP based applications.",
        "url": "http://webconcepts.info/specs/W3C/TR/WD-http-pep"
      },
      "The Platform for Privacy Preferences 1.0 (P3P1.0) Specification": {
        "document_name": "W3C TR http://www.w3.org/TR/P3P",
        "document_uri": "http://www.w3.org/TR/P3P",
        "online_version": "`http://www.w3.org/TR/P3P`",
        "abstract": "This is the specification of the Platform for Privacy Preferences (P3P). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P applications.",
        "url": "http://webconcepts.info/specs/W3C/TR/P3P"
      },
      "Server-Sent Events": {
        "document_name": "W3C TR http://www.w3.org/TR/eventsource",
        "document_uri": "http://www.w3.org/TR/eventsource",
        "online_version": "`http://www.w3.org/TR/eventsource`",
        "abstract": "specification defines an API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events. The API is designed such that it can be extended to work with other push notification schemes such as Push SMS.",
        "url": "http://webconcepts.info/specs/W3C/TR/eventsource"
      },
      "Hypertext Markup Language (HTML)": {
        "document_name": "W3C TR http://www.w3.org/TR/html4",
        "document_uri": "http://www.w3.org/TR/html4",
        "online_version": "`http://www.w3.org/TR/html4`",
        "abstract": "This specification defines the HyperText Markup Language (HTML), the publishing language of the World Wide Web. This specification defines HTML 4.01, which is a subversion of HTML 4. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML (HTML 3.2 and HTML 2.0), HTML 4 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide.",
        "url": "http://webconcepts.info/specs/W3C/TR/html4"
      },
      "Edge Architecture Specification": {
        "document_name": "W3C TR http://www.w3.org/TR/edge-arch",
        "document_uri": "http://www.w3.org/TR/edge-arch",
        "online_version": "`http://www.w3.org/TR/edge-arch`",
        "abstract": "This document defines the Edge Architecture, which extend the Web infrastructure through the use of HTTP surrogates - intermediaries that act on behalf of an origin server.",
        "url": "http://webconcepts.info/specs/W3C/TR/edge-arch"
      },
      "Webmention": {
        "document_name": "W3C TR http://www.w3.org/TR/webmention",
        "document_uri": "http://www.w3.org/TR/webmention",
        "online_version": "`http://www.w3.org/TR/webmention`",
        "abstract": "Webmention is a simple way to notify any URL when you link to it on your site. From the receiver's perspective, it's a way to request notifications when other sites link to it.",
        "url": "http://webconcepts.info/specs/W3C/TR/webmention"
      },
      "Tracking Preference Expression (DNT)": {
        "document_name": "W3C TR http://www.w3.org/TR/tracking-dnt",
        "document_uri": "http://www.w3.org/TR/tracking-dnt",
        "online_version": "`http://www.w3.org/TR/tracking-dnt`",
        "abstract": "This specification defines the technical mechanisms for expressing a tracking preference via the DNT request header field in HTTP, via an HTML DOM property readable by embedded scripts, and via properties accessible to various user agent plug-in or extension APIs. It also defines mechanisms for sites to signal whether and how they honor this preference, both in the form of a machine-readable tracking status resource at a well-known location and via a Tk response header field, and a mechanism for allowing the user to approve exceptions to DNT as desired.",
        "url": "http://webconcepts.info/specs/W3C/TR/tracking-dnt"
      },
      "Efficient XML Interchange (EXI) Format 1.0": {
        "document_name": "W3C TR http://www.w3.org/TR/exi",
        "document_uri": "http://www.w3.org/TR/exi",
        "online_version": "`http://www.w3.org/TR/exi`",
        "abstract": "This document is the specification of the Efficient XML Interchange (EXI) format. EXI is a very compact representation for the Extensible Markup Language (XML) Information Set that is intended to simultaneously optimize performance and the utilization of computational resources. The EXI format uses a hybrid approach drawn from the information and formal language theories, plus practical techniques verified by measurements, for entropy encoding XML information. Using a relatively simple algorithm, which is amenable to fast and compact implementation, and a small set of datatype representations, it reliably produces efficient encodings of XML event streams. The grammar production system and format definition of EXI are presented.",
        "url": "http://webconcepts.info/specs/W3C/TR/exi"
      },
      "Protocol for Web Description Resources (POWDER): Description Resources": {
        "document_name": "W3C TR http://www.w3.org/TR/powder-dr",
        "document_uri": "http://www.w3.org/TR/powder-dr",
        "online_version": "`http://www.w3.org/TR/powder-dr`",
        "abstract": "The purpose of the Protocol for Web Description Resources (POWDER) is to provide a means for individuals or organizations to describe a group of resources through the publication of machine-readable metadata, as motivated by the POWDER Use Cases. This document details the creation and lifecycle of Description Resources (DRs), which encapsulate such metadata. These are typically represented in a highly constrained XML dialect that is relatively human-readable. The meaning of such DRs are underpinned by formal semantics, accessible by performing a GRDDL Transform.",
        "url": "http://webconcepts.info/specs/W3C/TR/powder-dr"
      },
      "Content Security Policy Level 3": {
        "document_name": "W3C TR http://www.w3.org/TR/CSP3",
        "document_uri": "http://www.w3.org/TR/CSP3",
        "online_version": "`http://www.w3.org/TR/CSP3`",
        "abstract": "This document defines a mechanism by which web developers can control the resources which a particular page can fetch or execute, as well as a number of security-relevant policy decisions.",
        "url": "http://webconcepts.info/specs/W3C/TR/CSP3"
      },
      "Entry Point Regulation (EPR)": {
        "document_name": "W3C TR http://www.w3.org/TR/epr",
        "document_uri": "http://www.w3.org/TR/epr",
        "online_version": "`http://www.w3.org/TR/epr`",
        "abstract": "Entry Point Regulation aims to mitigate the risk of reflected cross-site scripting (XSS), cross-site script inclusion (XSSI), and cross-site request forgery (CSRF) attacks by demarcating the areas of an application which are intended to be externally referencable. A specified policy is applied on external requests for all non-demarcated resources.",
        "url": "http://webconcepts.info/specs/W3C/TR/epr"
      },
      "Micropub": {
        "document_name": "W3C TR http://www.w3.org/TR/micropub",
        "document_uri": "http://www.w3.org/TR/micropub",
        "online_version": "`http://www.w3.org/TR/micropub`",
        "abstract": "Micropub is an open API standard that is used to create posts on one's own domain using third-party clients. Web apps and native apps (e.g. iPhone, Android) can use Micropub to post short notes, photos, events or other posts to your own site.",
        "url": "http://webconcepts.info/specs/W3C/TR/micropub"
      },
      "Content Security Policy Level 2": {
        "document_name": "W3C TR http://www.w3.org/TR/CSP2",
        "document_uri": "http://www.w3.org/TR/CSP2",
        "online_version": "`http://www.w3.org/TR/CSP2`",
        "abstract": "This document defines a policy language used to declare a set of content restrictions for a web resource, and a mechanism for transmitting the policy from a server to a client where the policy is enforced.",
        "url": "http://webconcepts.info/specs/W3C/TR/CSP2"
      },
      "RDF 1.1 Concepts and Abstract Syntax": {
        "document_name": "W3C TR http://www.w3.org/TR/rdf11-concepts",
        "document_uri": "http://www.w3.org/TR/rdf11-concepts",
        "online_version": "`http://www.w3.org/TR/rdf11-concepts`",
        "abstract": "The Resource Description Framework (RDF) is a framework for representing information in the Web. This document defines an abstract syntax (a data model) which serves to link all RDF-based languages and specifications. The abstract syntax has two key data structures: RDF graphs are sets of subject-predicate-object triples, where the elements may be IRIs, blank nodes, or datatyped literals. They are used to express descriptions of resources. RDF datasets are used to organize collections of RDF graphs, and comprise a default graph and zero or more named graphs. RDF 1.1 Concepts and Abstract Syntax also introduces key concepts and terminology, and discusses datatyping and the handling of fragment identifiers in IRIs within RDF graphs.",
        "url": "http://webconcepts.info/specs/W3C/TR/rdf11-concepts"
      }
    }
  }
}