adding RFC 7207

dret · Oct 23, 2017 · 9f6bdf5 · 9f6bdf5
1 parent a72066e
commit 9f6bdf5
Show file tree

Hide file tree

Showing 14 changed files with 152 additions and 10 deletions.
diff --git a/_includes/concepts.md b/_includes/concepts.md
@@ -1 +1 @@
-720 values for 32 Web Concepts
+721 values for 32 Web Concepts
diff --git a/_includes/specs.md b/_includes/specs.md
@@ -1 +1 @@
-259 specifications in 6 specification series
+260 specifications in 6 specification series
diff --git a/concepts.json b/concepts.json
@@ -7232,6 +7232,16 @@
               "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/8057",
               "spec-name" : "RFC 8057" } ] },
 
+        { "value" : "eurosystem",
+          "concept" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/",
+          "id" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/eurosystem",
+          "details" : 
+          [ 
+            { "description" : "The goal of the \"eurosystem\" namespace is to ensure the stability and uniqueness of the names of various items that are used within the messages exchanged between the Eurosystem and the users of TARGET2-Securities (or potentially, other future projects of the Eurosystem).",
+              "documentation" : "http:\/\/tools.ietf.org\/html\/rfc7207#section-2",
+              "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/7207",
+              "spec-name" : "RFC 7207" } ] },
+
         { "value" : "example",
           "concept" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/",
           "id" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/example",

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 720 distinct values) that have been harvested from all [available specifications](/specs):
+This is an overview of 32 Web Concepts (with a total of 721 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)
@@ -33,7 +33,7 @@ This is an overview of 32 Web Concepts (with a total of 720 distinct values) tha
 * [Profile URIs](profile-uri/) (1)
 * [Structured Syntax Suffixes](structured-syntax-suffix/) (10)
 * [URI Schemes](uri-scheme/) (32)
-* [URN Namespaces](urn-namespace/) (13)
+* [URN Namespaces](urn-namespace/) (14)
 * [Well-Known URIs](well-known-uri/) (21)
 * [XML Namespaces](xml-ns/) (2)
 * [XML Schemas](xml-schema/) (1)
diff --git a/concepts/urn-namespace.json b/concepts/urn-namespace.json
@@ -46,6 +46,16 @@
             "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/8057",
             "spec-name" : "RFC 8057" } ] },
 
