- From: Michiel de Jong <michiel@unhosted.org>
- Date: Sat, 28 Apr 2012 14:23:15 +0200
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: David Nicol <davidnicol@gmail.com>, Web Payments <public-webpayments@w3.org>
i'm not saying you should specify law and workflow decisions, just that you admit that 'currency: EUR' is /meant/ to mean that the amount is in euros. you picked the field names with an intended use, right? you intend the 'currency' field to be used for the currency, and not for the country where the transaction took place? then say so. maybe make the current version a 'syntax' spec and put the meaning of each field in a separate 'interpretation' spec if you must. but syntax without interpretation is useless. it will only be human-readable, and not machine-readable. it's like saying a vinyl record should be round, 12 inches in diameter, and with grooves, so that it will fit onto all record players (the syntax standard), but without referring to how it relates to sound (the interpretation standard).
Received on Saturday, 28 April 2012 12:23:43 UTC