W3C

Common Markup for micropayment per-fee-links

W3C Working Draft 25 August 1999

This version:
http://www.w3.org/TR/1999/WD-Micropayment-Markup-19990825
Latest version:
http://www.w3.org/TR/Micropayment-Markup
Previous versions:
http://www.w3.org/TR/1999/WD-Micropayment-Markup-19990609
http://www.w3.org/TR/1999/WD-Micropayment-Markup-19990315
Editor:
Thierry Michel (tmichel@w3.org)


Abstract

This specification provides an extensible way to embed in a Web page all the information necessary to initialize a micropayment (amounts and currencies, payment systems, etc). This embedding allows different micropayment electronic wallets to coexist in a interoperable manner.

Status of this document

The Micropayment Markup Working Group (W3C Members only), with this 1999 August 25th Final Public Working Draft, invites comment on our specification for "Common Markup for Micropayment per-fee-links".
This Working Group is part of the Micropayment task within the ECommerce Activity.

The W3C Membership and other interested parties are invited to review this public specification and report implementation experience. Please send comments to the publicly archived list www-micropay-comments@w3.org (archive).

This specification is in last call, comments from the Team and the Working Groups  are requested before 30th September 1999.
However this final Public Working Draft will be held at this stage to await significant implementation experience, allow possibly related work in other Micropayment WGs to progress further, and collect comments on the public mailing list.
The amount of implementation received by 2000 March 31th on the mailing list will determine if this draft  will be submitted for Proposed Recommendation is to occur. In that case, comments will be considered for a new Proposed Recommendation version that will follow very soon after.

While we welcome implementation experience reports, the Micropayment Markup Working Group will not allow early implementation to constrain its ability to make changes to this specification prior to final release .

This Working  Draft may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress".
A list of current W3C working drafts can be found at http://www.w3.org/TR.

Table of contents

  1. Introduction
    1. Origin and Goals
    2. Current status
    3. Principles and Parties
  2. Architecture
    1. Basic architecture
    2. Security
  3. Requirements
    1. Conformance Requirements
    2. Embedding Requirements
  4. Defined fields
    1. Fields description
      1. Price
      2. Text and Image to be linked
      3. Requesturl
      4. Buyid
      5. Specific field
      6. Title
      7. Longdesc
      8. Baseurl
      9. Merchant Identifier
      10. Duration
      11. Expiration
      12. Target
      13. Language
      14. Type
      15. AccessKey
      16. Character Encoding
      17. ExtData
      18. ExtDataParm
    2. General notes on fields
  5. Implementation
  6. Appendices
    1. Embedding information in HTML pages-Encoding for Plug-in or Applets
    2. Embedding information using RDF encoding
    3. Generate Embedding on the Server side
    4. Detecting the Browser capabilities
    5. Generate Encoding using Javascript on the client side
    6. List of payment systems
    7. Currency naming
  7. Acknowledgments
  8. References


1. Introduction

1.1 Origin and Goals

Micropayments provide an alternative revenue source for content providers (initially of text and pictures, presumably multimedia later on) beyond advertising and subscriptions. Micropayments may also provide revenue streams for service providers (database lookup, proxy services etc.).

Currently, there is no clear definition of a "Web micropayment" that encompasses all systems claiming to be micropayment systems. However, these systems all share the goal of minimizing the cost overhead of a single transaction. Most of these micropayment systems try to save costs, including financial risk-management costs, operational costs (including communication, processing, storage), and set-up costs.
Most micropayment systems also try to provide a simple user interface, especially making buying as easy as possible. We believe that to pay a small amount for content or services, the user should use the same user interface metaphor as for regular web content: just click on a hypertext link.
Namely, micropayment content shall be reached by clicking on special, new sort of links, which we call per-fee-links. Many of the existing micropayment systems do follow this approach, however each of them is using its own proprietary method of creating a per-fee-link and encoding the vital information in the per-fee-link.

This document proposes an extensible and interoperable way to embed in a Web page all the information necessary to initialize a micropayment, and in particular for encoding per-fee-links.

1.2 Current status

Today, a merchant willing to support multiple payment systems needs to embed in each Web page payment information specific to each target system, using a proprietary encoding for each one. Proprietary encodings introduce redundancy of information and extra work for Web page authors.
This situation motivates the need for a common markup supported by multiple payment systems.

1.3 Principles and Parties

Micropayments involve a buyer/customer C, a vendor/merchant M, and potentially one or more additional parties that keep accounts (usually called brokers [in Millicent], billing servers [in IBM MicroPayments], intermediaries [in France Telecom Micropayments], etc.). However in this document we focus only on the flow from the merchant to the customer, involved in the initialization of a micropayment.

2. Architecture

Parties involved in this specification architecture are Client and Merchant.

The Client initiates the micropayment when requesting information from the server.

2.1 Basic architecture

The basic architecture consist of:

basic architecture:Server,PFLH,Wallet,Browser,

[1] Merchant HTTP Server to Per Fee Link Handler flow
[2] Per Fee Link Handler to Wallet and Wallet to Per Fee Link Handler flows

This document focuses on the Merchant server to Per Fee Link Handler-Browser flow and specifies the payment markup information.

This document does not address:

Note. The API from Per Fee Link Handler (PFLH) to Wallet will be addressed in another specific API Working Draft. The PFLH functionalities will also be addressed in another specific PFLH Working Draft.

2.2 Security

This document specifies the encoding of per-fee-links inside HTML page sent from the merchant to the consumers browser. The specification does not describe the specific transport mechanism of the HTML page, although we expect that HTTP will be used as it is the transport mechanism used by existing browsers. In particular, the specification does not address security concerns related to the transmission of the per-fee-link from merchant to client, such as authentication of the parameters in the per-fee-link (such as price) and confidentiality of the per-fee-link. If such security concerns exist, the application SHOULD use appropriate mechanisms, e.g. protect the confidentiality and authenticity of all communication between consumer and merchant using the Secure Sockets Layer [SSL] (HTTPS) protocol.

3 Requirements

This document section specifies requirements for interoperability among micropayment systems.

3.1 Conformance requirements

The words "MUST" (or "required"), "SHOULD" (or "recommended"), and "MAY" (or "optional") are used throughout the document and should be read as interoperability requirements. The words are used as defined in RFC2119 [RFC2119] for defining the significance of each particular requirement.

An implementation conforms to this specification if it satisfies all of the normative statements ("MUST" or "required") in this document.

3.2 Embedding requirements:

Requirements for embedding micropayment information in web pages are:

4. Defined fields

4.1 Field description

All the following common fields MUST be provided for conformance:  price,  textlink, requesturl, payment system.

In addition, there SHOULD be a title field. There  MAY be an imagelink, buyid, baseurl, longdesc, merchantname, durationexpiration, target, hreflang, type, accesskey,  charset, ExtData, ExtDataParm and information that a specific payment system requires.

