adding RFC 7396

dret · Jan 26, 2018 · 69a2e46 · 69a2e46
1 parent 0f8ad39
commit 69a2e46
Show file tree

Hide file tree

Showing 14 changed files with 150 additions and 10 deletions.
diff --git a/_includes/concepts.md b/_includes/concepts.md
@@ -1 +1 @@
-736 values for 32 Web Concepts
+737 values for 32 Web Concepts
diff --git a/_includes/specs.md b/_includes/specs.md
@@ -1 +1 @@
-266 specifications in 6 specification series
+267 specifications in 6 specification series
diff --git a/concepts.json b/concepts.json
@@ -5389,6 +5389,16 @@
               "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/6207",
               "spec-name" : "RFC 6207" } ] },
 
+        { "value" : "application\/merge-patch+json",
+          "concept" : "http:\/\/webconcepts.info\/concepts\/media-type\/",
+          "id" : "http:\/\/webconcepts.info\/concepts\/media-type\/application\/merge-patch+json",
+          "details" : 
+          [ 
+            { "description" : "The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content. A JSON merge patch document describes changes to be made to a target JSON document using a syntax that closely mimics the document being modified.",
+              "documentation" : "http:\/\/tools.ietf.org\/html\/rfc7396#section-1",
+              "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/7396",
+              "spec-name" : "RFC 7396" } ] },
+
         { "value" : "application\/mets+xml",
           "concept" : "http:\/\/webconcepts.info\/concepts\/media-type\/",
           "id" : "http:\/\/webconcepts.info\/concepts\/media-type\/application\/mets+xml",

diff --git a/concepts/index.md b/concepts/index.md
@@ -3,7 +3,7 @@ layout: page
 title:  "Web Concepts: Overview"
 ---
 
-This is an overview of 32 Web Concepts (with a total of 736 distinct values) that have been harvested from all [available specifications](/specs):
+This is an overview of 32 Web Concepts (with a total of 737 distinct values) that have been harvested from all [available specifications](/specs):
 
 * [HTTP Authentication Schemes](http-authentication-scheme/) (10)
 * [HTTP Cache Directives](http-cache-directive/) (15)
@@ -19,7 +19,7 @@ This is an overview of 32 Web Concepts (with a total of 736 distinct values) tha
 * [JSON Web Token Claims](jwt-claim/) (8)
 * [JWT Confirmation Methods](jwt-confirmation-method/) (4)
 * [Link Relations](link-relation/) (101)
-* [Media Types](media-type/) (106)
+* [Media Types](media-type/) (107)
 * [OAuth Access Token Types](oauth-access-token-type/) (2)
 * [OAuth Authorization Endpoint Response Types](oauth-authorization-endpoint-response-type/) (2)
 * [OAuth Dynamic Client Registration Metadata](oauth-client-metadata/) (20)

diff --git a/concepts/media-type.json b/concepts/media-type.json
@@ -501,6 +501,16 @@
             "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/6207",
             "spec-name" : "RFC 6207" } ] },
 
