adding @mnot's new RFC 8288

obsoleting RFC 5988 and draft-nottingham-rfc5988bis

_includes/specs.md

@@ -1 +1 @@
-262 specifications in 6 specification series
+261 specifications in 6 specification series

concepts.json

@@ -1451,14 +1451,9 @@
           "details" : 
           [ 
             { "description" : "The Link header field provides a means for serialising one or more links into HTTP headers.",
-              "documentation" : "http:\/\/tools.ietf.org\/html\/draft-nottingham-rfc5988bis#section-3",
-              "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/I-D\/nottingham-rfc5988bis",
-              "spec-name" : "Internet Draft nottingham-rfc5988bis" },
-
-            { "description" : "The Link entity-header field provides a means for serialising one or more links in HTTP headers. It is semantically equivalent to the <LINK> element in HTML, as well as the atom:link feed-level element in Atom.",
-              "documentation" : "http:\/\/tools.ietf.org\/html\/rfc5988#section-5",
-              "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/5988",
-              "spec-name" : "RFC 5988" } ] },
+              "documentation" : "http:\/\/tools.ietf.org\/html\/rfc8288#section-3",
+              "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/8288",
+              "spec-name" : "RFC 8288" } ] },
 
         { "value" : "Link-Template",
           "concept" : "http:\/\/webconcepts.info\/concepts\/http-header\/",

concepts/http-header.json

@@ -1032,14 +1032,9 @@
         "details" : 
         [ 
           { "description" : "The Link header field provides a means for serialising one or more links into HTTP headers.",
-            "documentation" : "http:\/\/tools.ietf.org\/html\/draft-nottingham-rfc5988bis#section-3",
-            "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/I-D\/nottingham-rfc5988bis",
-            "spec-name" : "Internet Draft nottingham-rfc5988bis" },
-
-          { "description" : "The Link entity-header field provides a means for serialising one or more links in HTTP headers. It is semantically equivalent to the <LINK> element in HTML, as well as the atom:link feed-level element in Atom.",
-            "documentation" : "http:\/\/tools.ietf.org\/html\/rfc5988#section-5",
-            "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/5988",
-            "spec-name" : "RFC 5988" } ] },
+            "documentation" : "http:\/\/tools.ietf.org\/html\/rfc8288#section-3",
+            "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/8288",
+            "spec-name" : "RFC 8288" } ] },
 
       { "value" : "Link-Template",
         "concept" : "http:\/\/webconcepts.info\/concepts\/http-header\/",

concepts/http-header.md

@@ -6,7 +6,7 @@ permalink: /concepts/http-header/
 
 
 
-The following 202 HTTP Header Field values (191 distinct values) were found in [all available `webconcepts.info` specifications](/specs). Please be advised that the table shown here is maintained and compiled from [Web Concepts](/) sources. The [official HTTP Header Field registry](http://www.iana.org/assignments/message-headers/message-headers.xhtml) is maintained by the [*Internet Assigned Numbers Authority (IANA)*](http://www.iana.org/).
+The following 201 HTTP Header Field values (191 distinct values) were found in [all available `webconcepts.info` specifications](/specs). Please be advised that the table shown here is maintained and compiled from [Web Concepts](/) sources. The [official HTTP Header Field registry](http://www.iana.org/assignments/message-headers/message-headers.xhtml) is maintained by the [*Internet Assigned Numbers Authority (IANA)*](http://www.iana.org/).
 
 HTTP Header Field | Specification
 -------: | :-------
@@ -108,7 +108,7 @@ HTTP Header Field | Specification
 [`Label`](/concepts/http-header/Label "For certain methods (e.g. GET, PROPFIND), if the request-URL identifies a version-controlled resource, a label can be specified in a Label request header to cause the method to be applied to the version selected by that label from the version history of that version-controlled resource.") | [**RFC 3253**: Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)](/specs/IETF/RFC/3253 "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.")
 [`Last-Event-ID`](/concepts/http-header/Last-Event-ID "The Last-Event-ID HTTP header specifies the value of the event source's last event ID string, encoded as UTF-8.") | [**W3C TR http://www.w3.org/TR/eventsource**: Server-Sent Events](/specs/W3C/TR/eventsource " 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.")
 [`Last-Modified`](/concepts/http-header/Last-Modified "The "Last-Modified" header field in a response provides a timestamp indicating the date and time at which the origin server believes the selected representation was last modified, as determined at the conclusion of handling the request.") | [**RFC 7232**: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests](/specs/IETF/RFC/7232 "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.")
-[`Link`](/concepts/http-header/Link "The Link header field provides a means for serialising one or more links into HTTP headers.")<sub title="There are 2 definitions for this value">2</sub> | [**Internet Draft nottingham-rfc5988bis**: Web Linking](/specs/IETF/I-D/nottingham-rfc5988bis "This specification defines a way to indicate the relationships between resources on the Web (&#34;links&#34;) and the type of those relationships (&#34;link relation types&#34;). It also defines the use of such links in HTTP headers with the Link header field.")<br/>[**RFC 5988**: Web Linking](/specs/IETF/RFC/5988 "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.")
+[`Link`](/concepts/http-header/Link "The Link header field provides a means for serialising one or more links into HTTP headers.") | [**RFC 8288**: Web Linking](/specs/IETF/RFC/8288 "This specification defines a way to indicate the relationships between resources on the Web (&#34;links&#34;) and the type of those relationships (&#34;link relation types&#34;). It also defines the use of such links in HTTP headers with the Link header field.")
 [`Link-Template`](/concepts/http-header/Link-Template "The Link-Template entity-header field provides a means for serialising one or more links into HTTP headers. It is semantically equivalent to the Link header field, except that it uses URI Templates to convey the structure of links.") | [**Internet Draft nottingham-link-template**: The Link-Template HTTP Header Field](/specs/IETF/I-D/nottingham-link-template "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.")
 [`Location`](/concepts/http-header/Location "The &#34;Location&#34; header field is used in some responses to refer to a specific resource in relation to the response. The type of relationship is defined by the combination of request method and status code semantics.") | [**RFC 7231**: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content](/specs/IETF/RFC/7231 "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.")
 [`Lock-Token`](/concepts/http-header/Lock-Token "The Lock-Token request header is used with the UNLOCK method to identify the lock to be removed.") | [**RFC 4918**: HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)](/specs/IETF/RFC/4918 "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).")

concepts/http-header/Link.json

@@ -5,11 +5,6 @@
     "details" : 
     [ 
       { "description" : "The Link header field provides a means for serialising one or more links into HTTP headers.",
-        "documentation" : "http:\/\/tools.ietf.org\/html\/draft-nottingham-rfc5988bis#section-3",
-        "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/I-D\/nottingham-rfc5988bis",
-        "spec-name" : "Internet Draft nottingham-rfc5988bis" },
-
-      { "description" : "The Link entity-header field provides a means for serialising one or more links in HTTP headers. It is semantically equivalent to the <LINK> element in HTML, as well as the atom:link feed-level element in Atom.",
-        "documentation" : "http:\/\/tools.ietf.org\/html\/rfc5988#section-5",
-        "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/5988",
-        "spec-name" : "RFC 5988" } ] }
+        "documentation" : "http:\/\/tools.ietf.org\/html\/rfc8288#section-3",
+        "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/8288",
+        "spec-name" : "RFC 8288" } ] }

