m (→Value: Prime/double prime possible solution)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
(26 intermediate revisions by 7 users not shown)
Line 1:
Line 1:
(削除) <h1> (削除ここまで)Measure microformat(削除) </h1> (削除ここまで)
(追記) {{DISPLAYTITLE: (追記ここまで)Measure microformat (追記) research}} (追記ここまで)
(削除) Currently this (削除ここまで)microformat (削除) is in exploratory stage (削除ここまで). (削除) Contributions should focus on real (削除ここまで)examples (削除) from the Web, existing (削除ここまで)formats(削除) /encoding of measures. (削除ここまで)
(追記) <div style="float:right;margin-left:1em">__TOC__</div> (追記ここまで)
(追記) This page is for researching and developing a [[measure]] (追記ここまで)microformat. (追記) Per the [[process]]: (追記ここまで)
(追記) * [[measure- (追記ここまで)examples(追記) ]] (追記ここまで)
(追記) * [[measure- (追記ここまで)formats(追記) ]] (追記ここまで)
(追記) * [[measure-brainstorming]] (追記ここまで)
== The problem ==
== The problem ==
Line 11:
Line 16:
The Measurement microformat will enable unambiguous description of physical quantities and thus provide a solid ground for data sharing and automation in many areas.
The Measurement microformat will enable unambiguous description of physical quantities and thus provide a solid ground for data sharing and automation in many areas.
== (削除) Draft Schema (削除ここまで)==
== (追記) Next Steps (追記ここまで)==
* (追記) clean (追記ここまで)-(追記) up (追記ここまで)[[measure-(追記) examples (追記ここまで)]] to refer to <(追記) em (追記ここまで)>(追記) current (追記ここまで)</(追記) em (追記ここまで)> (追記) real (追記ここまで)world (追記) examples (追記ここまで)
(削除) Rationale: The names "value" and "type" are taken from [[hCard]]; "item" is used from hReview. (削除ここまで)
(追記) * update (追記ここまで)[[(追記) measure (追記ここまで)-(追記) formats (追記ここまで)]] (追記) with formats from other recent efforts such (追記ここまで)as (追記) schema (追記ここまで).(追記) org (追記ここまで)
* (追記) massive clean (追記ここまで)-(追記) up (追記ここまで)of [[(追記) measure (追記ここまで)-(追記) brainstorming (追記ここまで)]]
(削除) === Standard Measure Schema === (削除ここまで)
(削除) * '''<code>hmeasure</code>''' (削除ここまで)
(削除) ** '''<code>value</code>''' {1} (numeric) (削除ここまで)
(削除) ** '''<code>unit</code>''' {1} (unit) (削除ここまで)
(削除) ** <code>item</code>? (text | [[hcard|hCard]] | [[hcalendar|hCalendar]]) (削除ここまで)
(削除) ** <code>type</code> ? (text, e.g. "height", "width", "weight") (削除ここまで)
(削除) ** <code>tolerance</code> ? (percentage | hmeasure) (削除ここまで)
(削除) === Angular Measure Schema === (削除ここまで)
(削除) * '''<code>hmeasure</code>''' (削除ここまで)
(削除) ** '''<code>value</code>''' {1} (degree) (削除ここまで)
(削除) ** <code>item</code>? (text | [[hcard|hCard]] | [[hcalendar|hCalendar]]) (削除ここまで)
(削除) ** <code>type</code> ? (text, e.g. "angle of elevation") (削除ここまで)
(削除) ** <code>tolerance</code> ? (percentage | hmeasure) (削除ここまで)
(削除) === Money Schema === (削除ここまで)
* (削除) '''<code>hmoney</code>''' (削除ここまで)
(削除) ** '''<code>value</code>''' {1} (numeric) (削除ここまで)
(削除) ** '''<code>unit</code>''' {1} ([http://en.wikipedia.org/wiki/ISO_4217 ISO 4217 code]) (削除ここまで)
(削除) ** <code>tolerance</code> ? (percentage | hmoney) (削除ここまで)
(削除) == Value == (削除ここまで)
(削除) Arbitrary white space {{may}} be included in the value to improve readability. Parsers {{must}} strip out all white space before further processing. (削除ここまで)
(削除) In the standard and money schemas, the value {{must}} be a number, formatted according to the following EBNF pattern: (削除ここまで)
(削除) <pre>non (削除ここまで)-(削除) zero-digit = "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" ; (削除ここまで)
(削除) digit = "0" | non-zero-digit ; (削除ここまで)
(削除) natural = non-zero-digit , {digit} ; (削除ここまで)
(削除) integer = "0" | (削除ここまで)[ (削除) "-" ] , natural ; (削除ここまで)
(削除) dot-decimal = integer , "." , {digit} ; (削除ここまで)
(削除) comma-decimal = integer , "," , {digit} ; (削除ここまで)
(削除) e-sign = "e" | "E" ; (削除ここまで)
(削除) mantissa = dot-decimal | comma-decimal | integer ; (削除ここまで)
(削除) sci-number = mantissa , e-sign , integer ; (削除ここまで)
(削除) number = dot-decimal | comma-decimal | integer | sci-number ;</pre> (削除ここまで)
(削除) This roughly corresponds to a subset of (削除ここまで)[(削除) http://en.wikipedia.org/wiki/C_syntax#Floating_point_types C syntax] for floating points and integers, excluding octal and hexadecimal representations. However, note that both commas and stops may be used as decimal points. (削除ここまで)
(削除) The Unicode minus sign (U+2212) and ASCII-compatible hyphen-minus (U+002D) {{must}} both be treated as acceptable indicators of a negative number. In addition, the symbols ¼ (U+00BC), ½ (U+00BD) and ¾ (U+00BE) {{should}} be supported as aliases for 0.25, 0.5 and 0.75 respectively. (削除ここまで)
(削除) In the angular measure schema, a (削除ここまで)measure (削除) is expressed as a combination of up to three numeric components: called degrees, minutes and seconds. Any combination of these components may be used, except when degrees and seconds are given minutes {{must}} be present. The components {{must}} appear in the correct order (degrees, minutes, seconds). Each component must match the production rule for "mantissa" above, with the following additional constraints: (削除ここまで)
(削除) * Only the first component can bear a minus sign. Subsequent components "inherit" the negativity (or lack thereof) from their predecessors. (削除ここまで)
(削除) * All components except the last must match the production rule for "integer". (削除ここまで)
(削除) The numeric components {{must}} be indicated by appending a suffix to each component. Valid suffixes are: (削除ここまで)
(削除) * degree: "deg", U+00B0 degree symbol (°) (削除ここまで)
(削除) * minute: "min", straight single quote ('), U+2032 prime (′) (削除ここまで)
(削除) * second: "sec", straight double quote ("), U+2033 double prime (″) (削除ここまで)
(削除) {{OpenIssue}} What about 5′ 10″ used to mean 5 foot, 10 inches? (削除ここまで)
(削除) * Possible solution: (削除ここまで)
(削除) <pre><abbr title="70 inch">5′ 10″</abbr></pre> (削除ここまで)
(削除) === Value Examples === (削除ここまで)
(削除) * 1729 (the smallest number that can be expressed as the sum of two cubes in two different ways) (削除ここまで)
(削除) * 1.61803399 (the golden ratio) (削除ここまで)
(削除) * 2,99792458e8 (the speed of light in a vacuum, measured in metres per second) (削除ここまで)
(削除) * -40 (value at which Celcius and Farenheit scales are equal) (削除ここまで)
(削除) * 1,000,000,000 (''Invalid:'' commas may be used as decimal points, but not for grouping thousands.) (削除ここまで)
(削除) * 57.2958 deg (1 radian, in degrees) (削除ここまで)
(削除) * -57° 17′ 45.1″ (-1 radian, in degrees, minutes and seconds) (削除ここまで)
(削除) * 4° 30″ (''Invalid'': no minutes) (削除ここまで)
(削除) * 4° -30′ (''Invalid'': only first component may be negative) (削除ここまで)
(削除) In the standard schema, the "unit" class is defined as an arbitrary string. Any unit may be used, but authors {{should}} attempt to use official SI units of measurement where appropriate. Parsers {{must}} recognise the following case-sensitive list of units, derived from the SI list of base units and official recognised derived units, with the addition of bits and bytes, which are commonly used on web pages, and litres, degrees Celsius and radians. (Note that gram appears in this table instead of kilogram. This is deliberate.) (削除ここまで)
(削除) {| border="1" (削除ここまで)
(削除) | K, K (U+212A) (削除ここまで)
(削除) | Ω (U+03A9), Ω (U+2126) (削除ここまで)
(削除) | L, l, ℓ (U+2113) (削除ここまで)
(削除) | ℃ (U+2103), °C (U+00B0 followed by captial C) (削除ここまで)
(削除) The following SI prefixes {{must}} be supported. (削除ここまで)
(削除) {| border="1" (削除ここまで)
(削除) ! 10<sup>n</sup> (削除ここまで)
(削除) | 10<sup>24</sup> (削除ここまで)
(削除) | 10<sup>21</sup> (削除ここまで)
(削除) | 10<sup>18</sup> (削除ここまで)
(削除) | 10<sup>15</sup> (削除ここまで)
(削除) | 10<sup>12</sup> (削除ここまで)
(削除) | 10<sup>9</sup> (削除ここまで)
(削除) | 10<sup>6</sup> (削除ここまで)
(削除) | 10<sup>3</sup> (削除ここまで)
(削除) | k<!-- (K)--> (削除ここまで)
(削除) | 10<sup>2</sup> (削除ここまで)
(削除) | h<!-- (H)--> (削除ここまで)
(削除) | 10<sup>1</sup> (削除ここまで)
(削除) | da<!-- (D)--> (削除ここまで)
(削除) | 10<sup>0</sup> (削除ここまで)
(削除) | 10<sup>−1</sup> (削除ここまで)
(削除) | 10<sup>−2</sup> (削除ここまで)
(削除) | 10<sup>−3</sup> (削除ここまで)
(削除) | 10<sup>−6</sup> (削除ここまで)
(削除) | μ (U+00B5), μ (U+03BC), u (削除ここまで)
(削除) | 10<sup>−9</sup> (削除ここまで)
(削除) | 10<sup>−12</sup> (削除ここまで)
(削除) | 10<sup>−15</sup> (削除ここまで)
(削除) | 10<sup>−18</sup> (削除ここまで)
(削除) | 10<sup>−21</sup> (削除ここまで)
(削除) | 10<sup>−24</sup> (削除ここまで)
(削除) The full names and for SI prefixes {{must}} only be combined with the full names for the units (or their aliases). Likewise the symbols for SI prefixes {{must}} only be combined with the symbols for the units. (削除ここまで)
(削除) * kilometre (削除ここまで)
(削除) * milligramme (削除ここまで)
(削除) * microV (''Invalid'') (削除ここまで)
(削除) * kgram (''Invalid'') (削除ここまで)
(削除) {{OpenIssue}} Perhaps, because of i18n issues, and the difficulty of supporting plurals, only the symbols should be ''required'' to be supported? (Using the ABBR design pattern it would still be possible to ''display'' the full name of the unit.) (削除ここまで)
(削除) === Combining units === (削除ここまで)
(削除) Units may be multiplied by separating with whitespace, or divided using a slash (/) or U+2215 division slash (∕). Units may be raised to an integer power using a caret character. The unicode superscript numerals 2 to 9 (U+00B2, U+00B3, U+2074-79) {{must}} be supported as aliases for raising to the appropriate integer powers. Multiplication is more associative than division. (削除ここまで)
(削除) * <span class="unit">kg m / s</span> (削除ここまで)
(削除) * <span class="unit">m/s^2</span> (削除ここまで)
(削除) * <span class="unit">meter³</span> (削除ここまで)
(削除) * <abbr class="unit" title="μm">micron</abbr> (削除ここまで)
(削除) === Angular units === (削除ここまで)
(削除) Units {{must not}} be given for measurements expressed in the degree schema: the degree itself is the unit. If the standard schema is used, units may be given in radians (rad). (削除ここまで)
(削除) === Other / Non-SI Units === (削除ここまで)
(削除) Authors {{may}} specify units other than those defined above, but {{should not}} assume that parsers will be able to interpret them. Authors using other units {{may}} provide a [[existing-rel-values|rel=glossary (削除ここまで)]] (削除) link (削除ここまで)to (削除) a page or fragment that defines the units. (削除ここまで)
(削除) ==== Explicitly Defining a Unit ==== (削除ここまで)
(削除) hmeasure may be used with the <dfn> element to explicitly define a unit in terms of pre-defined units. The "title" attribute (if any) is taken to be an alias of the unit name. (削除ここまで)
(削除) <pre><p class="hmeasure" id="dfn-inch"> (削除ここまで)
(削除) An <dfn class="item" title="in">inch</dfn> is defined as (削除ここまで)
(削除) <span class="value">0.0254</span> <span class="unit">m</span>. (削除ここまで)
(削除) Other instances of hmeasure may then (削除ここまで)refer to (削除) this definition, implicitly: (削除ここまで)
(削除) <pre> (削除ここまで)<(削除) p class="hmeasure" (削除ここまで)>
(削除) The <span class="item">action figure (削除ここまで)</(削除) span (削除ここまで)> (削除) has a <span class="type">height</span> of (削除ここまで)
(削除) <span class="value">5</span> <span class="unit">in</span>. (削除ここまで)
(削除) or explicitly: (削除ここまで)
(削除) <pre><p class="hmeasure"> (削除ここまで)
(削除) The <span class="item">action figure</span> has a <span class="type">height</span> of (削除ここまで)
(削除) <span class="value">5</span> (削除ここまで)
(削除) <a class="unit" rel="glossary" href="#dfn-inch">in</a>. (削除ここまで)
(削除) {{OpenIssue}} Farenheit is reasonably common in some parts of the (削除ここまで)world(削除) . As °C and °F do not share their zero points, it is impossible to use this pattern to define °F. °F thus remains an opaque string with no meaning assigned to it my this spec. Should we add it to the list of pre-defined units? (削除ここまで)
(削除) === Currency Units === (削除ここまで)
(削除) If the money schema is being used, the unit is not an arbitrary string. It {{must}} be a three-letter ISO 4217 code. The following aliases for the four largest reserve currencies (as of 2008) are allowed: (削除ここまで)
(削除) {| border="1" (削除ここまで)
(削除) Other currencies {{may}} be displayed using these symbols only through the (削除ここまで)[[(削除) abbr (削除ここまで)-(削除) design-pattern|ABBR design pattern (削除ここまで)]](削除) : (削除ここまで)
(削除) <pre><span class="hmoney"> (削除ここまで)
(削除) <abbr class="unit" title="AUD">$</a><span class="value">5.00</span> (削除ここまで)
(削除) </span></pre> (削除ここまで)
(削除) An hCard, hCalendar event or textual description of the item being measured may be supplied. (削除ここまで)
(削除) <pre><p class="hmeasure"> (削除ここまで)
(削除) <span class="item vcard">The <span class="fn">Great Wall</span>of (削除ここまで)
(削除) <span class="adr"><span class="country-name">China</span></span></span> (削除ここまで)
(削除) is about <span class="value">6 700</span> <abbr title="km">kilometres</abbr> (削除ここまで)
(削除) <abbr title="length" class="type">long</abbr>. (削除ここまで)
(削除) The item is optional. (削除ここまで)
(削除) The type specifies the dimension being measured. A measurement in, say, metres may be ambiguous because it could refer to a depth, a height, a length or a width. The optional type parameter allows you to specify a human-readable dimension. (削除ここまで)
(削除) == Tolerance == (削除ここまで)
(削除) An optional tolerance may be specified (削除ここまで)as (削除) a percentage or as a nested hmeasure/hmoney (削除ここまで).
(削除) <pre><span class="hmeasure"> (削除ここまで)
(削除) <span class="type">Height</span>: (削除ここまで)
(削除) <span class="value">5</span> <span class="unit">m</span> (削除ここまで)
(削除) ± <span class="tolerance">2%</span> (削除ここまで)
(削除) </span></pre> (削除ここまで)
(削除) <pre><span class="hmoney"> (削除ここまで)
(削除) <span class="unit">$</span><span class="value">5.00</span> (削除ここまで)
(削除) ± <span class="tolerance hmoney"><span class="unit">$</span><span class="value">1.00</span></span> (削除ここまで)
(削除) </span></pre> (削除ここまで)
(削除) When no tolerance is provided, a default tolerance of 0% {{must not}} be assumed — the tolerance is simply unknown. (削除ここまで)
(削除) == Minimisation Techniques == (削除ここまで)
(削除) === hmeasure === (削除ここまで)
(削除) If no "value" is given, then the first number conforming to the EBNF above is taken to be the value. If no unit is given, then the entire string within the "hmeasure" (less the value, item, type and tolerance) is taken to be the unit. (削除ここまで)
(削除) For example: (削除ここまで)
(削除) <pre><span class="hmeasure">3 pints <span class="item">beer</span></span></pre> (削除ここまで)
(削除) * '''Value:''' 3 (削除ここまで)
(削除) * '''Unit:''' "pints" (削除ここまで)
* (削除) '''Item:''' "beer" (削除ここまで)
(削除) <pre><span class="hmeasure">4 m</span></pre> (削除ここまで)
(削除) * '''Value:''' 4 (削除ここまで)
(削除) * '''Unit:''' metre (削除ここまで)
(削除) {{OpenIssue}} What about cases where there is no white space? SI says white space should always separate the quantity and unit, but in practice, many people do not include white space in measures. (削除ここまで)
(削除) {{OpenIssue}} When no unit is explicitly given, how do we know which of the following two behaviours to take? (削除ここまで)
(削除) * Assume unit minimisation and follow the procedures here; or (削除ここまで)
(削除) * Assume angular schema and treat number as a degree/minute/second. (削除ここまで)
(削除) === hmoney === (削除ここまで)
(削除) If no "value" is given, then the first number conforming to the EBNF above is taken to be the value. If no "unit" is given, the first three (削除ここまで)-(削除) letter word (or single character alias) is taken to be the unit. White space between the implied unit and value is considered optional. The following are to be equivalent: (削除ここまで)
(削除) <span class="hmoney"><span class="unit">EUR</span> <span class="value">1,00</span></span> (削除ここまで)
(削除) <span class="hmoney">EUR <span class="value">1,00</span></span> (削除ここまで)
(削除) <span class="hmoney">EUR1,00</span> (削除ここまで)
(削除) <span class="hmoney">1,00 EUR</span> (削除ここまで)
(削除) <span class="hmoney">1.00 <abbr class="unit" title="EUR">euro</abbr></span> (削除ここまで)
(削除) <span class="hmoney">1,00ドル</span> (削除ここまで)
(削除) <abbr class="hmoney" title="EUR 1,00">a euro</abbr> (削除ここまで)
(削除) === Minimising Tolerence === (削除ここまで)
(削除) If the tolerance is not a percentage (i.e. it is a nested hmeasure/hmoney) and it does not contain a unit (either explicit, or by minimisation rules), then the unit is taken to be the unit (削除ここまで)of (削除) the parent hmeasure/hmoney. (削除ここまで)
(削除) If no explicit tolerance is given, the hmeasure string should be examined for an occurrence of the substring "±". If this is present, the substring after it, and continuing to the end of the hmeasure string is taken to be a tolerance. If the tolerance contains a "%" character, the tolerance is taken to be a percentage. Otherwise is it taken to be an implicit nested hmeasure/hmoney. (削除ここまで)
(削除) === Worked example === (削除ここまで)
(削除) The following example shows a series of expansions taken by a parser encountering a minimised hmoney: (削除ここまで)
(削除) <pre><span class="hmoney">1ドル.54 ± 0.01</span></pre> (削除ここまで)
(削除) The "±" sign introduces a tolerance, which does not include a "%" symbol, so is treated as a nested hmoney. (削除ここまで)
(削除) <pre><span class="hmoney">1ドル.54 ±<span class="hmoney tolerance">0.01</span></span></pre> (削除ここまで)
(削除) No explicit units or values are given in either hmoney, so units and values are extracted as per hmoney minimisation: (削除ここまで)
(削除) <pre><span class="hmoney"><span class="unit">$</span><span class="value">1.54</span> (削除ここまで)
(削除) ±<span class="hmoney tolerance"><span class="value">0.01</span></span></span></pre> (削除ここまで)
(削除) The nested hmoney contains no unit, so it inherits its unit from the parent hmoney: (削除ここまで)
(削除) <pre><span class="hmoney"><span class="unit">$</span><span class="value">1.54</span> (削除ここまで)
(削除) ±<span class="hmoney tolerance"><span class="unit">$</span> <span class="value">0.01</span></span></span></pre> (削除ここまで)
(削除) Parsed values: (削除ここまで)
(削除) * '''Unit:''' USD (削除ここまで)
(削除) * '''Value:''' 1.54 (削除ここまで)
(削除) * '''Tolerance:''' (削除ここまで)
(削除) ** '''Unit:''' USD (削除ここまで)
(削除) ** '''Value:''' 0.01 (削除ここまで)
(削除) == Examples == (削除ここまで)
(削除) An example weather forecast using hmeasure, (削除ここまで)[[(削除) adr]], [[geo]] and [[hCalendar]] with the [[include (削除ここまで)-(削除) pattern|include pattern (削除ここまで)]](削除) : (削除ここまで)
(削除) Weather for (削除ここまで)
(削除) <span id="loc-lewes"> (削除ここまで)
(削除) <span class="adr location"> (削除ここまで)
(削除) <span class="locality">Lewes</span>, (削除ここまで)
(削除) <span class="region">East Sussex</span> (削除ここまで)
(削除) (<span class="geo">50.8730;0.005</span>) (削除ここまで)
(削除) <span class="vevent item" id="day-20080325"> (削除ここまで)
(削除) <a class="include" href="#loc-lewes"></a> (削除ここまで)
(削除) <span class="summary">Tuesday</span> (削除ここまで)
(削除) <abbr class="dtstart" title="2008年03月25日">25 March</abbr> (削除ここまで)
(削除) <abbr class="dtend" title="2008年03月26日"></abbr> (削除ここまで)
(削除) <span class="hmeasure"> (削除ここまで)
(削除) <a class="include" href="#day-20080325"></a> (削除ここまで)
(削除) <abbr title="Maximum temperature" class="type">High</abbr> (削除ここまで)
(削除) <span class="hmeasure"> (削除ここまで)
(削除) <a class="include" href="#day-20080325"></a> (削除ここまで)
(削除) <abbr title="Minimum temperature" class="type">Low</abbr> (削除ここまで)
(削除) </div></pre> (削除ここまで)
(削除) (The above example does not necessarily represent best practice. Authors should make themselves aware of the accessibility issues currently being discussed around the include and abbr design patterns.) (削除ここまで)
(削除) == Parsing Hints == (削除ここまで)
(削除) This section is ''informative''. Parsers should note that (with the exception of certain non-ascii characters, which can be converted manually first) all the pre-defined non-currency units can be understood by the [http://www.gnu.org/software/units/ GNU units] program. A parser could act as a wrapper to a GNU units installation, or make use of a GNU units-based web service to convert between units. (削除ここまで)
== Related microformats ==
== Related microformats ==
* [[hcalendar]] can provide a complete quantitative description of a natural event (for example an earthquake) occurring at a specified time (dtstart/dtend) and location (embedded [[geo]]), by just embedding measured physical quantities in the 'descrition' span.
* [[hcalendar]] can provide a complete quantitative description of a natural event (for example an earthquake) occurring at a specified time (dtstart/dtend) and location (embedded [[geo]]), by just embedding measured physical quantities in the 'descrition' span.
* [[job-listing]] can use time measure for specify per what period of time the salary is for.
* [[job-listing]] can use time measure for specify per what period of time the salary is for.
* [[hlisting]] product dimensions; weight/mass; time period (as above).
* [[hlisting]] product dimensions; weight/mass; time period (as above)(追記) ; price (追記ここまで).
* [[directions-examples]] can use length measure for mileage and time to go from one point to the next.
* [[directions-examples]] can use length measure for mileage and time to go from one point to the next.
* [[recipe-examples]] can use weight, volume and time measure for ingredients and preparation time.
* [[recipe-examples]] can use weight, volume and time measure for ingredients and preparation time.
* [[currency]] can be viewed as a measurement unit, or as a component of a measurement unit, as in $ per hour.
* [[currency]] can be viewed as a measurement unit, or as a component of a measurement unit, as in $ per hour.
(削除) == Contributors == (削除ここまで)
(削除) * Guillaume Lebleu (削除ここまで)
(削除) * [[User:AndyMabbett|Andy Mabbett]] (削除ここまで)
(削除) * Luca Postpischl (削除ここまで)
(削除) * [[User:ManuSporny|Manu Sporny]] (削除ここまで)
(削除) * [[User:TobyInk|TobyInk]] (削除ここまで)
==References==
==References==
Latest revision as of 16:28, 18 July 2020
This page is for researching and developing a measure microformat. Per the process:
The problem
Measures (e.g. weights, sizes, temperatures) occur frequently on the Web, they are constituted of a value a unit-measure and, in scientific and technical contexts, an experimental uncertainty. These 3 elements should be marked-up consistently across websites so that they can be easily identified and acted upon (export, compute, convert) in collaborative distributed applications.
Unit-measures differ from locale to locale (e.g. Fahrenheit vs. Celsius, pound versus Kilogram), making comparison and matching of offerings difficult.
The Measurement microformat will enable unambiguous description of physical quantities and thus provide a solid ground for data sharing and automation in many areas.
Next Steps
Related microformats
- hcalendar can provide a complete quantitative description of a natural event (for example an earthquake) occurring at a specified time (dtstart/dtend) and location (embedded geo), by just embedding measured physical quantities in the 'descrition' span.
- job-listing can use time measure for specify per what period of time the salary is for.
- hlisting product dimensions; weight/mass; time period (as above); price.
- directions-examples can use length measure for mileage and time to go from one point to the next.
- recipe-examples can use weight, volume and time measure for ingredients and preparation time.
- currency can be viewed as a measurement unit, or as a component of a measurement unit, as in $ per hour.
References
See also