measure-brainstorming - Revision history

Tantek: move a historical brainstorm using Normalized Scientific Notation from measure-formats to here

2024-08-30T22:45:34Z

move a historical brainstorm using Normalized Scientific Notation from measure-formats to here

@@ Line 841: / Line 841: @@
 ** '''Unit:''' USD
 ** '''Num:''' 0.01
 == Examples ==

GRegorLove: s///

2023-07-26T21:06:07Z

s/<source>/<syntaxhighlight>/

← Older revision		Revision as of 21:06, 26 July 2023
Line 54:		Line 54:

	==== Example Markup ====		==== Example Markup ====
			<syntaxhighlight lang="html">
	<~~source~~ lang=~~html4strict~~>
	<span class="h-measure">		<span class="h-measure">
	<data class="p-type" value="weight">weighs</data>		<data class="p-type" value="weight">weighs</data>
Line 70:		Line 69:
	<data class="p-unit" value="USD">$</data><span class="p-num">9.90</span>		<data class="p-unit" value="USD">$</data><span class="p-num">9.90</span>
	</span>		</span>
	</~~source~~>		</syntaxhighlight>

	==== Example Parsed JSON ====		==== Example Parsed JSON ====
			<syntaxhighlight lang="json">
	<~~source~~ lang=~~javascript~~>
	{		{
	"type": [		"type": [
Line 107:		Line 105:
	}		}
	}		}
	</~~source~~>		</syntaxhighlight>

	==== Issues ====		==== Issues ====
Line 130:		Line 128:

	==== Example Markup ====		==== Example Markup ====
			<syntaxhighlight lang="html">
	<~~source~~ lang=~~html4strict~~>
	<span class="m-weight">		<span class="m-weight">
	<data class="p-num" value="79300">79.3</data><data class="p-unit" value="g">kg</data>		<data class="p-num" value="79300">79.3</data><data class="p-unit" value="g">kg</data>
Line 141:		Line 138:

	Price: <span class="m-price"><data class="p-unit" value="USD">$</data><span class="p-num">9.90</span></span>		Price: <span class="m-price"><data class="p-unit" value="USD">$</data><span class="p-num">9.90</span></span>
	</~~source~~>		</syntaxhighlight>

	==== Example Parsed JSON ====		==== Example Parsed JSON ====
			<syntaxhighlight lang="json">
	<~~source~~ lang=~~javascript~~>
	{		{
	"weight": [		"weight": [
Line 188:		Line 184:
	]		]
	}		}
	</~~source~~>		</syntaxhighlight>

	==== Issues ====		==== Issues ====
Line 211:		Line 207:

	==== Example Markup ====		==== Example Markup ====
			<syntaxhighlight lang="html">
	<~~source~~ lang=~~html4strict~~>
	Standalone measure: <span class="h-measure">		Standalone measure: <span class="h-measure">
	<span class="p-name">Weight of a widget</span>: <data class="p-num">1.5</data><data class="p-unit">kg</data>		<span class="p-name">Weight of a widget</span>: <data class="p-num">1.5</data><data class="p-unit">kg</data>
Line 234:		Line 229:
	</span>		</span>
	</div>		</div>
	</~~source~~>		</syntaxhighlight>

	==== Example Parsed JSON ====		==== Example Parsed JSON ====
			<syntaxhighlight lang="json">
	<~~source~~ lang=~~javascript~~>
	{		{
	"items": [		"items": [
Line 316:		Line 310:
	}		}
	]		]
	}</~~source~~>		}</syntaxhighlight>

	==== Issues ====		==== Issues ====

Tantek: HTML proposals / quantity element

2023-07-26T18:56:27Z

HTML proposals / quantity element