+      { "value" : "application\/merge-patch+json",
+        "concept" : "http:\/\/webconcepts.info\/concepts\/media-type\/",
+        "id" : "http:\/\/webconcepts.info\/concepts\/media-type\/application\/merge-patch+json",
+        "details" : 
+        [ 
+          { "description" : "The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content. A JSON merge patch document describes changes to be made to a target JSON document using a syntax that closely mimics the document being modified.",
+            "documentation" : "http:\/\/tools.ietf.org\/html\/rfc7396#section-1",
+            "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/7396",
+            "spec-name" : "RFC 7396" } ] },
+
       { "value" : "application\/mets+xml",
         "concept" : "http:\/\/webconcepts.info\/concepts\/media-type\/",
         "id" : "http:\/\/webconcepts.info\/concepts\/media-type\/application\/mets+xml",

diff --git a/concepts/media-type.md b/concepts/media-type.md
@@ -6,7 +6,7 @@ permalink: /concepts/media-type/
 
 
 
-The following 108 Media Type values (106 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 Media Type registry](http://www.iana.org/assignments/media-types/media-types.xhtml) is maintained by the [*Internet Assigned Numbers Authority (IANA)*](http://www.iana.org/).
+The following 109 Media Type values (107 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 Media Type registry](http://www.iana.org/assignments/media-types/media-types.xhtml) is maintained by the [*Internet Assigned Numbers Authority (IANA)*](http://www.iana.org/).
 
 Media Type | Specification
 -------: | :-------
@@ -59,6 +59,7 @@ Media Type | Specification
 [`application/manifest+json`](/concepts/media-type/application/manifest+json "A manifest is a JSON document that contains startup parameters and application defaults for when a web application is launched. A manifest consists of a top-level object that contains zero or more members.") | [**W3C TR http://www.w3.org/TR/appmanifest**: Manifest for Web Application](/specs/W3C/TR/appmanifest "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 &#34;scope&#34; a web application to a URL. This restricts the URLs to which the application can be navigated and provides a means to &#34;deep link&#34; 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.")
 [`application/marc`](/concepts/media-type/application/marc "Since there are different flavors of MARC which would be processed by different applications, this content-type/subtype refers to the harmonized USMARC/CANMARC specification. Additional content-types/subtypes may be defined in the future (e.g. application/unimarc).") | [**RFC 2220**: The Application/MARC Content-type](/specs/IETF/RFC/2220 "This memorandum provides a mechanism for representing objects which are files of Machine-Readable Cataloging records (MARC). The MARC formats are standards for the representation and communication of bibliographic and related information. A MARC record contains metadata for an information resource following MARC format specifications.")
 [`application/marcxml+xml`](/concepts/media-type/application/marcxml+xml "An XML schema for the direct XML representation of the MARC format (for which there already exists a media type, application/marc).") | [**RFC 6207**: The Media Types application/mods+xml, application/mads+xml, application/mets+xml, application/marcxml+xml, and application/sru+xml](/specs/IETF/RFC/6207 "This document specifies media types for the following formats: MODS (Metadata Object Description Schema), MADS (Metadata Authority Description Schema), METS (Metadata Encoding and Transmission Standard), MARCXML (MARC21 XML Schema), and the SRU (Search/Retrieve via URL Response Format) protocol response XML schema. These are all XML schemas providing representations of various forms of information including metadata and search results.")
+[`application/merge-patch+json`](/concepts/media-type/application/merge-patch+json "The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content. A JSON merge patch document describes changes to be made to a target JSON document using a syntax that closely mimics the document being modified.") | [**RFC 7396**: JSON Merge Patch](/specs/IETF/RFC/7396 "This specification defines the JSON merge patch format and processing rules. The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content.")
 [`application/mets+xml`](/concepts/media-type/application/mets+xml "An XML schema for encoding descriptive, administrative, and structural metadata regarding objects within a digital library.") | [**RFC 6207**: The Media Types application/mods+xml, application/mads+xml, application/mets+xml, application/marcxml+xml, and application/sru+xml](/specs/IETF/RFC/6207 "This document specifies media types for the following formats: MODS (Metadata Object Description Schema), MADS (Metadata Authority Description Schema), METS (Metadata Encoding and Transmission Standard), MARCXML (MARC21 XML Schema), and the SRU (Search/Retrieve via URL Response Format) protocol response XML schema. These are all XML schemas providing representations of various forms of information including metadata and search results.")
 [`application/mods+xml`](/concepts/media-type/application/mods+xml "An XML schema for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.") | [**RFC 6207**: The Media Types application/mods+xml, application/mads+xml, application/mets+xml, application/marcxml+xml, and application/sru+xml](/specs/IETF/RFC/6207 "This document specifies media types for the following formats: MODS (Metadata Object Description Schema), MADS (Metadata Authority Description Schema), METS (Metadata Encoding and Transmission Standard), MARCXML (MARC21 XML Schema), and the SRU (Search/Retrieve via URL Response Format) protocol response XML schema. These are all XML schemas providing representations of various forms of information including metadata and search results.")
 [`application/nlsml+xml`](/concepts/media-type/application/nlsml+xml "The Natural Language Semantics Markup Language (NLSML) is an XML data structure with elements and attributes designed to carry result information from recognizer (including enrollment) and verifier resources.") | [**RFC 6768**: Media Resource Control Protocol Version 2 (MRCPv2)](/specs/IETF/RFC/6768 "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 &#34;stand-alone&#34; 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.")

diff --git a/concepts/media-type/application/merge-patch+json.json b/concepts/media-type/application/merge-patch+json.json
@@ -0,0 +1,10 @@
+
+  { "value" : "application\/merge-patch+json",
+    "concept" : "http:\/\/webconcepts.info\/concepts\/media-type\/",
+    "id" : "http:\/\/webconcepts.info\/concepts\/media-type\/application\/merge-patch+json",
+    "details" : 
+    [ 
+      { "description" : "The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content. A JSON merge patch document describes changes to be made to a target JSON document using a syntax that closely mimics the document being modified.",
+        "documentation" : "http:\/\/tools.ietf.org\/html\/rfc7396#section-1",
+        "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/7396",
+        "spec-name" : "RFC 7396" } ] }
diff --git a/concepts/media-type/application/merge-patch+json.md b/concepts/media-type/application/merge-patch+json.md
@@ -0,0 +1,16 @@
+---
+layout:        concept
+permalink:     "/concepts/media-type/application/merge-patch+json"
+title:         "Media Type: application/merge-patch+json"
+concept-name:  Media Type
+concept-value: application/merge-patch+json
+description: "The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content. A JSON merge patch document describes changes to be made to a target JSON document using a syntax that closely mimics the document being modified."
+---
+
+[The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content. A JSON merge patch document describes changes to be made to a target JSON document using a syntax that closely mimics the document being modified.](http://tools.ietf.org/html/rfc7396#section-1 "Read documentation for Media Type &#34;application/merge-patch+json&#34;") (**[RFC 7396: JSON Merge Patch](/specs/IETF/RFC/7396 "This specification defines the JSON merge patch format and processing rules. The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content.")**)
+
+<br/>
+<hr/>
+
+<p style="float : left"><a href="./application/merge-patch+json.json" title="JSON representing this particular Web Concept value">JSON</a></p>
+<p style="text-align: right">Return to list of all ( <a href="../media-type/">Media Types</a> | <a href="../">Web Concepts</a> )</p>
diff --git a/specs.json b/specs.json
@@ -1805,6 +1805,15 @@
       "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.",
       "concepts": [{
        "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/coap-group+json" }]}},{
+     "7396": {
+      "id": "http://webconcepts.info/specs/IETF/RFC/7396",
+      "title": "JSON Merge Patch",
+      "name": "RFC 7396",
+      "URI": "urn:ietf:rfc:7396",
+      "URL": "http://tools.ietf.org/html/rfc7396",
+      "abstract": "This specification defines the JSON merge patch format and processing rules. The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content.",
+      "concepts": [{
+       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/merge-patch+json" }]}},{
      "7464": {
       "id": "http://webconcepts.info/specs/IETF/RFC/7464",
       "title": "JavaScript Object Notation (JSON) Text Sequences",

diff --git a/specs/IETF/RFC/7396.html b/specs/IETF/RFC/7396.html
@@ -0,0 +1,75 @@
+---
+layout:      page
+title:       "JSON Merge Patch"
+description: "This specification defines the JSON merge patch format and processing rules. The merge
+patch format is primarily intended for use with the HTTP PATCH method as a means of
+describing a set of modifications to a target resource's content."
+---
+
+<table cellpadding="5">
+   <tr>
+      <th valign="top" align="right">
+         <em>Document Name:</em>
+      </th>
+      <td>RFC 7396</td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Document URI:</em>
+      </th>
+      <td>
+         <code>urn:ietf:rfc:7396</code>
+      </td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Online Version:</em>
+      </th>
+      <td>
+         <code>
+            <a href="http://tools.ietf.org/html/rfc7396">http://tools.ietf.org/html/rfc7396</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 the JSON merge patch format and processing rules. The merge
+         patch format is primarily intended for use with the HTTP PATCH method as a means of
+         describing a set of modifications to a target resource's content.
+      </td>
+   </tr>
+</table>
+<br></br>
+<hr></hr>
+<h2 id="concepts">Specified Web Concepts:</h2>
+<h3 id="media-type">
+   <a href="/concepts/media-type/" title="List of all Media Types">Media Types</a>
+</h3>
+<code>
+   <a href="/concepts/media-type/application/merge-patch+json" title="The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content. A JSON merge patch document describes changes to be made to a target JSON document using a syntax that closely mimics the document being modified.">application/merge-patch+json</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>
diff --git a/specs/IETF/RFC/index.md b/specs/IETF/RFC/index.md
@@ -4,7 +4,7 @@ title:       "IETF Request for Comments Series"
 description: "List of specifications in the Request for Comments (RFC) series by the Internet Engineering Task Force (IETF)"
 ---
 
-There are currently 173 listed specifications in the [Internet Engineering Task Force (IETF)](..)'s Request for Comments (RFC) series.
+There are currently 174 listed specifications in the [Internet Engineering Task Force (IETF)](..)'s Request for Comments (RFC) series.
 
   * [A Media Type Structured Syntax Suffix for JSON Text Sequences (RFC 8091)](8091)
   * [A Media Type for XML Patch Operations (RFC 7351)](7351)
@@ -83,6 +83,7 @@ There are currently 173 listed specifications in the [Internet Engineering Task
   * [Hypertext Transfer Protocol Version 2 (RFC 7540)](7540)
   * [Instance Digests in HTTP (RFC 3230)](3230)
   * [Internet Printing Protocol/1.1: IPP URL Scheme (RFC 3510)](3510)
+  * [JSON Merge Patch (RFC 7396)](7396)
   * [JSON Web Key (JWK) (RFC 7517)](7517)
   * [JSON Web Signature (JWS) (RFC 7515)](7515)
   * [JSON Web Token (JWT) (RFC 7519)](7519)

diff --git a/specs/IETF/index.md b/specs/IETF/index.md
@@ -4,7 +4,7 @@ title:       "Internet Engineering Task Force: Specification Series"
 description: "List of specification series by the Internet Engineering Task Force (IETF/)"
 ---
 
-Here is a list of all specification series by the [Internet Engineering Task Force (IETF)](http://www.ietf.org/) that are currently available, for a total of 217 specifications:
+Here is a list of all specification series by the [Internet Engineering Task Force (IETF)](http://www.ietf.org/) that are currently available, for a total of 218 specifications:
 
   * [Internet Draft (I-D)](I-D/) Series: 44 Specifications
-  * [Request for Comments (RFC)](RFC/) Series: 173 Specifications
+  * [Request for Comments (RFC)](RFC/) Series: 174 Specifications