<div>Dear Andy Mabbett (and others who are interested in the Currency Proposal and/or Measurements),</div>
<div><br>with the yesterdays update-comments of the <a href="http://microformats.org/wiki/currency-examples">currency-example</a>, you asked if anyone remember the currency proposal ... and yes I do ;-) After my answer to your
<a href="http://microformats.org/wiki/currency-issues#Comments">comment</a> on my <a href="http://microformats.org/wiki/currency-issues#Unit_and_Value">currency-issue</a> I watched the recent changes regularly. As a newbie I am a little bit doubtful to the process and so I do not have the heart to do something more. So instead of editing something in the wiki, I like to discuss it with before.
<div><br>As I wrote on the <a href="http://microformats.org/wiki/measure-brainstorming#Approach">measurement brainstorming</a>, I suggest to treat the currency microformat as a kind of subpattern - since it is a kind of measurement, too. But I have the problem with the microformat claim, to have a real-world problem and real-world-practice, before making it a microformat. Today I might found a solution: like the date-time has the
<a href="http://microformats.org/wiki/datetime-design-pattern#Discussion">same problem</a>, it is not a microformat, but a microformat-design-pattern.</div>
<div><br>So my revised suggestion would consist of two parts:<br>1. Creating a measurement-design-pattern-proposal (like an abstract class):<br>a measurement has the following properties (which is expandable by an instance):
<br>- required value: can mark up a machine-readable numerical value with a spanelement or a string value with a abbr whose title attribute contains the machine-readable numerical value (See abbr-design-pattern).<br>- required unit: reference to the unit (include-pattern) or "markup a value" / "use the abbr-design-pattern to provide the equivalent machine readable value", which is allowed by the instance format.
<br>- optional scale: reference to a scale (include-pattern). Must markup a <a href="http://aurora.regenstrief.org/UCUM/ucum.html#section-Prefixes">Unified Code for Units of Measure Prefix</a> (column name or c/s or c/i) or use the abbr-design-pattern to provide the equivalent machine readable value to the Prefix (column c/i = case insensitive to avoid errors) marked up human-readable value.
<div>2. Adapting your Proposal:</div>
<div>Defining the currency-format as an instance of the measurement-design-pattern</div>
<div>- renaming amount to value</div>
<div>- renaming currency to unit and making it required (otherwise you only have a number). </div>
<div>- renaming unit to scale</div>
<div>- defining the range of unit to the ISO 4217 (as you suggested)</div>
<div>- adding the date following the datetime-design-pattern (as you suggested) </div>
<div>What do you think about this?</div>