← Older revision		Revision as of 18:56, 26 July 2023
Line 2:		Line 2:

	This page collects ideas on how to use semantic XHTML to represent unambiguously [[measure]]s.		This page collects ideas on how to use semantic XHTML to represent unambiguously [[measure]]s.

			== HTML proposals ==
			There is some evidence of past proposals to add measures/quantities directly to HTML, which should be considered in the context of any overall markup solution:

			=== quantity element ===
			https://lists.w3.org/Archives/Public/public-whatwg-archive/2009Aug/0234.html proposed a quantity element
			<pre>
			[…]

			I've been looking at the meter element, which specifically states that
			"There is no explicit way to specify units in the meter element, but the
			units may be specified in the title attribute in free-form text."

			Having used the web for the past 15 years I've always felt that it's a
			shame when you run into a page with a set of measurements and those
			can't be interpreted automatically in a sensible fashion. Especially
			with the fact that there are both imperial and metric units still around
			in this day and age.

			An backwards compatible inline element to specify a quantity would be
			rather trivial:

			<quantity unit="cm">12 cm</quantity>
			<quantity unit="kg">2 kg</quantity>

			With this implementation a number inside the quantity element would be
			interpreted as the numerical value of the unit. Other characters would
			be ignored.

			[…]
			</pre>


	== microformats2 ==		== microformats2 ==

Aaronpk: /* Examples in the Wild */

2017-04-25T21:17:48Z

Examples in the Wild

← Older revision		Revision as of 21:17, 25 April 2017
Line 299:		Line 299:

	* [[User:Aaronpk\|aaronpk]] publishes his weight: http://aaronparecki.com/metrics		* [[User:Aaronpk\|aaronpk]] publishes his weight: http://aaronparecki.com/metrics
			* https://www.jerrysv.xyz/ publishes environmental measurements on the home page
			** including radiation levels with an accuracy amount: <code>0.0785 +/- 0.0087</code>

	= Old pre-mf2 brainstorming =		= Old pre-mf2 brainstorming =

Tantek: fix frag link to be local

2016-01-17T19:26:03Z

fix frag link to be local

