- From: Daniel Dardailler <danield@w3.org>
- Date: Thu, 30 Sep 1999 21:40:20 +0200
- To: www-micropay-comments@w3.org
Here are some comments on http://www.w3.org/TR/1999/WD-Micropayment-Markup-19990825/ steaming from personal review and also discussion on the WAI PF list. * 4.1 Field description Please separate the price field in price (amount) and currency (iso code). It's much more easy to parse that way. * Appendix 6: List of payment systems. I want to understand why there is a need for a central registry (e.g. W3C) of payment system name. A central registry is a lot of work and can be a lot of trouble. There's already one: DNS, and we should use it (i.e. use URI) as much as we can. If it's not necessary (e.g. for convenience) then it should be avoided. Isnt' there a way to still use short name ($MP$) without registry, just like namespace do ? (i.e. bind the URI of the payment system to the short name dynamically - in the payment info coming from the server) * Reword section 4.1.5 on payment specific to make clear what, among 1.mpname , 1.mpparamname, 1.mpurl is part of the syntax and what can vary * Appendix 7: Put currently extension in payment specific field Extension Currency naming is really confusing, particularly the z-x mechanism. Can't the currency extension info be put in a payment specific field and keep the currency just to ISO codes ? * The examples using Javascript to produce the link are nice, but there needs to be a noscript option for getting at the object. Maybe that is the place for a straight-out link that is handled by a helper app.
Received on Thursday, 30 September 1999 15:40:24 UTC