Update ReSpec glossary to use dynamic terms list.
authorManu Sporny <msporny@digitalbazaar.com>
Wed, 15 Jul 2015 01:36:56 -0400
changeset 452 b59b62f1c2a7
parent 451 ac40aaeec5e7
child 453 1d7b4d045aa3
Update ReSpec glossary to use dynamic terms list.
latest/common/biblio.js
latest/glossary/index.html
--- a/latest/common/biblio.js	Wed Jul 15 00:59:17 2015 -0400
+++ b/latest/common/biblio.js	Wed Jul 15 01:36:56 2015 -0400
@@ -1,5 +1,17 @@
 var biblio = {
-	
+	"ISO-20022-CAPE": {
+    "authors": [
+      "SWIFT"
+    ],
+    "etAl": true,
+    "href": "http://www.iso20022.org/cards_and_retail_messages.page",
+    "title": "ISO 20022 Cards and Related Retail Financial Services",
+    "status": "International Standard",
+    "publisher": "International Standards Organization (ISO)",
+    "deliveredBy": [
+      "http://www.iso20022.org/contact.page"
+    ]
+	}
 // capture localBiblio entries here if needed - example below
 //	"WAI-ARIA-10": {
 //		"authors": [
--- a/latest/glossary/index.html	Wed Jul 15 00:59:17 2015 -0400
+++ b/latest/glossary/index.html	Wed Jul 15 01:36:56 2015 -0400
@@ -1,60 +1,385 @@
-<dl>
-  <dt><tdef>entity</tdef></dt>
-  <dd>
-A person, organization, or software agent that is capable of interacting with
-the world.
-  </dd>
-  <dt><tdef>payer</tdef></dt>
-  <dd>
-An <tref>entity</tref> that provides a source of funds as required by a
-<tref>transaction</tref>.
-  </dd>
-  <dt><tdef>payee</tdef></dt>
-  <dd>
-An <tref>entity</tref> that receives funds as required by a
-<tref>transaction</tref>.
-  </dd>
-  <dt><tdef>merchant</tdef></dt>
-  <dd>
-An <tref>entity</tref> receiving payment for goods, services, or other things
-of value; abstractly known as a <tref>payee</tref>.
-  </dd>
-  <dt><tdef>customer</tdef></dt>
-  <dd>
-An <tref>entity</tref> paying to receive goods, services, or other things
-of value; abstractly known as a <tref>payer</tref>.
-  </dd>
-  <dt><tdef>transaction</tdef></dt>
-  <dd>
-An instance of an exchange of value such as buying or selling something.
-  </dd>
-  <dt><tdef>payment scheme</tdef></dt>
-  <dd>
-Sets of rules and technical standards for the execution of payment transactions
-that have to be followed by adhering entities
-(<tref title="payment processor">payment processors</tref>,
-<tref title="payer">payers</tref> and <tref title="payee">payees</tref>).
-  </dd>
-  <dt><tdef>payment instrument</tdef></dt>
-  <dd>
-A mechanism used to transfer value from a <tref>payer</tref> to a
-<tref>payee</tref>.
-  </dd>
-  <dt><tdef>payment processor</tdef></dt>
-  <dd>
-Submits and processes payments using a particular
-<tref>payment instrument</tref> to a payment network.
-  </dd>
-  <dt><tdef>credential</tdef></dt>
-  <dd>
-A qualification, achievement, personal quality, aspect of an
-<tref>entity</tref>'s background, or verifiable statement by an entity about
-another entity.
-  </dd>
-  <dt><tdef>payment agent</tdef></dt>
-  <dd>
-A piece of software operating on an <tref title="entity">entity's</tref>
-behalf that is capable of executing
-<tref title="transaction">transactions</tref>.
-  </dd>
-</dl>
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>Web Payments Glossary 1.0</title>
+    <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
+    <script src="../common/biblio.js" class="remove"></script>
+    <script src='../respec-w3c-common.js' class='remove'></script>
+    <script src='../respec-webpayments.js' class='remove'></script>
+    <script src="../common/script/resolveReferences.js" class="remove"></script>
+    <script class='remove'>
+      var respecConfig = {
+          // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+          specStatus:           "ED",
+
+          // the specification's short name, as in http://www.w3.org/TR/short-name/
+          shortName:            "web-payments-glossary",
+
+          // if you wish the publication date to be other than today, set this
+          //publishDate:  "2015-04-16",
+
+          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+          // and its maturity status
+          // previousPublishDate:  "1977-03-15",
+          // previousMaturity:  "CG-DRAFT",
+
+          // if there a publicly available Editor's Draft, this is the link
+          edDraftURI:           "https://dvcs.w3.org/hg/webpayments/raw-file/default/latest/glossary/index.html",
+
+          // if this is a LCWD, uncomment and set the end of its review period
+          // lcEnd: "2009-08-05",
+
+          // if you want to have extra CSS, append them to this list
+          // it is recommended that the respec.css stylesheet be kept
+          //extraCSS:             [],
+          localBiblio: biblio,
+
+          // editors, add as many as you like
+          // only "name" is required
+          editors:  [
+              { name: "Evert Fekkes", url: "https://www.linkedin.com/in/fekkes",
+                company: "Rabobank", companyURL: "https://www.rabobank.com/" },
+              { name: "Shane McCarron", url: "https://www.linkedin.com/in/halindrome",
+                company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/" },
+              { name: "Manu Sporny", url: "https://manu.sporny.org/",
+                company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/" }
+          ],
+
+          // authors, add as many as you like.
+          // This is optional, uncomment if you have authors as well as editors.
+          // only "name" is required. Same format as editors.
+
+          authors:  [
+              { name: "Evert Fekkes", url: "https://www.linkedin.com/in/fekkes",
+                company: "Rabobank", companyURL: "https://www.rabobank.com/" },
+              { name: "Ian Jacobs", url: "http://www.w3.org/People/Jacobs/",
+                company: "W3C", companyURL: "http://www.w3.org/" },
+              { name: "Manu Sporny", url: "https://manu.sporny.org/",
+                company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/" }
+          ],
+
+          otherLinks: [{
+            key: "Version control",
+            data: [{
+              value: "Github Repository",
+              href: "https://github.com/w3c/webpayments-ig"
+            }, {
+              value: "Issues",
+              href: "http://www.w3.org/Payments/IG/track/products/1"
+            }]
+          }],
+
+          // maximum level of table of contents
+          maxTocLevel: 3,
+
+          // name of the WG
+          wg:           "Web Payments Interest Group",
+
+          // URI of the public WG page
+          wgURI:        "http://www.w3.org/blog/wpig/",
+
+          // name of the public mailing to which comments are due
+          wgPublicList: "public-webpayments-comments",
+
+          // URI of the patent status for this WG, for Rec-track documents
+          // !!!! IMPORTANT !!!!
+          // This is important for Rec-track documents, do not copy a patent URI from a random
+          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+          // Team Contact.
+          wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/73816/status",
+
+          //preProcess: [ webpayments.preProcess ]
+          /*,
+          alternateFormats: [ {uri: "diff-20111214.html", label: "diff to previous version"} ],
+          */
+      };
+      //respecEvents.sub('start-all', webpayments.preProcess.apply);
+    </script>
+  </head>
+<body>
+
+  <section id='abstract'>
+    <p>
+This document is the unified glossary used by all Web Payments Interest Groups
+and Working Groups operating under the W3C Web Payments Activity.
+    </p>
+  </section>
+
+  <section id='sotd'>
+    <p>
+This document is a work in progress and is being released early and often
+using an agile process; it is incomplete.
+    </p>
+    <p>
+The group continues to actively align the Web Payments terminology with
+definitions produced by other standardization bodies around the world.
+    </p>
+  </section>
+
+  <section>
+    <h2>Introduction</h2>
+    <p>
+This document is the unified glossary used by all Web Payments Interest Groups
+and Working Groups operating under the W3C Web Payments Activity.
+    </p>
+  </section>
+
+  <section>
+    <h2>Terminology</h2>
+
+    <div data-include="../common/terms.html">
+    </div>
+
+  </section>
+
+  <section>
+    <h2>Cross References</h2>
+
+    <p>
+This section contains cross references from terminology defined in this
+document to industry terminology defined in other specifications.
+    </p>
+
+    <section>
+      <h3><a>payer</a></h3>
+      <p>An entity that provides a source of funds as required by a transaction. </p>
+
+
+      <table border="1">
+	<tr>
+	  <th>Related Term</th>
+	  <th>Definition</th>
+	  <th>Scheme</th>
+	  <th>Relation</th>
+	  <th>Reference</th>
+	</tr>
+	<tr>
+	  <th>acceptor</th>
+	  <td class="term-dfn">An entity accepting payment related cards </td>
+	  <td>Credit/Debit</td>
+	  <td>Synonym</td>
+	  <td>[[ISO-20022-CAPE]]</td>
+	</tr>
+	<tr>
+	  <th>merchant</th>
+	  <td class="term-dfn">An entity which provides goods and/or services at one or several sites (physical or virtual). The merchant signs a contract with one or several acquirers. The merchant can perform the role of an acceptor or delegate it to another party (agent).</td>
+	  <td>General</td>
+	  <td>Specialization</td>
+	  <td>[[ISO-20022-CAPE]]</td>
+	</tr>
+      </table>
+
+    </section>
+
+    <section>
+      <h3><a>payee</a></h3>
+      <p>An entity that receives funds as required by a transaction.</p>
+
+      <table border="1">
+	<tr>
+	  <th>Related Term</th>
+	  <th>Definition</th>
+	  <th>Scheme</th>
+	  <th>Relation</th>
+	  <th>Reference</th>
+	</tr>
+	<tr>
+	  <th>customer</th>
+	  <td class="term-dfn">A party purchasing goods or services at a merchant </td>
+	  <td>General</td>
+	  <td>Specialization</td>
+	  <td>[[ISO-20022-CAPE]]</td>
+	</tr>
+      </table>
+
+    </section>
+
+    <section>
+      <h3><a>transaction</a></h3>
+      <p>An instance of an exchange of value such as buying or selling something. </p>
+
+      <table border="1">
+	<tr>
+	  <th>Related Term</th>
+	  <th>Definition</th>
+	  <th>Scheme</th>
+	  <th>Relation</th>
+	  <th>Reference</th>
+	</tr>
+	<tr>
+	  <th>transaction </th>
+	  <td class="term-dfn">An economic transaction is the whole of transfer of products, the rendering of services and transfers of money which are needed to complete a purchase or any other economic trade. An economic transaction can be seen as the complete economic session from start to finish between two or more parties. </td>
+	  <td>General</td>
+	  <td>Synonym</td>
+	  <td><a href="#UETP">UETP</a></td>
+	</tr>
+	<tr>
+	  <th>financial transaction</th>
+	  <td class="term-dfn">The act of a cardholder and a merchant or acquirer that results in the exchange of goods or services against payment. </td>
+	  <td>Credit/Debit</td>
+	  <td>Synonym</td>
+	  <td><a href="#EMVCO_TOKEN">EMVCO_TOKEN</a></td>
+	</tr>
+      </table>
+
+
+    </section>
+
+    <section>
+      <h3><a>purchase</a></h3>
+
+      <p>Activities surrounding and including a transaction (e.g., discovery of an offer, negotiation of terms, selection of payment instrument, delivery, etc.). </p>
+
+    </section>
+
+    <section>
+      <h3><a>payment</a></h3>
+      <p>@@TBD@@</p>
+
+      <table border="1">
+	<tr>
+	  <th>Related Term</th>
+	  <th>Definition</th>
+	  <th>Scheme</th>
+	  <th>Relation</th>
+	  <th>Reference</th>
+	</tr>
+	<tr>
+	  <th>payment</th>
+	  <td class="term-dfn">A payment is the transfer of an item of value from one party (such as a person or company) to another in exchange for the provision of goods, services or both, or to fulfill a legal obligation. Thus, a payment is a transfer of one form of good, service or monetary unit in exchange for another form of good, service or monetary unit in proportions that have been previously agreed upon by all parties involved. payment can be made in the form of funds (including cryptocurrencies) or assets. </td>
+	  <td>General</td>
+	  <td>Synonym</td>
+	  <td><a href="#UETP">UETP</a></td>
+	</tr>
+	<tr>
+	  <th>payment</th>
+	  <td class="term-dfn">The basic service which allows the cardholder to pay for the purchase of goods and services from a card acceptor using their card applications or credentials </td>
+	  <td>Credit/Debit</td>
+	  <td>Synonym</td>
+	  <td><a href="#EPC_Vol_1">EPC_Vol_1</a></td>
+	</tr>
+      </table>
+
+    </section>
+
+    <section>
+      <h3><a>payment scheme</a></h3>
+      <p>Sets of rules and technical standards for the execution of payment transactions that have to be followed by adhering entities (payment processors, payers and payees). </p>
+
+      <table border="1">
+	<tr>
+	  <th>Related Term</th>
+	  <th>Definition</th>
+	  <th>Scheme</th>
+	  <th>Relation</th>
+	  <th>Reference</th>
+	</tr>
+	<tr>
+	  <th>payment network</th>
+	  <td class="term-dfn">An electronic payment system used to accept, transmit, or process transactions made by payment cards for money, goods, or services, and to transfer information and funds among Issuers, Acquirers, Payment Processors, Merchants, and Cardholders.</td>
+	  <td>Credit/Debit</td>
+	  <td>Synonym</td>
+	  <td><a href="#EMVCO_TOKEN">EMVCO_TOKEN</a></td>
+	</tr>
+	<tr>
+	  <th>four party scheme</th>
+	  <td class="term-dfn">A Card Scheme which includes the following stakeholders: The Cardholder, the Issuer (who has a relationship with the Cardholder), the Acceptor and the Acquirer (which has a relationship with the Acceptor). The Scheme defines the rules which apply to all parties; there are no limitations as to who may join the scheme, as long as the requirements of the scheme are met. </td>
+	  <td>Credit</td>
+	  <td>Specialization</td>
+	  <td><a href="#EPC_Vol_1">EPC_Vol_1</a></td>
+	</tr>
+	<tr>
+	  <th>three party scheme</th>
+	  <td class="term-dfn">A Card Scheme including the following Stakeholders: the Cardholder, the Issuer (who has a relationship with the Cardholder), the Acceptor and the Acquirer (who has a relationship with the Acceptor), but the Issuer and the Acquirer are the same entity.</td>
+	  <td>Debit</td>
+	  <td>Specialization</td>
+	  <td><a href="#EPC_Vol_1">EPC_Vol_1</a></td>
+	</tr>
+      </table>
+
+
+    </section>
+
+    <section>
+      <h3><a>payment instrument</a></h3>
+
+      <p>A mechanism used to transfer value from a payer to a payee (payment method). </p>
+
+      <table border="1">
+	<tr>
+	  <th>Related Term</th>
+	  <th>Definition</th>
+	  <th>Scheme</th>
+	  <th>Relation</th>
+	  <th>Reference</th>
+	</tr>
+	<tr>
+	  <th>debit card</th>
+	  <td class="term-dfn">A card enabling its holder to make purchases and/or withdraw cash and have these transactions directly and immediately debited from the accounts </td>
+	  <td>Debit</td>
+	  <td>Specialization</td>
+	  <td><a href="#EPC_Vol_1">EPC_Vol_1</a></td>
+	</tr>
+	<tr>
+	  <th>credit card</th>
+	  <td class="term-dfn">A card enabling its holder to make purchases and/or withdraw cash and have these transactions directly and immediately debited from the accounts </td>
+	  <td>Credit</td>
+	  <td>Specialization</td>
+	  <td><a href="#EPC_Vol_1">EPC_Vol_1</a></td>
+	</tr>
+	<tr>
+	  <th>user account</th>
+	  <td class="term-dfn">In Web-based payment providers, payers are identified to the payment processor via user accounts.</td>
+	  <td>General</td>
+	  <td>Specialization</td>
+	  <td>None</td>
+	</tr>
+	<tr>
+	  <th>virtual currency</th>
+	  <td class="term-dfn">Virtual Currency is a digital representation of value, not issued by a central bank, credit institution or e-money institution, which, in some circumstances, can be used as an alternative to money. </td>
+	  <td>Digital Currency</td>
+	  <td>Specialization</td>
+	  <td><a href="#ECB">ECB</a></td>
+	</tr>
+      </table>
+
+    </section>
+
+    <section>
+      <h3><a>payment processor</a></h3>
+      <p>Submits and processes payments using a particular payment instrument to a payment network.</p>
+
+      <table border="1">
+	<tr>
+	  <th>Related Term</th>
+	  <th>Definition</th>
+	  <th>Scheme</th>
+	  <th>Relation</th>
+	  <th>Reference</th>
+	</tr>
+	<tr>
+	  <th>payment processor</th>
+	  <td class="term-dfn">An entity that provides payment processing services for Acquirers and / or Issuers. A Payment Processor may in addition to processing provide operational, reporting and other services for the Acquirer or Card Issuer. </td>
+	  <td>Credit/Debit</td>
+	  <td>Synonym</td>
+	  <td><a href="#EMVCO_TOKEN">EMVCO_TOKEN</a></td>
+	</tr>
+      </table>
+
+    </section>
+
+  </section>
+
+  <section class="appendix">
+    <h2>Acknowledgements</h2>
+    <p>
+The editors wish to thank the participants of the
+<a href="http://www.w3.org/Payments/IG/">Web Payments Interest Group</a>
+for discussions about and contributions to this document, as well as the
+<a href="https://www.w3.org/community/webpayments/">Web Payments Community
+Group</a> for earlier work that informed this document.
+    </p>
+  </section>
+
+  </body>
+</html>