https://microformats.org/wiki/api.php?action=feedcontributions&user=Niuhaibiao&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-29T01:13:23ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=measure-brainstorming&diff=41638measure-brainstorming2010-01-14T06:34:45Z<p>Niuhaibiao: /* List of possible Sub-Formats */</p>
<hr />
<div>= Measure Microformat Brainstorming =<br />
<br />
This page collects ideas on how to use semantic XHTML to represent unambiguously [[measure]]s.<br />
<br />
== Guillaume Lebleu ==<br />
<br />
Basic example with elementary unit using the abbr pattern and the UNECE code (see [[measure-formats]])<br />
<br />
<pre><br />
<span class="length">5 <abbr class="unit" title="FOT">Feet</abbr></span><br />
</pre><br />
<br />
Optional "value" could be useful in some cases, for instance when the value is provided in plain text:<br />
<br />
<pre><br />
<span class="length"><abbr class="value" title="5">Five</abbr> <abbr class="unit" title="FOT">Feet</abbr></span><br />
</pre><br />
<br />
<br />
==Andy Mabbett==<br />
<br />
===Converter Extension===<br />
This Firefox extension may be of interest. Note, though, that it's been criticised for having a "nag" screen: [https://addons.mozilla.org/firefox/2286/ Converter] [[User:AndyMabbett|AndyMabbett]] 15:32, 3 Oct 2006 (PDT)<br />
<br />
:This is the author of that extension. I don't want to go much into this, but I just want to clarify this briefly. The part with the nag screen is wrong on two counts: (1) that dialog isn't there anymore, and (2) even if it was there, you only needed to read a paragraph and click a button to make it go away ''forever'' -- but you don't have to take my word for it, install it for yourselves and see. Andy's report is accurate however -- the extension '''''was''''' criticized for that dialog (that's what you get from your free extension's users when you ask for 15 seconds of their time in return for hundreds of hours of your time). --[[User:BogdanStancescu|BogdanStancescu]] 09:35, 9 Oct 2006 (PDT)<br />
<br />
===Wikipedia converter===<br />
Wikipedia's [http://en.wikipedia.org/wiki/Template:Convert Convert Template] automatically converts from metric to imperial and vice versa. It's worth noting the measurements it supports. <br />
<br />
===Google calculator===<br />
A Google search, e.g. for "0.6 miles" [http://www.google.co.uk/search?q=0.6+miles returns a metric conversion]. See also [http://www.google.co.uk/intl/en/help/calculator.html Google calculator help].<br />
<br />
===HTML Entities===<br />
*For squared and cubic values, the HTML entities <code>&amp;sup2;</code> and <code>&amp;sup3;</code> should be borne in mind.<br />
<br />
*For temperatures and angels, the HTML entity <code>&amp;deg;</code> exists.<br />
<br />
*The following currency entities exist: <br />
**<code>&curren;</code> - <code>&amp;curren;</code> - currency <br />
**<code>&cent;</code> - <code>&amp;cent;</code> - cent<br />
**<code>&pound;</code> - <code>&amp;pound;</code> - pound<br />
**<code>&yen;</code> - <code>&amp;yen;</code> - yen<br />
**<code>&euro;</code> - <code>&amp;euro;</code> - Euro<br />
<br />
==Bogdan Stăncescu==<br />
Here are my findings related to automatic parsing of measurements on web pages while developing the [http://converter.mozdev.org Converter] extension. Please ask away if you want me to go into more detail on any of the topics -- I'm not sure which of my experiences are relevant to microformats, so I'm going to give you an overview of my conclusions.<br />
<br />
By the way of an introduction, the Converter is a Firefox extension which tries to convert all measurements it finds in any web page to their Imperial or metric counterpart (e.g. Fahrenheit to Celsius, and Celsius to Fahrenheit; meters to feet and feet to meters). There are two steps to the conversion process: (1) identifying the measurements in the page, and (2) converting them. As expected, the conversion part is trivial, at least conceptually. The parsing is the tricky bit, and that's also where the Converter's challenges also become relevant for microformats.<br />
<br />
Here are the main challenges I have encountered while writing the Converter:<br />
<br />
;Presentation standardization: The first, biggest and most obvious challenge is lack of almost any ''de facto'' standardization in respect to data presentation. What I mean is that although the units themselves are more or less standardized (more on that later), they are ''presented'' in various ways within web pages. Take these examples: "50 foot monster", "50 ft monster", "50 feet monster", "50-foot monster", "50-feet monster" -- and my personal favorite, "fifty-foot monster" (more on this later);<br />
<br />
:Note that using a microformat using in particular the [[abbr-design-pattern]] would make each of these examples less ambiguous if not unambiguous. See below --[[User:Guillaume_Lebleu|Guillaume_Lebleu]]:<br />
<br />
<pre><br />
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">foot</abbr></span> monster<br />
</pre><br />
<br />
<pre><br />
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">ft</abbr></span> monster<br />
</pre><br />
<br />
<pre><br />
<span class="height"><span class="value">50</span>-<abbr class="unit" title="FOT">foot</abbr></span> monster<br />
</pre><br />
<br />
<pre><br />
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">feet</abbr></span> monster<br />
</pre><br />
<br />
<pre><br />
<span class="height"><abbr class="value" title="50">fifty</abbr><abbr class="unit" title="FOT">foot</abbr></span> monster<br />
</pre><br />
<br />
:: Of course; as far as I could gather, that's actually the ''purpose'' of microformats -- bridging the gap between what humans and machines can understand, no? --[[User:BogdanStancescu|BogdanStancescu]] 00:30, 11 Oct 2006 (PDT)<br />
<br />
;Unit standardization: I live in Europe, where I've always used the metric system. As such, this probably was a much bigger nasty surprise for me than it is for a user of the Imperial/U.S. Customary system: in the Imperial system, the units themselves vary depending on where you are -- miles, pints, and a whole lot of other units come in many different flavors, but they're all written the same in regular usage;<br />
<br />
;Language: "1 meter" vs. "1 metre" is a reasonable difference -- but non-SI units are usually translated. Even some SI units have different plurals, depending on the language, although in theory SI units are actually denoted by ''symbols'', not "words", as to make them non-translatable, and truly international (hence the name of the SI). I haven't really given much thought to a solution towards parsing these, because I find it overwhelming for the time.<br />
<br />
;The sheer number of units: surprisingly, most people don't realize just how many units we humans have invented. Just take a look here: [http://www.asknumbers.com/ asknumbers.com] -- see how many categories there are? Now click on Flow Rate -- a non-ubiquitous type of measurement. Three sub-categories only for flow rates! Now click on Volume Flow Rate and take a look at the number of units in those lists. Remember, those are just in one of the three categories for flow rate! The UNECE standard mentioned in the [[measure-formats#Measure_Formats|measure formats]] page is useful to define just that -- a ''standard'' set of units. But in practice there are a lot more being used out there.<br />
<br />
:Do you have examples from the Web (a URL) of non-UNECE units. One possibility would be to provide the ability for a unit to be defined as a division of products of other units. This is consistent with the [[measure-formats#Systeme_International]], which defines 7 base units and all other units as derived units (of course some units, even though they are derived are much easily represented as simple ones). This is what XBRL has done for financial/accounting/reporting. See [[currency-formats#XBRL]] and theorical example (ampere acre per second) below --[[User:Guillaume_Lebleu|Guillaume_Lebleu]]:<br />
<br />
::Unfortunately I don't have URLs -- almost at all -- with measurements, although I've been in the "business" for a while. The reason for this is that I collect URLs of pages I encounter which are not properly parsed by the Converter, and when I release a version which understands those, I delete the URLs. Also, I never intended to cover all units in the Converter myself, for a multitude of reasons -- therefore I was never interested in the more exotic ones.<br />
<br />
<small>Guillaume Lebleu's example</small><br />
<pre><br />
<span class="unit"><br />
<abbr class="unit" title="AMP">Ampere</abbr> <abbr class="unit" title="ACR">acre</abbr> <span class="divide">per</span> <abbr class="unit" title="SEC">second</abbr><br />
</span><br />
</pre><br />
<br />
::Regarding your idea of breaking down the units in base units, that's something I've also been toying with in my head for the Converter. For my particular application, it's technically more difficult to implement this breakdown. For microformats, it would be easier, but there still remains at least one potential problem: you end up with a huge mess in the page. If a standard is too complicated to follow, one tends to give up altogether.<br />
<br />
::Consider a document which actually discusses some sort of current variation per farm, and therefore needs to repeatedly refer to ampere acres per second. For human use, they'd simply define the AAS somewhere at the top of the document, and then refer to AAS, KAAS or MAAS as needed. Maybe a similar approach should be considered for microformats as well:<br />
<br />
<pre><br />
We define the <br />
<span class="unit_definition"><br />
<abbr class="unit_name">AAS</span><br />
as<br />
<abbr class="unit" title="AMP">Ampere</abbr><br />
<abbr class="unit" title="ACR">acre</abbr><br />
<span class="divide">per</span><br />
<abbr class="unit" title="SEC">second</abbr><br />
</span>.<br />
</pre><br />
<br />
::And then use the "AAS" throughout the document as any other pre-defined unit. How would you define (and use) the KAAS (1000 AAS) or MAAS (1,000,000 AAS) though? Is there any standard way already to use data multipliers in microformats? Or should we discuss that? Or is it out of scope? --[[User:BogdanStancescu|BogdanStancescu]] 00:30, 11 Oct 2006 (PDT)<br />
<br />
That's all I can think of as major hurdles right now. If I remember anything else, I'll post here. Please do give me feedback here if you want to ask more about any of the topics I touched above, or if you have other questions I might be able to reply to. --[[User:BogdanStancescu|BogdanStancescu]] 12:08, 9 Oct 2006 (PDT)<br />
<br />
<br />
==Discoleo==<br />
=== Measurement Classification ===<br />
<br />
Because it is easier to provide examples, I will first list examples.<br />
<br />
==== Categorical vs Ordinal Data ====<br />
<br />
Various measurements may produce '''NON-Numerical''' values:<br />
* a pain scale: '''most severe''', '''very severe''', '''severe''', ...<br />
* or the TNM tumour classification system: T0, Tx, T1, T2, T3, T4, N0, ...<br />
<br />
<br />
There is even a more fundamental issue related to numbers themselves, e.g.:<br />
* '''Lists''' or '''Years''' are sometimes written using '''Roman Numbers'''<br />
** however, the strings corresponding to ''Roman Numbers'', when sorted alphabetically, do NOT retain the correct order<br />
** i.e. C (100) preceds L (50), which preceds X (10)<br />
* there are other numbering schemes<br />
<br />
==== A Single Value / Data Point ====<br />
<br />
This is the most simple data format and pretty straitforward to implement.<br />
<br />
* the distance between 2 cities is '''40 km'''<br />
* the velocity is '''62 mph'''<br />
* most other simple entires (...)<br />
<br />
==== An Interval Measurement ====<br />
<br />
* time: the shop is open between '''6am - 18pm''' on every day of the week, exept Saturdays from '''9am - 16pm''' and Sundays from '''9am - 13pm'''<br />
**[[hcalendar|hCalendar]]? [[User:AndyMabbett|Andy Mabbett]] 09:24, 22 Nov 2006 (PST)<br />
<br />
This is more about an interval measurement. Every variable can have 2 (or more) values, e.g.:<br />
* the levels of rain fall were between 25mm - 35mm<br />
* the maximum velocity of various cars was 220 - 250 km/h<br />
<br />
Should these values be stored as separate values? [e.g. low / high]<br />
Or should the microformats be able to store an interval?<br />
<br />
See also the examples for statistical summaries below.<br />
<br />
*Mark up each as a separate measurement, and wrap them in a "range" microformat? [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)<br />
<br />
==== Matrices ====<br />
<br />
* the GPS coordinates are '''12°14' N and 25°55' E'''<br />
**[[geo|Geo]]? [[User:AndyMabbett|Andy Mabbett]] 09:25, 22 Nov 2006 (PST)<br />
* the dimension of the box is '''3m x 2m x 0.55m'''<br />
**this is three separate, single measurements, surely? [[User:AndyMabbett|Andy Mabbett]] 09:21, 22 Nov 2006 (PST)<br />
** 3 x 2 x 0.55 cubic meter, still 3 measurements, BUT given as cubic meter => ONE measurement?<br />
***Who writes 3x2x0.55 cubic meter? You'd write "3.3m<sup>3</sup>" [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)<br />
** the surface was 2 x 3 square feet ???<br />
***Who writes 2x3 sq ft? You'd write "2ftx3ft" or "6ft<sup>2</sup>" [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)<br />
<br />
<br />
* IF we write "3.3m<sup>3</sup>" or "6ft<sup>2</sup>", we '''loose information'''<br />
* IF I want a surface, I would prefer the '''sqare feet''' unit, and NOT '''...feet x ...feet'''<br />
* writing for every measure a markup, will '''bloat''' the code extensively<br />
** data matrices would be very effective here<br />
*** how would you make such a matrix? There are different ways how such information can be "compounded". (length per time = speed, length * length = area). Maybe a we can group those measurements by a surrounding information, what the context is. --Emil 02:50, 25 Dec 2006 (PST)<br />
<br />
==== Statistical Measurements ====<br />
<br />
Often, a group of data is summarized using a statistics:<br />
* the mean length was 1.3m (SD 0.12m, group size 22)<br />
* the median age was 42 years (interquartile range 95% 18 - 97)<br />
<br />
==== Measurement Scales ====<br />
<br />
===== Accuracy vs. Precision =====<br />
<br />
'''QUESTIONS'''<br />
* How detailed should a measurement be stored?<br />
**Microformats aren't for storing measurements; they're for "labelling" the measurements that are already present. [[User:AndyMabbett|Andy Mabbett]] 09:23, 22 Nov 2006 (PST)<br />
* If Accuracy and precision are relevant to the measurement, how do we store these?<br />
<br />
===== Standardization of Measurement =====<br />
<br />
* sometimes we may need to store the calibration information / calibration curves<br />
* we may need to store the reference point the measurement is based on<br />
* we may need to store the '''normal values'''<br />
** biomedical measurements are often laboratory dependent, so it does NOT make sense to have the measurement without the corresponding normal values<br />
** e.g. anti-Hepatitis B surface antigen antibody (anti-HBs) Titer: 32 MIU/ml<br />
*** normal: 0 (non-infected, non-past infection, non-immunity)<br />
*** protective immunity: >10 MIU/ml<br />
*** interpretation is however more complex, depending on other tests as well<br />
<br />
== Emil Thies ==<br />
<br />
From my understanding, this microformat should concentrate on the notation of a measurement. So there will be some aspects, which has to be covered (elsewhere?) to improve the automatic use it or this microformat only uses some base informationens (units / dimensions) and derives all used from those base / build-in once.<br />
<br />
=== Dimension vs. Unit vs. Scale vs. Measurement ===<br />
<br />
A measurement is the combination of a number (value) and a unit (kind).<br />
* 3km (3 Kilo Metre = 3.000 Metre)<br />
<br />
A unit is a view for a measure of a dimension. There are two kinds how units can be different to each user:<br />
* Units Differ by Scale (Prefix)<br />
** 3km is the same as 3.000 meter or 300.000 cm (Its the same unit, with a different prefix, which works like a factor for the value, to lower the amount of symbols / numbers. The scale should be an own element and we can make use of the standard prefixes, like they are defined on [http://aurora.regenstrief.org/UCUM/ucum.html#section-Prefixes The Unified Code for Units of Measure] or [http://www.w3.org/TR/mathml-units/#SI-prefixes MathML]).<br />
* Different units of the same dimension can be transferred into each other.<br />
** Metre is a unit of the dimension length.<br />
** Foot is a unit of the dimension length.<br />
<br />
A Dimension is a base-dimension (see SI-System) or a compound dimension.<br />
* length is a base dimension<br />
* time is a base dimension<br />
* speed is a compound dimension (length per time). There for a measurement of speed has one number and two unit by a math expression, which form their own unit. e.g. 10 m/s (10 Metre per second).<br />
<br />
If we express a measurement in a microformat by the unit, the dimension is indirect provided by it. But a microformat, which uses measurement as a part, needs to define the dimension of it, to keep the use of the unit as an user choice. So, we could have a general measurement element, which allows all kinds of units to use. As a derived format, we can have sub-formats, which limit the list of units (or define an alternate list) by only allowing specific dimension(s).<br />
<br />
E.G. <br />
* [[currency-proposal]], with the money element which uses the same elements value (should then replace amount), scale (should be introduced), unit (should replace currency) which is limit to the ISO 4217 list.<br />
* length, which only allows units which measures the dimension length, like FOT, MTR ...<br />
<br />
=== Identification of Units ===<br />
<br />
There are so many Units around - not only the existing one. There are deprecated ones like from Rome empire etc. For example "[http://en.wikipedia.org/wiki/Foot_(unit_of_length) Foot]" is not an unique identification of a unit. There is not only the British and U.S., there are for example same old German ones, before those areas joined the international metre convention in 1875:<br />
* 25 cm in Hessen<br />
* 28,935 cm in Bremen <br />
* 29,641 cm in Oldenburg <br />
* 29,1859 cm in Bayern <br />
* 30,385 cm in Meiningen-Hildburghausen <br />
* 31,385 cm in Preußen <br />
* 31,608 cm in Wien/Österreich <br />
* 32,61 cm in Bad Homburg vor der Höhe <br />
* 33 1/3 cm in der Pfalz <br />
<br />
So there is the need of a unique identification of those units. I found two approach right:<br />
<br />
==== In MathML ====<br />
<br />
MathML [http://www.w3.org/TR/mathml-units/#definitionURL defines] the construction of an URI like:<br />
<br />
<nowiki>http://base/units/unit name[/context][/country][#prefix]</nowiki><br />
<br />
<pre><br />
http://.../units/foot/de<br />
</pre><br />
<br />
But as you can see, there is right now no way to distinguish the different German foots based on the area inside Germany. Furthermore the context is so variable, that the same unit can be described by different URLs.<br />
<br />
==== In OpenMath ====<br />
<br />
OpenMath [http://www.openmath.org/cdgroups/units.html defines] the units inside of content directories:<br />
<br />
<pre><br />
http://www.openmath.org/cd/units_us1.xhtml#foot_us_survey<br />
</pre><br />
<br />
So there is a unique URLs for a Unit, but not every Unit is covered.<br />
<br />
=== Transformation of Units ===<br />
<br />
A real benefit is the automatic transformation of a unit, so that the write can write the measurement in his context (e.g. in the U.S. foot, or a quote from an antike text in Rome Empire foot) and the reader can get a transformation in his context (e.g. the value in metre). There fore there is the need of additional transformation information. And there are some different kinds of transformation:<br />
<br />
==== units of same dimension ====<br />
<br />
e.g. foot to metre<br />
<br />
==== units of compound but same dimension ====<br />
<br />
e.g. metre/s and mach-number<br />
<br />
==== compound measurement context ====<br />
<br />
<pre>This switch works up to 5 Ampere by 220 Volt</pre><br />
<br />
The reader might to now, which Watt device he can attach (1100 Watt would be the answer).<br />
<br />
<pre>The dimension of the box is 3m x 2m x 0.55m</pre><br />
<br />
There might be some question like:<br />
* volume (3,3 m³)<br />
* surface (17,5 m²)<br />
<br />
=== Approach ===<br />
<br />
A general measurement should make use of the following informations:<br />
<br />
value: a number, which represents the amount of the measurement. The number should follow one of the following representation:<br />
* natural (positive and negative): e.g. -1, 0, 1<br />
* decimal fraction (positive and negative): e.g. -2.5, 0.123<br />
* natural fraction (positive and negative): e.g. -2/3, 3/7<br />
scale: a factor used to lower the needed numbers of the value. The scale should be either<br />
* a letter to refer a build-in factor, which is defined in [http://aurora.regenstrief.org/UCUM/ucum.html#section-Prefixes The Unified Code for Units of Measure] or [http://www.w3.org/TR/mathml-units/#SI-prefixes MathML]).<br />
* a number like defined on value<br />
unit: the unit used for the measurement. The unit should follow one of the following representation:<br />
* build-in short-form like defined on [http://www.unece.org/etrades/units.htm Standards for Trade and Electronic Business] (or any other defined list which will be defined as the standard list for this format)<br />
* a reference to a unit definition. (I think there is the need of a markup/language to define new units and/or the transformation between units).<br />
<br />
<br />
<pre><br />
<span class="measurement"><abbr class="value" title="5">Five</abbr> <abbr class="scale" title="k">kilo</abbr> <abbr class="unit" title="MTR">metre</abbr></span><br />
</pre><br />
<br />
when we have a defined sub-measurement format for length, it could also be written:<br />
<br />
<pre><br />
<span class="length"><abbr class="value" title="5">Five</abbr> <abbr class="scale" title="k">kilo</abbr> <abbr class="unit" title="MTR">metre</abbr></span><br />
</pre><br />
<br />
==== List of possible Sub-Formats ====<br />
<br />
Here is a (first) list of possible keywords for sub-formats and their unit list or compound kind:<br />
<br />
* money - unit limit to the ISO 4217 List (or could be a sparate [[currency]] microformat)<br />
* '''length''' - unit limited to e.g. MTR (Metre), FOT (Foot) ....)<br />
** '''area''' <br />
*** Either a measurement with units like MTK (Square Metre), FTK (Square Foot) <br />
*** or a compound format with elements (width:length, height:length)<br />
** '''volume''' <br />
*** Either a measurement with units like MTQ (Cubic Metre), FTQ (Cubic Foot), LTR (Litre) ...<br />
*** or a compound format with elements (width:length, height:length, depth:length)<br />
* time or duration or '''period''' - unit limited to e.g. sec (second), min (minute) ...<br />
* '''frequency''' - unit limited to Hertz<br />
* mass or '''weight''' - unit limited to GRM (Gram), ...<br />
* power or '''electricity([http://www.skldintl.com solar garden light])''' - unit limited to AMP (Ampere), OHM (Ohm), ...<br />
<br />
==Straw man==<br />
Based on [[currency-brainstorming#Taylor_Cowan|Taylor Cowan's currency suggestion]], and [http://microformats.org/discuss/mail/microformats-new/2007-September/000921.html subsequent mailing list discussion], the following straw man (rendering the above sub-formats unnecessary) is proposed:<br />
<br />
<pre><nowiki><br />
<span class="hmeasure"><br />
[value]<br />
</span><br />
<br />
<abbr class="hmeasure" title="[value]"><br />
[text]<br />
</abbr><br />
</nowiki></pre><br />
<br />
Where "value" is a number-type pair ("3Kg", "456g") using [http://en.wikipedia.org/wiki/SI_units SI] or other standard unit-codes and where parsers must accept the formats:<br />
<br />
*[unit-code][number]<br />
*[unit-code][space][number]<br />
*[number][unit-code]<br />
*[number]space[unit-code]<br />
<br />
and where the acceptable codes are to be determined.<br />
<br />
Further comment is invited. A test page is available, at http://www.westmidlandbirdclub.com/test/measure.htm<br />
<br />
===Notes===<br />
*This is extensible, using agreed new codes for unusual or archaic measurements (say "FUR" for "furlong"); such codes could be contained in the microformat's profile.<br />
*Otherwise, it works as-is for sub-divisions of currencies:<br />
<br />
<pre><nowiki><br />
<abbr class="hmeasure" title="635mm"><br />
2' 1"<br />
</abbr><br />
</nowiki></pre><br />
<br />
:(2' 1" is "two feet one inch" in imperial measurement).<br />
<br />
===Issues===<br />
*is hmeasure the appropriate class-name?<br />
*Is [[currency|money]] a separate microformat, or a measurement, with the ISO currency code as the unit-code?<br />
*What standard sources for unit-codes exist? <br />
**[http://www.bipm.org/en/si/ International System of Units]<br />
*This is still susceptible to the [[accessibility-issues#abbr-design-pattern]]<br />
*How should stops (.) and commas (,) be interpreted? [[User:TobyInk|TobyInk]] 04:13, 18 Nov 2007 (PST)<br />
*Do we also need sub-classes?<br />
<br />
<pre><nowiki><br />
<span class="hmeasure"><br />
The <span class="unit-code">kg</span> weight was, in total <span class="value">5</span>.<br />
</span><br />
</nowiki></pre><br />
<br />
*If so, where would this be used? And are "unit-code" and "value" appropriate class-names?<br />
*<p>'''[http://en.wikipedia.org/wiki/Measurement Measurement errors]''' are fundamental in many technical and scientific fields, they must be supported. [[User:LucaPost|LucaPost]]<br />
<br />
<pre><nowiki><br />
<span class="hmeasure"><br />
<a href="/depth" rel="tag" class="data-name">Depth</a>:<br />
( <span class="data-value">2.17</span> +/-<br />
<span class="data-error"> 0.02</span> )<br />
x 10<sup class="exp">3</sup><br />
<abbr class="unit-measure" title="m">meters</abbr>.<br />
</span><br />
</nowiki></pre><br />
</p><br />
:#Here the actual physical quantity is better 'defined' with rel-tag, and the optional data-error is clearly identified with its own span; alternatively parsers might identify the data-error part by looking for the '&plusmn;' html-entity.<br />
:# The standard '''[http://en.wikipedia.org/wiki/Scientific_Notation scientific notation]''' requires the data and the error values to be rounded to the same number of digits; the exponential notation in powers of ten is useful to have a singular format for values of any order of magnitude.<br />
:# data-error and exp are not needed outside scientific contexts, thus they would be optional; the above HTML still represents a semantic structure when they're left out.<br />
<br />
===Suggested amendment 1===<br />
<br />
*Use only:<br />
<br />
<pre><nowiki><br />
<abbr class="hmeasure" title="[value]"><br />
[text]<br />
</abbr><br />
</nowiki></pre><br />
<br />
Where "value" is a number-type pair ("3 kg", "456 g") using [http://en.wikipedia.org/wiki/SI_units SI] or other standard unit-codes where the parser must accept the following formats:<br />
<br />
*Single measurements - [number][space][[http://en.wikipedia.org/wiki/SI_prefix SI-prefix]][[http://www.bipm.org/en/si/si_brochure/chapter5/5-2.html SI-unit]]<br />
*Compound measurements - [number][space][[http://en.wikipedia.org/wiki/SI_prefix SI-prefix]][[http://www.bipm.org/en/si/si_brochure/chapter5/5-2.html SI-unit]][/][[[http://en.wikipedia.org/wiki/SI_prefix SI-prefix]][[http://www.bipm.org/en/si/si_brochure/chapter5/5-2.html SI-unit]]<br />
<br />
====Notes====<br />
*The only values allowed are SI values and prefixes<br />
<br />
<pre><nowiki><br />
<abbr class="hmeasure" title="635 mm"><br />
2' 1"<br />
</abbr><br />
<br />
<abbr class="hmeasure" title="635 km/s"><br />
635 kilometers per second<br />
</abbr><br />
<br />
<abbr class="hmeasure" title="0.5 m^3/s^2"><br />
half a cubic metre per second squared<br />
</abbr><br />
</nowiki></pre><br />
<br />
====Supported SI Prefixes====<br />
<br />
* yotta Y Quadrillion -1 000 000 000 000 000 000 000 000<br />
* zetta Z Trilliard (thousand trillion) - 1 000 000 000 000 000 000 000<br />
* exa- E Quintillion Trillion 1 000 000 000 000 000 000<br />
* peta- P Quadrillion Billiard (thousand billion) 1 000 000 000 000 000<br />
* tera- T Trillion Billion 1 000 000 000 000<br />
* giga- G Billion Milliard (thousand million) 1 000 000 000<br />
* mega- M Million 1 000 000<br />
* kilo- k Thousand 1 000<br />
* hecto- h Hundred 100<br />
* deca- da Ten 10<br />
* deci- d Tenth 0.1<br />
* centi- c Hundredth 0.01<br />
* milli- m Thousandth 0.001<br />
* micro- u Millionth 0.000 001<br />
** There is already a unicode character for the micro, sign: &#xB5; (U+00B5). Better to use it than substituting a "u". [[User:TobyInk|TobyInk]] 03:56, 18 Nov 2007 (PST)<br />
* nano- n Billionth Milliardth 0.000 000 001<br />
* pico- p Trillionth Billionth 0.000 000 000 001<br />
* femto- f Quadrillionth Billiardth 0.000 000 000 000 001<br />
* atto- a Quintillionth Trillionth 0.000 000 000 000 000 001<br />
* zepto- z Sextillionth Trilliardth 0.000 000 000 000 000 000 001<br />
* yocto- y Septillionth Quadrillionth 0.000 000 000 000 000 000 000 001<br />
<br />
====Supported SI Units====<br />
<br />
*meter (m) - length<br />
*gram (g) - mass<br />
*kilogram (kg) - mass<br />
*second (s) - time<br />
*ampere (A) - electric current<br />
*kelvin (K) - thermodynamic temperature<br />
*mole (mol) - amount of substance<br />
*candela (cd) - luminous intensity<br />
<br />
====Supported Derived SI Units====<br />
*hertz (Hz) - frequency<br />
*newton - (N) force, weight<br />
*pascal - (Pa) pressure, stress<br />
*joule (J) - energy, work, heat<br />
*watt (W) - power, radiant flux<br />
*coulomb (C) - electric charge or electric flux<br />
*volt (V) - voltage, electrical potential difference, electromotive force<br />
*farad (F) - electric capacitance<br />
*ohm (ohm) - electric resistance, impedance, reactance<br />
*siemens (S) - electrical conductance<br />
*weber (Wb) - magnetic flux<br />
*tesla (T) - magnetic field<br />
*henry (H) - inductance<br />
*lumen (lm) - luminous flux<br />
*lux (lx) - illuminance<br />
*becquerel (Bq) - radioactivity (decays per unit time)<br />
*sievert (Sv) - equivalent dose (of ionizing radiation)<br />
*katal (kat) - catalytic activity<br />
<br />
====Supported Non-SI Units====<br />
<br />
*minute (min) - time<br />
*hour (h) - time<br />
*day (d) - time<br />
*radian (rad) - angle<br />
*degree of arc (deg) - angle<br />
** Use instead U+00B0 (&#xB0;, degree) [[User:TobyInk|TobyInk]] 04:06, 18 Nov 2007 (PST)<br />
*minute of arc (') - angle<br />
** Use instead U+2032 (&#x2032;, prime) [[User:TobyInk|TobyInk]] 04:06, 18 Nov 2007 (PST)<br />
*second of arc (<nowiki>''</nowiki>) - angle<br />
** Use instead U+2033 (&#x2033;, double-prime) [[User:TobyInk|TobyInk]] 04:06, 18 Nov 2007 (PST)<br />
*steradian (sr) - solid angle<br />
*square degree (deg^2) - solid angle<br />
*litre (L) - volume<br />
*tonne (t) - mass<br />
<br />
====Units Defined by Microformats.org====<br />
<br />
*celcius (cel) - temperature<br />
** Use U+2103 (&#x2103;, degrees celcius) [[User:TobyInk|TobyInk]] 04:07, 18 Nov 2007 (PST)<br />
*bit (bit) - computing<br />
*year (y) - year<br />
*inch (in) - inch<br />
*foot (ft) - foot<br />
<br />
====Supported SI Markup====<br />
<br />
*solidus (/) - divisor<br />
** Division slash (&#x2215;, U+2215) more appropriate [[User:TobyInk|TobyInk]] 04:09, 18 Nov 2007 (PST)<br />
*caret (^) - exponentiation<br />
<br />
==See also==<br />
{{measure-related-pages}}</div>Niuhaibiaohttps://microformats.org/wiki/index.php?title=measure-brainstorming&diff=41637measure-brainstorming2010-01-14T06:34:20Z<p>Niuhaibiao: /* List of possible Sub-Formats */</p>
<hr />
<div>= Measure Microformat Brainstorming =<br />
<br />
This page collects ideas on how to use semantic XHTML to represent unambiguously [[measure]]s.<br />
<br />
== Guillaume Lebleu ==<br />
<br />
Basic example with elementary unit using the abbr pattern and the UNECE code (see [[measure-formats]])<br />
<br />
<pre><br />
<span class="length">5 <abbr class="unit" title="FOT">Feet</abbr></span><br />
</pre><br />
<br />
Optional "value" could be useful in some cases, for instance when the value is provided in plain text:<br />
<br />
<pre><br />
<span class="length"><abbr class="value" title="5">Five</abbr> <abbr class="unit" title="FOT">Feet</abbr></span><br />
</pre><br />
<br />
<br />
==Andy Mabbett==<br />
<br />
===Converter Extension===<br />
This Firefox extension may be of interest. Note, though, that it's been criticised for having a "nag" screen: [https://addons.mozilla.org/firefox/2286/ Converter] [[User:AndyMabbett|AndyMabbett]] 15:32, 3 Oct 2006 (PDT)<br />
<br />
:This is the author of that extension. I don't want to go much into this, but I just want to clarify this briefly. The part with the nag screen is wrong on two counts: (1) that dialog isn't there anymore, and (2) even if it was there, you only needed to read a paragraph and click a button to make it go away ''forever'' -- but you don't have to take my word for it, install it for yourselves and see. Andy's report is accurate however -- the extension '''''was''''' criticized for that dialog (that's what you get from your free extension's users when you ask for 15 seconds of their time in return for hundreds of hours of your time). --[[User:BogdanStancescu|BogdanStancescu]] 09:35, 9 Oct 2006 (PDT)<br />
<br />
===Wikipedia converter===<br />
Wikipedia's [http://en.wikipedia.org/wiki/Template:Convert Convert Template] automatically converts from metric to imperial and vice versa. It's worth noting the measurements it supports. <br />
<br />
===Google calculator===<br />
A Google search, e.g. for "0.6 miles" [http://www.google.co.uk/search?q=0.6+miles returns a metric conversion]. See also [http://www.google.co.uk/intl/en/help/calculator.html Google calculator help].<br />
<br />
===HTML Entities===<br />
*For squared and cubic values, the HTML entities <code>&amp;sup2;</code> and <code>&amp;sup3;</code> should be borne in mind.<br />
<br />
*For temperatures and angels, the HTML entity <code>&amp;deg;</code> exists.<br />
<br />
*The following currency entities exist: <br />
**<code>&curren;</code> - <code>&amp;curren;</code> - currency <br />
**<code>&cent;</code> - <code>&amp;cent;</code> - cent<br />
**<code>&pound;</code> - <code>&amp;pound;</code> - pound<br />
**<code>&yen;</code> - <code>&amp;yen;</code> - yen<br />
**<code>&euro;</code> - <code>&amp;euro;</code> - Euro<br />
<br />
==Bogdan Stăncescu==<br />
Here are my findings related to automatic parsing of measurements on web pages while developing the [http://converter.mozdev.org Converter] extension. Please ask away if you want me to go into more detail on any of the topics -- I'm not sure which of my experiences are relevant to microformats, so I'm going to give you an overview of my conclusions.<br />
<br />
By the way of an introduction, the Converter is a Firefox extension which tries to convert all measurements it finds in any web page to their Imperial or metric counterpart (e.g. Fahrenheit to Celsius, and Celsius to Fahrenheit; meters to feet and feet to meters). There are two steps to the conversion process: (1) identifying the measurements in the page, and (2) converting them. As expected, the conversion part is trivial, at least conceptually. The parsing is the tricky bit, and that's also where the Converter's challenges also become relevant for microformats.<br />
<br />
Here are the main challenges I have encountered while writing the Converter:<br />
<br />
;Presentation standardization: The first, biggest and most obvious challenge is lack of almost any ''de facto'' standardization in respect to data presentation. What I mean is that although the units themselves are more or less standardized (more on that later), they are ''presented'' in various ways within web pages. Take these examples: "50 foot monster", "50 ft monster", "50 feet monster", "50-foot monster", "50-feet monster" -- and my personal favorite, "fifty-foot monster" (more on this later);<br />
<br />
:Note that using a microformat using in particular the [[abbr-design-pattern]] would make each of these examples less ambiguous if not unambiguous. See below --[[User:Guillaume_Lebleu|Guillaume_Lebleu]]:<br />
<br />
<pre><br />
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">foot</abbr></span> monster<br />
</pre><br />
<br />
<pre><br />
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">ft</abbr></span> monster<br />
</pre><br />
<br />
<pre><br />
<span class="height"><span class="value">50</span>-<abbr class="unit" title="FOT">foot</abbr></span> monster<br />
</pre><br />
<br />
<pre><br />
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">feet</abbr></span> monster<br />
</pre><br />
<br />
<pre><br />
<span class="height"><abbr class="value" title="50">fifty</abbr><abbr class="unit" title="FOT">foot</abbr></span> monster<br />
</pre><br />
<br />
:: Of course; as far as I could gather, that's actually the ''purpose'' of microformats -- bridging the gap between what humans and machines can understand, no? --[[User:BogdanStancescu|BogdanStancescu]] 00:30, 11 Oct 2006 (PDT)<br />
<br />
;Unit standardization: I live in Europe, where I've always used the metric system. As such, this probably was a much bigger nasty surprise for me than it is for a user of the Imperial/U.S. Customary system: in the Imperial system, the units themselves vary depending on where you are -- miles, pints, and a whole lot of other units come in many different flavors, but they're all written the same in regular usage;<br />
<br />
;Language: "1 meter" vs. "1 metre" is a reasonable difference -- but non-SI units are usually translated. Even some SI units have different plurals, depending on the language, although in theory SI units are actually denoted by ''symbols'', not "words", as to make them non-translatable, and truly international (hence the name of the SI). I haven't really given much thought to a solution towards parsing these, because I find it overwhelming for the time.<br />
<br />
;The sheer number of units: surprisingly, most people don't realize just how many units we humans have invented. Just take a look here: [http://www.asknumbers.com/ asknumbers.com] -- see how many categories there are? Now click on Flow Rate -- a non-ubiquitous type of measurement. Three sub-categories only for flow rates! Now click on Volume Flow Rate and take a look at the number of units in those lists. Remember, those are just in one of the three categories for flow rate! The UNECE standard mentioned in the [[measure-formats#Measure_Formats|measure formats]] page is useful to define just that -- a ''standard'' set of units. But in practice there are a lot more being used out there.<br />
<br />
:Do you have examples from the Web (a URL) of non-UNECE units. One possibility would be to provide the ability for a unit to be defined as a division of products of other units. This is consistent with the [[measure-formats#Systeme_International]], which defines 7 base units and all other units as derived units (of course some units, even though they are derived are much easily represented as simple ones). This is what XBRL has done for financial/accounting/reporting. See [[currency-formats#XBRL]] and theorical example (ampere acre per second) below --[[User:Guillaume_Lebleu|Guillaume_Lebleu]]:<br />
<br />
::Unfortunately I don't have URLs -- almost at all -- with measurements, although I've been in the "business" for a while. The reason for this is that I collect URLs of pages I encounter which are not properly parsed by the Converter, and when I release a version which understands those, I delete the URLs. Also, I never intended to cover all units in the Converter myself, for a multitude of reasons -- therefore I was never interested in the more exotic ones.<br />
<br />
<small>Guillaume Lebleu's example</small><br />
<pre><br />
<span class="unit"><br />
<abbr class="unit" title="AMP">Ampere</abbr> <abbr class="unit" title="ACR">acre</abbr> <span class="divide">per</span> <abbr class="unit" title="SEC">second</abbr><br />
</span><br />
</pre><br />
<br />
::Regarding your idea of breaking down the units in base units, that's something I've also been toying with in my head for the Converter. For my particular application, it's technically more difficult to implement this breakdown. For microformats, it would be easier, but there still remains at least one potential problem: you end up with a huge mess in the page. If a standard is too complicated to follow, one tends to give up altogether.<br />
<br />
::Consider a document which actually discusses some sort of current variation per farm, and therefore needs to repeatedly refer to ampere acres per second. For human use, they'd simply define the AAS somewhere at the top of the document, and then refer to AAS, KAAS or MAAS as needed. Maybe a similar approach should be considered for microformats as well:<br />
<br />
<pre><br />
We define the <br />
<span class="unit_definition"><br />
<abbr class="unit_name">AAS</span><br />
as<br />
<abbr class="unit" title="AMP">Ampere</abbr><br />
<abbr class="unit" title="ACR">acre</abbr><br />
<span class="divide">per</span><br />
<abbr class="unit" title="SEC">second</abbr><br />
</span>.<br />
</pre><br />
<br />
::And then use the "AAS" throughout the document as any other pre-defined unit. How would you define (and use) the KAAS (1000 AAS) or MAAS (1,000,000 AAS) though? Is there any standard way already to use data multipliers in microformats? Or should we discuss that? Or is it out of scope? --[[User:BogdanStancescu|BogdanStancescu]] 00:30, 11 Oct 2006 (PDT)<br />
<br />
That's all I can think of as major hurdles right now. If I remember anything else, I'll post here. Please do give me feedback here if you want to ask more about any of the topics I touched above, or if you have other questions I might be able to reply to. --[[User:BogdanStancescu|BogdanStancescu]] 12:08, 9 Oct 2006 (PDT)<br />
<br />
<br />
==Discoleo==<br />
=== Measurement Classification ===<br />
<br />
Because it is easier to provide examples, I will first list examples.<br />
<br />
==== Categorical vs Ordinal Data ====<br />
<br />
Various measurements may produce '''NON-Numerical''' values:<br />
* a pain scale: '''most severe''', '''very severe''', '''severe''', ...<br />
* or the TNM tumour classification system: T0, Tx, T1, T2, T3, T4, N0, ...<br />
<br />
<br />
There is even a more fundamental issue related to numbers themselves, e.g.:<br />
* '''Lists''' or '''Years''' are sometimes written using '''Roman Numbers'''<br />
** however, the strings corresponding to ''Roman Numbers'', when sorted alphabetically, do NOT retain the correct order<br />
** i.e. C (100) preceds L (50), which preceds X (10)<br />
* there are other numbering schemes<br />
<br />
==== A Single Value / Data Point ====<br />
<br />
This is the most simple data format and pretty straitforward to implement.<br />
<br />
* the distance between 2 cities is '''40 km'''<br />
* the velocity is '''62 mph'''<br />
* most other simple entires (...)<br />
<br />
==== An Interval Measurement ====<br />
<br />
* time: the shop is open between '''6am - 18pm''' on every day of the week, exept Saturdays from '''9am - 16pm''' and Sundays from '''9am - 13pm'''<br />
**[[hcalendar|hCalendar]]? [[User:AndyMabbett|Andy Mabbett]] 09:24, 22 Nov 2006 (PST)<br />
<br />
This is more about an interval measurement. Every variable can have 2 (or more) values, e.g.:<br />
* the levels of rain fall were between 25mm - 35mm<br />
* the maximum velocity of various cars was 220 - 250 km/h<br />
<br />
Should these values be stored as separate values? [e.g. low / high]<br />
Or should the microformats be able to store an interval?<br />
<br />
See also the examples for statistical summaries below.<br />
<br />
*Mark up each as a separate measurement, and wrap them in a "range" microformat? [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)<br />
<br />
==== Matrices ====<br />
<br />
* the GPS coordinates are '''12°14' N and 25°55' E'''<br />
**[[geo|Geo]]? [[User:AndyMabbett|Andy Mabbett]] 09:25, 22 Nov 2006 (PST)<br />
* the dimension of the box is '''3m x 2m x 0.55m'''<br />
**this is three separate, single measurements, surely? [[User:AndyMabbett|Andy Mabbett]] 09:21, 22 Nov 2006 (PST)<br />
** 3 x 2 x 0.55 cubic meter, still 3 measurements, BUT given as cubic meter => ONE measurement?<br />
***Who writes 3x2x0.55 cubic meter? You'd write "3.3m<sup>3</sup>" [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)<br />
** the surface was 2 x 3 square feet ???<br />
***Who writes 2x3 sq ft? You'd write "2ftx3ft" or "6ft<sup>2</sup>" [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)<br />
<br />
<br />
* IF we write "3.3m<sup>3</sup>" or "6ft<sup>2</sup>", we '''loose information'''<br />
* IF I want a surface, I would prefer the '''sqare feet''' unit, and NOT '''...feet x ...feet'''<br />
* writing for every measure a markup, will '''bloat''' the code extensively<br />
** data matrices would be very effective here<br />
*** how would you make such a matrix? There are different ways how such information can be "compounded". (length per time = speed, length * length = area). Maybe a we can group those measurements by a surrounding information, what the context is. --Emil 02:50, 25 Dec 2006 (PST)<br />
<br />
==== Statistical Measurements ====<br />
<br />
Often, a group of data is summarized using a statistics:<br />
* the mean length was 1.3m (SD 0.12m, group size 22)<br />
* the median age was 42 years (interquartile range 95% 18 - 97)<br />
<br />
==== Measurement Scales ====<br />
<br />
===== Accuracy vs. Precision =====<br />
<br />
'''QUESTIONS'''<br />
* How detailed should a measurement be stored?<br />
**Microformats aren't for storing measurements; they're for "labelling" the measurements that are already present. [[User:AndyMabbett|Andy Mabbett]] 09:23, 22 Nov 2006 (PST)<br />
* If Accuracy and precision are relevant to the measurement, how do we store these?<br />
<br />
===== Standardization of Measurement =====<br />
<br />
* sometimes we may need to store the calibration information / calibration curves<br />
* we may need to store the reference point the measurement is based on<br />
* we may need to store the '''normal values'''<br />
** biomedical measurements are often laboratory dependent, so it does NOT make sense to have the measurement without the corresponding normal values<br />
** e.g. anti-Hepatitis B surface antigen antibody (anti-HBs) Titer: 32 MIU/ml<br />
*** normal: 0 (non-infected, non-past infection, non-immunity)<br />
*** protective immunity: >10 MIU/ml<br />
*** interpretation is however more complex, depending on other tests as well<br />
<br />
== Emil Thies ==<br />
<br />
From my understanding, this microformat should concentrate on the notation of a measurement. So there will be some aspects, which has to be covered (elsewhere?) to improve the automatic use it or this microformat only uses some base informationens (units / dimensions) and derives all used from those base / build-in once.<br />
<br />
=== Dimension vs. Unit vs. Scale vs. Measurement ===<br />
<br />
A measurement is the combination of a number (value) and a unit (kind).<br />
* 3km (3 Kilo Metre = 3.000 Metre)<br />
<br />
A unit is a view for a measure of a dimension. There are two kinds how units can be different to each user:<br />
* Units Differ by Scale (Prefix)<br />
** 3km is the same as 3.000 meter or 300.000 cm (Its the same unit, with a different prefix, which works like a factor for the value, to lower the amount of symbols / numbers. The scale should be an own element and we can make use of the standard prefixes, like they are defined on [http://aurora.regenstrief.org/UCUM/ucum.html#section-Prefixes The Unified Code for Units of Measure] or [http://www.w3.org/TR/mathml-units/#SI-prefixes MathML]).<br />
* Different units of the same dimension can be transferred into each other.<br />
** Metre is a unit of the dimension length.<br />
** Foot is a unit of the dimension length.<br />
<br />
A Dimension is a base-dimension (see SI-System) or a compound dimension.<br />
* length is a base dimension<br />
* time is a base dimension<br />
* speed is a compound dimension (length per time). There for a measurement of speed has one number and two unit by a math expression, which form their own unit. e.g. 10 m/s (10 Metre per second).<br />
<br />
If we express a measurement in a microformat by the unit, the dimension is indirect provided by it. But a microformat, which uses measurement as a part, needs to define the dimension of it, to keep the use of the unit as an user choice. So, we could have a general measurement element, which allows all kinds of units to use. As a derived format, we can have sub-formats, which limit the list of units (or define an alternate list) by only allowing specific dimension(s).<br />
<br />
E.G. <br />
* [[currency-proposal]], with the money element which uses the same elements value (should then replace amount), scale (should be introduced), unit (should replace currency) which is limit to the ISO 4217 list.<br />
* length, which only allows units which measures the dimension length, like FOT, MTR ...<br />
<br />
=== Identification of Units ===<br />
<br />
There are so many Units around - not only the existing one. There are deprecated ones like from Rome empire etc. For example "[http://en.wikipedia.org/wiki/Foot_(unit_of_length) Foot]" is not an unique identification of a unit. There is not only the British and U.S., there are for example same old German ones, before those areas joined the international metre convention in 1875:<br />
* 25 cm in Hessen<br />
* 28,935 cm in Bremen <br />
* 29,641 cm in Oldenburg <br />
* 29,1859 cm in Bayern <br />
* 30,385 cm in Meiningen-Hildburghausen <br />
* 31,385 cm in Preußen <br />
* 31,608 cm in Wien/Österreich <br />
* 32,61 cm in Bad Homburg vor der Höhe <br />
* 33 1/3 cm in der Pfalz <br />
<br />
So there is the need of a unique identification of those units. I found two approach right:<br />
<br />
==== In MathML ====<br />
<br />
MathML [http://www.w3.org/TR/mathml-units/#definitionURL defines] the construction of an URI like:<br />
<br />
<nowiki>http://base/units/unit name[/context][/country][#prefix]</nowiki><br />
<br />
<pre><br />
http://.../units/foot/de<br />
</pre><br />
<br />
But as you can see, there is right now no way to distinguish the different German foots based on the area inside Germany. Furthermore the context is so variable, that the same unit can be described by different URLs.<br />
<br />
==== In OpenMath ====<br />
<br />
OpenMath [http://www.openmath.org/cdgroups/units.html defines] the units inside of content directories:<br />
<br />
<pre><br />
http://www.openmath.org/cd/units_us1.xhtml#foot_us_survey<br />
</pre><br />
<br />
So there is a unique URLs for a Unit, but not every Unit is covered.<br />
<br />
=== Transformation of Units ===<br />
<br />
A real benefit is the automatic transformation of a unit, so that the write can write the measurement in his context (e.g. in the U.S. foot, or a quote from an antike text in Rome Empire foot) and the reader can get a transformation in his context (e.g. the value in metre). There fore there is the need of additional transformation information. And there are some different kinds of transformation:<br />
<br />
==== units of same dimension ====<br />
<br />
e.g. foot to metre<br />
<br />
==== units of compound but same dimension ====<br />
<br />
e.g. metre/s and mach-number<br />
<br />
==== compound measurement context ====<br />
<br />
<pre>This switch works up to 5 Ampere by 220 Volt</pre><br />
<br />
The reader might to now, which Watt device he can attach (1100 Watt would be the answer).<br />
<br />
<pre>The dimension of the box is 3m x 2m x 0.55m</pre><br />
<br />
There might be some question like:<br />
* volume (3,3 m³)<br />
* surface (17,5 m²)<br />
<br />
=== Approach ===<br />
<br />
A general measurement should make use of the following informations:<br />
<br />
value: a number, which represents the amount of the measurement. The number should follow one of the following representation:<br />
* natural (positive and negative): e.g. -1, 0, 1<br />
* decimal fraction (positive and negative): e.g. -2.5, 0.123<br />
* natural fraction (positive and negative): e.g. -2/3, 3/7<br />
scale: a factor used to lower the needed numbers of the value. The scale should be either<br />
* a letter to refer a build-in factor, which is defined in [http://aurora.regenstrief.org/UCUM/ucum.html#section-Prefixes The Unified Code for Units of Measure] or [http://www.w3.org/TR/mathml-units/#SI-prefixes MathML]).<br />
* a number like defined on value<br />
unit: the unit used for the measurement. The unit should follow one of the following representation:<br />
* build-in short-form like defined on [http://www.unece.org/etrades/units.htm Standards for Trade and Electronic Business] (or any other defined list which will be defined as the standard list for this format)<br />
* a reference to a unit definition. (I think there is the need of a markup/language to define new units and/or the transformation between units).<br />
<br />
<br />
<pre><br />
<span class="measurement"><abbr class="value" title="5">Five</abbr> <abbr class="scale" title="k">kilo</abbr> <abbr class="unit" title="MTR">metre</abbr></span><br />
</pre><br />
<br />
when we have a defined sub-measurement format for length, it could also be written:<br />
<br />
<pre><br />
<span class="length"><abbr class="value" title="5">Five</abbr> <abbr class="scale" title="k">kilo</abbr> <abbr class="unit" title="MTR">metre</abbr></span><br />
</pre><br />
<br />
==== List of possible Sub-Formats ====<br />
<br />
Here is a (first) list of possible keywords for sub-formats and their unit list or compound kind:<br />
<br />
* money - unit limit to the ISO 4217 List (or could be a sparate [[currency]] microformat)<br />
* '''length''' - unit limited to e.g. MTR (Metre), FOT (Foot) ....)<br />
** '''area''' <br />
*** Either a measurement with units like MTK (Square Metre), FTK (Square Foot) <br />
*** or a compound format with elements (width:length, height:length)<br />
** '''volume''' <br />
*** Either a measurement with units like MTQ (Cubic Metre), FTQ (Cubic Foot), LTR (Litre) ...<br />
*** or a compound format with elements (width:length, height:length, depth:length)<br />
* time or duration or '''period''' - unit limited to e.g. sec (second), min (minute) ...<br />
* '''frequency''' - unit limited to Hertz<br />
* mass or '''weight''' - unit limited to GRM (Gram), ...<br />
* power or '''electricity(http://www.skldintl.com solar garden light])''' - unit limited to AMP (Ampere), OHM (Ohm), ...<br />
<br />
==Straw man==<br />
Based on [[currency-brainstorming#Taylor_Cowan|Taylor Cowan's currency suggestion]], and [http://microformats.org/discuss/mail/microformats-new/2007-September/000921.html subsequent mailing list discussion], the following straw man (rendering the above sub-formats unnecessary) is proposed:<br />
<br />
<pre><nowiki><br />
<span class="hmeasure"><br />
[value]<br />
</span><br />
<br />
<abbr class="hmeasure" title="[value]"><br />
[text]<br />
</abbr><br />
</nowiki></pre><br />
<br />
Where "value" is a number-type pair ("3Kg", "456g") using [http://en.wikipedia.org/wiki/SI_units SI] or other standard unit-codes and where parsers must accept the formats:<br />
<br />
*[unit-code][number]<br />
*[unit-code][space][number]<br />
*[number][unit-code]<br />
*[number]space[unit-code]<br />
<br />
and where the acceptable codes are to be determined.<br />
<br />
Further comment is invited. A test page is available, at http://www.westmidlandbirdclub.com/test/measure.htm<br />
<br />
===Notes===<br />
*This is extensible, using agreed new codes for unusual or archaic measurements (say "FUR" for "furlong"); such codes could be contained in the microformat's profile.<br />
*Otherwise, it works as-is for sub-divisions of currencies:<br />
<br />
<pre><nowiki><br />
<abbr class="hmeasure" title="635mm"><br />
2' 1"<br />
</abbr><br />
</nowiki></pre><br />
<br />
:(2' 1" is "two feet one inch" in imperial measurement).<br />
<br />
===Issues===<br />
*is hmeasure the appropriate class-name?<br />
*Is [[currency|money]] a separate microformat, or a measurement, with the ISO currency code as the unit-code?<br />
*What standard sources for unit-codes exist? <br />
**[http://www.bipm.org/en/si/ International System of Units]<br />
*This is still susceptible to the [[accessibility-issues#abbr-design-pattern]]<br />
*How should stops (.) and commas (,) be interpreted? [[User:TobyInk|TobyInk]] 04:13, 18 Nov 2007 (PST)<br />
*Do we also need sub-classes?<br />
<br />
<pre><nowiki><br />
<span class="hmeasure"><br />
The <span class="unit-code">kg</span> weight was, in total <span class="value">5</span>.<br />
</span><br />
</nowiki></pre><br />
<br />
*If so, where would this be used? And are "unit-code" and "value" appropriate class-names?<br />
*<p>'''[http://en.wikipedia.org/wiki/Measurement Measurement errors]''' are fundamental in many technical and scientific fields, they must be supported. [[User:LucaPost|LucaPost]]<br />
<br />
<pre><nowiki><br />
<span class="hmeasure"><br />
<a href="/depth" rel="tag" class="data-name">Depth</a>:<br />
( <span class="data-value">2.17</span> +/-<br />
<span class="data-error"> 0.02</span> )<br />
x 10<sup class="exp">3</sup><br />
<abbr class="unit-measure" title="m">meters</abbr>.<br />
</span><br />
</nowiki></pre><br />
</p><br />
:#Here the actual physical quantity is better 'defined' with rel-tag, and the optional data-error is clearly identified with its own span; alternatively parsers might identify the data-error part by looking for the '&plusmn;' html-entity.<br />
:# The standard '''[http://en.wikipedia.org/wiki/Scientific_Notation scientific notation]''' requires the data and the error values to be rounded to the same number of digits; the exponential notation in powers of ten is useful to have a singular format for values of any order of magnitude.<br />
:# data-error and exp are not needed outside scientific contexts, thus they would be optional; the above HTML still represents a semantic structure when they're left out.<br />
<br />
===Suggested amendment 1===<br />
<br />
*Use only:<br />
<br />
<pre><nowiki><br />
<abbr class="hmeasure" title="[value]"><br />
[text]<br />
</abbr><br />
</nowiki></pre><br />
<br />
Where "value" is a number-type pair ("3 kg", "456 g") using [http://en.wikipedia.org/wiki/SI_units SI] or other standard unit-codes where the parser must accept the following formats:<br />
<br />
*Single measurements - [number][space][[http://en.wikipedia.org/wiki/SI_prefix SI-prefix]][[http://www.bipm.org/en/si/si_brochure/chapter5/5-2.html SI-unit]]<br />
*Compound measurements - [number][space][[http://en.wikipedia.org/wiki/SI_prefix SI-prefix]][[http://www.bipm.org/en/si/si_brochure/chapter5/5-2.html SI-unit]][/][[[http://en.wikipedia.org/wiki/SI_prefix SI-prefix]][[http://www.bipm.org/en/si/si_brochure/chapter5/5-2.html SI-unit]]<br />
<br />
====Notes====<br />
*The only values allowed are SI values and prefixes<br />
<br />
<pre><nowiki><br />
<abbr class="hmeasure" title="635 mm"><br />
2' 1"<br />
</abbr><br />
<br />
<abbr class="hmeasure" title="635 km/s"><br />
635 kilometers per second<br />
</abbr><br />
<br />
<abbr class="hmeasure" title="0.5 m^3/s^2"><br />
half a cubic metre per second squared<br />
</abbr><br />
</nowiki></pre><br />
<br />
====Supported SI Prefixes====<br />
<br />
* yotta Y Quadrillion -1 000 000 000 000 000 000 000 000<br />
* zetta Z Trilliard (thousand trillion) - 1 000 000 000 000 000 000 000<br />
* exa- E Quintillion Trillion 1 000 000 000 000 000 000<br />
* peta- P Quadrillion Billiard (thousand billion) 1 000 000 000 000 000<br />
* tera- T Trillion Billion 1 000 000 000 000<br />
* giga- G Billion Milliard (thousand million) 1 000 000 000<br />
* mega- M Million 1 000 000<br />
* kilo- k Thousand 1 000<br />
* hecto- h Hundred 100<br />
* deca- da Ten 10<br />
* deci- d Tenth 0.1<br />
* centi- c Hundredth 0.01<br />
* milli- m Thousandth 0.001<br />
* micro- u Millionth 0.000 001<br />
** There is already a unicode character for the micro, sign: &#xB5; (U+00B5). Better to use it than substituting a "u". [[User:TobyInk|TobyInk]] 03:56, 18 Nov 2007 (PST)<br />
* nano- n Billionth Milliardth 0.000 000 001<br />
* pico- p Trillionth Billionth 0.000 000 000 001<br />
* femto- f Quadrillionth Billiardth 0.000 000 000 000 001<br />
* atto- a Quintillionth Trillionth 0.000 000 000 000 000 001<br />
* zepto- z Sextillionth Trilliardth 0.000 000 000 000 000 000 001<br />
* yocto- y Septillionth Quadrillionth 0.000 000 000 000 000 000 000 001<br />
<br />
====Supported SI Units====<br />
<br />
*meter (m) - length<br />
*gram (g) - mass<br />
*kilogram (kg) - mass<br />
*second (s) - time<br />
*ampere (A) - electric current<br />
*kelvin (K) - thermodynamic temperature<br />
*mole (mol) - amount of substance<br />
*candela (cd) - luminous intensity<br />
<br />
====Supported Derived SI Units====<br />
*hertz (Hz) - frequency<br />
*newton - (N) force, weight<br />
*pascal - (Pa) pressure, stress<br />
*joule (J) - energy, work, heat<br />
*watt (W) - power, radiant flux<br />
*coulomb (C) - electric charge or electric flux<br />
*volt (V) - voltage, electrical potential difference, electromotive force<br />
*farad (F) - electric capacitance<br />
*ohm (ohm) - electric resistance, impedance, reactance<br />
*siemens (S) - electrical conductance<br />
*weber (Wb) - magnetic flux<br />
*tesla (T) - magnetic field<br />
*henry (H) - inductance<br />
*lumen (lm) - luminous flux<br />
*lux (lx) - illuminance<br />
*becquerel (Bq) - radioactivity (decays per unit time)<br />
*sievert (Sv) - equivalent dose (of ionizing radiation)<br />
*katal (kat) - catalytic activity<br />
<br />
====Supported Non-SI Units====<br />
<br />
*minute (min) - time<br />
*hour (h) - time<br />
*day (d) - time<br />
*radian (rad) - angle<br />
*degree of arc (deg) - angle<br />
** Use instead U+00B0 (&#xB0;, degree) [[User:TobyInk|TobyInk]] 04:06, 18 Nov 2007 (PST)<br />
*minute of arc (') - angle<br />
** Use instead U+2032 (&#x2032;, prime) [[User:TobyInk|TobyInk]] 04:06, 18 Nov 2007 (PST)<br />
*second of arc (<nowiki>''</nowiki>) - angle<br />
** Use instead U+2033 (&#x2033;, double-prime) [[User:TobyInk|TobyInk]] 04:06, 18 Nov 2007 (PST)<br />
*steradian (sr) - solid angle<br />
*square degree (deg^2) - solid angle<br />
*litre (L) - volume<br />
*tonne (t) - mass<br />
<br />
====Units Defined by Microformats.org====<br />
<br />
*celcius (cel) - temperature<br />
** Use U+2103 (&#x2103;, degrees celcius) [[User:TobyInk|TobyInk]] 04:07, 18 Nov 2007 (PST)<br />
*bit (bit) - computing<br />
*year (y) - year<br />
*inch (in) - inch<br />
*foot (ft) - foot<br />
<br />
====Supported SI Markup====<br />
<br />
*solidus (/) - divisor<br />
** Division slash (&#x2215;, U+2215) more appropriate [[User:TobyInk|TobyInk]] 04:09, 18 Nov 2007 (PST)<br />
*caret (^) - exponentiation<br />
<br />
==See also==<br />
{{measure-related-pages}}</div>Niuhaibiaohttps://microformats.org/wiki/index.php?title=distributed-conversation-brainstorming&diff=41636distributed-conversation-brainstorming2010-01-14T06:30:29Z<p>Niuhaibiao: /* Problem */</p>
<hr />
<div>=citeRel brainstorming=<br />
Various parties have proposed microformats related to citations and distributed online conversations. Ryan King and Eran Globen started with hVia (which became citeVia and later citeRel :-)). You can see the conversation in these blog posts:<br />
<br />
People already cite their sources in their blog posts and it would be great (and shouldn't be too difficult) to track that information. In that vein, read [http://theryanking.com/blog/archives/2005/05/06/hvia/ this post] which covers the initial thinking on the topic. ([http://theryanking.com/blog/archives/2005/05/09/citevia/ This] was a followup post).<br />
<br />
Later, [http://hellononline.com Eran] [http://hellonline.com/blog/?p=18 expanded the idea] to encompass not just via citations, but replies and updates as well. Follow up post [http://hellonline.com/blog/?p=19 here].<br />
<br />
[[distributed-conversation-examples]]<br />
<br />
== Note for general text citations ==<br />
<br />
This page is all about hyperlink citations, either explicity through the use of an <code>&lt;a href&gt;</code> or a mostly hidden "cite" attribute on the <code>&lt;blockquote&gt;</code> and <code>&lt;q&gt;</code> elements.<br />
<br />
For general text citations, please take a look at:<br />
* [[cite-examples]], [[cite-formats]], [[cite-brainstorming]]<br />
<br />
==Problem==<br />
The basic idea we're trying to solve here is the tracking of distributed conversation- more specifically, distributed conversation between blog posts– the scope is intentionally limited here, though other aspects of distributed conversation are certainly important and related.<br />
<br />
<br />
:A smaller portion of the problem is in identifying the most authoritative sources in a web-wide thread. In researching anything, the ability to identify a primary source is invaluable. Adding this kind of ordinality would add value to any list of related links such as a tag page.<br />
<br />
::Finding an authoritative source is not a smaller problem, but a larger problem- you have to have the whole conversation graph in order to find the root nodes. --RyanKing<br />
<br />
:::The definition of Authority here is murky at best. This is far beyond the scope of this discussion. --[[User:EranGloben|EranGloben]] 13:41, 21 Jan 2006 (PST)<br />
<br />
:Citing (quoting or refering to as an authoritative source or precedent) and hat-tipping (giving credit to a non-primary source for calling attention to a primary [authoritative] source) are certainly two different animals. Common etiquette suggests use of anchor tags because they can be actuated by the user.<br />
<br />
:I dug around at [http://www.w3.org W3C] and found rel="cite" is ''already defined'' in the [http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-metaAttributes.html XHTML Metainformation Attributes Module]. In the [http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-hyperAttributes.html XHTML 2.0 Hypertext Attribute Collection], href and cite attributes are defined and may coexist but they behave differently: The href attribute "specifies a URI that is actuated when the element is activated." For the cite attribute, "User Agents MUST provide a means for the user to actuate the link."<br />
<br />
::This has already been covered in the above blog posts. Admitedly, it needs to be brought into this document, though. --RyanKing<br />
<br />
:Whereas authors in general like their work to be cited with hyperlinks, and whereas users can be counted upon to cite primary and non-primary sources simultaneously without differentiating them, and whereas the only difference between a primary citation and a non-primary citation is the potential for skipped vias when considered across a distributed conversation, and whereas the use of existing specifications is preferred to the creation of redundant systems, and whereas increasing attributes is less severe than increasing nested elements, I propose that good definition and use of rel="cite" will resolve the problem of crediting sources via anchors. <cite>Andy Skelton</cite><br />
<br />
::I see the conclusion as quite the opposite. Because rel="cite" *is* defined in XHTML2 drafts, and microformats allow you add rel values to HTML4/XHTML1 *now*, adopting the same convention makes a lot of sense.<br />
<br />
::If anything it bolsters the case for rel="cite" (as opposed to some other value like rel="source").<br />
<br />
::In a relCite microformat, you would define the "cite" value by normatively referencing XHTML2, rather than redefining it (even copy/pasting the definition from the XHTML2 spec -- though one could do so "informatively"), just like in [[hcard|hCard]], we define the properties by normatively referencing vCard. <cite>Tantek</cite><br />
<br />
:::[http://www.w3.org/TR/2005/WD-xhtml2-20050527/ XHTML 2.0] states that it "should in no way be considered stable, and should not be normatively referenced for any purposes whatsoever." <cite>Andy Skelton</cite><br />
<br />
:::: That is a very good point Andy. Thus we should define rel-cite compatibly, and then give attribution and informatively reference XHTML2. <cite>Tantek</cite><br />
<br />
:There is a related problem which is not exactly the same. Let's say that you have a bit of microformatted data which implies an assertion, and the asserter is the containing page. For example a relTag might have semantic value like "I claim that this object is a FOO." When that assertion is copied over to a new page, the identity of the asserter has to be made explicit: "according to the original containing page at BAR, this object is a FOO." Now let's say somebody copies over the copy. This might happen if there was a B-lister who had an entry picked up by an A-lister, and the A-lister's entry was then copied by a vast number of C-listers. (That's a typical pattern for data diffusion). For the data to keep its integrity, the source of the citation would always have to be the original containing page (the B-lister) rather than the containing page that the copy was fetched from (the A-lister). <cite>Lucas Gonze</cite><br />
<br />
::Lucas- that's why God invented &lt;blockquote&gt;. Content ''copied'' from one site to another should be quoted. --RyanKing<br />
<br />
::The question isn't about whether something was copied but what the cite source is. This is a case where the difference between a primary citation and a non-primary citation affects the meaning of the data. <cite>Lucas Gonze</cite><br />
<br />
::This illustrates the difference between types of citations. C quoting A's text found on B's blog. C would use a reply or forward type citation when referencing A's text and would add a via type citation when mentioning his source, B. --[[User:EranGloben|EranGloben]] 13:41, 21 Jan 2006 (PST)<br />
<br />
:I have a related problem that may shed some [http://www.skldintl.com solar garden light] on this one. I came to this page because I was just looking at a scientific journal citation and thought "that could be a microformat." There are already standard formats for citations of all sorts, including websites (e.g. [http://owl.english.purdue.edu/handouts/research/r_mla.html Modern Language Association]), so maybe converting these into microformats would solve the problem stated here, and more. -- Scott Reynen<br />
<br />
== Nested cite/anchor tags ==<br />
<br />
== rel="cite" / rev="cite" ==<br />
<br />
This could be a way to indicate a citation of linked content, typically web pages (or portions thereof, like blog posts) but inclusive of any kind of resource with a URL. "Cite" is defined as "to quote or refer to as a precedent or authority."<br />
<br />
By adding <code>rel="cite"</code> to a hyperlink, an author could indicate that the destination of that hyperlink is an authoritative source or a precedent to the current page. rel="cite" would be used whether an author cites by quotation:<br />
<pre><blockquote>Our liberty depends on the freedom of the<br />
press, and that cannot be limited without being lost.<br />
<a href="http://en.wikiquote.org/wiki/Thomas_Jefferson" rel="cite"><br />
Thomas Jefferson</a></blockquote></pre><br />
or by reference only:<br />
<pre><a href="http://example.com/joeschmoe/article/99/" rel="cite"><br />
Joe Schmoe's latest rant</a> is wrong, wrong, wrong...</pre><br />
<br />
<code>rel="cite"</code> hyperlinks are intended to be visible links on pages and posts. Note that other markup may be used to indicate citation:<br />
<pre><blockquote cite="http://en.wikiquote.org/wiki/Thomas_Jefferson"><br />
Our liberty depends on the freedom of the press, and that cannot be<br />
limited without being lost.<cite>Thomas Jefferson</cite></blockquote></pre><br />
but User Agents are not compelled to expose a link to the cited resource. Hyperlinks are preferred by most authors because they afford the user easy access to the cited resource.<br />
<br />
== citeRel vs. relCite ==<br />
For basic structure and markup of citations it has been suggested that we use the following:<br />
<pre><br />
<!-- relCite example --><br />
<a rel="cite" href="source.url">source.title</a><br />
</pre><br />
instead of <br />
<pre><br />
<!-- citeRel example --><br />
<cite><a href="source.url">source.title</a></cite><br />
</pre><br />
<br />
There are several reasons to prefer the citeRel form over the relCite form of markup:<br />
# citeRel uses only existing XHTML elements and values where relCite uses a new rel value.<br />
# citeRel is easily extensible without breaking it's existing meaning.<br />
<br />
==When is a bare href (not) a citation==<br />
A href is a citation when:<br />
* A blog entry refers to another entry or to a presentation, then talks about that entry or presentation. eg "I believe it was more or less the same &lt;a href="...">presentation&lt;/a> he gave at SxSW this year" [http://theryanking.com/blog/archives/2005/05/06/hvia/ Ryan King].<br />
<br />
A href is not a citation when:<br />
* A blog entry refers to the author of an entry or presentation using the author's homepage url, then talks about the entry or presentation. eg "For my Internet Systems Research class last night, we had &lt;a href="...">Tantek Çelik&lt;/a> come speak on microformats" [http://theryanking.com/blog/archives/2005/05/06/hvia/ Ryan King]<br />
* A blog provides a blog-roll, or "recent bookmarks" panel<br />
<br />
== Moving Forward ==<br />
Based on the examples found in my research, previous formats and discussions with several people I see the following possibilities for this format. <br />
<br />
'''Option 1'''<br />
&lt;cite class=”foo”>&lt;a href=”source url”>source title&lt;/a>&lt;/cite><br />
&lt;blockquote><br />
Quoted text<br />
&lt;/blockquote><br />
<br />
'''Option 2a'''<br />
&lt;blockquote cite=”sourceurl” class=”foo”><br />
Quoted text<br />
&lt;/blockquote><br />
<br />
'''Option 2b'''<br />
&lt;a href=”source url”>source title&lt;/a><br />
&lt;blockquote cite=”sourceurl” class=”foo”><br />
Qouted text<br />
&lt;/blockquote><br />
<br />
'''Option 3'''<br />
&lt;a href=”source url” rev=”cite/via”>source title&lt;/a><br />
&lt;blockquote><br />
Quoted text<br />
&lt;/blockquote><br />
<br />
'''Notes'''<br />
# In the preceding examples you may substitute &lt;Q> for &lt;BLOCKQUOTE><br />
# Options 1 and 2 are not necessarily mutually-exclusive. <br />
# In both 1 and 2 replace foo with the appropriate class name (e.g. via, rev-reply, rel-update, etc.)<br />
<br />
'''Discussion'''<br />
<br />
Option 1 is based on Tantek’s suggestion in [http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML] and was reached at independently by Ryan King (see [[distributed-conversation-examples| examples page]]). It seems to imply that the current document is citing the entirty of the linked document.<br />
<br />
Option 2a is based on existing and emerging HTML standards and some existing patterns of use. To make the relationship explicit, the class attribute is used but this can be replaced by a rel/rev attribute as soon as one is introduced in quote elements. This option is currently problematic as no user agent I am aware of properly exposes the value of the cite attribute to the user.<br />
<br />
Option 2b tries to solve that problem by adding a link to the cited document. This solution has the obvious disadvantage of repeating data but will evolve naturally into option 2a as soon as user agents improve their handling of cite attributes.<br />
<br />
Option 3 is based on the cite rel value introduced in several standards and the via rel value introduced in atom. It builds on what seems to be the most popular format in use. Caveats:<br />
* Given the existence of the CITE element it seems that the cite rel value is redundant although it appears that it will become a part of upcoming standards. <br />
* Another problem with this format is that the cite and via values are not specific enough. Using this format in a more precise manner will require using non-standard rel values.<br />
<br />
'''Current Resolution'''<br />
<br />
After discussion the above options were converged into the following syntax:<br />
<br />
&lt;cite id="$cite.id$" class="$relationship$">&lt;a href="$source.url$">source title&lt;/a>&lt;/cite><br />
&lt;blockquote cite="#$cite.id$"><br />
Quoted text<br />
&lt;/blockquote><br />
<br />
The use of the cite attribute connectes the blockquote (or quote) element with the appropriate cite. Use of this feature is optional.<br />
<br />
==Additional Resources==<br />
* Thread Description Language - TDL is an RDF vocabulary for describing threaded discussions, such as Usenet, weblogs, bulletin boards, and e-mail conversations.<br />
** http://www.eyrie.org/~zednenem/2002/web-threads/<br />
** http://www.eyrie.org/~zednenem/2002/wtprofile/<br />
* Usenet discussions used the references field which includes ALL referenced posts with the one replied to last in a space separated list.<br />
** http://www.w3.org/Protocols/rfc1036/rfc1036.html See section 2.2.5<br />
* [http://www.faqs.org/rfcs/rfc2076.html RFC2076 - Common Internet Message Headers] section 3.6 has the following:<br />
** In-Reply-To - Reference to message which this message is a reply to.<br />
** References - In e-mail: reference to other related messages, in Usenet News reference to replied-to-articles.<br />
** See-Also - References to other related articles in Usenet News.<br />
** Obsoletes - Reference to previous message being corrected and replaced.<br />
** Supersedes - Commonly used in Usenet News in similar ways to the "Obsoletes" header described above. In Usenet News, however, Supersedes causes a full deletion of the replaced article in the server, while "Supersedes" and "Obsoletes" in e-mail is implemented in the client and often does not remove the old version of the text.<br />
** Article-Updates - Only in Usenet News, similar to "Supersedes:" but does not cause the referenced article to be physically deleted.<br />
** Article-Names - Reference to specially important articles for a particular Usenet Newsgroup.<br />
* Try Googling around "IBIS" (Issue-Based Information Systems), it's an approach to collaborative problem solving that looks very like discussion threads, see also [http://collab.blueoxen.net/cgi-bin/wiki.pl?HomePage BlueOxen Wiki], [http://collab.blueoxen.net/cgi-bin/wiki.pl?MailingLists BlueOxen Mailing Lists]</div>Niuhaibiaohttps://microformats.org/wiki/index.php?title=hlisting-examples&diff=41635hlisting-examples2010-01-14T06:28:39Z<p>Niuhaibiao: /* Live Product Examples */</p>
<hr />
<div><h1>Listing Examples </h1><br />
{{TOC-right}}<br />
<br />
This page is '''informative'''.<br />
<br />
The purpose of the content on this page is to serve as background for the improvement of the transactional/listing (hListing) microformat. There are examples in the wild, and this page can serve as a supplement for those examples and for experimentation and implementation.<br />
<br />
== Editors/Authors ==<br />
(alphabetical)<br />
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]<br />
<br />
== New Examples ==<br />
If you have implemented hListing on your own page, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hlisting|hListing]] markup. <br />
<br />
=== Live Product Examples ===<br />
<br />
* [http://ottawa.en.craigslist.ca/sys/1135033483.html craiglist]<br />
** Properties: item info, condition, description, price, lister, list date, availability, shipping<br />
<br />
* [http://www.skldintl.com solar garden light]<br />
**Properties: item info, condition, description, price, list date, shipping<br />
<br />
* [http://www.cowboom.com/index.cfm cow boom]<br />
** Properties: item info, condition, price, what's included, shipping<br />
<br />
* [http://auctions.overstock.com/Sony-HF-10-Pack-60-Minute-HiFi-Audio-Cassette-Tape/Computers-Networking/item/44773540 Overstock auctions]<br />
** Properties: item info, list date, expiriry date, shipping, condition, description<br />
<br />
* [http://cgi.ebay.com/4-OCTAVE-WOODEN-MARIMBA-DIRECT-FROM-ARTIST_W0QQitemZ25035963638*6QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item250359636386&_trksid=p3286.c0.m14&_trkparms=72%3A1205|66%3A2|65%3A12|39%3A1|240%3A1318|301%3A1|293%3A1|294%3A50 ebay]<br />
** Properties: price, shipping, payment options, item info, quantity, condition, origin, product type, description, return policy, payment details<br />
<br />
* [http://www.ubid.com/DAVIDOFF+COOL+WATER+for+men+New+in+box+Popular+5+ML+.17+FL.+OZ./a802600100-c0-s9.html ubid]<br />
** Properties: photo, quantity, item info, condition, quantity, shipping<br />
<br />
* [http://www.bidz.com/bzJApp/ProductDisplay.action?sid=100&tid=100&auctionId=34170660 bidz.com]<br />
** Properties: price, item info, availability, condition, country of origin, description, shipping<br />
<br />
* [http://www.dellauction.com/cgi-bin/ncommerce3/ProductDisplay?prrfnbr=104283039&prmenbr=75267554&aunbr=104629749 dell auctions]<br />
** item info, price, list date, expiriry date, shipping, condition<br />
<br />
* [http://astore.amazon.com/httpwwwsusaco-20/detail/B001KW0A3E amazon marketplace]<br />
** Properties: availability, name, manufacturer, price, shipping, shopping cart link<br />
<br />
* [http://shopping.msn.com/prices/best-of-esteban/itemid598175900/?itemtext=itemname:best-of-esteban&stext=esteban msn shopping]<br />
** Properties: title, artist, photo, description, condition, price, buy, shipping, seller<br />
<br />
* [http://www.shopping.com/xPO-Keurig-Keurig-Special-Edition-B60-Brewer-Coffee-Machine shopping.com]<br />
** Properties: photo, title, rating (aggregate), details, manufacturer, description, seller, shipping, price, condition, availability<br />
<br />
* [http://www4.dealtime.com/xPO-DRY_PAK_Dry_Pak_Roll_Top_Dry_Gear_Bags dealtime.com]<br />
** Properties: photo, price range, link, seller, specs, title, shipping, description, availability<br />
<br />
* [http://www.pronto.com/GUESS-Kids-Girls-Shoes-Tyler-p_1164738515-PP pronto.com]<br />
** Properties: photo, price, availability, rating, shipping, link, <br />
<br />
* [http://musical-instruments.pricegrabber.com/dj-turntables/Pioneer-CDJ-1000MK3-Digital-Vinyl-Turntable/m18215594.html/st=product/sv=title pricegrabber.com]<br />
** Properties: photo, price, rating, description, shipping, tax, seller, condition, availability<br />
<br />
* [http://shopper.cnet.com/smartphones/rim-blackberry-curve-8900/4014-6452_9-33485567.html?tag=contentMain;contentBody shopper.com]<br />
** Properties: title, price range, ratings, description, seller(s), seller rating, dtstart, shipping, availability<br />
<br />
* [http://www.mysimon.com/9015-11034_8-30883813.html my simon]<br />
** Properties: price range, seller, store rating, availability, price, link, shipping<br />
<br />
* [http://www.compuplus.com/i-BellO-AVSC-2123-Contemporary-Tall-Design-Audio-Video-System-BlackCherry-AVSC2123-1034723~.html?sid=5b5f55n09w5lssu compu plus]<br />
** Properties: condition, availability, shipping, price, description<br />
<br />
* [http://www.smarter.com/tv-stands/bello-avsc-2123-42-in-glass-tv-stand-brown/pd--ch-3--pi-361211.html smarter.com]<br />
** Properties: seller, price, reviews, availability, condition<br />
<br />
* [http://www.nextag.com/The-Tin-Drum-934321/prices-html nextag.com]<br />
** Properties: format, seller(s), seller reviews, condition, availability, price, link, name/title, shipping<br />
<br />
* [http://www.epier.com/BiddingForm.asp?1921228 epier.com]<br />
** Properties: bid, reserve, num bids, dtstart, dtend, quantity, shipping, condition, fulfillment details, seller, title<br />
<br />
* [http://us.nine.ebid.net/perl/auction.cgi?auction=16097877&mo=auction ebid.net]<br />
** Properties: photo, seller, price, title, quantity, condition, views, location, dtstart, dtend, shipping, payment methods<br />
<br />
* [http://www.etsy.com/view_listing.php?listing_id=19974630&ref=fp_feat_2 etsy.com]<br />
** Properties: title, photo, description, shipping, payment methods, price, quantity<br />
<br />
* [http://dealspl.us/product/sony-bravia-kdl-46s4100-46-inch-1080p-lcd-tv dealsplus]<br />
** Properties: price, shipping, dtend, description, seller(s), title, availability<br />
<br />
* [http://www.petco.com/product/14363/Totally-Ferret-Premium-Food-for-Active-Show-and-Pet-Ferrets.aspx petco.com]<br />
** Properties: price, seller, reviews, shipping, dtends, availability, description <br />
<br />
* [http://www.allposters.com/gallery.asp?startat=/getposter.asp&APNum=290796&CID=AC3917B0E4E4452CBC36B60F9B66A923&PPID=1&search=matisse&f=c&FindID=26501&P=1&PP=13&sortby=PD&cname=Henri+Matisse&SearchID allposters.com]<br />
** Properties: price, shipping, related, availability, description<br />
<br />
* [http://www.target.com/Britax-Decathlon-Sahara-Convertible-Seat/dp/B000JIWU4W/sr=1-1/qid=1230579365/ref=sr_1_1/179-9254632-8007737?ie=UTF8&rh=k%3Atoddler%20car%20seats%20britax&page=1 target.com]<br />
** Properties: price, quantity, reviews, shipping, availability, shipping info, description<br />
<br />
* [http://www.fastforklifts.com/electric-forklift-trucks-electric-forklift-walkie-forklift-xp1229-12.html fastforklifts.com]<br />
** Properties: description, quantity, price, shipping, availability<br />
<br />
* [http://www.leotardworld.com/Wiggles-Sparkle-Butterfly-Back-Leotard-p/mw1425-356h.htm leotardworld.com]<br />
** Properties: price, description, availability, shipping, quantity<br />
<br />
* [http://www.amazon.com/Nikon-Coolpix-Digital-Camera-Optical/dp/B0011MVWZ8/ref=pd_bbs_sr_1?ie=UTF8&s=electronics&qid=1231272206&sr=8-1 amazon.com]<br />
** Properties: price, availability, shipping, description, ratings, quantity, condition<br />
<br />
* [http://www1.macys.com/catalog/product/index.ognc?ID=290741&CategoryID=42212 macys.com]<br />
** Properties: description, rating, shipping, returns, availability, price<br />
<br />
* [http://www.lowes.com/lowes/lkn?action=productDetail&productId=132135-444-C14024A&lpage=none lowes.com]<br />
** Properties: price, availability, shipping<br />
<br />
* [http://www.homedepot.com/webapp/wcs/stores/servlet/ProductDisplay?storeId=10051&langId=-1&catalogId=10053&productId=100189145 homedepot.com]<br />
** Properties: price, shipping, quantity, availability, ratings<br />
<br />
* [http://www.acehardware.com/product/index.jsp?productId=1290429&cp=&sr=1&kw=lathes&origkw=lathes&parentPage=search&searchId=34784674863 acehardware.com]<br />
** Properties: related, price, size, quantity, shipping, availability<br />
<br />
* [http://www.walgreens.com/store/product.jsp?CATID=100218&navAction=jump&navCount=0&nug=VPD&skuid=sku359744&id=prod359743 walgreens.com]<br />
** Properties: price, quantity, shipping, availability<br />
<br />
* [http://www.appliancewarehousedirect.com/counterdepth-sidebyside-refrigerator-with-glass-shelves-humidity-controls-transition-lighting-external-button-icewater-dispenser-p-18476.html?cPath=3 appliancewarehousedirect.com]<br />
** Properties: price, shipping, warranty, condition, packaging, description<br />
<br />
* [http://www.birdbaths.com/bird-baths/resin-bird-baths/portsmouthsolarbirdbathfountain.cfm birdbaths.com]<br />
** Properties: price, savings, rating, shipping, quantity, availability, description<br />
<br />
* [http://www.circuitcity.com/applications/SearchTools/item-details.asp?EdpNo=3574573&CatId=1902 circuitcity.com]<br />
** Properties: condition, price, availability, quantity, shipping, description<br />
<br />
* [http://www.magersandquinn.com/index.php?main_page=product_info&products_id=1905787&isbn_id=4027890 magersandquinn.com]<br />
** Properties: price, condition, availability, description, <br />
<br />
* [http://www.bestbuy.com/site/olspage.jsp?skuId=9015638&type=product&id=1852883 bestbuy.com]<br />
** Properties: shipping, price, description, availability<br />
<br />
* [http://www.cduniverse.com/productinfo.asp?pid=1109198&cart=827546365 cduniverse.com]<br />
** Properties: price, availability, shipping, description, format<br />
<br />
* [http://www.autozone.com/autozone/catalog/accessories/accProductDetails.jsp?displayName=AirFreshener&itemId=prod63065&navValue=100507&parentId=cat30093&productId=574949&fromString=&itemIdentifier=574949_0_0_&filterByKeyWord=&categoryNValue=&subSubPartId=&subPartId=prod63065&store=3076&skuDisplayName=2pk.StrawberryExtraStrengthHangingAirFreshener&categoryDisplayName=CarCare&_requestid=742334 autozone.com]<br />
** Properties: availability, shipping, quantity<br />
<br />
* [http://www.napaonline.com/MasterPages/NOLMaster.aspx?PageId=470&LineCode=BSH&PartNumber=N69487&Description=Fuel+Pump+-+Electric+In-Tank+Type+-+OEM+Equivalent napaonline.com]<br />
** Properties: description, availability, price, shipping, condition<br />
<br />
* [http://www.toysrus.com/product/index.jsp?productId=2332387 toysrus.com]<br />
** Properties: description, price, availability, shipping<br />
<br />
* [http://www.usedsports.com/category/289/Drivers/listings/437/New-Extreme-Distance-Driver.html usedsports.com]<br />
** Properties: condition, price, quantity, location, shipping, dtends, description, terms<br />
<br />
* [http://www.biblio.com/details.php?dcx=166670305&aid=frg biblio.org]<br />
** Properties: price, seller, date published, condition, shipping<br />
<br />
* [http://kidzugoodbuy.ecrater.com/product.php?pid=3888669 kugby]<br />
** Properties: price, shipping, availability, condition, payment options, description<br />
<br />
* [http://microcenter.com/single_product_results.phtml?product_id=0310220 microcenter.com]<br />
** Properties: condition, price, availability, quantity<br />
<br />
* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 amazon outlet]<br />
** Properties: price, condition, availability, shipping, quantity<br />
<br />
* [http://www.amazon.com/Factory-Reconditioned-Bostitch-RN46-1-4-Inch-Roofing/dp/B000F10HWU/ref=sr_1_2?ie=UTF8&s=hi&qid=1243453632&sr=1-2 louisiana machinery]<br />
** Properties: price, condition, rating, shipping<br />
<br />
* [http://product.half.ebay.com/Too-Fat-to-Fish_W0QQtgZinfoQQprZ69582903 half.com]<br />
** Properties: description, condition, price, format, shipping<br />
<br />
* [http://www.tradeups.com/ tradeups.com]<br />
** Properties: price, condition, quantity, shipping<br />
<br />
* [http://www.itxchange.com i.t. xchange]<br />
** Properties: description, condition, quantity, price, availability, shipping<br />
<br />
* [http://discountechnology.com/Dell-E176FP-17-LCD-Flat-Panel-Analog-Monitor?sc=2&category=265 discount technology]<br />
** Properties: description, condition, quantity, shipping, availability<br />
<br />
* [http://www.microreplay.com/index.php?main_page=index&cPath=16_27 micro replay]<br />
** Properties: condition, description, warranty, availability<br />
<br />
* [http://www.clive.nl/audio-tv/p60-active-filter-unit-project-z60 clive.nl retro computer collections]<br />
** Properties: title, price, condition, availability, shipping<br />
<br />
* [http://shopping.lycos.com/product/view/m/88973303 lycos shopping]<br />
** Properties: seller, condition, price, availability<br />
<br />
* [http://www.abt.com/product/37181/Apple-MB528LLA.html?utm_source=scpgrabber&utm_medium=sc&utm_campaign=pricegrabber&mr:referralID=67af328a-546b-11de-8327-000423bb4e79 abt.com]<br />
** Properties: availability, description, shipping, price<br />
<br />
* [http://store.apple.com/us/product/FB528LL/A?afid=p210|pgbr apple store]<br />
** Properties: title, description, price, shipping, availability, condition<br />
<br />
* [http://lycos.pgpartner.com/user_sales_getprod.php?masterid=88973303&lot_id=9449215 the source storefront]<br />
** Properties: price, availability, payment options, shipping, condition, buy<br />
<br />
* [http://www.buy.com/prod/schwinn-windwood-26-men-s-cruiser-bicycle/q/loc/17250/206649684.html?dcaid=15890 buy.com]<br />
** Properties: price, shipping, availability, quantity, <br />
<br />
* [http://www.prosportsmemorabilia.com/Carolina-Hurricanes---Rod-BrindAmour---2006-Stanley-Cup-Jr-Ticket-Frame-_860780691_PD.html?pgrabber=35-84999 pro sports memorabilia]<br />
** Properties: price, quantity, availability, shipping<br />
<br />
* [http://www.techexcess.net/011656-001-proliant-dl380-motherboard-system-board-w-cmos-batt-289554-001.aspx Tech Excess]<br />
** Properties: price, description, condition, quantity, <br />
<br />
* [http://www.kitchengourmet.com.au/ kitchen gourmet]<br />
** Properties: title, condition, price, quantity, shipping, description<br />
<br />
* [http://stores.channeladvisor.com/thephotospot/Items/ko_1434273_NW_4X?&caSKU=ko_1434273_NW_4X&caTitle=Kodak%20Greeting%20Cards%20%26%20Invitations%20Printing%20Kit%20NEW%204%20PACK the photo spot/channel advisor]<br />
** Properties: title, price, quantity, condition, shipping<br />
<br />
* [http://www.pixmania.co.uk/uk/uk/757607/hoover/all_merchant/tc1206001-steam-cleaner.html?state=USE pixmania.co.uk]<br />
** Properties: seller, price, condition, shipping, availability<br />
<br />
* [http://www.samedaymusic.com/product--ALEDM5PROKIT same day music]<br />
** Properties: condition, availability, shipping, price, description<br />
<br />
* [http://www.onlinesurplus.com/products/prod_details.asp?Tg=1308&Sc=0 online surplus]<br />
** Properties: condition, shipping, quantity, availability, price, description<br />
<br />
* [http://www.secondspin.com/music/product-detail.jsp?id=2706699 second spin]<br />
** Properties: availability, quantity, price, condition (implied)<br />
<br />
* [http://www.wherehouse.com/music/product-detail.jsp?id=2691046 wherehouse.com]<br />
** Properties: availability, price, condition, description<br />
<br />
* [http://www.gamestop.com/Catalog/ProductDetails.aspx?Product_ID=71813 gamestop]<br />
** Properties: shipping, price, condition, availability<br />
<br />
* [http://www.bigwords.com/details/book/The_5000_Year_Leap_A_Miracle_That_Changed_the_World/9780880801485/0880801484 big words]<br />
** Properties: condition, seller, description, price, shipping, availability<br />
<br />
* [http://www.alibris.com/musicsearch?qwork=400860855&cm_sp=rec-_-mnhome-_-youMightLike&matches=0 alibris]<br />
** Properties: title, condition, format, shipping, availability, price<br />
<br />
* [http://www.mastermagnets.com/content/view/22/122/lang,en/ master magnets]<br />
** Properties: title, availability, quantity, description, condition<br />
<br />
* [http://yhst-31241655524746.stores.yahoo.net/quicklok-t20-single-x-keyboard-stand--us20.html soundtree audio and music technology solutions]<br />
** Properties: price, description, condition, availability<br />
<br />
* [http://ezcafe.com/index.php?main_page=product_info&cPath=4&products_id=7&zenid=1d586a3c214b9f0f354d508ebc178e2e ezcafe]<br />
** Properties: title, price, description, condition, availability, dtstart<br />
<br />
* [http://www.holtcat.com/app_used.asp holt cat]<br />
** Properties: manufacturer, price, availability, condition<br />
<br />
* [http://www.amhboston.com/index.cfm?event=ProductDetails&CategoryID=48&ProductID=159 american material handling group]<br />
** Properties: condition, size, price, quantity, shipping/delivery, availability <br />
<br />
* [http://store.academyofscuba.com/suvydswrcowu.html academy of scuba]<br />
** Properties: price, condition, availability, description, <br />
<br />
* [http://www.horseclicks.com/products/lp0mry/ horse clicks]<br />
** Properties: availability, condition, price<br />
<br />
* [http://www.siliconsolar.com/used-genlight-fixture-p-17995.html silicon solar]<br />
** Properties: condition, price, quantity, availability<br />
<br />
* [http://www.joessports.com/product/index.jsp?productId=3071464&CAWELAID=155516067 joe's sports]<br />
** Properties: price, description, quantity, availability, shipping<br />
<br />
* [http://www.amazon.com/gp/product/B000O7I6VE amazon.com]<br />
** Properties: title, price, condition, availability, shipping<br />
<br />
* [http://www1.tradetang.com/for-sale/Free_shipping_10pics_Brand_New_2_8_Touch_Screen_8GB_MP3_MP4_Player_2_0M_Video_Camera/110562-1239396.html tradetang.com]<br />
** Properties: price, title, condition, shipping, availability<br />
<br />
* [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=4355391&CatId=2628 tiger direct]<br />
** Properties: price, quantity, condition, availability, shipping<br />
<br />
* [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=8198552921665401960 sony/ sonystyle]<br />
** Properties: condition, price, rating, description, availability, shipping<br />
<br />
* [http://www.shopping.hp.com/webapp/shopping/product_detail.do?product_code=CC436AR%23ABA&aoid=14655&srccode=cii_10043468&cpncode=22-18868711-2 hewlett packard]<br />
** Properties: price, condition, availability, shipping, quantity<br />
<br />
* [http://estore.usa.canon.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10051&storeId=10051&productId=156469&langId=-1&parent_category_rn=12056&top_category=12252 canon estore]<br />
** Properties: condition, price, availability<br />
<br />
=== Analysis of hListing Research ===<br />
<br />
To date, analysis on 87 commerce or product listing sites was performed to represent a wide array of offers. The new hListing proposal adds three elements -- availability, condition, and shipping. The findings up to this point indicate many commerce and product related sites utilizing the proposed hlisting attributes of availability, condition and shipping. The research produced these results for the proposed new attributes:<br />
<br />
* Availability (79.1%)<br />
* Condition (71.2%)<br />
* Shipping (82%)</div>Niuhaibiaohttps://microformats.org/wiki/index.php?title=geo-extension-nonWGS84-fr&diff=41634geo-extension-nonWGS84-fr2010-01-14T06:25:30Z<p>Niuhaibiao: /* Brent A. Archinal */</p>
<hr />
<div>=Geo Extension Straw-Man Proposition=<br />
<br />
Further to proposals for [[luna-fr]] and [[mars-fr]] equivalents to [[geo-fr]], the following is a "straw-man" proposal, to incorporate those ideas (and likewise for other bodies) into geo, and to make Geo available for other terrestrial schema than WGS84, in order that further debate may take place. Please feel free to critique it harshly but fairly!<br />
<br />
==Auteur==<br />
[[User:AndyMabbett|Andy Mabbett]]<br />
<br />
==Straw-Man==<br />
<br />
<pre><nowiki><br />
<span class="geo"><br />
<br />
<span class="body"><br />
Mars [1]<br />
</span><br />
<br />
<span class="reference frame"><br />
[name of mapping schema] [2]<br />
</span><br />
<br />
<span class="latitude">37.386013</span>, <br />
<span class="longitude">-122.082932</span> [3]<br />
</span><br />
</nowiki></pre><br />
<br />
===Notes===<br />
# A list of acceptable, case-insensitive, values for 'body' would need to be drawn up (e.g. "Earth", "Mars", "Moon", "Venus", etc.) wither "Earth" being assumed if none is specified.<br />
# A list of acceptable values for 'reference frame' would need to be drawn up, for each body, with one being declared the default, to be used if no value is present (geo for Earth uses the datum of [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84] by default. This extension would also allow for other terrestrial schema, of which there are many, such as OSGB36).<br />
# As currently with geo, if the "latitude" and "longitude" classes are omitted, the two values MUST be separated by a semi-colon and latitude MUST be first:<code><nowiki><span class=geo">37.386013;-122.082932</span></nowiki></code><br />
:Also:<br />
:*If latitude is present, so MUST be longitude, and vice versa.<br />
:*The same number of decimal places SHOULD be used in each value; zeros are significant<br />
:*The [http://planetarynames.wr.usgs.gov/ Gazetteer of Planetary Nomenclature] has coordinates for other planets, e.g. [http://planetarynames.wr.usgs.gov/jsp/FeatureTypesData2.jsp?systemID=2&bodyID=17&typeID=10&system=Venus&body=Venus&type=Dorsum,%20dorsa&sort=AName&show=Fname&show=Lat&show=Long&show=Diam&show=Stat&show=Orig Venus] and moons, e.g. [http://planetarynames.wr.usgs.gov/jsp/FeatureTypesData2.jsp?systemID=5&bodyID=7&typeID=15&system=Jupiter&body=Io&type=Fluctus,%20fluct%C5%ABs&sort=AName&show=Fname&show=Lat&show=Long&show=Diam&show=Stat&show=Orig Io].<br />
<br />
==problématiques==<br />
*Should other bodies be included in ''geo'', or have stand-alone microformats?<br />
*What effect will this have on existing 'geo' parsers, and it is safe to ignore that?<br />
*What appropriate "reference frame" sets exist?<br />
**Earth: [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84], [http://itrf.ensg.ign.fr/ITRF_solutions/2005/ ITRF2005], [http://www.ordnancesurvey.co.uk/oswebsite/gps/information/gpsbackground/glossary.html EtrS89]<br />
**Moon: Mean Earth Polar Axis<br />
**Mars: IAU2000<br />
***'Report of the IAU/IAG Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites: 2000', Celestial Mechanics and Dynamical Astronomy 82: 83-110, 2002 [http://astrogeology.usgs.gov/Projects/ISPRS/PREPRINTS/index_preprints.html]<br />
*Moon is the preferred name, per [ http://planetarynames.wr.usgs.gov/ IAU nomenclature working group]<br />
*Is it appropriate to use the name "geo" (which means "Earth") for other bodies?<br />
*is ''body '' an acceptable class name, given that it's also an HTML element?<br />
<br />
===longitude centrée sur la planète===<br />
<br />
Geographical longitude on, for example, Mars is not 180 degrees west to 180 degrees east: 18N,226E is a legal Martian location.<br />
<br />
This is from [http://en.wikipedia.org/wiki/Timekeeping%20on%20Mars Timekeeping on Mars] ([http://www.esa.int/SPECIALS/Mars_Express/SEM0VQV4QWD_0.html])<br />
<br />
<blockquote><br />
Note that the modern standard for measuring longitude on Mars s "planetocentric longitude", which is measured from 0°–360° East and measures angles from the center of Mars. The older "planetographic longitude" was measured from 0°–360° West and used coordinates mapped onto the surface.<br />
</blockquote><br />
<br />
You can also check the description in JPL Horizons document, which uses planetographic longitude rather than planetocentric longitude, and gives much more longitude ranges used for different planets and moons, at http://ssd.jpl.nasa.gov/horizons_doc.html#sitecoord<br />
<br />
==Commentaires==<br />
===thare===<br />
Commentaires de [[User:PlanetGeo|thare]]<br />
*geo does stand for Earth but it has previously been generalized for the planetary case. For example, the term geology is used for planetary bodies.<br />
*using ''body'' is fine by me and do not see a conflict as an HTML element. <br />
*by schema do you mean a natural surficial property like earthquake, volcano, or crater? Or do you also want to include man-made items building, house, landing site?<br />
**No, I mean, for example, WGS84, or the Martian or lunar equivalents. Is "schema" perhaps the wrong word?. [[User:AndyMabbett|Andy Mabbett]]<br />
*** Perhaps "reference frame" would be a less confusing term than "schema"? --[[User:DavidCary|DavidCary]] 17:06, 5 Apr 2007 (PDT)<br />
**** The HTML class attribute is a space seperated list, so 'class="reference frame"' is semantically equivalent to 'class="frame reference"' or 'class="reference" class="frame"' (though the latter is not syntactically valid). This could clash with, say, a theoretical microformat for footnotes, endnotes and references. Hyphenating ('class="reference-frame"') may be an improvement. [[User:TobyInk|TobyInk]] 12:29, 6 Jun 2007 (PDT)<br />
*I would suggest just using "''Moon''". For other spellings for planetary bodies I would look toward the IAU/IAG documentation (an international working group) [http://astrogeology.usgs.gov/Projects/WGCCRE/ IAU/IAG Working Group (WG) on Cartographic Coordinates and Rotational Elements]<br />
*Since this is a simple case, I tried to stay away from this issue but just can't. What does Earth really mean? There a many definitions for the size of Earth that need to be resolved when using lat/lon coordinates. Is the size of the Earth defined by the WGS84 or NAD27 definition? For Mars, is it the definition used in 1991 or redefined in 2000? This has previously been solved in web GIS applications by using an "EPSG" code. For planetary bodies we are attempting to define a similar coded standard which currently is called the IAU2000 code or namespace. Thus for Mars the code might be IAU2000:49900.<br />
**Hence 'schema'. [[User:AndyMabbett|Andy Mabbett]]<br />
*still working - more later<br />
**Thank you. [[User:AndyMabbett|Andy Mabbett]]<br />
<br />
===Brent A. Archinal=== <br />
<br />
(e-mail reproduit par [[User:AndyMabbett|Andy Mabbett]], avec l'aimable permission)<br />
<br />
*I appreciate the information you've provided and certainly the general idea of using "microformats" to indicate geographical location of points on [http://www.skldintl.com solar garden light]system bodies is interesting.<br />
*As to any comments on the general idea or any specific implementation, I think my colleague, Trent Hare, has already addressed any primary concerns or questions (above).<br />
*The main issue seems to be that both the body, and the specific definition (technically a "reference frame") in question need to be specified, e.g. 1) Earth, ITRF2005, 2) Moon, ULCN 2005, 3) Mars, "IAU2000" or similar. Note that these frames are actually realizations of various "reference systems" 1) ITRS, 2) mean Earth/polar axis system, 3) IAU2000 Mars body fixed, respectively), but the system is apparent once the frame has been identified.<br />
*A secondary issue is that obviously a third coordinate may need to be specified, i.e. some sort of "radius" (from the body center of mass) or "elevation" about a reference surface. If the latter, then that reference surface needs to be specified as well (e.g. Mars, "IAU2000", "IAU2000 sphere").<br />
*If the microformat(s) were expandable to handle these cases when necessary (and others we haven't yet thought of) then obviously they could have a lot of utility.<br />
*There are plenty of GIS and standards organization formats out there for handling this type of data, even for the solar system case. I'm not at all an expert on what's available, but obviously for something like the microformats to be generally used, their advantages over these existing formats would have to be made clear. <br />
*As to usage here, we'll let others know of the existence of these formats, but I can't say how much immediate interest there might be in using them. We already (and Trent could say more) use a wide range of GIS and even flat file formats to carry e.g. lists of point-like data. <br />
*Regarding one other point on the web pages, I believe the "Moon" (capitalized) is the primary recognized name for the Moon. There is an [IAU nomenclature working group http://planetarynames.wr.usgs.gov/] that handles not only the names of features on planetary bodies, but of the bodies themselves, and I believe this is their position on this (since confirmed - [[User:AndyMabbett|Andy Mabbett]]).<br />
<br />
::Brent A. Archinal, Geodesist, Astrogeology Team, U.S. Geological Survey<br />
<br />
=== plusieurs représentations du même endroit ===<br />
<br />
I assume that someday, some other reference frame will replace the WGS84 reference frame.<br />
During the changeover,<br />
I expect many people to post 2 descriptions for a particular location (giving slightly different lat/long coordinates for each reference frame).<br />
<br />
Even today, I can imagine someone wanting to tag a single location with WSG84, UTM (universal transverse Mercator), MGRS (military grid reference system), and the Maidenhead locator system.<br />
So readers can use whichever system they find most convenient, and ignore the others.<br />
<br />
* Would it be better to put all these ways of describing a location inside a single<br />
<code><nowiki><span class="geo"> ... </span></nowiki></code><br />
span? If so, what is the best way to make sure that each set of lat/long numbers gets associated with the correct reference frame?<br />
* Or would it be better to put all those descriptions in their own independent<br />
<code><nowiki><span class="geo"> ... </span></nowiki></code><br />
span? In that case, how do we indicate that they all (are indended to) indicate the same location, rather than a series of locations ?<br />
<br />
--[[User:DavidCary|DavidCary]] 17:06, 5 Apr 2007 (PDT)<br />
===autre===<br />
I'm no expert on these matters, and am not sure if this is the right place for such comments, but these are are a few ideas/issues that came to mind after reading this page:<br />
<br />
'''Multiple (Image) geo-tagging'''<br />
<br />
A single XHTML document might make reference to (or include images of) multiple locations. It is not clear from the documents on this site how thee are to be dealt with. Should an <IMG ... > be child of the < div class=geo > or should both tags be on the same level in a parent < div >?<br />
<br />
'''Geo-tagging areas and images of landscapes'''<br />
Geo-tags specify a single point which occupies no space. It might be desirable to be able to define areas, or single locations in a more fuzzy manner. Sometimes, as in the case of pictures of landscapes, you might want to indicate the Point of View (i.e. the location of the viewer)<br />
<br />
To accomplish all of this would require three additions to the geo microformat.<br />
# a ''precision'' attribute: This can be generally useful as even GPS devices have a margin of error, which you might want to indicate. Otherwise it can be used to give an idea of the ''bounding sphere'' of a large object like a building.<br />
# an ''area'' attribute: This could use a system similar to that used by [http://www.w3.org/TR/SVG11/paths.html#PathData SVG] for defining paths, but using lat and long for defining points. It is rather odd that, for example on wikipedia, entire countries or cities are identified by a single point.<br />
# some sort of ''vector'' attribute: While the only use I can think of for this if for photos of landscapes, it would be good to be able to indicate that the Geographic information relates to the position of the viewer rather than the subject. The ''vector'' would indicate where the viewer (camera) is looking<br />
<br />
I'm not sure whether the ''area'' and ''vector'' features are well suited to be extensions of ''geo'' or should be independent microformats. Particularly the ''vector'' might be better suited for inclusion in some 'EXIF-data equivalent micro format'. Unless of course it you can think of a use beyond photos of landscapes.<br />
<br />
--[[User:Inkwina|Inkwina]] 01:54, 30 Nov 2007 (PST)<br />
<br />
==pages en rapport==<br />
{{geo-related-pages-fr}}<br />
<br />
==voir aussi==<br />
[http://www.theregister.com/2006/12/19/nasa_4_google/ NASA shares space with Google] (2006-12-20)</div>Niuhaibiaohttps://microformats.org/wiki/index.php?title=geo-extension-nonWGS84&diff=41633geo-extension-nonWGS842010-01-14T06:22:35Z<p>Niuhaibiao: /* Brent A. Archinal */</p>
<hr />
<div>=Geo Extension Straw-Man Proposal=<br />
<br />
Further to proposals for [[luna]] and [[mars]] equivalents to [[geo]], the following is a "straw-man" proposal, to incorporate those ideas (and likewise for other bodies) into geo, and to make Geo available for other terrestrial schema than WGS84, in order that further debate may take place. Please feel free to critique it harshly but fairly!<br />
<br />
==Author==<br />
[[User:AndyMabbett|Andy Mabbett]]<br />
<br />
==Straw-Man==<br />
<br />
<pre><nowiki><br />
<span class="geo"><br />
<br />
<span class="body"><br />
Mars [1]<br />
</span><br />
<br />
<span class="reference frame"><br />
[name of mapping schema] [2]<br />
</span><br />
<br />
<span class="latitude">37.386013</span>, <br />
<span class="longitude">-122.082932</span> [3]<br />
</span><br />
</nowiki></pre><br />
<br />
===Notes===<br />
# A list of acceptable, case-insensitive, values for 'body' would need to be drawn up (e.g. "Earth", "Mars", "Moon", "Venus", etc.) with "Earth" being assumed if none is specified.<br />
# A list of acceptable values for 'reference frame' would need to be drawn up, for each body, with one being declared the default, to be used if no value is present (geo for Earth uses the datum of [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84] by default. This extension would also allow for other terrestrial schema, of which there are many, such as OSGB36).<br />
# As currently with geo, if the "latitude" and "longitude" classes are omitted, the two values MUST be separated by a semi-colon and latitude MUST be first:<code><nowiki><span class=geo">37.386013;-122.082932</span></nowiki></code><br />
:Also:<br />
:*If latitude is present, so MUST be longitude, and vice versa.<br />
:*The same number of decimal places SHOULD be used in each value; zeros are significant<br />
:*The [http://planetarynames.wr.usgs.gov/ Gazetteer of Planetary Nomenclature] has coordinates for other planets, e.g. [http://planetarynames.wr.usgs.gov/jsp/FeatureTypesData2.jsp?systemID=2&bodyID=17&typeID=10&system=Venus&body=Venus&type=Dorsum,%20dorsa&sort=AName&show=Fname&show=Lat&show=Long&show=Diam&show=Stat&show=Orig Venus] and moons, e.g. [http://planetarynames.wr.usgs.gov/jsp/FeatureTypesData2.jsp?systemID=5&bodyID=7&typeID=15&system=Jupiter&body=Io&type=Fluctus,%20fluct%C5%ABs&sort=AName&show=Fname&show=Lat&show=Long&show=Diam&show=Stat&show=Orig Io].<br />
<br />
==Issues==<br />
*Should other bodies be included in ''geo'', or have stand-alone microformats?<br />
*What effect will this have on existing 'geo' parsers, and it is safe to ignore that?<br />
*What appropriate "reference frame" sets exist?<br />
**Earth: [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84], [http://itrf.ensg.ign.fr/ITRF_solutions/2005/ ITRF2005], [http://www.ordnancesurvey.co.uk/oswebsite/gps/information/gpsbackground/glossary.html EtrS89]<br />
**Moon: Mean Earth Polar Axis<br />
**Mars: IAU2000<br />
***'Report of the IAU/IAG Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites: 2000', Celestial Mechanics and Dynamical Astronomy 82: 83-110, 2002 [http://astrogeology.usgs.gov/Projects/ISPRS/PREPRINTS/index_preprints.html]<br />
*Moon is the preferred name, per [ http://planetarynames.wr.usgs.gov/ IAU nomenclature working group]<br />
*Is it appropriate to use the name "geo" (which means "Earth") for other bodies?<br />
*is ''body '' an acceptable class name, given that it's also an HTML element?<br />
<br />
===Planetocentric longitude===<br />
<br />
Geographical longitude on, for example, Mars is not 180 degrees west to 180 degrees east: 18N,226E is a legal Martian location.<br />
<br />
This is from [http://en.wikipedia.org/wiki/Timekeeping%20on%20Mars Timekeeping on Mars] ([http://www.esa.int/SPECIALS/Mars_Express/SEM0VQV4QWD_0.html])<br />
<br />
<blockquote><br />
Note that the modern standard for measuring longitude on Mars s "planetocentric longitude", which is measured from 0°–360° East and measures angles from the center of Mars. The older "planetographic longitude" was measured from 0°–360° West and used coordinates mapped onto the surface.<br />
</blockquote><br />
<br />
You can also check the description in JPL Horizons document, which uses planetographic longitude rather than planetocentric longitude, and gives much more longitude ranges used for different planets and moons, at http://ssd.jpl.nasa.gov/horizons_doc.html#sitecoord<br />
<br />
==Comments==<br />
===thare===<br />
Comments from [[User:PlanetGeo|thare]]<br />
*geo does stand for Earth but it has previously been generalized for the planetary case. For example, the term geology is used for planetary bodies.<br />
*using ''body'' is fine by me and do not see a conflict as an HTML element. <br />
*by schema do you mean a natural surficial property like earthquake, volcano, or crater? Or do you also want to include man-made items building, house, landing site?<br />
**No, I mean, for example, WGS84, or the Martian or lunar equivalents. Is "schema" perhaps the wrong word?. [[User:AndyMabbett|Andy Mabbett]]<br />
*** Perhaps "reference frame" would be a less confusing term than "schema"? --[[User:DavidCary|DavidCary]] 17:06, 5 Apr 2007 (PDT)<br />
**** The HTML class attribute is a space seperated list, so 'class="reference frame"' is semantically equivalent to 'class="frame reference"' or 'class="reference" class="frame"' (though the latter is not syntactically valid). This could clash with, say, a theoretical microformat for footnotes, endnotes and references. Hyphenating ('class="reference-frame"') may be an improvement. [[User:TobyInk|TobyInk]] 12:29, 6 Jun 2007 (PDT)<br />
***** Often a reference system like WGS84 is referred to as [http://en.wikipedia.org/wiki/Datum datum] [[User:RichardFlapper|Richard Flapper]] 23:28 21 May 2008 (MET)<br />
*I would suggest just using "''Moon''". For other spellings for planetary bodies I would look toward the IAU/IAG documentation (an international working group) [http://astrogeology.usgs.gov/Projects/WGCCRE/ IAU/IAG Working Group (WG) on Cartographic Coordinates and Rotational Elements]<br />
*Since this is a simple case, I tried to stay away from this issue but just can't. What does Earth really mean? There a many definitions for the size of Earth that need to be resolved when using lat/lon coordinates. Is the size of the Earth defined by the WGS84 or NAD27 definition? For Mars, is it the definition used in 1991 or redefined in 2000? This has previously been solved in web GIS applications by using an "EPSG" code. For planetary bodies we are attempting to define a similar coded standard which currently is called the IAU2000 code or namespace. Thus for Mars the code might be IAU2000:49900.<br />
**Hence 'schema'. [[User:AndyMabbett|Andy Mabbett]]<br />
*still working - more later<br />
**Thank you. [[User:AndyMabbett|Andy Mabbett]]<br />
<br />
===Brent A. Archinal=== <br />
<br />
(reproduced from e-mail to [[User:AndyMabbett|Andy Mabbett]], by kind permission)<br />
<br />
*I appreciate the information you've provided and certainly the general idea of using "microformats" to indicate geographical location of points on [http://www.skldintl.com solar garden light]system bodies is interesting.<br />
*As to any comments on the general idea or any specific implementation, I think my colleague, Trent Hare, has already addressed any primary concerns or questions (above).<br />
*The main issue seems to be that both the body, and the specific definition (technically a "reference frame") in question need to be specified, e.g. 1) Earth, ITRF2005, 2) Moon, ULCN 2005, 3) Mars, "IAU2000" or similar. Note that these frames are actually realizations of various "reference systems" 1) ITRS, 2) mean Earth/polar axis system, 3) IAU2000 Mars body fixed, respectively), but the system is apparent once the frame has been identified.<br />
*A secondary issue is that obviously a third coordinate may need to be specified, i.e. some sort of "radius" (from the body center of mass) or "elevation" about a reference surface. If the latter, then that reference surface needs to be specified as well (e.g. Mars, "IAU2000", "IAU2000 sphere").<br />
*If the microformat(s) were expandable to handle these cases when necessary (and others we haven't yet thought of) then obviously they could have a lot of utility.<br />
*There are plenty of GIS and standards organization formats out there for handling this type of data, even for the solar system case. I'm not at all an expert on what's available, but obviously for something like the microformats to be generally used, their advantages over these existing formats would have to be made clear. <br />
*As to usage here, we'll let others know of the existence of these formats, but I can't say how much immediate interest there might be in using them. We already (and Trent could say more) use a wide range of GIS and even flat file formats to carry e.g. lists of point-like data. <br />
*Regarding one other point on the web pages, I believe the "Moon" (capitalized) is the primary recognized name for the Moon. There is an [IAU nomenclature working group http://planetarynames.wr.usgs.gov/] that handles not only the names of features on planetary bodies, but of the bodies themselves, and I believe this is their position on this (since confirmed - [[User:AndyMabbett|Andy Mabbett]]).<br />
<br />
::Brent A. Archinal, Geodesist, Astrogeology Team, U.S. Geological Survey<br />
<br />
=== multiple representations of the same location ===<br />
<br />
I assume that someday, some other reference frame will replace the WGS84 reference frame.<br />
During the changeover,<br />
I expect many people to post 2 descriptions for a particular location (giving slightly different lat/long coordinates for each reference frame).<br />
<br />
Even today, I can imagine someone wanting to tag a single location with WSG84, UTM (universal transverse Mercator), MGRS (military grid reference system), and the Maidenhead locator system.<br />
So readers can use whichever system they find most convenient, and ignore the others.<br />
<br />
* Would it be better to put all these ways of describing a location inside a single<br />
<code><nowiki><span class="geo"> ... </span></nowiki></code><br />
span? If so, what is the best way to make sure that each set of lat/long numbers gets associated with the correct reference frame?<br />
* Or would it be better to put all those descriptions in their own independent<br />
<code><nowiki><span class="geo"> ... </span></nowiki></code><br />
span? In that case, how do we indicate that they all (are indended to) indicate the same location, rather than a series of locations ?<br />
<br />
--[[User:DavidCary|DavidCary]] 17:06, 5 Apr 2007 (PDT)<br />
<br />
* Why not use the same approach as used in GML? Use the [http://en.wikipedia.org/wiki/Geography_Markup_Language#Coordinate_Reference_System srsName] attribute when referring to a Coordinate Reference System (CRS) (or Datum). This way a coordinate can be recalculated to whatever CRS. <br />
<br />
--[[User:RichardFlapper|Richard Flapper]] 23:46, 21 May 2008 (MET)<br />
<br />
===Other===<br />
I'm no expert on these matters, and am not sure if this is the right place for such comments, but these are are a few ideas/issues that came to mind after reading this page:<br />
<br />
'''Multiple (Image) geo-tagging'''<br />
<br />
A single XHTML document might make reference to (or include images of) multiple locations. It is not clear from the documents on this site how thee are to be dealt with. Should an <IMG ... > be child of the < div class=geo > or should both tags be on the same level in a parent < div >?<br />
<br />
* This is solved by using [[figure]]. [[User:TobyInk|TobyInk]] 10:54, 24 Feb 2008 (PST)<br />
<br />
'''Geo-tagging areas and images of landscapes'''<br />
Geo-tags specify a single point which occupies no space. It might be desirable to be able to define areas, or single locations in a more fuzzy manner. Sometimes, as in the case of pictures of landscapes, you might want to indicate the Point of View (i.e. the location of the viewer)<br />
<br />
To accomplish all of this would require three additions to the geo microformat.<br />
# a ''precision'' attribute: This can be generally useful as even GPS devices have a margin of error, which you might want to indicate. Otherwise it can be used to give an idea of the ''bounding sphere'' of a large object like a building.<br />
# an ''area'' attribute: This could use a system similar to that used by [http://www.w3.org/TR/SVG11/paths.html#PathData SVG] for defining paths, but using lat and long for defining points. It is rather odd that, for example on wikipedia, entire countries or cities are identified by a single point.<br />
# some sort of ''vector'' attribute: While the only use I can think of for this if for photos of landscapes, it would be good to be able to indicate that the Geographic information relates to the position of the viewer rather than the subject. The ''vector'' would indicate where the viewer (camera) is looking<br />
<br />
I'm not sure whether the ''area'' and ''vector'' features are well suited to be extensions of ''geo'' or should be independent microformats. Particularly the ''vector'' might be better suited for inclusion in some 'EXIF-data equivalent micro format'. Unless of course it you can think of a use beyond photos of landscapes.<br />
<br />
--[[User:Inkwina|Inkwina]] 01:54, 30 Nov 2007 (PST)<br />
<br />
===Astronomical Coordinates===<br />
Comments from [[User:StuartLowe|Stuart]]<br />
<br />
Rather than limit the format to the surfaces of planets and moons, would it be possible to include astronomical coordinates for objects in celestial coordinate frames? This would be very useful for tagging astronomical objects (e.g. M41 or NGC 7027).<br />
<br />
If you do not want to break the existing ''geo'' tag might I suggest the more generic term ''coord''?<br />
<br />
As suggested already it is important to define a reference frame. The term ''coordinate-frame'' (or ''coord-frame'') might also avoid ambiguities that exist for the word ''reference''. In astronomical applications it is necessary to provide both a frame (e.g. FK5) and an equinox/epoch (e.g. 2000.0). Astronomical coordinate frames that are widely supported are: ICRS, FK5, FK4, ECL, GAL, SGAL.<br />
<br />
==Related pages==<br />
{{geo-related-pages}}<br />
<br />
==See also==<br />
[http://www.theregister.com/2006/12/19/nasa_4_google/ NASA shares space with Google] (2006-12-20)</div>Niuhaibiaohttps://microformats.org/wiki/index.php?title=project&diff=41632project2010-01-14T06:19:34Z<p>Niuhaibiao: /* duration */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== Analysis of Examples (Based on 8 examples.)==<br />
<br />
=== Common practical project fields ===<br />
* fn (100%)<br />
* summary (100%)<br />
* author (50%)<br />
* instructions (100%)<br />
* requirement (50%)<br />
* published (50%)<br />
* duration (25%)<br />
* tags (25%)<br />
<br />
=== Common abstract project fields ===<br />
* fn (100%)<br />
* summary (75%)<br />
* author (50%)<br />
* due (50%)<br />
* goal (25%)<br />
* duration (25%)<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
== Format ==<br />
=== In General ===<br />
The projecta format documents practical (how-you-can-do) projects. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]], [[hatom|hAtom]], [[hcalendar|hCalendar]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under [http://www.skldintl.com solar garden light] source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Niuhaibiaohttps://microformats.org/wiki/index.php?title=xfolk&diff=41631xfolk2010-01-14T06:16:00Z<p>Niuhaibiao: We are professional Solar light,Solar Garden Light,Solar Street Light manufacturers and factory in China.We can produce Solar light,Solar Garden Light,Solar Street Light according to your requirements</p>
<hr />
<div><entry-title>xFolk RC1</entry-title><br />
{{DraftSpecification}}<br />
<br />
'''xFolk''' (from "xFolksomony") is a simple and open format for publishing collections of bookmarks. It better enables services for improving user experience and sharing data in web-based bookmarking software. xFolk may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. It is one of several open [[microformats|microformat]] standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification ==<br />
<br />
=== Editor/Author ===<br />
[http://thecommunityengine.com/ Bud Gibson] ([http://thecommunityengine.com The Community Engine])<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2005}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
=== Inspiration and Acknowledgments ===<br />
Thanks to: [http://www.cnbc.cmu.edu/~plaut/ David Plaut] who introduced me to the idea that items may partially belong to many categories at once. More recently, thanks to: [http://tantek.com/ Tantek Çelik], [http://epeus.blogspot.com/ Kevin Marks], [http://steve.osdir.com/ Steve Mallet], [http://hybernaut.com/ Brian DelVecchio], and [http://blogmarks.net François Hodierne] who have contributed to the development of xFolk with thoughtful critiques and implementations.<br />
<br />
== Introduction ==<br />
Social bookmarking services let users save and tag bookmarks to share with other users. Over the past year, the number of these services has mushroomed to [http://en.wikipedia.org/wiki/Social_bookmarking over 20], with popular examples including: [http://del.icio.us del.icio.us], [http://furl.net furl], [http://de.lirio.us de.lirio.us], [http://jots.com jots], and [http://blogmarks.net blogmarks]. <br />
<br />
Lack of an open, interoperable data standard is a major issue in using social bookmarking services. An open standard would make it possible to easily collect social bookmark data and remix it to invent new services along the lines of [http://gataga.com gataga]'s experimental bookmark search engine. An open standard would also make it possible to write javascripts that work across services [http://johnvey.com/features/deliciousdirector/ as some currently do for del.icio.us], enabling across-the-board improvements in user experience.<br />
<br />
xFolk is an open social bookmarking standard that aims to achieve both benefits. Social bookmarking services that adopt xFolk will continue to differentiate themselves with data services. But, the data itself will be easy to manipulate by third party scripts and easy to share. As a result, bookmarking services will be able to offer a wider array of options to their users at low cost and focus on what truly differentiates them. Individuals or groups operating standalone bookmark repositories will have access to a wider array of functionality than they can produce on their own.<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
Extensive analysis of social bookmarking services and linkblogs, reported on [http://thecommunityengine.com/home/archives/xfolk elsewhere], reveals that the data published by both bookmarking services and '''many''' different linkblogs are described by the following implied schema:<br />
<br />
* A bookmarked or tagged link.<br />
* A title for the entry.<br />
* Tags for the link.<br />
* An extended description or summary of the link.<br />
<br />
As demonstrated in early iterations of the xFolk standard, this general schema can be translated into markup by:<br />
<br />
# creating a container element for each entry of class <code>xfolkentry</code>, <br />
# using an <a> element for the bookmarked or tagged link of class <code>taggedlink</code>, <br />
# using title attribute for the tagged link <a> element, if it exists, as the entry title, otherwise using the element value,<br />
# using [[rel-tag]] for the tags, and<br />
# using a container element of class <code>description</code>, such as &lt;p>, for any extended description or summary.<br />
<br />
A given xFolk entry will always contain a tagged link including a title with all other elements optional. Entries may have more than one tag as well as more than one element of class <code>description</code>. Multiple elements of class <code>description</code> are ordered by default document order. Semantic elements within xFolk entries may be nested at arbitray depths.<br />
<br />
Many social bookmarking systems exist, each with its own markup conventions. Further, many people are already publishing personal link blogs. xFolk is designed with ease of adapting to these current practices as a primary goal. Therefore, few assumptions are made as to the exact kinds of elements used for an xFolk entry. Rather, the work of defining semantics is left entirely to the class and rel (in the case of [[rel-tag]]) attribute values.<br />
<br />
It is expected that developers will use [http://www.w3.org/TR/xpath XPath] or equivalent syntax in accessing xFolk entry elements. a requirement for XPath is that the HTML document be well-formed but not necessarily valid. Thus, while not optimal, it is possible to serviceably use xFolk in an HTML document that does not validate.<br />
<br />
=== XMDP Profile ===<br />
<br />
See the [[xfolk-profile|xFolk profile]] for the [http://gmpg.org/xmdp XMDP] profile of xFolk.<br />
<br />
== Example ==<br />
Here is a sample bookmark as displayed in [http://del.icio.us del.icio.us]'s standard markup. Lines where the value of elements' class attributes must change to conform to xFolk are marked with a comment at the end.<br />
<pre>&lt;div class="post"&gt; <!--will change--><br />
&lt;div&gt;<br />
&lt;a class="delLink" href="http://www.sifry.com/alerts/archives/000306.html"&gt; <!--will change--><br />
Sifry's Alerts: Technorati launches Related Tags<br />
&lt;/a&gt; <br />
&lt;/div&gt;<br />
&lt;div class="extended"&gt; <!--will change--><br />
Ever wanted to see what posts are related to other posts, what tags <br />
are related to others? Now you can! Just check under the Tag <br />
description on most tag pages, like this one, or this one, and you'll<br />
see the patterns. Can you smell the emergence?<br />
&lt;/div&gt;<br />
&lt;div class="meta"&gt;<br />
to<br />
&lt;a class="delNav" href="/fpgibson/folksonomy"&gt;folksonomy&lt;/a&gt; <!--will change--><br />
&lt;a class="delNav" href="/fpgibson/technorati"&gt;technorati&lt;/a&gt; <!--will change--><br />
... &lt;a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49"&gt;<br />
and 1 other person<br />
&lt;/a&gt;<br />
... on 2005-04-09<br />
&lt;/div&gt;<br />
&lt;/div&gt;</pre><br />
<br />
The equivalent in xFolk is as follows. Comments are placed at the end of lines where class attribute changes were required. <br />
<pre><nowiki><br />
&lt;div class="xfolkentry"&gt; <!-- changed --><br />
&lt;div&gt;<br />
&lt;a class="taggedlink" href="http://www.sifry.com/alerts/archives/000306.html"&gt; <!-- changed --><br />
Sifry's Alerts: Technorati launches Related Tags<br />
&lt;/a&gt; <br />
&lt;/div&gt;<br />
&lt;div class="description"&gt; <!-- changed --><br />
Ever wanted to see what posts are related to other posts, what tags <br />
are related to others? Now you can! Just check under the Tag <br />
description on most tag pages, like this one, or this one, and you'll<br />
see the patterns. Can you smell the emergence?<br />
&lt;/div&gt;<br />
&lt;div class="meta"&gt;<br />
to<br />
&lt;a rel="tag" href="/fpgibson/folksonomy"&gt;folksonomy&lt;/a&gt; <!-- changed --><br />
&lt;a rel="tag" href="/fpgibson/technorati"&gt;technorati&lt;/a&gt; <!-- changed --><br />
... &lt;a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49"&gt;<br />
and 1 other person<br />
&lt;/a&gt;<br />
... on 2005-04-09<br />
&lt;/div&gt;<br />
&lt;/div&gt;<br />
</nowiki></pre><br />
<br />
Converting markup to be conformant with xFolk is almost always this easy. The advantage of xFolk is that it provides one set of class attributes that can be reused across all services and link blogs, almost always with no loss of granularity. The next section presents several more examples to illustrate this point.<br />
<br />
Another simple example (using lists markup) :<br />
<pre><br />
<nowiki><br />
<ul><!--xfolk is about *collections* of bookmarks--><br />
<li><br />
<ul class="xfolkentry"> <br />
<li><a class="taggedlink" href="http://microformats.org/wiki/Main_Page">microformats wiki</a></li><br />
<li class="description">The main place for understanding microformats and playing with...</li><br />
<li class="description">Community driven wiki</li><br />
<li class="meta"><br />
Tags :<br />
<a rel="tag" href="http://del.icio.us/tag/microformats">microformats</a><br />
<a rel="tag" href="http://del.icio.us/tag/websocial">websocial</a><br />
<a rel="tag" href="http://del.icio.us/tag/semantics">semantics</a><br />
</li><br />
</ul><br />
</li><br />
<br />
<li><br />
<!--Another xfolkentry as above, and so on...--><br />
</li><br />
<br />
</ul><br />
</nowiki><br />
</pre><br />
<br />
== Many more examples ==<br />
<br />
We have numerous examples to help developers incorporate xFolk into their sites.<br />
<br />
=== In the wild ===<br />
<br />
These are real live examples of functioning systems that publish bookmarks in xFolk. These are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you publish using xFolk, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://greenvoice.com Greenvoice] has a user-generated environmental news link list, which is marked up with xFolk.<br />
* [http://www.idoneos.com Idoneos.com] , a conceptually networked collection of information pages (mostly spanish), is tagging bookmarks with xFolk.<br />
* [http://ashaszin.lautre.net/ Ashaszin] - Small blog running with [http://spip.net SPIP] : del.icio.us links and web feeds tagged with xFolk .<br />
* [http://www.rolandinsh.lv/blog/ Rolands Umbrovskis - blog] all blog posts are marked up with xFolk.<br />
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] a social network mashup, uses basic xFolk for bookmarking hAtom entries. See [http://dharmafly.com/blog/bangladeshboat Dharmafly blog discussion].<br />
* [http://waferbaby.com/hussy waferbaby's Hussy] currently publishes links using xFolk.<br />
* [http://smarking.com/ Smarking] currently publishes all shared links (including search results) using xFolk.<br />
* [http://unalog.com unalog] currently publishes all shared links (including search results) using xFolk.<br />
* [http://de.lirio.us de.lirio.us] currently publishes its bookmarks using xFolk (with the deprecated class attribute <code>extended</code> in place of <code>description</code>, see [[xfolk-profile | the XMDP]]).<br />
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] currently exports bookmarks to blogs in xFolk (scroll down to the export example on the page; the deprecated class attribute <code>extended</code> is used in place of <code>description</code>, see [[xfolk-profile | the XMDP]]).<br />
* [http://thecommunityengine.com The Community Engine] uses xFolk (with the deprecated class attribute <code>extended</code> in place of <code>description</code>, see [[xfolk-profile | the XMDP]]) for its [http://thecommunityengine.com/home main entries] and for its [http://thecommunityengine.com/webcites republished bookmarks].<br />
* [http://groovymother.com/links/ Groovy Links] is a link blog which is marked up with xFolk.<br />
* [http://tommorris.org/blog/ Tom Morris] - daily del.icio.us links are marked up with xFolk, [[hCard]] and [[vote-links]].<br />
<br />
=== Additional social bookmarking services ===<br />
<br />
This example illustrates how xFolk may be applied to one additional service:<br />
<br />
* [[xfolk-scuttle | scuttle]]<br />
<br />
=== Link blogs ===<br />
<br />
Social bookmarking services are only the most recent examples of people publishing links. Link blogs have been around almost since the beginning of blogging. They represent somewhat more of a challenge for xFolk because their markup tends to be less semantic from the outset. The following examples illustrate some particular challenges and how they can be overcome.<br />
<br />
* [[xfolk-kottke | kottke]]<br />
* [[xfolk-pollas | pollas]]<br />
* [[xfolk-jacobian | jacobian]]<br />
* [[xfolk-julian-bez | julian-bez]]<br />
* [http://www.skldintl.com solar garden light]<br />
<br />
=== Spam ===<br />
Some spammers are adding xFolk tags to their link farms. (It's probably a bad idea to actually link to these sites.) For example,<br />
* phontron.info<br />
<br />
== Implementations ==<br />
<br />
The following implementations have been developed which generate or use xFolk. If you have an xFolk implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://buzka.com Buzka], a social bookmarking service, now supports xFolk<br />
* [http://blip.tv Blip.tv], a video hosting site, now [http://blog.blip.tv/blog/2006/08/19/blip-supports-xfolk/ supports xFolk].<br />
* [http://www.s9y.org/ Serendipity], a PHP-powered, flexible Blogging/CMS application, now has a [http://www.numblog.de/archives/241-Social-Bookmarks-Plugin-for-Serendipity.html social bookmarks plugin] that supports xFolk.<br />
* [http://claimid.com claimID] has implemented xFolk for people's links.<br />
* [http://ma.gnolia.com ma.gnolia] now supports xFolk.<br />
* [http://smarking.com/ Smarking.com] (a social bookmarking service) marks up their tagged links with xFolk! Hat tip: [http://3spots.blogspot.com/2006/05/social-bookmarking-smarking.html 3spots: Social + bookMARKING = Smarking] which itself is an [[hreview|hReview]].<br />
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar<br />
* [http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.<br />
* Bud Gibson and Mike Migurski [http://thecommunityengine.com/home/archives/2005/09/vegomatic_an_al.html have written] [http://thecommunityengine.com/veg-o-matic veg-o-matic], an xFolk reblogging tool and service.<br />
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including xFolk and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''<br />
* [http://www.midgard-project.org/midcom-permalink-6416db7e1f0e297b4cf3dcc285702a8d net.nemein.bookmarks], the bookmark manager in [http://www.midgard-project.org/ Midgard CMS] uses xFolk as the native output format, with added <code>abbr class=posted</code> for publication date and <code>abbr class=poster</code> for user who added the bookmark. See [http://bergie.iki.fi/links/ example]<br />
* [http://de.lirio.us de.lirio.us] currently publishes its bookmarks using xFolk 0.4 (the class attribute <code>extended</code> is used in place of description).<br />
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] currently exports bookmarks to blogs in xFolk 0.4 (scroll down to the export example on the page; the class attribute <code>extended</code> is used in place of <code>description</code>).<br />
* [http://pokkari.com/microformat/javadoc/ Sivitols] is a Java library for microformats. Currently only the xFolk RC1 standard is implemented, but additional microformat support is planned. (adapted from [http://blog.blip.tv/blog/microformats/])<br />
* [http://bildu.net Bildu] a social bookmarking service in Basque that supports xFolk (an also rel-tag).<br />
* [http://bookmarks.excite.co.uk/ Excite Bookmarks] a social bookmarking service that supports xFolk and rel-tag.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]<br />
* [[rel-tag]]<br />
<br />
=== Informative References ===<br />
* [http://thecommunityengine.com/home/archives/xfolk articles about xFolk]<br />
* [http://thecommunityengine.com/home/archives/tags/microformats articles about the business value of microformats]<br />
* [http://gataga.com gataga social bookmark search engine]<br />
* [http://johnvey.com/features/deliciousdirector/ an ajax based interface for del.icio.us]<br />
* [http://en.wikipedia.org/wiki/Social_bookmarking social bookmarking defined at wikipedia]<br />
<br />
=== Similar Work ===<br />
* [[hreview | hReview]]<br />
<br />
== Work in progress ==<br />
Although this specification has recently begun to stabilize as indicated by the version RC1, it is still a work in progress. If warranted, I am prepared to go through multiple release candidates to achieve the narrow purpose of making bookmark entries more genrally accessible with as with as light weight a format as possible. All changes since the last iteration have been motivated by the implementation experience of developers attempting to achieve this narrow aim. Further changes will also most likely be motivated by implementation concerns. See "future directions" below for additional microformat possibilities.<br />
<br />
=== Changes since xFolk 0.4 ===<br />
The class attribute value <code>extended</code> was deprecated in favor <code>description</code> to better conform with other microformat usage and some requests during implementation. The other change has been to allow use of multiple elements of class <code>extended</code> based on some use cases discovered in implementation.<br />
<br />
=== Future directions ===<br />
There are several extensions one might imagine for xFolk. Frequently, these extensions are best achieved by combining xFolk with another microformat. For instance, one might want to indicate his or her evaluation of the bookmarked item. This might be achieved by using [[vote-links | Vote Links]] or [[hreview | hReview]] with xFolk.<br />
<br />
One can also imagine extending xFolk to provide data conformant with various social bookmarking service APIs, for instance to provide all bookmarks by tag. These APIs are currently too fluid for specification in any kind of standard. The APIs and the functionality they provide represent one way social bookmarking services and meta services can differentiate themselves.<br />
<br />
A companion format called "xFolk definition" is under development. xFolk definition will provide a means of explicitly defining the tags used in social bookmarks.<br />
<br />
=== Brainstorming ===<br />
* [[xfolk-brainstorming|xFolk brainstorming]]<br />
<br />
== Discussions ==<br />
<br />
=== Q&A ===<br />
* If you have any questions about xFolk, check the [[xfolk-faq|xFolk FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[xfolk-issues|xFolk issues]] document.<br />
<br />
==Related pages==<br />
{{template:xfolk-related-pages}}<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:xFolk]]</div>Niuhaibiao