adding RFC 4112

dret · Oct 12, 2017 · 4e5cbad · 4e5cbad
1 parent f6dfcc8
commit 4e5cbad
Show file tree

Hide file tree

Showing 14 changed files with 158 additions and 12 deletions.
diff --git a/_includes/concepts.md b/_includes/concepts.md
@@ -1 +1 @@
-717 values for 32 Web Concepts
+718 values for 32 Web Concepts
diff --git a/_includes/specs.md b/_includes/specs.md
@@ -1 +1 @@
-256 specifications in 6 specification series
+257 specifications in 6 specification series
diff --git a/concepts.json b/concepts.json
@@ -7534,7 +7534,17 @@
             { "description" : "This document defines a framework for authorization policies controlling access to application-specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains.",
               "documentation" : "http:\/\/tools.ietf.org\/html\/rfc4745#section-15.1",
               "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/4745",
-              "spec-name" : "RFC 4745" } ] } ] },
+              "spec-name" : "RFC 4745" } ] },
+
+        { "value" : "urn:ietf:params:xml:schema:ECMLv2",
+          "concept" : "http:\/\/webconcepts.info\/concepts\/xml-ns\/",
+          "id" : "http:\/\/webconcepts.info\/concepts\/xml-ns\/urn:ietf:params:xml:schema:ECMLv2",
+          "details" : 
+          [ 
+            { "description" : "ECML (Electronic Commerce Modeling Language) provides a set of hierarchical payment-oriented data structures that will enable automated software, including electronic wallets from multiple vendors, to supply and query for needed data in a more uniform manner.",
+              "documentation" : "http:\/\/tools.ietf.org\/html\/rfc4112#section-1",
+              "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/4112",
+              "spec-name" : "RFC 4112" } ] } ] },
 
     { "concept" : "xml-schema",
       "id" : "http:\/\/webconcepts.info\/concepts\/xml-schema\/",

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 717 distinct values) that have been harvested from all [available specifications](/specs):
+This is an overview of 32 Web Concepts (with a total of 718 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)
@@ -35,5 +35,5 @@ This is an overview of 32 Web Concepts (with a total of 717 distinct values) tha
 * [URI Schemes](uri-scheme/) (31)
 * [URN Namespaces](urn-namespace/) (12)
 * [Well-Known URIs](well-known-uri/) (21)
-* [XML Namespaces](xml-ns/) (1)
+* [XML Namespaces](xml-ns/) (2)
 * [XML Schemas](xml-schema/) (1)
diff --git a/concepts/xml-ns.json b/concepts/xml-ns.json
@@ -14,4 +14,14 @@
           { "description" : "This document defines a framework for authorization policies controlling access to application-specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains.",
             "documentation" : "http:\/\/tools.ietf.org\/html\/rfc4745#section-15.1",
             "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/4745",
-            "spec-name" : "RFC 4745" } ] } ] }
+            "spec-name" : "RFC 4745" } ] },
+
+      { "value" : "urn:ietf:params:xml:schema:ECMLv2",
+        "concept" : "http:\/\/webconcepts.info\/concepts\/xml-ns\/",
+        "id" : "http:\/\/webconcepts.info\/concepts\/xml-ns\/urn:ietf:params:xml:schema:ECMLv2",
+        "details" : 
+        [ 
+          { "description" : "ECML (Electronic Commerce Modeling Language) provides a set of hierarchical payment-oriented data structures that will enable automated software, including electronic wallets from multiple vendors, to supply and query for needed data in a more uniform manner.",
+            "documentation" : "http:\/\/tools.ietf.org\/html\/rfc4112#section-1",
+            "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/4112",
+            "spec-name" : "RFC 4112" } ] } ] }
diff --git a/concepts/xml-ns.md b/concepts/xml-ns.md
@@ -6,11 +6,12 @@ permalink: /concepts/xml-ns/
 
 
 