Micropayment fields
Field name Short Description Format Requirements
price Specifies the default amount and currency that the Customer will be charged upon following the per-fee-link. character string MUST be provided
textlink Textual description of what the client is requesting. The text source of the per-fee-link. character string MUST be provided
imagelink Graphical description of what the client is requesting. The graphic source of the per-fee-link. (here textlink provides a textual equivalent of the image for accessibility). URI MAY be provided
requesturl Identifies what the client is actually requesting URI MUST be provided
payment system Identifies the micropayment systems supported by the merchant
and can also provide information unique to each payment system
URI
character string
MUST be provided
MAY be provided
buyid Identifies the merchant offer the client is buying or has already bought URI MAY be provided
baseurl Provides a common prefix for  relative URIs (e.g. the buyid and requesturl parameters) absolute URI MAY be provided
title Titles the content of the merchant offer the client is buying or has already bought character string SHOULD be provided
longdesc Describes in detail the content of the merchant offer the client is buying or has already bought URI MAY be provided
merchantname Specifies a merchant designation character string MAY be provided
duration Indicates the time after purchase any URIs with the same buyid can be retrieved without further payment. integer number MAY  be provided
expiration Indicates a date until which the offer from the merchant is valid. date/time string
YYYY-MM-DDThh:mm:ssZ
MAY be provided
target Specifies the name of a frame where a document is to be loaded. character string MAY be provided
hreflang Specifies the base language of the resource designated by the per-fee-link. language codes MAY be provided
type Specifies the content type of  the linked resource, designated by the per-fee-link. Mimetypes MAY be provided
accesskey Assigns an access key to a per-fee-link. character string MAY be provided
charset Specifies the character encoding of the resource designated by the per-fee-link. Charset MAY be provided
ExtData Allows linking to an external metadata  file describing additional information regarding the per-fee-link. URI MAY be provided
ExtDataParm Provides a parameter to be applied for interpreting the contents of the ExtData file. character string MAY be provided

4.1.1 Price

The price parameter, which takes a character string, specifies the default amount and currency that the Customer will be charged upon following the link (if not already paid for). However this price may be overridden by the specific payment system with which the payment is to be made. The character string MUST be encoded as an amount followed by a currency unit as follows:

This price parameter is mandatory and MUST be provided unless ExtData  parameter is provided and the price is specified there.

4.1.2 Text or Image to be linked

The textlink parameter, which takes a character string, provides a textual description of what the client is requesting. It is the text source of the per-fee-link.
This textlink parameter is mandatory and MUST be provided.

The imagelink parameter, which takes a URI, provides a graphical description of what the client is requesting. It is the graphic source of the per-fee-link.
When using this imagelink  parameter, the textlink parameter provides a textual equivalent for the image and is necessary for accessibility.

4.1.3 Requesturl

The requesturl parameter, which takes a URI, identifies what the client is actually requesting through the current per-fee-link. This requested url is a part of the merchant offer identified by buyid. It can be either an absolute URI or relative URI only if the baseurl parameter is specified. (allowing the wallet to construct the final URL)

This requesturl parameter is mandatory and MUST be provided.

4.1.4 Buyid

The buyid parameter, which takes a URI, identifies the merchant offer the client is buying (or has already bought). It can be either an absolute URI or relative URI only if the baseurl parameter is specified. (allowing the wallet to construct the final URL).
This parameter MAY be identical to the requesturl parameter. It MAY be different if, for example, the client has purchased a collection of pages and requests only one of these pages. In this case, the resource identified by buyid is larger than that identified by requesturl parameter.
A merchant offer has an associated set of requesturl's, that is a set of per-fee-links. requesturl are identifiers for per-fee-links. Payment for the whole set is required when you first request one per-fee-link of the set.
This buyid parameter is optional and MAY be provided. If it is omitted we assume it is identical to requesturl.

4.1.5 Payment System Identifier and specific field

This specific field MUST be present in order to provide an identifier of at least one usable payment system, and all suitable systems SHOULD be named.  When required, it MAY also provide parameters specific to each payment system identified as mentioned above, insuring coexistence among the different payment systems. Thus, there can be as many parameter sets  (identifier and specific parameters) as there are payments systems supported by the merchant.

The identifier for a payment system MUST be a URI, unless this payment system is registered (see Appendix 6), in which case the registered short name is to be used.
Additional specific information MAY be provided with a character string.
Information  provided in the specific field SHOULD be used to override information  specified in the common fields above. To allow multiple specific parameters, one MUST provide and use the following naming convention:

Note. We recommend that when a system uses specific parameters for the same meaning as the common (non-specific) parameters defined above in the specification, the same parameter name will be used e.g. name="1.mpprice", name="1.mpbaseurl"  and the same syntax if possible. Normally such a parameter SHOULD override the common (non-specific) parameter.

4.1.6 Title

The title parameter, which takes a character string, titles the resource of the merchant offer the client is buying or has already bought (needed for registration in wallet log files for example).
This title parameter is optional but SHOULD be provided.

4.1.7 Longdesc

The longdesc parameter, which takes a URI, provides a detailed description of the merchant offer the client is buying.
This longdesc parameter is optional and MAY be provided.

4.1.8 Baseurl

The baseurl parameter specifies an absolute URI that acts as the base URI for resolving relative URIs (e.g. a prefix for the buyid and requesturl parameters).
It identifies the merchant site where the purchase is to occur, plus a path and a specific character string $MP$ to be replaced by the wallet by a proper payment system short code name. This search for $MP$ happens before  any unescaping of the URL is done. (see Appendix 6).

Examples of such a string are:

http://www.merchant.org/shop/sales/$MP$/
http://www.$MP$.merchant.org/shop/sales/

This baseurl parameter is optional and MAY be provided.

4.1.9 Merchant Site Identifier

The merchantname parameter, which takes a character string, allows giving a merchant name designation. This optional  parameter provides a user-viewable version of the name of the merchant. The wallet will need to validate this (to make sure this really corresponds to the merchant ID in the payment system - MAY also use some specific parameter if needed).

4.1.10 Duration

The duration parameter, which takes an integer number of seconds, indicates the time after purchase any URIs with the same buyid can be retrieved without further payment.
This duration parameter MAY be provided. In case it is not provided, a default value is set to zero (meaning that the per-fee-link can be only retrieved once after purchase).

4.1.11 Expiration

The expiration parameter, which takes a date and time, indicates a date and time until which the offer from the merchant is valid. After this given date and time the offer has expired and any attempt to buy it will be rejected.

rejected
It is an optional parameter and MAY be provided.

The value of this parameter, a date/time string, MUST use the following format as described in [DATETIME]:

   YYYY-MM-DDThh:mm:ssTZD

This format includes the complete date (YYYY-MM-DD) separated from the time  by the letter (T), which MUST include hours (hh), minutes (mm), seconds (ss) and a time zone designator (TZD) where TZD is restricted to Z. Times are always expressed in UTC (Coordinated Universal Time), with the special UTC designator ("Z").
An example of such a string is "1999-11-05T13:15:30Z"
Please consult [DATETIME] for the meaning of each field.