concepts/http-header/Link.md

@@ -7,9 +7,7 @@ concept-value: Link
 description: "The Link header field provides a means for serialising one or more links into HTTP headers."
 ---
 
-[The Link header field provides a means for serialising one or more links into HTTP headers.](http://tools.ietf.org/html/draft-nottingham-rfc5988bis#section-3 "Read documentation for HTTP Header Field "Link"") (**[Internet Draft nottingham-rfc5988bis: Web Linking](/specs/IETF/I-D/nottingham-rfc5988bis "This specification defines a way to indicate the relationships between resources on the Web ("links") and the type of those relationships ("link relation types"). It also defines the use of such links in HTTP headers with the Link header field.")**)
-
-[The Link entity-header field provides a means for serialising one or more links in HTTP headers. It is semantically equivalent to the <LINK> element in HTML, as well as the atom:link feed-level element in Atom.](http://tools.ietf.org/html/rfc5988#section-5 "Read documentation for HTTP Header Field &#34;Link&#34;") (**[RFC 5988: Web Linking](/specs/IETF/RFC/5988 "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.")**)
+[The Link header field provides a means for serialising one or more links into HTTP headers.](http://tools.ietf.org/html/rfc8288#section-3 "Read documentation for HTTP Header Field &#34;Link&#34;") (**[RFC 8288: Web Linking](/specs/IETF/RFC/8288 "This specification defines a way to indicate the relationships between resources on the Web (&#34;links&#34;) and the type of those relationships (&#34;link relation types&#34;). It also defines the use of such links in HTTP headers with the Link header field.")**)
 
 <br/>
 <hr/>

specs.json

@@ -299,15 +299,6 @@
       "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.",
       "concepts": [{
        "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Link-Template" }]}},{
-     "nottingham-rfc5988bis": {
-      "id": "http://webconcepts.info/specs/IETF/I-D/nottingham-rfc5988bis",
-      "title": "Web Linking",
-      "name": "Internet Draft nottingham-rfc5988bis",
-      "URI": "urn:ietf:id:nottingham-rfc5988bis",
-      "URL": "http://tools.ietf.org/html/draft-nottingham-rfc5988bis",
-      "abstract": "This specification defines a way to indicate the relationships between resources on the Web (\"links\") and the type of those relationships (\"link relation types\"). It also defines the use of such links in HTTP headers with the Link header field.",
-      "concepts": [{
-       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Link" }]}},{
      "pratt-httpbis-bytes-live-range-unit": {
       "id": "http://webconcepts.info/specs/IETF/I-D/pratt-httpbis-bytes-live-range-unit",
       "title": "HTTP bytes-live Range Unit for Live Content",
@@ -1096,15 +1087,6 @@
       "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.",
       "concepts": [{
        "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/held+xml" }]}},{
-     "5988": {
-      "id": "http://webconcepts.info/specs/IETF/RFC/5988",
-      "title": "Web Linking",
-      "name": "RFC 5988",
-      "URI": "urn:ietf:rfc:5988",
-      "URL": "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.",
-      "concepts": [{
-       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Link" }]}},{
      "6017": {
       "id": "http://webconcepts.info/specs/IETF/RFC/6017",
       "title": "Electronic Data Interchange - Internet Integration (EDIINT) Features Header Field",
@@ -2379,7 +2361,16 @@
       "abstract": "This document defines the 'multipart/multilingual' content type, which is an addition to the Multipurpose Internet Mail Extensions (MIME) standard. This content type makes it possible to send one message that contains multiple language versions of the same information. The translations would be identified by a language tag and selected by the email client based on a user's language settings.",
       "concepts": [{
        "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Translation-Type" }, {
-       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/multipart/multilingual" }]}}]}}]},
+       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/multipart/multilingual" }]}},{
+     "8288": {
+      "id": "http://webconcepts.info/specs/IETF/RFC/8288",
+      "title": "Web Linking",
+      "name": "RFC 8288",
+      "URI": "urn:ietf:rfc:8288",
+      "URL": "http://tools.ietf.org/html/rfc8288",
+      "abstract": "This specification defines a way to indicate the relationships between resources on the Web (\"links\") and the type of those relationships (\"link relation types\"). It also defines the use of such links in HTTP headers with the Link header field.",
+      "concepts": [{
+       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Link" }]}}]}}]},
  "ISO": {
   "id": "http://webconcepts.info/specs/ISO/",
   "name": "International Organization for Standardization",

specs/IETF/I-D/index.md

@@ -4,7 +4,7 @@ title:       "IETF Internet Draft Series"
 description: "List of specifications in the Internet Draft (I-D) series by the Internet Engineering Task Force (IETF)"
 ---
 
-There are currently 45 listed specifications in the [Internet Engineering Task Force (IETF)](..)'s Internet Draft (I-D) series.
+There are currently 44 listed specifications in the [Internet Engineering Task Force (IETF)](..)'s Internet Draft (I-D) series.
 
   * [A JSON Media Type for Describing the Structure and Meaning of JSON Documents (Internet Draft zyp-json-schema)](zyp-json-schema)
   * [Accept-Push-Policy Header Field (Internet Draft ruellan-http-accept-push-policy)](ruellan-http-accept-push-policy)
@@ -49,5 +49,4 @@ There are currently 45 listed specifications in the [Internet Engineering Task F
   * [The Sunset HTTP Header (Internet Draft wilde-sunset-header)](wilde-sunset-header)
   * [The Tunnel-Protocol HTTP Header Field (Internet Draft ietf-httpbis-tunnel-protocol)](ietf-httpbis-tunnel-protocol)
   * [Voluntary Application Server Identification (VAPID) for Web Push (Internet Draft ietf-webpush-vapid)](ietf-webpush-vapid)
-  * [Web Linking (Internet Draft nottingham-rfc5988bis)](nottingham-rfc5988bis)
   * [cite-as: A Link Relation to Convey a Preferred URI for Referencing (Internet Draft vandesompel-citeas)](vandesompel-citeas)

specs/IETF/RFC/8288.html

@@ -0,0 +1,75 @@
+---
+layout:      page
+title:       "Web Linking"
+description: "This specification defines a way to indicate the relationships between resources on
+the Web (\"links\") and the type of those relationships (\"link relation types\").
+It also defines the use of such links in HTTP headers with the Link header field."
+---
+
+<table cellpadding="5">
+   <tr>
+      <th valign="top" align="right">
+         <em>Document Name:</em>
+      </th>
+      <td>RFC 8288</td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Document URI:</em>
+      </th>
+      <td>
+         <code>urn:ietf:rfc:8288</code>
+      </td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Online Version:</em>
+      </th>
+      <td>
+         <code>
+            <a href="http://tools.ietf.org/html/rfc8288">http://tools.ietf.org/html/rfc8288</a>
+         </code>
+      </td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Organization:</em>
+      </th>
+      <td>
+         <a href="../" title="List of specification series by this organization">Internet Engineering Task Force (IETF)</a>
+      </td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Series:</em>
+      </th>
+      <td>
+         <a href="./" title="List of specifications in this series">Request for Comments (RFC)</a>
+      </td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Abstract:</em>
+      </th>
+      <td>This specification defines a way to indicate the relationships between resources on
+         the Web ("links") and the type of those relationships ("link relation types"). It
+         also defines the use of such links in HTTP headers with the Link header field.
+      </td>
+   </tr>
+</table>
+<br></br>
+<hr></hr>
+<h2 id="concepts">Specified Web Concepts:</h2>
+<h3 id="http-header">
+   <a href="/concepts/http-header/" title="List of all HTTP Header Fields">HTTP Header Fields</a>
+</h3>
+<code>
+   <a href="/concepts/http-header/Link" title="The Link header field provides a means for serialising one or more links into HTTP headers.">Link</a>
+</code>
+<br></br>
+<hr></hr>
+<p style="text-align: right">Return to ( 
+   <a href="./">Series</a> | 
+   <a href="../">Organization</a> | 
+   <a href="../../">all Specifications</a> )
+</p>