+      { "value" : "eurosystem",
+        "concept" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/",
+        "id" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/eurosystem",
+        "details" : 
+        [ 
+          { "description" : "The goal of the \"eurosystem\" namespace is to ensure the stability and uniqueness of the names of various items that are used within the messages exchanged between the Eurosystem and the users of TARGET2-Securities (or potentially, other future projects of the Eurosystem).",
+            "documentation" : "http:\/\/tools.ietf.org\/html\/rfc7207#section-2",
+            "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/7207",
+            "spec-name" : "RFC 7207" } ] },
+
       { "value" : "example",
         "concept" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/",
         "id" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/example",

diff --git a/concepts/urn-namespace.md b/concepts/urn-namespace.md
@@ -6,14 +6,15 @@ permalink: /concepts/urn-namespace/
 
 
 
-The following 13 URN Namespace 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 URN Namespace registry](http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml) is maintained by the [*Internet Assigned Numbers Authority (IANA)*](http://www.iana.org/).
+The following 14 URN Namespace 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 URN Namespace registry](http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml) is maintained by the [*Internet Assigned Numbers Authority (IANA)*](http://www.iana.org/).
 
 URN Namespace | Specification
 -------: | :-------
 [`adid`](/concepts/urn-namespace/adid "Ad-ID is the industry standard for identifying advertising assets across all media platforms (e.g., over the air, online, over the top, mobile, and place based). Ad-IDs are unique codes for each creative advertising asset. Those unique codes are applied to all media.") | [**RFC 8107**: Advertising Digital Identifier (Ad-ID) URN Namespace Definition](/specs/IETF/RFC/8107 "Advertising Digital Identifiers (Ad-IDs) are used to identify advertising assets across all media platforms. This document defines the formal Uniform Resource Name (URN) Namespace Identifier (NID) &#34;adid&#34; for Ad-IDs.")
 [`bbf`](/concepts/urn-namespace/bbf "The &#34;bbf&#34; NID is for new work efforts related to data models for protocols other than the Customer Premises Equipment (CPE) WAN Management Protocol (CWMP).") | [**RFC 8057**: Uniform Resource Name (URN) Namespaces for Broadband Forum](/specs/IETF/RFC/8057 "This document describes the Namespace Identifiers (NIDs) &#34;bbf&#34;, &#34;broadband-forum-org&#34;, and &#34;dslforum-org&#34; for Uniform Resource Names (URNs) used to identify resources published by Broadband Forum (BBF). BBF specifies and manages resources that utilize these three URN identification models. Management activities for these and other resource types are handled by BBF.")
 [`broadband-forum-org`](/concepts/urn-namespace/broadband-forum-org "The &#34;broadband-forum-org&#34; and &#34;dslforum-org&#34; NIDs are used for all data models related to CWMP.") | [**RFC 8057**: Uniform Resource Name (URN) Namespaces for Broadband Forum](/specs/IETF/RFC/8057 "This document describes the Namespace Identifiers (NIDs) &#34;bbf&#34;, &#34;broadband-forum-org&#34;, and &#34;dslforum-org&#34; for Uniform Resource Names (URNs) used to identify resources published by Broadband Forum (BBF). BBF specifies and manages resources that utilize these three URN identification models. Management activities for these and other resource types are handled by BBF.")
 [`dslforum-org`](/concepts/urn-namespace/dslforum-org "The &#34;broadband-forum-org&#34; and &#34;dslforum-org&#34; NIDs are used for all data models related to CWMP. Use of the &#34;dslforum-org&#34; NID started prior the organization's 2008 name change from DSL Forum to Broadband Forum.") | [**RFC 8057**: Uniform Resource Name (URN) Namespaces for Broadband Forum](/specs/IETF/RFC/8057 "This document describes the Namespace Identifiers (NIDs) &#34;bbf&#34;, &#34;broadband-forum-org&#34;, and &#34;dslforum-org&#34; for Uniform Resource Names (URNs) used to identify resources published by Broadband Forum (BBF). BBF specifies and manages resources that utilize these three URN identification models. Management activities for these and other resource types are handled by BBF.")
+[`eurosystem`](/concepts/urn-namespace/eurosystem "The goal of the &#34;eurosystem&#34; namespace is to ensure the stability and uniqueness of the names of various items that are used within the messages exchanged between the Eurosystem and the users of TARGET2-Securities (or potentially, other future projects of the Eurosystem).") | [**RFC 7207**: A Uniform Resource Name (URN) Namespace for Eurosystem Messaging](/specs/IETF/RFC/7207 "This document defines and registers with IANA a Uniform Resource Name (URN) namespace for usage within messages standardized by the Eurosystem. The URN namespace is managed by Deutsche Bundesbank, which is a member of the European System of Central Banks (ESCB).")
 [`example`](/concepts/urn-namespace/example "The &#34;example&#34; NID is intended to provide a clean, easily recognizable space for minting examples to be used in documentation and in URN-related testing and experimentation. ") | [**RFC 6963**: A Uniform Resource Name (URN) Namespace for Examples](/specs/IETF/RFC/6963 "This document defines a Uniform Resource Name (URN) namespace identifier enabling the generation of URNs that are appropriate for use in documentation and in URN-related testing and experimentation.")
 [`ieee`](/concepts/urn-namespace/ieee "The Institute of Electrical and Electronic Engineers (IEEE) is an organization whose objectives include the educational and technical advancement of electrical and electronic engineering, telecommunications, computer engineering, and allied disciplines. As part of these specification efforts, there is a need to maintain identifiers in a managed namespace that is unique and persistent.") | [**RFC 8069**: URN Namespace for IEEE](/specs/IETF/RFC/8069 "This document describes the Namespace Identifier (NID) 'ieee' for Uniform Resource Names (URNs) used to identify resources published by the Institute of Electrical and Electronics Engineers (IEEE). IEEE specifies and manages resources that utilize this URN identification model. Management activities for these and other resources types are handled by the manager of the IEEE Registration Authority.")
 [`ietf`](/concepts/urn-namespace/ietf "This document proposes the &#34;ietf&#34; namespace, which consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC editor and the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences.") | [**RFC 2648**: A URN Namespace for IETF Documents](/specs/IETF/RFC/2648 "A system for Uniform Resource Names (URNs) must be capable of supporting new naming systems. As an example of proposing a new namespace, this document proposes the &#34;ietf&#34; namespace. This namespace consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC Editor, the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences, and the Internet Drafts published by the Internet Drafts Editor. Both the current URN framework and URN syntax support this namespace.")

diff --git a/concepts/urn-namespace/eurosystem.json b/concepts/urn-namespace/eurosystem.json
@@ -0,0 +1,10 @@
+
+  { "value" : "eurosystem",
+    "concept" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/",
+    "id" : "http:\/\/webconcepts.info\/concepts\/urn-namespace\/eurosystem",
+    "details" : 
+    [ 
+      { "description" : "The goal of the \"eurosystem\" namespace is to ensure the stability and uniqueness of the names of various items that are used within the messages exchanged between the Eurosystem and the users of TARGET2-Securities (or potentially, other future projects of the Eurosystem).",
+        "documentation" : "http:\/\/tools.ietf.org\/html\/rfc7207#section-2",
+        "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/7207",
+        "spec-name" : "RFC 7207" } ] }
diff --git a/concepts/urn-namespace/eurosystem.md b/concepts/urn-namespace/eurosystem.md
@@ -0,0 +1,16 @@
+---
+layout:        concept
+permalink:     "/concepts/urn-namespace/eurosystem"
+title:         "URN Namespace: eurosystem"
+concept-name:  URN Namespace
+concept-value: eurosystem
+description: "The goal of the \"eurosystem\" namespace is to ensure the stability and uniqueness of the names of various items that are used within the messages exchanged between the Eurosystem and the users of TARGET2-Securities (or potentially, other future projects of the Eurosystem)."
+---
+
+[The goal of the "eurosystem" namespace is to ensure the stability and uniqueness of the names of various items that are used within the messages exchanged between the Eurosystem and the users of TARGET2-Securities (or potentially, other future projects of the Eurosystem).](http://tools.ietf.org/html/rfc7207#section-2 "Read documentation for URN Namespace &#34;eurosystem&#34;") (**[RFC 7207: A Uniform Resource Name (URN) Namespace for Eurosystem Messaging](/specs/IETF/RFC/7207 "This document defines and registers with IANA a Uniform Resource Name (URN) namespace for usage within messages standardized by the Eurosystem. The URN namespace is managed by Deutsche Bundesbank, which is a member of the European System of Central Banks (ESCB).")**)
+
+<br/>
+<hr/>
+
+<p style="float : left"><a href="./eurosystem.json" title="JSON representing this particular Web Concept value">JSON</a></p>
+<p style="text-align: right">Return to list of all ( <a href="../urn-namespace/">URN Namespaces</a> | <a href="../">Web Concepts</a> )</p>
diff --git a/specs.json b/specs.json
@@ -1554,6 +1554,15 @@
       "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.",
       "concepts": [{
        "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Additions" }]}},{
+     "7207": {
+      "id": "http://webconcepts.info/specs/IETF/RFC/7207",
+      "title": "A Uniform Resource Name (URN) Namespace for Eurosystem Messaging",
+      "name": "RFC 7207",
+      "URI": "urn:ietf:rfc:7207",
+      "URL": "http://tools.ietf.org/html/rfc7207",
+      "abstract": "This document defines and registers with IANA a Uniform Resource Name (URN) namespace for usage within messages standardized by the Eurosystem. The URN namespace is managed by Deutsche Bundesbank, which is a member of the European System of Central Banks (ESCB).",
+      "concepts": [{
+       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/eurosystem" }]}},{
      "7230": {
       "id": "http://webconcepts.info/specs/IETF/RFC/7230",
       "title": "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing",

diff --git a/specs/IETF/RFC/7207.html b/specs/IETF/RFC/7207.html
@@ -0,0 +1,77 @@
+---
+layout:      page
+title:       "A Uniform Resource Name (URN) Namespace for Eurosystem Messaging"
+description: "This document defines and registers with IANA a Uniform Resource Name (URN) namespace
+for usage within messages standardized by the Eurosystem. The URN namespace is managed
+by Deutsche Bundesbank, which is a member of the European System of Central Banks
+(ESCB)."
+---
+
+<table cellpadding="5">
+   <tr>
+      <th valign="top" align="right">
+         <em>Document Name:</em>
+      </th>
+      <td>RFC 7207</td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Document URI:</em>
+      </th>
+      <td>
+         <code>urn:ietf:rfc:7207</code>
+      </td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Online Version:</em>
+      </th>
+      <td>
+         <code>
+            <a href="http://tools.ietf.org/html/rfc7207">http://tools.ietf.org/html/rfc7207</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 document defines and registers with IANA a Uniform Resource Name (URN) namespace
+         for usage within messages standardized by the Eurosystem. The URN namespace is managed
+         by Deutsche Bundesbank, which is a member of the European System of Central Banks
+         (ESCB).
+      </td>
+   </tr>
+</table>
+<br></br>
+<hr></hr>
+<h2 id="concepts">Specified Web Concepts:</h2>
+<h3 id="urn-namespace">
+   <a href="/concepts/urn-namespace/" title="List of all URN Namespaces">URN Namespaces</a>
+</h3>
+<code>
+   <a href="/concepts/urn-namespace/eurosystem" title="The goal of the &amp;#34;eurosystem&amp;#34; namespace is to ensure the stability and uniqueness of the names of various items that are used within the messages exchanged between the Eurosystem and the users of TARGET2-Securities (or potentially, other future projects of the Eurosystem).">eurosystem</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,14 +4,15 @@ 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 167 listed specifications in the [Internet Engineering Task Force (IETF)](..)'s Request for Comments (RFC) series.
+There are currently 168 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)
   * [A Reputation Query Protocol (RFC 7072)](7072)
   * [A URN Namespace for IETF Documents (RFC 2648)](2648)
   * [A URN Namespace for OASIS (RFC 3121)](3121)
   * [A Uniform Resource Identifier for Geographic Locations ('geo' URI) (RFC 5870)](5870)
+  * [A Uniform Resource Name (URN) Namespace for Eurosystem Messaging (RFC 7207)](7207)
   * [A Uniform Resource Name (URN) Namespace for Examples (RFC 6963)](6963)
   * [A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO) (RFC 5141)](5141)
   * [A Uniform Resource Name (URN) Namespace for the Near Field Communication (NFC) Forum (RFC 4729)](4729)

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 212 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 213 specifications:
 
   * [Internet Draft (I-D)](I-D/) Series: 45 Specifications
-  * [Request for Comments (RFC)](RFC/) Series: 167 Specifications
+  * [Request for Comments (RFC)](RFC/) Series: 168 Specifications
diff --git a/specs/index.md b/specs/index.md
@@ -8,9 +8,9 @@ This is a list of all organizations and their specification series (listing {% i
 
 * [International Organization for Standardization (ISO)](ISO/): 3 Specifications
   * [International Electrotechnical Commission (IEC) Series](ISO/IEC/ "Series overview"): 3 Specifications
-* [Internet Engineering Task Force (IETF)](IETF/): 212 Specifications
+* [Internet Engineering Task Force (IETF)](IETF/): 213 Specifications
   * [Internet Draft (I-D) Series](IETF/I-D/ "Series overview"): 45 Specifications
-  * [Request for Comments (RFC) Series](IETF/RFC/ "Series overview"): 167 Specifications
+  * [Request for Comments (RFC) Series](IETF/RFC/ "Series overview"): 168 Specifications
 * [Java Community Process (JCP)](JCP/): 1 Specifications
   * [Java Specification Request (JSR) Series](JCP/JSR/ "Series overview"): 1 Specifications
 * [Organization for the Advancement of Structured Information Standards (OASIS)](OASIS/): 4 Specifications