4.1.12 Target

The target parameter, which takes a character string, specifies the name of a frame where a document is to be loaded.

By assigning a name to a frame via the name attribute, authors can refer to it as the "target" of per-fee-links. Except for the reserved names listed below, frame target names MUST begin with an alphabetic character (a-zA-Z). User agents SHOULD ignore all other target names.
The following target names are reserved and have special meanings:

This target parameter is optional and MAY be provided. If not provided, a default value is set to _self (meaning that the document  will load in the same frame as current per-fee-link).

4.1.13 Language

The hreflang parameter identifies the language of  the linked resource.
[RFC1766] defines and explains the language codes to be used. Briefly, language codes consist of a primary code and a possibly empty series of subcodes: language-code = primary-code ( "-" subcode )*
Here are some sample language codes:
"en": English
"en-US": the U.S. version of English.
"en-cockney": the Cockney version of English.
"i-navajo": the Navajo language spoken by some Native Americans.
"x-klingon": The primary tag "x" indicates an experimental language tag

Two-letter primary codes are reserved for [ISO639] language abbreviations. Two-letter codes include fr (French), de (German), it (Italian), nl (Dutch), el (Greek), es (Spanish), pt (Portuguese), ar (Arabic), he (Hebrew), ru (Russian), zh (Chinese), ja (Japanese), hi (Hindi), ur (Urdu), and sa (Sanskrit). Any two-letter subcode is understood to be a [ISO3166] country code.

This hreflang parameter is optional and MAY be provided.

4.1.14 Type

The type parameter specifies the content type of  the linked resource.
Examples of content types include "text/html", "image/png", "image/gif", "video/mpeg", "audio/basic", "text/tcl", "text/javascript", and "text/vbscript". For the current list of registered MIME types, please consult [MIMETYPES].

This type parameter is optional and MAY be provided.

4.1.15 AccessKey

The accesskey parameter, which takes a character string, assigns an access key to a per-fee-link. An access key is a single character from the document character set.
Pressing an access key assigned to a per-fee-link gives focus to the per-fee-link. When a user activates a per-fee-link, the user agent generally follows the link.

Examples of such a string is:
accesskey="L". Typing this access key takes the user to the requested document of the current per-fee-link.

This accesskey parameter is optional and MAY be provided.

4.1.16 Character Encoding

The charset parameter specifies the character encoding of the resource designated by the per-fee-link, allowing conversion of  a sequence of bytes into a sequence of characters. Please consult the section on character encodings in the HTML4.0 Recommendation for more details.
Values must be strings (e.g., "euc-jp") from the [IANA] registry (see [CHARSETS] for a complete list). Names of character encodings are case-insensitive.
An example of such a string is charset="ISO-8859-1"

This charset parameter is optional and MAY be provided.

4.1.17 ExtData

The ExtData  parameter, which takes a URI, allows linking to an external metadata  file describing additional information regarding the per-fee-link.

Formats for this metadata file will be defined in future documents of this group, and are likely to be expressed using the Resource Description Framework ([RDF]). This metadata file will typically express parameters common to many per-fee-links such as currency conversion table, price-code table (mapping from price code to price), general information and policy of the seller, etc. The information may override parameters provided with the per-fee-link (e.g. price).
This ExtData parameter is optional and MAY be provided.

4.1.18 ExtDataParm

Provides a parameter to be applied for interpreting the contents of the ExtData file. A typical example would be a price code, to be used as the entry into a price-code table to provide the actual price.
This ExtDataParm parameter is optional, it MAY be provided but only if ExtData is provided.

4.2 General notes on fields

Note. It is an error to provide:

In these cases response is undefined (preferably an error message - probably done by browser.)

Note. Any common parameters provided in an external file through the ExtData parameter SHOULD override information specified in all the common parameters above.

Note. The parameters baseurl, requesturl are passed by PFLH to the wallets, allowing to construct the payment-system-specific URL for the merchandise (to be used in the HTTP GET/POST back to the merchant server). These fields MAY be overruled if necessary, by a payment-system specific baseurl parameter (e.g. if different payment systems are on different web servers at the merchant).

The URL sent to the wallet  identifies a merchant site where the purchase is to occur, plus a path and a specific character string $MP$ to be replaced by the wallet by a proper payment system short code name (see Appendix 6).

Fields involved in final URL constructed by Wallet
baseurl parameter requesturl parameter
Merchant site Path Payment system URL suffix (Client Requested url)
http://www.merchant.org/ shop/sales/ $MP$ elvis.html
URL sent to Wallet: http://www.merchant.org/shop/sales/$MP$/elvis.html
Final URL constructed by Wallet for Payment Order : http://www.merchant.org/shop/sales/Micropay/elvis.html

5. Implementation

One of the main requirements expressed in this document is that embedding micropayment information in HTML SHOULD work with all current browsers.
The Working Group has also required interoperability among micropayment systems though a common Markup.

For current browsers, embedding information in HTML pages MUST be done using a Per Fee Link Handler, which MUST  be a plug-in or JAVA Applet.
This embedding MUST be done as described in  Appendix 1.

Today most browsers are non-RDF-aware browsers, but we cite an example embedding of micropayment information using Resource Description Framework ([RDF]) for future RDF-compliant user agents in Appendix 2.

In order to have this embedding using RDF to work with current browsers, a "transformation engine" hosted on the server could transform the HTML document linked and the RDF document into an HTML document that includes either OBJECT or APPLET or EMBED elements, making it understandable by current browser versions. This architecture is proposed for informational purposes in Appendix 3.

In order to send to the browser  the proper HTML page (with OBJECT or APPLET or EMBED elements) the Merchant server needs to know the capabilities of this browser. Is the Browser JAVA enabled ? Is the  right Plugin installed in the browser ? etc. Solutions and code  are  proposed for informational purposes in Appendix 4.

An Alternative implementation is to generate the HTML page on the client side using Javascript for example. After detection of the browser capabilities, a script can generate the elements and attributes for each fee link.Solutions and code  are  proposed in Appendix 5.


Appendices

Appendix 1: Embedding micropayment information  in HTML pages using encodings for Plug-ins or Applets.

Due to requirements expressed above, embedding micropayment information SHOULD use standard (or de-facto standard) features which are implemented by most currently available browsers.

All requested information needed to start micropayment MUST be present in the HTML page sent from the merchant server.
For current browsers, embedding information in HTML pages can be done using a Per Fee Link Handler, which MUST either be a plug-in or JAVA Applet.

In order to allow the Per Fee Link Handler to process this information, it SHOULD be stored in an OBJECT element.

For user agents that do not support the OBJECT element, and for reasons of backward compatibility, authors MAY use the APPLET or EMBED element.
Note.
The APPLET element is deprecated in HTML 4.0 and SHOULD be avoided. The EMBED element is not part of a W3C Recommendation and SHOULD be avoided. Authors SHOULD use the  OBJECT element.

A1.1 OBJECT element