-The following 1 XML 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 XML Namespace registry](https://www.iana.org/assignments/xml-registry/xml-registry.xhtml#ns) is maintained by the [*Internet Assigned Numbers Authority (IANA)*](http://www.iana.org/).
+The following 2 XML 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 XML Namespace registry](https://www.iana.org/assignments/xml-registry/xml-registry.xhtml#ns) is maintained by the [*Internet Assigned Numbers Authority (IANA)*](http://www.iana.org/).
 
 XML Namespace | Specification
 -------: | :-------
 [`urn:ietf:params:xml:ns:common-policy`](/concepts/xml-ns/urn:ietf:params:xml:ns:common-policy) | [**RFC 4745**: Common Policy: A Document Format for Expressing Privacy Preferences](/specs/IETF/RFC/4745 "This document defines a framework for authorization policies controlling access to application-specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains.")
+[`urn:ietf:params:xml:schema:ECMLv2`](/concepts/xml-ns/urn:ietf:params:xml:schema:ECMLv2) | [**RFC 4112**: Electronic Commerce Modeling Language (ECML) Version 2 Specification](/specs/IETF/RFC/4112 "Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically-organized payment-related information field names in an XML syntax is defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meet the requirements of RFC 3505.")
 
 <br/>
 <hr/>

diff --git a/concepts/xml-ns/urn:ietf:params:xml:schema:ECMLv2.json b/concepts/xml-ns/urn:ietf:params:xml:schema:ECMLv2.json
@@ -0,0 +1,10 @@
+
+  { "value" : "urn:ietf:params:xml:schema:ECMLv2",
+    "concept" : "http:\/\/webconcepts.info\/concepts\/xml-ns\/",
+    "id" : "http:\/\/webconcepts.info\/concepts\/xml-ns\/urn:ietf:params:xml:schema:ECMLv2",
+    "details" : 
+    [ 
+      { "description" : "ECML (Electronic Commerce Modeling Language) provides a set of hierarchical payment-oriented data structures that will enable automated software, including electronic wallets from multiple vendors, to supply and query for needed data in a more uniform manner.",
+        "documentation" : "http:\/\/tools.ietf.org\/html\/rfc4112#section-1",
+        "specification" : "http:\/\/webconcepts.info\/specs\/IETF\/RFC\/4112",
+        "spec-name" : "RFC 4112" } ] }
diff --git a/concepts/xml-ns/urn:ietf:params:xml:schema:ECMLv2.md b/concepts/xml-ns/urn:ietf:params:xml:schema:ECMLv2.md
@@ -0,0 +1,16 @@
+---
+layout:        concept
+permalink:     "/concepts/xml-ns/urn%3Aietf%3Aparams%3Axml%3Aschema%3AECMLv2"
+title:         "XML Namespace: urn:ietf:params:xml:schema:ECMLv2"
+concept-name:  XML Namespace
+concept-value: urn:ietf:params:xml:schema:ECMLv2
+description: "ECML (Electronic Commerce Modeling Language) provides a set of hierarchical payment-oriented data structures that will enable automated software, including electronic wallets from multiple vendors, to supply and query for needed data in a more uniform manner."
+---
+
+[ECML (Electronic Commerce Modeling Language) provides a set of hierarchical payment-oriented data structures that will enable automated software, including electronic wallets from multiple vendors, to supply and query for needed data in a more uniform manner.](http://tools.ietf.org/html/rfc4112#section-1 "Read documentation for XML Namespace &#34;urn:ietf:params:xml:schema:ECMLv2&#34;") (**[RFC 4112: Electronic Commerce Modeling Language (ECML) Version 2 Specification](/specs/IETF/RFC/4112 "Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically-organized payment-related information field names in an XML syntax is defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meet the requirements of RFC 3505.")**)
+
+<br/>
+<hr/>
+
+<p style="float : left"><a href="./urn:ietf:params:xml:schema:ECMLv2.json" title="JSON representing this particular Web Concept value">JSON</a></p>
+<p style="text-align: right">Return to list of all ( <a href="../xml-ns/">XML Namespaces</a> | <a href="../">Web Concepts</a> )</p>
diff --git a/specs.json b/specs.json
@@ -775,6 +775,15 @@
       "abstract": "This document defines the \"application/soap+xml\" media type which can be used to describe SOAP 1.2 messages serialized as XML 1.0.",
       "concepts": [{
        "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/soap+xml" }]}},{
+     "4112": {
+      "id": "http://webconcepts.info/specs/IETF/RFC/4112",
+      "title": "Electronic Commerce Modeling Language (ECML) Version 2 Specification",
+      "name": "RFC 4112",
+      "URI": "urn:ietf:rfc:4112",
+      "URL": "http://tools.ietf.org/html/rfc4112",
+      "abstract": "Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically-organized payment-related information field names in an XML syntax is defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meet the requirements of RFC 3505.",
+      "concepts": [{
+       "http://webconcepts.info/concepts/xml-ns/": "http://webconcepts.info/concepts/xml-ns/urn:ietf:params:xml:schema:ECMLv2" }]}},{
      "4122": {
       "id": "http://webconcepts.info/specs/IETF/RFC/4122",
       "title": "A Universally Unique IDentifier (UUID) URN Namespace",

diff --git a/specs/IETF/RFC/4112.html b/specs/IETF/RFC/4112.html
@@ -0,0 +1,81 @@
+---
+layout:      page
+title:       "Electronic Commerce Modeling Language (ECML) Version 2 Specification"
+description: "Electronic commerce frequently requires a substantial exchange of information in order
+to complete a purchase or other transaction, especially the first time the parties
+communicate. A standard set of hierarchically-organized payment-related information
+field names in an XML syntax is defined so that this task can be more easily automated.
+This is the second version of an Electronic Commerce Modeling Language (ECML) and
+is intended to meet the requirements of RFC 3505."
+---
+
+<table cellpadding="5">
+   <tr>
+      <th valign="top" align="right">
+         <em>Document Name:</em>
+      </th>
+      <td>RFC 4112</td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Document URI:</em>
+      </th>
+      <td>
+         <code>urn:ietf:rfc:4112</code>
+      </td>
+   </tr>
+   <tr>
+      <th valign="top" align="right">
+         <em>Online Version:</em>
+      </th>
+      <td>
+         <code>
+            <a href="http://tools.ietf.org/html/rfc4112">http://tools.ietf.org/html/rfc4112</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>Electronic commerce frequently requires a substantial exchange of information in order
+         to complete a purchase or other transaction, especially the first time the parties
+         communicate. A standard set of hierarchically-organized payment-related information
+         field names in an XML syntax is defined so that this task can be more easily automated.
+         This is the second version of an Electronic Commerce Modeling Language (ECML) and
+         is intended to meet the requirements of RFC 3505.
+      </td>
+   </tr>
+</table>
+<br></br>
+<hr></hr>
+<h2 id="concepts">Specified Web Concepts:</h2>
+<h3 id="xml-ns">
+   <a href="/concepts/xml-ns/" title="List of all XML Namespaces">XML Namespaces</a>
+</h3>
+<code>
+   <a href="/concepts/xml-ns/urn:ietf:params:xml:schema:ECMLv2" title="ECML (Electronic Commerce Modeling Language) provides a set of hierarchical payment-oriented data structures that will enable automated software, including electronic wallets from multiple vendors, to supply and query for needed data in a more uniform manner.">urn:ietf:params:xml:schema:ECMLv2</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 164 listed specifications in the [Internet Engineering Task Force (IETF)](..)'s Request for Comments (RFC) series.
+There are currently 165 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)
@@ -41,6 +41,7 @@ There are currently 164 listed specifications in the [Internet Engineering Task
   * [Content-ID and Message-ID Uniform Resource Locators (RFC 2392)](2392)
   * [Delta encoding in HTTP (RFC 3229)](3229)
   * [Domain Name System Uniform Resource Identifiers (RFC 4501)](4501)
+  * [Electronic Commerce Modeling Language (ECML) Version 2 Specification (RFC 4112)](4112)
   * [Electronic Data Interchange - Internet Integration (EDIINT) Features Header Field (RFC 6017)](6017)
   * [Encrypted Content-Encoding for HTTP (RFC 8188)](8188)
   * [Enrollment over Secure Transport (RFC 7030)](7030)

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 209 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 210 specifications:
 
   * [Internet Draft (I-D)](I-D/) Series: 45 Specifications
-  * [Request for Comments (RFC)](RFC/) Series: 164 Specifications
+  * [Request for Comments (RFC)](RFC/) Series: 165 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/): 209 Specifications
+* [Internet Engineering Task Force (IETF)](IETF/): 210 Specifications
   * [Internet Draft (I-D) Series](IETF/I-D/ "Series overview"): 45 Specifications
-  * [Request for Comments (RFC) Series](IETF/RFC/ "Series overview"): 164 Specifications
+  * [Request for Comments (RFC) Series](IETF/RFC/ "Series overview"): 165 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

diff --git a/src/specs/rfc4112.xml b/src/specs/rfc4112.xml
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<service primary="IETF" secondary="RFC" id="4112">
+    <title>Electronic Commerce Modeling Language (ECML) Version 2 Specification</title>
+    <documentation source="http://tools.ietf.org/html/rfc4112">Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically-organized payment-related information field names in an XML syntax is defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meet the requirements of RFC 3505.</documentation>
+    <xml-ns def="urn:ietf:params:xml:schema:ECMLv2">
+        <documentation source="http://tools.ietf.org/html/rfc4112#section-1">ECML (Electronic Commerce Modeling Language) provides a set of hierarchical payment-oriented data structures that will enable automated software, including electronic wallets from multiple vendors, to supply and query for needed data in a more uniform manner.</documentation>
+    </xml-ns>
+</service>