← Older revision		Revision as of 19:26, 17 January 2016
Line 9:		Line 9:
	=== Proposal: <code>h-measure</code>, <code>h-angle</code>, <code>h-money</code> ===		=== Proposal: <code>h-measure</code>, <code>h-angle</code>, <code>h-money</code> ===

	Based on existing ~~draft schema for~~ [[~~measure~~#Draft_Schema\|~~hmeasure~~]]		Based on existing [[#Draft_Schema\|old draft schema]]

	==== Example Readable Text ====		==== Example Readable Text ====

Tantek: move brainstorming here from the measure page

2016-01-17T19:24:42Z

move brainstorming here from the measure page

Show changes

Barnabywalters: /* Proposal: h-measure named with p-* */ updated examples to show context, gave real JSON

2013-06-16T20:23:33Z

Proposal: h-measure named with p-*: updated examples to show context, gave real JSON

Show changes

Aaronpk: /* Issues */

2013-06-16T20:07:43Z

Issues

← Older revision		Revision as of 20:07, 16 June 2013
Line 246:		Line 246:

	<div class="discussion">		<div class="discussion">
	* There is no distinction between "standard", "angular" and "money" types other than the units present. This may or may not be important, need to gather some use cases and examples for each.		* There is no distinction between "standard", "angular" and "money" types other than the units present. This may or may not be important, need to gather some use cases and examples for each. [[User:Aaronpk\|Aaronpk]] 20:07, 16 June 2013 (UTC)
	* If there is no <code>p-*</code> property defined, the <code>h-measure</code> will end up in the "children" array.		* If there is no <code>p-*</code> property defined, the <code>h-measure</code> will end up in the "children" array. [[User:Aaronpk\|Aaronpk]] 20:07, 16 June 2013 (UTC)
	* This only works when h-measure is a child microformat, i.e. the example given actually makes no sense. But otherwise I feel this is the sanest proposal --[[User:Barnabywalters\|bw]] 20:05, 16 June 2013 (UTC)		* This only works when h-measure is a child microformat, i.e. the example given actually makes no sense. But otherwise I feel this is the sanest proposal --[[User:Barnabywalters\|bw]] 20:05, 16 June 2013 (UTC)
			** If the <code>p-*</code> property is omitted and the <code>h-measure</code>, wouldn't this just become a new top-level item in the <code>items</code> array? [[User:Aaronpk\|Aaronpk]] 20:07, 16 June 2013 (UTC)
	</div>		</div>

Barnabywalters: /* Proposal: h-measure named with p-* */ added child-only limitation

2013-06-16T20:05:27Z

Proposal: h-measure named with p-*: added child-only limitation

← Older revision		Revision as of 20:05, 16 June 2013
Line 192:		Line 192:

	Price:		Price:
	<span class="h-~~money~~ p-price">		<span class="h-measure p-price">
	<data class="p-unit" value="USD">$</data><span class="p-num">9.90</span>		<data class="p-unit" value="USD">$</data><span class="p-num">9.90</span>
	</span>		</span>
Line 245:		Line 245:
	==== Issues ====		==== Issues ====

			<div class="discussion">
	* There is no distinction between "standard", "angular" and "money" types other than the units present. This may or may not be important, need to gather some use cases and examples for each.		* There is no distinction between "standard", "angular" and "money" types other than the units present. This may or may not be important, need to gather some use cases and examples for each.
	* If there is no <code>p-*</code> property defined, the <code>h-measure</code> will end up in the "children" array.		* If there is no <code>p-*</code> property defined, the <code>h-measure</code> will end up in the "children" array.
			* This only works when h-measure is a child microformat, i.e. the example given actually makes no sense. But otherwise I feel this is the sanest proposal --[[User:Barnabywalters\|bw]] 20:05, 16 June 2013 (UTC)
			</div>

	=== Examples in the Wild ===		=== Examples in the Wild ===

Barnabywalters: /* microformats2 */ made code blocks s to get syntax highlighting

2013-06-16T20:01:42Z

microformats2: made code blocks <source>s to get syntax highlighting

← Older revision		Revision as of 20:01, 16 June 2013
Line 23:		Line 23:
	==== Example Markup ====		==== Example Markup ====

	<~~pre~~>		<source lang=html4strict>
	<span class="h-measure">		<span class="h-measure">
	<data class="p-type" value="weight">weighs</data>		<data class="p-type" value="weight">weighs</data>
Line 38:		Line 38:
	<data class="p-unit" value="USD">$</data><span class="p-num">9.90</span>		<data class="p-unit" value="USD">$</data><span class="p-num">9.90</span>
	</span>		</span>
	</~~pre~~>		</source>

	==== Example Parsed JSON ====		==== Example Parsed JSON ====

	<~~pre~~>		<source lang=javascript>
	{		{
	"type": [		"type": [
Line 75:		Line 75:
	}		}
	}		}
	</~~pre~~>		</source>

	==== Issues ====		==== Issues ====
Line 99:		Line 99:
	==== Example Markup ====		==== Example Markup ====

	<~~pre~~>		<source lang=html4strict>
	<span class="m-weight">		<span class="m-weight">
	<data class="p-num" value="79300">79.3</data><data class="p-unit" value="g">kg</data>		<data class="p-num" value="79300">79.3</data><data class="p-unit" value="g">kg</data>
Line 109:		Line 109:

	Price: <span class="m-price"><data class="p-unit" value="USD">$</data><span class="p-num">9.90</span></span>		Price: <span class="m-price"><data class="p-unit" value="USD">$</data><span class="p-num">9.90</span></span>
	</~~pre~~>		</source>

	==== Example Parsed JSON ====		==== Example Parsed JSON ====

	<~~pre~~>		<source lang=javascript>
	{		{
	"weight": [		"weight": [
Line 156:		Line 156:
	]		]
	}		}
	</~~pre~~>		</source>

	==== Issues ====		==== Issues ====
Line 180:		Line 180:
	==== Example Markup ====		==== Example Markup ====

	<~~pre~~>		<source lang=html4strict>
	weighs		weighs
	<span class="h-measure p-weight">		<span class="h-measure p-weight">
Line 195:		Line 195:
	<data class="p-unit" value="USD">$</data><span class="p-num">9.90</span>		<data class="p-unit" value="USD">$</data><span class="p-num">9.90</span>
	</span>		</span>
	</~~pre~~>		</source>

	==== Example Parsed JSON ====		==== Example Parsed JSON ====

	<~~pre~~>		<source lang=javascript>
	{		{
	"weight": [		"weight": [
Line 241:		Line 241:
	}		}
	]		]
	}</~~pre~~>		}</source>

	==== Issues ====		==== Issues ====