HTML 4.0 introduced the OBJECT element ([HTML40], section 13.3) to allow HTML authors to specify everything required by an object for its presentation by a user agent: source code, initial values, and run-time data. The term "object" refers to applets, plug-ins, media handlers, etc.

<OBJECT codetype="application/java" 
         classid="http://www.miamachina.org/applet/micropayment.class">
<PARAM name="duration" value="60" valuetype="data"> A per-fee-link that needs an applet for rendering </OBJECT>

The HTML 4.0 specification defines the attributes of the OBJECT element.
The "classid" attribute specifies the location of the OBJECT's implementation with a URL.
The "codetype" attribute specifies the content type of data to expect when downloading the OBJECT.
The PARAM element within an OBJECT element specifies values to give to the object at run-time (as name/value pairs).

A1.2 APPLET element

For user agents that do not support the OBJECT element and for reasons of backward compatibility, authors MAY use the APPLET element. HTML 3.2 ([HTML32]) introduced the APPLET element to allow designers to embed a Java applet in an HTML document. It is supported by all Java-enabled browsers, but has been deprecated in HTML 4.0 in favor of the OBJECT element.

<APPLET codebase="http://www.miamachina.org/applet/" 
        code="micropayment.class" 
        archive="myclasses.jar,myaudio.jar">
     <PARAM name="duration" value="60" valuetype="data">
A per-fee-link that needs an applet for rendering.
</APPLET>

The HTML 4.0 specification ([HTML40], section 13.4) defines the attributes of the (deprecated) APPLET element.
The "codebase" attribute specifies the base URL for the applet.
The "code" attribute specifies either the name of the class file that contains the applet's compiled applet subclass or the path to get the class.
The "archive" attribute specifies a comma-separated list of URIs designated resources to preload such as signed (trusted) code such as a Per Fee Link Handler.
The PARAM element within an APPLET element specifies values to give to the object at run-time (as name/value pairs).

A1.3 EMBED element

For user agents that do not support the OBJECT element and for reasons of backward compatibility, authors MAY use EMBED element.
Note.
Whenever the OBJECT element can be used, authors SHOULD avoid EMBED because it is not defined by a W3C Recommendation.

This EMBED element, supported by all plug-in-enabled browsers, allows designers to embed a plug-in in an HTML document.

<EMBED src="http://www.miamachina.org/MicropaymentPlugin.exe" 
       duration="60">
A per-fee-link that needs a plug-in for rendering.
</EMBED>

Optional parameters within EMBED element will be used to pass required information by the plug-in at run-time.

PARAMETER_NAME=PARAMETER_VALUE

A1.4 Per Fee Link Handler for OBJECT, APPLET, and EMBED element.

The PFL Handler is a module that can either be a plug-in or a Java Applet.
It could be implemented in Java 1.2 allowing signed JAVA applets in browsers supporting it, and otherwise as a plug-in.

The Per Fee Link Handler (PFLH) functionalities will be addressed in a specific Working Draft.

A1.5 Syntax for embedded per-fee-link using OBJECT, APPLET, and EMBED element.

The Baseurl data field:

For OBJECT and APPLET:

<PARAM name="baseurl" value="http://www.merchant.org/shop"
valuetype="ref">
<PARAM name="merchantname" value="ShopAndPay" valuetype="data">

For EMBED:

baseurl="http://www.merchant.org/shop"
merchantname="ShopAndPay"

The ClientBuy data field:

For OBJECT and APPLET:

<PARAM name="buyid" value="catalog.html" valuetype="ref">

For EMBED:

buyid="catalog.html" 

The ClientRequest data field:

For OBJECT and APPLET:

<PARAM name="requesturl" value="elvis.html" valuetype="ref">

For EMBED:

requesturl="elvis.html"

The textlink and imagelink data fields :

For OBJECT and APPLET:

<PARAM name="textlink" value="Buy the biography of Elvis"
valuetype="data">
<PARAM name="imagelink" value="http://www.merchant.org/product.gif"
valuetype="ref">

For EMBED:

textlink="Buy the biography of Elvis"
imagelink="http://www.merchant.org/product.gif"

The Price data field:

For OBJECT and APPLET:

<PARAM name="price" value="+0.01USD" valuetype="data">
statement for one cent of a US Dollar.

For EMBED:

price="+1E-2FRF"
statement for one cent of a French Franc.

The Title data field:

For OBJECT and APPLET:

<PARAM name="title" value="Biography of Elvis"
  valuetype="data">

For EMBED:

title="Biography of Elvis"

The Duration data field

For OBJECT and APPLET:

<PARAM name="duration" value="60" valuetype="data">

For EMBED:

duration="60"

The Expiration date data field:

For OBJECT and APPLET:

<PARAM name="expiration" value="1999-11-05T13:15:30Z"
valuetype="data">

corresponds to November 5, 1999, 8:15:30 am, GMT Time.

For EMBED:

expiration="1999-11-05T13:15:30Z"

corresponds to the same instant as above.

For data fields specific to a micropayment system:

For OBJECT and APPLET:

<PARAM name="1.mpname" value="micropayment"
       valuetype="data">
<PARAM name="1.mpurl" value="http://www.foo.it/micropay"
       valuetype="ref">
<PARAM name="1.specific" value="124rfdetg14ft58rdef21f4251"
       valuetype="data">
<PARAM name="1.mpbaseurl" value="http://www.merchant.it/"
       valuetype="ref">


<PARAM name="2.mpname" value="millipayment" valuetype="data"> <PARAM name="2.mpurl" value="http://www.foo.it/millipay" valuetype="ref"> <PARAM name="2.specific" value="475rdg546tfeww12wcft254hy4" valuetype="data"> <PARAM name="2.mpbaseurl" value="http://www.merchant.fr/" valuetype="ref">

For EMBED:

1.mpname="micropayment"
1.mpurl="http://www.foo.it/micropay"
1.specific="124rfdetg14ft58rdef21f4251" 1.mpbaseurl="http://www.merchant.it/" 2.mpname="millipayment"
2.mpurl="http://www.foo.it/millipay" 2.specific="475rdg546tfeww12wcft254hy4" 2.mpbaseurl="http://www.merchant.fr/"

A1.6  HTML example of embedded per-fee-link using OBJECT element.

