measure - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:28:57Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:28, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Measure microformat research~~</entry-title>~~		{{DISPLAYTITLE:Measure microformat research}}

	<div style="float:right;margin-left:1em">__TOC__</div>		<div style="float:right;margin-left:1em">__TOC__</div>

Tantek: make this a top-level microformats research page, move brainstorming to *-brainstorming, see history for contributors, add next steps

2016-01-17T19:26:14Z

make this a top-level microformats research page, move brainstorming to *-brainstorming, see history for contributors, add next steps

Show changes

Brian: reverting spam

2008-12-20T22:36:23Z

reverting spam

Show changes

ZelerAcele: alcocaliv

2008-12-20T06:13:05Z

alcocaliv

Show changes

MonolOleto: laboch

2008-12-20T03:09:37Z

laboch

Show changes

AmeerDawood: /* hmeasure */

2008-11-17T23:44:34Z

hmeasure

← Older revision		Revision as of 23:44, 17 November 2008
Line 466:		Line 466:
	{{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}} 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.

	{{ClosedIssue}} 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.		{{ClosedIssue}} When no unit is explicitly given, how do we know which of the following two behaviors to take? Assume unit minimisation and follow the procedures here; or Assume angular schema and treat number as a degree/minute/second.
	* Changed root element class for angular schema to <tt>hangle</tt>		* Changed root element class for angular schema to <tt>hangle</tt>

TJSingleton: /* Related microformats */

2008-09-12T16:34:24Z

Related microformats

← Older revision		Revision as of 16:34, 12 September 2008
Line 590:		Line 590:
	* [[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.

TobyInk: tolerance out? dtmeasured in?

2008-07-15T14:09:26Z

tolerance out? dtmeasured in?

← Older revision		Revision as of 14:09, 15 July 2008
Line 14:		Line 14:

	Rationale: The names "type" and "item" are taken from [[hReview]].		Rationale: The names "type" and "item" are taken from [[hReview]].

			{{OpenIssue}} Is <code>tolerance</code> needed? It is useful for some circumstances, but perhaps not common enough to be included in the spec.
			{{OpenIssue}} A <code>dtmeasured</code> property may be useful, especially for <code>hmoney</code>, as prices fluctuate.

	=== Standard Measure Schema ===		=== Standard Measure Schema ===

TobyInk: /* `type`: The Dimension */ No default for hmoney.

2008-07-15T09:58:54Z

<tt>type</tt>: The Dimension: No default for hmoney.

← Older revision		Revision as of 09:58, 15 July 2008
Line 425:		Line 425:

	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.		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.

	~~For <code>hmoney</code>, when no <code>type</code> is explicitly provided, "price" is assumed.~~

	== <tt>tolerance</tt>: The Error Tolerance ==		== <tt>tolerance</tt>: The Error Tolerance ==

TobyInk: /* Draft Schema */ Other examples of hmoney types to prove this property is useful.

2008-07-14T14:22:44Z

Draft Schema: Other examples of hmoney types to prove this property is useful.

← Older revision		Revision as of 14:22, 14 July 2008
Line 38:		Line 38:
	** '''<code>unit</code>''' {1} ([http://en.wikipedia.org/wiki/ISO_4217 ISO 4217 code])		** '''<code>unit</code>''' {1} ([http://en.wikipedia.org/wiki/ISO_4217 ISO 4217 code])
	** <code>item</code>? (text \| [[hcard\|hCard]] \| [[hcalendar\|hCalendar]])		** <code>item</code>? (text \| [[hcard\|hCard]] \| [[hcalendar\|hCalendar]])
	** <code>type</code> ? (text, e.g. "~~costs~~")		** <code>type</code> ? (text, e.g. "price", "salary", "exchange rate")
	** <code>tolerance</code> ? (percentage \| hmoney)		** <code>tolerance</code> ? (percentage \| hmoney)

measure - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

Tantek: make this a top-level microformats research page, move brainstorming to *-brainstorming, see history for contributors, add next steps

Brian: reverting spam

ZelerAcele: alcocaliv

MonolOleto: laboch

AmeerDawood: /* hmeasure */

TJSingleton: /* Related microformats */

TobyInk: tolerance out? dtmeasured in?

TobyInk: /* type: The Dimension */ No default for hmoney.

TobyInk: /* Draft Schema */ Other examples of hmoney types to prove this property is useful.

TobyInk: /* `type`: The Dimension */ No default for hmoney.