<HTML><HEAD>
<TITLE>Example:Fee Link for an Java Applet PFLH using OBJECT element
</TITLE></HEAD> <BODY> <OBJECT codetype="application/java" classid="http://www.miamachina.org/applet/micropayment.class"> <PARAM name="baseurl" value="http://www.merchant.org/shop" valuetype="ref">
<PARAM name="merchantname" value="ShopAndPay" valuetype="data"> <PARAM name="buyid" value="catalog.html" valuetype="ref"> <PARAM name="requesturl" value="elvis.html" valuetype="ref"> <PARAM name="textlink" value="Buy the biography of Elvis"
valuetype="data"> <PARAM name="price" value="+0.01USD" valuetype="data">
<PARAM name="title" value="Biography of Elvis"
valuetype="data"> <PARAM name="duration" value="60" valuetype="data"> <PARAM name="expiration" value="1999-11-05T13:15:30Z"
valuetype="data">
<PARAM name="1.mpname" value="micropayment" valuetype="data"> <PARAM name="1.mpurl" value="http://www.foo.it/micropay" valuetype="ref"> <PARAM name="1.specific" value="124rfdetg14ft58rdef21f4251" valuetype="data"> <PARAM name="1.mpbaseurl" value="http://www.merchant.it/" valuetype="ref">
<PARAM name="2.mpname" value="millipayment" valuetype="data"> <PARAM name="2.mpurl" value="http://www.foo.it/millipay" valuetype="ref"> <PARAM name="2.specific" value="475rdg546tfeww12wcft254hy4" valuetype="data"> <PARAM name="2.mpbaseurl" value="http://www.merchant.fr/" valuetype="ref"> A per-fee-link that needs an applet for rendering. </OBJECT> </BODY></HTML>

A1.7  HTML example of embedded per-fee-link using APPLET element.

<HTML><HEAD>
<TITLE>Example:Fee Link for an Java Applet PFLH using APPLET element
</TITLE></HEAD> <BODY> <APPLET codebase="http://www.miamachina.org/applet/" code="micropayment.class" archive="myclasses.jar,myaudio.jar"> <PARAM name="baseurl" value="http://www.merchant.org/shop" valuetype="ref">
<PARAM name="merchantname" value="ShopAndPay" valuetype="data"> <PARAM name="buyid" value="catalog.html" valuetype="ref"> <PARAM name="requesturl" value="elvis.html" valuetype="ref"> <PARAM name="textlink" value="Buy the biography of Elvis"
valuetype="data"> <PARAM name="price" value="+0.01USD" valuetype="data">
<PARAM name="title" value="Biography of Elvis"
valuetype="data"> <PARAM name="duration" value="60" valuetype="data"> <PARAM name="expiration" value="1999-11-05T13:15:30Z"
valuetype="data">
<PARAM name="1.mpname" value="micropayment" valuetype="data"> <PARAM name="1.mpurl" value="http://www.foo.it/micropay" valuetype="ref"> <PARAM name="1.specific" value="124rfdetg14ft58rdef21f4251" valuetype="data"> <PARAM name="1.mpbaseurl" value="http://www.merchant.it/" valuetype="ref">
<PARAM name="2.mpname" value="millipayment" valuetype="data"> <PARAM name="2.mpurl" value="http://www.foo.it/millipay" valuetype="ref"> <PARAM name="2.specific" value="475rdg546tfeww12wcft254hy4" valuetype="data"> <PARAM name="2.mpbaseurl" value="http://www.merchant.fr/" valuetype="ref"> A per-fee-link that needs an applet for rendering. </APPLET> </BODY></HTML>

A1.8  HTML example of embedded per-fee-link using EMBED element.

<HTML><HEAD>
<TITLE>Example:Fee Link for a Plugin PFLH using EMBED element
</TITLE></HEAD> <BODY> <EMBED src="http://www.miamachina.org/MicropaymentPlugin.exe" baseurl="http://www.merchant.org/shop" merchantname="ShopAndPay" buyid="catalog.html" requesturl="elvis.html" textlink="Buy the biography of Elvis" price="+0.01USD"
title="Biography of Elvis"
duration="60" expiration="1999-11-05T13:15:30Z"
1.mpname="micropayment" 1.mpurl="http://www.foo.it/micropay"
1.specific="124rfdetg14ft58rdef21f4251" 1.mpbaseurl="http://www.merchant.it/" 2.mpname="millipayment"
2.mpurl="http://www.foo.it/millipay" 2.specific="475rdg546tfeww12wcft254hy4" 2.mpbaseurl="http://www.merchant.fr/" >
A per-fee-link that needs a plug-in for rendering.
</EMBED> </BODY></HTML>

A1.9  HTML example of embedded per-fee-link using OBJECT element and metadata file.

<HTML><HEAD>
<TITLE>Example:Fee Link for an Java Applet PFLH using OBJECT element and ExtData field
</TITLE></HEAD> <BODY> <OBJECT codetype="application/java" classid="http://www.miamachina.org/applet/micropayment.class"> <PARAM name="ExtData" value="http://www.merchant.org/shop/Micropayment-perfeelinks.rdf" valuetype="ref"> <PARAM name="price" value="+0.01USD" valuetype="data">
A per-fee-link that needs an applet for rendering. </OBJECT> </BODY></HTML>

In this last example the ExtData parameter allows linking to external metadata describing this per-fee-link. On retrieval of the RDF file, the Java applet parses this file and extracts the common micropayment fields (e.g. price,  textlink, requesturl, payment system, title, imagelink, buyid, baseurl, longdesc, merchantname, durationexpiration, etc.).
Refer to Apendix 2 for examples using RDF encoding.

Note. Information  provided in this ExtData parameter SHOULD be overriden by  information  specified in all the common parameters above.
So in this example, the price mentioned in the PARAM element will override any price mentioned in the RDF file.

Appendix 2: Embedding micropayment information using RDF encoding .

This embedding using  the Resource Description Framework ([RDF]) is an example implementation allowing different micropayment electronic wallets to coexist in a interoperable manner.
All the Required fields are stated above in this document.

A2.1 Benefits with RDF encoding:

Micropayment information can be embedded in HTML pages using RDF to be processed by RDF-compliant user agents.
Micropayment information are statements that are properly expressed according to the Resource Description Framework ([RDF]). There are a number of reasons to use RDF as a data format for micropayments:

As metadata, the information for micropayments can thereby be reasoned upon, and fully integrated with all the other information stored in  the World Wide Web.

A2.2 RDF Transport:

In order to fully exploit these benefits, it is suggested that the necessary parameters for micropayments are encoded in RDF and shipped by one or more of the following ways:

  1. External from the content, linked (in the case of HTML files with the LINK element). We recommend using the link relation type ([HTML40], section 6.12) of "meta" for this purpose. For example:
    <LINK rel="meta" href="Micropayment-links.RDF">
  2. Included in the content of a Web in the section of the HTML document (inside the HEAD element).
  3. Together with the content in the HTTP headers.


The recommended technique for embedding RDF expressions in an HTML document ([RDF], Appendix B.) is simply to insert the RDF in-line.

Note. The resulting document will no longer conform to HTML specifications up to and including [HTML40], but the W3C anticipates that the HTML language will evolve to support this. See current  new [XHTML] work.

A2.3 RDF Model:

The RDF model using nodes and arcs diagram

Figure 1: The RDF model (nodes and arcs diagram).

Note. The prose corresponding to this diagram could be read as follows :
The per-fee-link (#feelink-1) whose price is one centime of FRF, requesturl is "elvis.html", buyid is "catalog.html", longdesc is "description.html", baseurl is "http://www.merchant.org/shop/", duration is 60 seconds and expiration date is 1999-11-05T13:15:30Z, has alternative payment systems - identified by name "AlternativePaymentSystems".
The first payment system is called "micropay1". It has a name "http://www.foo.it/micropay1" and a value "xxxxxxxxxxxxxxxxxxxx".
The second payment system is called "micropay2". It has a name "http://www.foo.it/micropay2" and a value "yyyyyyyyyyyyyyyyyyyy".

A2.4 Example of per-fee-link using RDF encoding :

A2.4.1 Text or image to be linked :

The per-fee-link is specified with the A element from HTML 4.0.

For a text to be linked, the textlink parameter is in this case the content of the A element.
The  "id" attribute is used to assign a unique identifier to the A element.
The requesturl parameter is the value of the "href" attribute of the A element, identifying the source anchor. It could be either a relative or absolute URL.
The title parameter is the value of the "title" attribute of the A element.
The hreflang parameter is the value of the "hreflang" attribute of the A element.
The accesskey parameter is the value of the "accesskey" attribute of the A element.
The charset parameter is the value of the "charset" attribute of the A element.
The target parameter is the value of the "target" attribute of the A element.

<BODY>
<A href="elvis.html" id="feelink-1" 
title="Biography of Elvis"
accesskey="L" charset="ISO-8859-1" type="text/html"
hreflang="en-US" target="_blank">
Buy the Biography of Elvis through this Per-fee-link </A>
</BODY>

For an image to be linked, the per-fee-link is specified using the A and IMG elements of HTML.
The imagelink parameter is the value of the "src" attribute of IMG element and in this case the textlink parameter is the value of the "alt" attribute of IMG element.

<BODY>
<A href="elvis.html" id="feelink-img1"
title="Biography of Elvis">
<IMG src="http://www.merchant.org/product.gif" 
     alt="Buy the Biography of Elvis through this Per-fee-link"> </A>
</BODY>

The following RDF statements describing this per-fee-link are mentioned in the HEAD of the HTML document as follows:

a- Basic Serialization Syntax :

The specification of RDF uses the Extensible Markup Language [XML] encoding as its interchange syntax. RDF also requires the XML namespaces facility to precisely associate each property with the schema that defines the property; see Section 2.2.3., Schemas and Namespaces.

When a fragment of RDF is incorporated into an HTML document some browsers will render any exposed string content. Exposed string content is anything that appears between the ">" that ends one tag and the "<" that begins the next tag.

<HEAD>
<TITLE>Example of Fee Link - Basic Serialization RDF Syntax Encoding</TITLE>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:mp="http://www.w3.org/schema/micropay#"> <rdf:Description about="#feelink-1"> <mp:price>1E-2FRF</mp:price> <mp:baseurl rdf:resource="http://www.merchant.org/shop"/> <mp:buyid rdf:resource="catalog.html"/> <mp:requesturl rdf:resource="elvis.html"/> <mp:longdesc rdf:resource="description.html"/> <mp:duration>60</mp:duration> <mp:expiration>1999-11-05T13:15:30Z</mp:expiration> <mp:paymentsystem> <rdf:Alt> <rdf:li> <rdf:Description ID="micropay1"> <rdf:type resource="http://www.w3.org/schema/micropay#paymentoption"/> <mp:name rdf:resource="http://www.foo.it/micropay1"/> <rdf:value>xxxxxxxxxxxxxxxxxx</rdf:value> </rdf:Description> </rdf:li> <rdf:li> <rdf:Description ID="micropay2"> <rdf:type resource="http://www.w3.org/schema/micropay#paymentoption"/> <mp:name rdf:resource="http://www.foo.it/micropay2"/> <rdf:value>yyyyyyyyyyyyyyyyyyyy</rdf:value> </rdf:Description> </rdf:li> </rdf:Alt> </mp:paymentsystem> </rdf:Description> </rdf:RDF> </HEAD>

b-Basic Abbreviated Syntax

While the serialization syntax shows the structure of an RDF model most clearly, often it is desirable to use a more compact XML form. The RDF abbreviated syntax accomplishes this.

The RDF abbreviated syntax can frequently be used to write property values that are strings in attribute form and leave only white space as exposed content.

The following RDF abbreviated syntax is equivalent to the above Basic Serialization Syntax.

<HEAD>
<TITLE>Example of Fee Link - Abbreviated RDF Syntax Encoding</TITLE>
<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:mp="http://www.w3.org/schema/micropay#">
  <rdf:Description about="#feelink-1"
    mp:price="1E-2FRF"             
    mp:duration="60" 
    mp:expiration="1999-11-05T13:15:30Z">
    <mp:baseurl rdf:resource="http://www.merchant.org/shop"/>
    <mp:buyid rdf:resource="catalog.html"/>
    <mp:requesturl rdf:resource="elvis.html"/>
    <mp:longdesc rdf:resource="description.html"/>
    <mp:paymentsystem>
      <rdf:Alt>
        <rdf:li>
          <mp:paymentoption rdf:ID="micropay1" name="http://www.foo.it/micropay1"
          rdf:value="xxxxxxxxxxxxxxxxxx"/> </rdf:li>
        <rdf:li>
          <mp:paymentoption rdf:ID="micropay2" name="http://www.foo.it/micropay2"
          rdf:value="yyyyyyyyyyyyyyyyyy"/> </rdf:li>
      </rdf:Alt>
    </mp:paymentsystem>
  </rdf:Description>
</rdf:RDF>
</HEAD>

Note. Authors concerned about preventing their RDF content from rendering in old browsers MAY use the abbreviated syntax to move the property value into an attribute.
The above RDF Description MAY be external to the HTML document but linked with an LINK element and supplied by the transfer mechanism in the same retrieval transaction as that which returns the resource ("along-with"; e.g. with HTTP GET or HEAD). The RDF file would be a separate URI .This would allow the base HTML document to be cacheable.

Validate the above RDF description with  SiRPAC; a Simple RDF Parser and Compiler, written by Janne Saarela (W3C).

Appendix 3: Generate Embedding on the Server side.

This appendix is for information purpose only.
As today most browsers are non-aware RDF browsers, we have to provide to the user agent a comprehensive HTML page.

A.3.1.  Generate different type of HTML pages on the server.

A solution is to use a "transformation engine" hosted on the server (possibly a servlet or a proxy).
This engine would read as input the HTML document  and its linked RDF document  and transform these into an HTML document that includes either OBJECT or APPLET or EMBED elements, though  making it comprehensive according to the client browser version and brands.

This engine could be dynamic (process on flight the proper HTML page compliant to the client browser version) on client's request. These HTML generated pages could then be cached on the server for future request. This engine could also be a batch process to produce the alternative needed HTML page to cover most browsers versions.
On client's HTTP request, the server SHOULD first discover the client browser capabilities ( see Appendix 4) and  according to these capabilities send the HTML page using the proper embedding.

A.3.2. Benefits of generating HTML on the server :

This solution generation a final HTML page on the server from an HTML source and RDF documents will:

Appendix 4: Detecting the browser capabilities.

This appendix is for informational purposes only.
The Merchant server needs  to detect the browser capabilities in order to send  to it  the proper HLML page (with OBJECT or APPLET or EMBED elements).

Browser capabilities  depend on browser version and brand but also on preferences set up by the user. The user can for instance disable JAVA, disable Javascript, etc.

This detection can be done using Javascript.

A.4.1 Detecting if the Browser is Javascript-enabled

We can not write a JavaScriptEnabled() method in Javascript: a non-JavaScript browser or a browser with Javascript disabled will not be able to process the method call.
A simple solution is to use :

<SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> function1</SCRIPT> 
and  <NOSCRIPT> function 2 </NOSCRIPT>

One way of doing things is to redirect clients on test of enable or unable to execute javascript :
A JavaScript-enabled browser executes the script  (function 1) and automatically redirect to a scriptable  page "script.html"
A non-JavaScript browser follows the META element redirecting to another non scriptable page "noscript.html"

A.4.2 Detecting if the Browser is JAVA-enabled

A.4.3 Detecting if the Browser has the plugin installed

A.4.4 Detecting with HTML elements

Appendix 5: Generate Encoding using Javascript on the client side.

This implementation generates the HTML page on the client side using Javascript for example. After detection of the browser capabilities,  if the browser is Javascript-enabled, a script can generate the HTML elements and attributes for each fee link.

This implementation allows the elimination of  two HTTP round trips, (one for browser capabilities detection and an other one to send the proper HTML page)

Two possibilities have been overviewed :

  1. Fee links parameters are passed in a SCRIPT element.
  2. Fee links parameters are passed in a META element as attributes or in RDF elements as RDF statements.

A5.1 Example of code generating HTML

In this example all fee links parameters are passed in a SCRIPT element.

<HTML><HEAD>
<TITLE>Example of generated HTML</TITLE>
<SCRIPT language="JavaScript">
<-- function markup(p1,p2,p3,p4,p5,p6,p7,p8,p9,p10)
{
Supports = navigator.javaEnabled();
if (Supports)
writeapplet(p1,p2,p3,p4,p5,p6,p7,p8,p9,p10);
else
if (navigator.appName.indexOf("Netscape")!=-1)
{
if (navigator.plugins["NPMINIPAY Dynamic Link Library"])
writeembed(p1,p2,p3,p4,p5,p6,p7,p8,p9,p10);
else
document.writeln("You don't have Micropayment plugin installed and Java is not enabled in your browser")
}
else
alert("Please enable Java applets in your browser to make micropayments")
} //This function formats HTML 4.0 for a Java Applet" function writeobject(p1,p2,p3,p4,p5,p6,p7,p8,p9,p10)
{ document.writeln (' <OBJECT codetype="application/java
classid="http://www.miamachina.org/applet/micropayment.class">')
document.writeln (' <PARAM NAME = "baseurl" VALUE="' + p1 +'valuetype="ref" ')
document.writeln (' <PARAM NAME = "merchantname" VALUE="' + p2 +'valuetype="data" ')
document.writeln (' <PARAM NAME = "buyid" VALUE="' + p3 +'valuetype="ref"')
document.writeln (' <PARAM NAME = "requesturl" VALUE="' + p5 +'valuetype="ref"')
document.writeln (' <PARAM NAME = "textlink" VALUE="' + p6 +'valuetype="data"')
document.writeln (' <PARAM NAME = "price" VALUE="' + p7 +'valuetype="data"')
document.writeln (' <PARAM NAME = "title" VALUE="' + p8 +'valuetype="data"')
document.writeln (' <PARAM NAME = "duration" VALUE="' + p9 +'valuetype="data"')
document.writeln (' <PARAM NAME = "expiration" VALUE="' + p10 +'valuetype="data" ')
document.writeln ('</OBJECT>')
} //This function formats HTML 3.2 for a Java Applet function writeapplet(p1,p2,p3,p4,p5,p6,p7,p8,p9,p10)
{ document.writeln (' <APPLET codebase="http://www.miamachina.org/applet/" code="micropayment.class" archive="myclasses.jar,myaudio.jar">')
document.writeln (' <PARAM NAME = "baseurl" VALUE="' + p1 +'valuetype="ref" ')
document.writeln (' <PARAM NAME = "merchantname" VALUE="' + p2 +'valuetype="data" ')
document.writeln (' <PARAM NAME = "buyid" VALUE="' + p3 +'valuetype="ref"')
document.writeln (' <PARAM NAME = "requesturl" VALUE="' + p5 +'valuetype="ref"')
document.writeln (' <PARAM NAME = "textlink" VALUE="' + p6 +'valuetype="data"')
document.writeln (' <PARAM NAME = "price" VALUE="' + p7 +'valuetype="data"')
document.writeln (' <PARAM NAME = "title" VALUE="' + p8 +'valuetype="data"')
document.writeln (' <PARAM NAME = "duration" VALUE="' + p9 +'valuetype="data"')
document.writeln (' <PARAM NAME = "expiration" VALUE="' + p10 +'valuetype="data" ')
document.writeln (" </APPLET>")
} //This function formats non standard HTML for a Plugin function writeembed(p1,p2,p3,p4,p5,p6,p7,p8,p9,p10)
{ document.writeln (' <EMBED src="http://www.miamachina.org/MicropaymentPlugin.exe/">')
document.writeln (' <baseurl=+"p1"')
document.writeln (' <merchantname=+"p2"')
document.writeln (' <buyid=+"p3"')
document.writeln (' <requesturl=+"p5"')
document.writeln (' <textlink=+"p6"')
document.writeln (' <price=+"p7"')
document.writeln (' <title=+"p8"')
document.writeln (' <duration=+"p9"')
document.writeln (' <expiration=+"p10"')
document.writeln (' </EMBED> ')
}
</SCRIPT> </HEAD>
<BODY> <H2>Generate [Embed] or [Applet] depending on Browser capabilities</H2> <NOSCRIPT>This page uses JavaScript. You SHOULD enable JavaScript </NOSCRIPT> <SCRIPT language="JavaScript"> //Micropayment information needed for each fee link markup("http://www.merchant.org/shop","ShopAndPay","catalog.html", "elvis.html","Buy the biography of Elvis","+0.01USD", "Biography of Elvis","60","1999-11-05T13:15:30Z");
</SCRIPT> </BODY></HTML>

A5.2 Second example of code generating HTML

In this second example all fee link parameters are passed in a META element.(same kind of code would apply to parameters passed in an RDF element).

This needs to access the Document Object Model to extract META or RDF statements in order to generate the proper HTML page with OBJECT or APPLET or EMBED elements.
Netscape Browser Object  Model in Navigator 4.x or previous does not provide access to these elements.
Therefore this example works ONLY with Internet Explorer browser.

This code extracts attributes from META and RDF elements. To complete the process, other code has to first detect the browser capabilities (as shown in Appendix 4), and generate an HTML page as above.

a. Getting parameters from META elements

<HTML><HEAD>
<TITLE>Example of Getting parameters from META elements</TITLE>
<META  name="baseurl" value="http://www.merchant.org/shop">     
<META  name="buyid" value="catalog.html" >
<META  name="requesturl" value="elvis.html"> 
<META  name="textlink" value="Buy the biography of Elvis">  
<META  name="price" value="+0.01USD" >
<META  name="duration" value="60"> 
<META  name="expiration" value="1999-11-05T13:15:30Z">   
<META  name="1.mpname" value="micropayment">
<META  name="1.mpurl" value="http://www.foo.it/micropay">      
<META  name="1.specific" value="124rfdetg14ft58rdef21f4251">       
<META  name="1.mpbaseurl" value="http://www.merchant.it">    
<META  name="2.mpname" value="millipay"> 
<META  name="2.mpurl" value="http://www.foo.it/millipay">       
<META  name="2.specific" value="475rdg546tfeww12wcft254hy4">      
<META  name="2.mpbaseurl" value="http://www.merchant.fr/">
</HEAD>
<BODY>
<SCRIPT language="JavaScript">
var coll = document.all.tags("META");
//Write the OBJECT element and it's parameters - for each fee link
document.writeln ('<OBJECT codetype="application/java classid="http://www.miamachina.org/applet/micropayment.class" >')
for (i = 0; i < coll.length; i++) 
{
document.writeln('<PARAM NAME ="' + coll(i).name + '"' + ' VALUE="' + coll(i).value +'">');
}
document.writeln ('</OBJECT>')
</SCRIPT>
</BODY></HTML>

b. Getting parameters from RDF element

<HTML><HEAD>
<TITLE>Example  Getting parameters from RDF elements</TITLE>
<rdf:RDF>
<rdf:Description about="feelink-1" name="baseurl" value="http://www.merchant.org/shop">
....
</RDF:Description>
</rdf:RDF></HEAD>
<BODY>
<SCRIPT language="JavaScript">
//Write the OBJECT element and it's parameters - for each fee link
document.writeln ('<OBJECT codetype="application/java classid="http://www.miamachina.org/applet/micropayment.class" >')
var coll = document.all.tags("RDF:Description");
for (i = 0; i < coll.length; i++) 
{
document.writeln('<PARAM NAME ="' + coll(i).name + '"' + ' VALUE="' + coll(i).value +'">');
}
document.writeln ('</OBJECT>')
</SCRIPT>
</BODY></HTML>

Appendix 6: List of payment systems.

We need to  guarantee unique naming for payment system names and avoid collision.
For payment system names that are not registered in the following list, one  MUST provide:

The short code name is the string that replaces $MP$ in URLs, but short code names outside the following registry are meaningless. The URI  identifies and determines wich wallets to activate, not the short code name, allowing to prevent name collision. Therefore, a payment system which is not listed in  the following registry MUST provide both the short name (prefixed by "x-") and the unique URI.

Following is a small list of reserved short code names. We reserve the right to extend it, or delegate control of it in the future, with a guarantee that any changes or delegations will respect these rules and the names previously reserved.

List of registered payment systems
Company Payment System Short Code Name URI
Compaq MilliCent mcent http://www.millicent.com
IBM IBM Micro payments mpay http://www.hrl.il.ibm.com/mpay/
France Telecom France Telecom Micropayments mft to be specified

Appendix 7: Currency naming.

We need to guarantee unique naming for currency names and avoid collision.

For currency names that are not ISO 4217 codes registered, one MUST provide:

Example: a new currency for Air lines miles, could be named x-AM-zz (where zz is the airline code) and identified by a URI. http://www.airline.com/zz

Acknowledgments

The current and former members of the Micropayment Markup Working Group are:

Amir Herzberg, Chair (IBM); Anat Sarig, (IBM); Mark Manasse, Co-Chair (Compaq); Thierry Michel, Editor (W3C); Jean Claudes Pailles (France Telecom); Phillipe Michon (France Telecom) ; Aymeric de Solages (France Telecom).

References

[CHARSETS]
Registered charset values. Download a list of registered charset values from ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets.
[DATETIME]
"Date and Time Formats", M. Wolf and C. Wicksteed, 15 September 1997. This W3C Note is available at:
http://www.w3.org/TR/NOTE-datetime-970915
[HTML32]
"HTML 3.2 Reference Specification", D. Raggett, 14 January 1997. This W3C Recommendation is available at:
http://www.w3.org/TR/REC-html32.
[HTML40]
"HTML 4.0 Specification", D. Raggett, A. Le Hors, I. Jacobs, Revised 24 April 1998. This W3C Recommendation is available at:
http://www.w3.org/TR/1998/REC-html40-19980424.
[IANA]
"Assigned Numbers", STD 2, RFC 1700, USC/ISI, J. Reynolds and J. Postel, October 1994. Available at:
ftp://ftp.isi.edu/in-notes/rfc1700.txt
[ISO639]
"Codes for the representation of names of languages", ISO 639:1988. For more information, consult http://www.iso.ch/cate/d4766.html.
See also http://www.sil.org/sgml/iso639a.html.
[ISO3166]
"ISO3166: Codes for The Representation of Names of Countries." International Organization for Standardization.
[MIMETYPES]
List of registered content types (MIME types). Download a list of registered content types from ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/.
[RDF]
"Resource Description Framework (RDF) Model and Syntax Specification.", O. Lassila and R. Swick, 22 February 1999. This W3C Recommendation is available at:
http://www.w3.org/TR/1999/REC-rdf-syntax-19990222
[RFC1766]
"Tags for the Identification of Languages", H. Alvestrand, March 1995.Available at http://www.ietf.org/rfc/rfc1766.txt.
[RFC2119]
"Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997. Available at:
ftp://ftp.isi.edu/in-notes/rfc2119.txt
[SSL]
Secure Sockets Layer (SSL V3.0) protocol, Alan O. Freier, Philip Karlton, Paul C. Kocher, November 18, 1996. This document is available at:
http://home.netscape.com/eng/ssl3/draft302.txt
[URI]
"Uniform Resource Identifiers (URI): Generic Syntax", T. Berners-Lee, R. Fielding, L. Masinter, August 1998. Available at:
http://ds.internic.net/rfc/rfc2396.txt.
[XML 1.0]
"Extensible Markup Language (XML) 1.0 Specification", T. Bray, J. Paoli, C. M. Sperberg-McQueen, 10 February 1998. This W3C Recommendation is available at:
http://www.w3.org/TR/1998/REC-xml-19980210
[XML-Name]
"Namespaces in XML", T. Bray, D. Hollander, A. Layman, 14 January 1999. This W3C Recommendation is available at:
http://www.w3.org/TR/1999/REC-xml-names-19990114
[XHTML]
"XHTML™ 1.0: The Extensible HyperText Markup Language: a Reformulation of HTML 4.0 in XML 1.0. A W3C Public Working Draft is available at:
http://www.w3.org/TR/xhtml1


$Date: 1999/08/25 18:04:52 $