http://microformats.org/wiki/api.php?action=feedcontributions&user=Discoleo&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-28T22:28:36ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=measure-brainstorming&diff=10924measure-brainstorming2006-12-03T13:36:46Z<p>Discoleo: /* Categorical Data */ Numbering schemes</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 />
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 />
==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'' 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" microforamt? [[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 />
<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</div>Discoleohttp://microformats.org/wiki/index.php?title=measure-brainstorming&diff=10922measure-brainstorming2006-12-03T13:28:19Z<p>Discoleo: /* A Single Value / Data Point */ Simple Format</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 />
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 />
==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 Data ====<br />
<br />
* Various measurements may produce '''NON-Numerical''' values<br />
** a pain scale: '''most severe''', '''very severe''', '''severe''', ...<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" microforamt? [[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 />
<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</div>Discoleohttp://microformats.org/wiki/index.php?title=Main_Page&diff=29352Main Page2006-12-03T13:22:25Z<p>Discoleo: /* Exploratory Discussions */ (corrected small error)</p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. <br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]] {{NewMarker}}<br />
* [[hresume|hResume]] {{NewMarker}}<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}<br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] {{NewMarker}}<br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[hproduct|hProduct]] - [[hproduct-brainstorming|hProduct brainstorming]] | [[hproduct-feedback|hProduct discussion]] | [[hproduct-examples|hProduct examples]] {{NewMarker}}<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]] {{NewMarker}}<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* '''numbers''' {{NewMarker}}<br />
** often numbers may appear as '''Roman Numbers''' (e.g. for Years or in Lists) or some other numbering scheme<br />
** even this basic entitiy can have serious repercussions<br />
** e.g. 'VII' (7) should precede 'C' (100), yet as a string, this is NOT the case<br />
* photo note [[photo-note-examples|photo note examples]]<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{NewMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]]. {{NewMarker}}<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] {{NewMarker}}<br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
<br />
== General Microformats Issues ==<br />
<br />
Discusses/ points out some issues related ''to more than one'' / to all microformats. This should be a brainstorming session trying to tackle such general problems as microformats implementation, microformats efficiency and other advanced concepts.<br />
<br />
* [[microformats-issues]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]] {{NewMarker}}<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 50 articles<br />
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])</div>Discoleohttp://microformats.org/wiki/index.php?title=Main_Page&diff=29351Main Page2006-12-03T13:18:19Z<p>Discoleo: /* Exploratory Discussions */ Number Microformats</p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. <br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]] {{NewMarker}}<br />
* [[hresume|hResume]] {{NewMarker}}<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}<br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] {{NewMarker}}<br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[hproduct|hProduct]] - [[hproduct-brainstorming|hProduct brainstorming]] | [[hproduct-feedback|hProduct discussion]] | [[hproduct-examples|hProduct examples]] {{NewMarker}}<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]] {{NewMarker}}<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* '''numbers''' {{NewMarker}}<br />
** often numbers may appear as '''Roman Numbers''' (e.g. for Years or in Lists) or some other numbering scheme<br />
** even this basic entitiy can have serious repercussions<br />
** e.g. 'VII' (7) should precede 'X' (10), yet as a string, this is NOT the case<br />
* photo note [[photo-note-examples|photo note examples]]<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{NewMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]]. {{NewMarker}}<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] {{NewMarker}}<br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
<br />
== General Microformats Issues ==<br />
<br />
Discusses/ points out some issues related ''to more than one'' / to all microformats. This should be a brainstorming session trying to tackle such general problems as microformats implementation, microformats efficiency and other advanced concepts.<br />
<br />
* [[microformats-issues]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]] {{NewMarker}}<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 50 articles<br />
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])</div>Discoleohttp://microformats.org/wiki/index.php?title=Main_Page&diff=29350Main Page2006-12-03T13:08:48Z<p>Discoleo: /* General Microformats Issues */ Created Paragraph</p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. <br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]] {{NewMarker}}<br />
* [[hresume|hResume]] {{NewMarker}}<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}<br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] {{NewMarker}}<br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[hproduct|hProduct]] - [[hproduct-brainstorming|hProduct brainstorming]] | [[hproduct-feedback|hProduct discussion]] | [[hproduct-examples|hProduct examples]] {{NewMarker}}<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]] {{NewMarker}}<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{NewMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]]. {{NewMarker}}<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] {{NewMarker}}<br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
<br />
== General Microformats Issues ==<br />
<br />
Discusses/ points out some issues related ''to more than one'' / to all microformats. This should be a brainstorming session trying to tackle such general problems as microformats implementation, microformats efficiency and other advanced concepts.<br />
<br />
* [[microformats-issues]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]] {{NewMarker}}<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 50 articles<br />
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])</div>Discoleohttp://microformats.org/wiki/index.php?title=measure-brainstorming&diff=10921measure-brainstorming2006-11-23T12:02:40Z<p>Discoleo: /* Matrices */ Reasoning for Matrices</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 />
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 />
==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 Data ====<br />
<br />
* Various measurements may produce '''NON-Numerical''' values<br />
** a pain scale: '''most severe''', '''very severe''', '''severe''', ...<br />
<br />
==== A Single Value / Data Point ====<br />
<br />
* the distance between 2 cities is '''40 km'''<br />
* the velocity is '''62 mph'''<br />
* ...<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" microforamt? [[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 />
<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</div>Discoleohttp://microformats.org/wiki/index.php?title=issues&diff=10927issues2006-11-23T11:53:25Z<p>Discoleo: Further minor corrections</p>
<hr />
<div>Issues which apply to more than one microforamt.<br />
<br />
==Bloated Format==<br />
<br />
=== The Problem ===<br />
Unfortunately, current microformats implementation consume a vast amount of space. The complexity will increase even more, when wanting to ''solve/add'' more complex issues. A direct consequence of this is a '''bloated format''':<br />
* some of the markup is really bloated<br />
** instead of a number, we end sometimes with a whole '''new paragraph''' of markup<br />
** however, in order to be complete, the markup might need to be so<br />
** nevertheless, having a page with 1000 data points will be a horror scenario<br />
<br />
<br />
Therefore, I proposed to open this new brainstorming session/page on how to efficiently implement the microformats in web pages.<br />
<br />
=== Ideas/ Solutions ===<br />
<br />
If we think a little bit back about '''css''', one of the main reasons of its development was:<br />
* to separate content from style<br />
** page code becomes more easy to '''understand'''<br />
** and to '''maintain'''<br />
** and often the '''size''' shrinks significantly<br />
<br />
We must learn this lesson when dealing with microformats. Specifically, the following issues are important:<br />
* extensive microformat markup inside the page code will significantly reduce the readability of the code<br />
* repeating the markup will increase page size<br />
* it will become more difficult to maintain/change the page<br />
<br />
<br />
'''Solution'''<br />
* '''define microformat classes'''<br />
** e.g. in the page header, or<br />
** in a separate file (see later)<br />
* define '''abbreviations''' to those classes<br />
** use actually only the abbrevioations inside the web page, instead of the '''whole paragraph''' of markup<br />
<br />
<br />
* define the microformat classes inside a '''separate file''' (similarly to the css)<br />
** this file needs NOT to be downloaded automatically<br />
*** you do NOT need it for displaying the data<br />
*** it is only needed when wanting to import the data somewhere<br />
*** most viewers, however, only view the data<br />
** let the browser automatically download this file, only IF:<br />
*** there is enough bandwidth<br />
*** the user wants to copy that data<br />
*** the user wants to explicitly save the whole page<br />
** when the user wants to copy an item<br />
*** the web browser should acces that ''microformats'' additional page and<br />
*** download only the relevant class (NO need to actually download the whole page)<br />
*** '''EXTEND html protocol to be able to download ''web-file/class-defined-inside-file'' '''without beeing necessary to download the whole file<br />
<br />
<br />
=== Requirements ===<br />
<br />
New Tags:<br />
* '''<struct> ... </struct>''': like the C/C++ struct, will define the microformats structure<br />
* '''<v> ... </v>''': this will define the variable inside the ''struct'' that should be replaced<br />
* '''<v ... />''': similarly to above, but this will NOT be displayed by the browser<br />
** '''<v>''' is a shorthand for '''var''', to further reduce file size<br />
<br />
=== Examples ===<br />
<br />
Lets take this code:<br />
<pre><nowiki><br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn">Book Title</span><br />
<div class="chapter"><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
We would define this in the header like this:<br />
<pre><nowiki><br />
<struct><br />
MyName{<br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn"><v /></span><br />
<div class="chapter"><br />
<span class="fn"><v /></span><br />
</div><br />
</div><br />
</div><br />
}<br />
</struct><br />
</nowiki></pre><br />
<br />
or in a separate microformats file (NO struct needed):<br />
<pre><nowiki><br />
MyName{<br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn"><v /></span><br />
<div class="chapter"><br />
<span class="fn"><v /></span><br />
</div><br />
</div><br />
</div><br />
}<br />
</nowiki></pre><br />
<br />
Inside the web page we use:<br />
<pre><nowiki><br />
<struct class="MyName"><br />
<v>1st variable</v><br />
<v>2nd variable</v><br />
</struct><br />
</nowiki></pre><br />
<br />
<br />
IF, one variable should NOT be displayed by the browser, we would use <v val="..." /> instead (the ''val='' could be omitted), e.g.:<br />
<pre><nowiki><br />
<div class="geo"><br />
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <br />
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr><br />
</div><br />
</nowiki></pre><br />
<br />
Would become:<br />
* inside the microformats definition page write:<br />
<pre><nowiki><br />
MyGeoStructure{<br />
<div class="geo"><br />
<abbr class="latitude" title=v><v /></abbr> <br />
<abbr class="longitude" title=v><v /></abbr><br />
</div><br />
}<br />
</nowiki></pre><br />
<br />
* the code inside the web page:<br />
<pre><nowiki><br />
<struct class="MyGeoStructure"><br />
<v "37.408183" /><v>N 37° 24.491</v><br />
<v "-122.13855" /><v>W 122° 08.313</v><br />
</struct><br />
</nowiki></pre><br />
<br />
<br />
- discussion opened by [[discoleo|Leonard Mada]]</div>Discoleohttp://microformats.org/wiki/index.php?title=issues&diff=10446issues2006-11-23T11:46:26Z<p>Discoleo: Correcting Page Layout Errors</p>
<hr />
<div>Issues which apply to more than one microforamt.<br />
<br />
==Bloated Format==<br />
<br />
=== The Problem ===<br />
Unfortunately, current microformats implementation consume a vast amount of space. The complexity will increase even more, when wanting to ''solve/add'' more complex issues. A direct consequence of this is a '''bloated format''':<br />
* some of the markup is really bloated<br />
** instead of a number, we end sometimes with a whole '''new paragraph''' of markup<br />
** however, in order to be complete, the markup might need to be so<br />
** nevertheless, having a page with 1000 data points will be a horror scenario<br />
<br />
<br />
Therefore, I proposed to open this new brainstorming session/page on how to efficiently implement the microformats in web pages.<br />
<br />
=== Ideas/ Solutions ===<br />
<br />
If we think a little bit back about '''css''', one of the main reasons of its development was:<br />
* to separate content from style<br />
** page code becomes more easy to '''understand'''<br />
** and to '''maintain'''<br />
** and often the '''size''' shrinks significantly<br />
<br />
We must learn this lesson when dealing with microformats. Specifically, the following issues are important:<br />
* extensive microformat markup inside the page code will significantly reduce the readability of the code<br />
* repeating the markup will increase page size<br />
* it will become more difficult to maintain/change the page<br />
<br />
'''Solution'''<br />
* '''define microformat classes'''<br />
** e.g. in the page header, or<br />
** in a separate file (see later)<br />
* define '''abbreviations (qasi tags)''' to those classes<br />
** use actually only the abbrevioations inside the web page, instead of the '''whole paragraph''' of markup<br />
<br />
<br />
* define the microformat classes inside a '''separate file''' (similarly to the css)<br />
** this file needs NOT to be downloaded automatically<br />
*** you do NOT need it for displaying the data<br />
*** it is only needed when wanting to import the data somewhere<br />
*** most viewers, however, only view the data<br />
** let the browser automatically download this file, only IF:<br />
*** there is enough bandwidth<br />
*** the user wants to copy that data<br />
*** the user wants to explicitly save the whole page<br />
** when the user wants to copy an item<br />
*** the web browser should acces that ''microformats'' additional page and<br />
*** download only the relevant class (NO need to actually download the whole page)<br />
*** '''EXTEND html protocol to be able to download ''web-file/class-defined-inside-file'' '''without beeing necessary to download the whole file<br />
<br />
=== Requirements ===<br />
<br />
New Tags:<br />
* '''<struct> ... </struct>''': like the C/C++ struct, will define the microformats structure<br />
* '''<v> ... </v>''': will define the variable (part inside) ''struct'' that should be replaced<br />
* '''<v ... />''': similarly to point above, but NOT displayed by browser<br />
** '''<v>''' is a shorthand for '''var''', to further reduce file size<br />
<br />
=== Examples ===<br />
<br />
Lets take this code:<br />
<pre><nowiki><br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn">Book Title</span><br />
<div class="chapter"><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
We would define this in the header like this:<br />
<pre><nowiki><br />
<struct><br />
MyName{<br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn"><v /></span><br />
<div class="chapter"><br />
<span class="fn"><v /></span><br />
</div><br />
</div><br />
</div><br />
}<br />
</struct><br />
</nowiki></pre><br />
<br />
or in a separate microformats file (NO struct needed):<br />
<pre><nowiki><br />
MyName{<br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn"><v /></span><br />
<div class="chapter"><br />
<span class="fn"><v /></span><br />
</div><br />
</div><br />
</div><br />
}<br />
</nowiki></pre><br />
<br />
Inside the web page we use:<br />
<pre><nowiki><br />
<struct class="MyName"><br />
<v>1st variable</v><br />
<v>2nd variable</v><br />
</struct><br />
</nowiki></pre><br />
<br />
IF, one variable should NOT be displayed by the browser, we would use <var val="..." /> instead, e.g.:<br />
<pre><nowiki><br />
<div class="geo"><br />
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <br />
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr><br />
</div><br />
</nowiki></pre><br />
<br />
Would become:<br />
* the microformats definition page<br />
<pre><nowiki><br />
MyGeoStructure{<br />
<div class="geo"><br />
<abbr class="latitude" title=v><v /></abbr> <br />
<abbr class="longitude" title=v><v /></abbr><br />
</div><br />
}<br />
</nowiki></pre><br />
<br />
* the web page<br />
<pre><nowiki><br />
<struct class="MyGeoStructure"><br />
<v "37.408183" /><v>N 37° 24.491</v><br />
<v "-122.13855" /><v>W 122° 08.313</v><br />
</struct><br />
</nowiki></pre><br />
<br />
<br />
- discussion opened by [[discoleo|Leonard Mada]]</div>Discoleohttp://microformats.org/wiki/index.php?title=issues&diff=10445issues2006-11-23T11:37:22Z<p>Discoleo: /* Bloated Format */ Examples added</p>
<hr />
<div><br />
Issues which apply to more than one microforamt.<br />
<br />
==Bloated Format==<br />
<br />
=== The Problem ===<br />
Unfortunately, current microformats implementation consume a vast amount of space. The complexity will increase even more, when wanting to ''solve/add'' more complex issues. A direct consequence of this is a '''bloated format''':<br />
* some of the markup is really bloated<br />
** instead of a number, we end sometimes with a whole '''new paragraph''' of markup<br />
** however, in order to be complete, the markup might need to be so<br />
** nevertheless, having a page with 1000 data points will be a horror scenario<br />
<br />
<br />
Therefore, I proposed to open this new brainstorming session/page on how to efficiently implement the microformats in web pages.<br />
<br />
=== Ideas/ Solutions ===<br />
<br />
If we think a little bit back about '''css''', one of the main reasons of its development was:<br />
* to separate content from style<br />
** page code becomes more easy to '''understand'''<br />
** and to '''maintain'''<br />
** and often the '''size''' shrinks significantly<br />
<br />
We must learn this lesson when dealing with microformats. Specifically, the following issues are important:<br />
* extensive microformat markup inside the page code will significantly reduce the readability of the code<br />
* repeating the markup will increase page size<br />
* it will become more difficult to maintain/change the page<br />
<br />
'''Solution'''<br />
* '''define microformat classes'''<br />
** e.g. in the page header, or<br />
** in a separate file (see later)<br />
* define '''abbreviations (qasi tags)''' to those classes<br />
** use actually only the abbrevioations inside the web page, instead of the '''whole paragraph''' of markup<br />
<br />
<br />
* define the microformat classes inside a '''separate file''' (similarly to the css)<br />
** this file needs NOT to be downloaded automatically<br />
*** you do NOT need it for displaying the data<br />
*** it is only needed when wanting to import the data somewhere<br />
*** most viewers, however, only view the data<br />
** let the browser automatically download this file, only IF:<br />
*** there is enough bandwidth<br />
*** the user wants to copy that data<br />
*** the user wants to explicitly save the whole page<br />
** when the user wants to copy an item<br />
*** the web browser should acces that ''microformats'' additional page and<br />
*** download only the relevant class (NO need to actually download the whole page)<br />
*** '''EXTEND html protocol to be able to download ''web-file/class-defined-inside-file'' '''without beeing necessary to download the whole file<br />
<br />
=== Requirements ===<br />
<br />
New Tags:<br />
* '''<struct> ... </struct>''': like the C/C++ struct, will define the microformats structure<br />
* '''<var> ... </var>''': will define the part inside ''struct'' that should be replaced<br />
* '''<var ... />''': similarly to point above, but NOT displayed by browser<br />
** '''<var>''' could be shortend to '''<v>''', to further reduce file size<br />
<br />
=== Examples ===<br />
<br />
Lets take this code:<br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn">Book Title</span><br />
<div class="chapter"><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</div><br />
</div><br />
<br />
We would define this in the header like this:<br />
<struct><br />
MyName{<br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn"><var /></span><br />
<div class="chapter"><br />
<span class="fn"><var /></span><br />
</div><br />
</div><br />
</div><br />
}<br />
</struct><br />
<br />
or in a separate microformats file (NO struct needed):<br />
MyName{<br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn"><var /></span><br />
<div class="chapter"><br />
<span class="fn"><var /></span><br />
</div><br />
</div><br />
</div><br />
}<br />
<br />
Inside the web page we use:<br />
<struct class="MyName"><br />
<var>This is the first variable</var><br />
<var>This text is put in the 2nd variable</var><br />
</struct><br />
<br />
IF, one variable should NOT be displayed by the browser, we would use <var val="..." /> instead, e.g.:<br />
<div class="geo"><br />
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <br />
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr><br />
</div><br />
<br />
Would become:<br />
* the microformats definition page<br />
MyGeoStructure{<br />
<div class="geo"><br />
<abbr class="latitude" title=var><var /></abbr> <br />
<abbr class="longitude" title=var><var /></abbr><br />
</div><br />
}<br />
<br />
* the web page<br />
<struct class="MyGeoStructure"><br />
<var "37.408183" /><var>N 37° 24.491</var><br />
<var "-122.13855" /><var>W 122° 08.313</var><br />
</struct><br />
<br />
<br />
- discussion opened by [[discoleo|Leonard Mada]]</div>Discoleohttp://microformats.org/wiki/index.php?title=measure&diff=10438measure2006-11-22T18:06:37Z<p>Discoleo: /* Matrices */ ONE vs Multiple measuremnets?</p>
<hr />
<div>= Measure microformat =<br />
<br />
Currently this microformat is in exploratory stage. Contributions should focus on real examples from the Web, existing formats/encoding of measures.<br />
<br />
== The problem ==<br />
<br />
Measures (e.g. weights, sizes, temperatures) occur frequently on the Web, but they differ from locale to locale (e.g. Fahrenheit vs. Celsius, pound versus Kilogram) making comparison and matching of offerings difficult.<br />
<br />
The Measurement Unit microformat will enable unambiguous description of measures and as a result easier comparison and matching of offerings.<br />
<br />
== Related microformats ==<br />
<br />
* [[job-listing]] can use time measure for specify per what period of time the salary is for.<br />
* [[hlisting]] product dimensions; weight/mass; time period (as above). <br />
* [[directions-examples]] can use length measure for mileage and time to go from one point to the next.<br />
* [[recipe-examples]] can use weight, volume and time measure for ingredients and preparation time.<br />
* [[currency]] can be viewed as a measurement unit, or as a component of a measurement unit, as in $ per hour.<br />
<br />
== Measurement Classification ==<br />
<br />
Because it is easier to provide examples, I will first list examples.<br />
<br />
=== Categorical Data ===<br />
<br />
* Various measurements may produce '''NON-Numerical''' values<br />
** a pain scale: '''most severe''', '''very severe''', '''severe''', ...<br />
<br />
=== A Single Value / Data Point ===<br />
<br />
* the distance between 2 cities is '''40 km'''<br />
* the velocity is '''62 mph'''<br />
* ...<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 />
=== 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 />
** the surface was 2 x 3 square feet ???<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 />
== Contributors ==<br />
* Guillaume Lebleu<br />
* [[User:AndyMabbett|Andy Mabbett]]<br />
<br />
==References==<br />
*[http://www.bipm.org/en/si/ International System of Units (SI)]<br />
**[http://en.wikipedia.org/wiki/International_System_of_Units (Wikipedia)]<br />
<br />
==See also==<br />
* [[currency]]<br />
* [[measure-formats]]<br />
* [[measure-examples]]<br />
* [[measure-brainstorming]]</div>Discoleohttp://microformats.org/wiki/index.php?title=measure&diff=10436measure2006-11-22T18:01:18Z<p>Discoleo: /* An Interval Measurement */ minor spelling correction</p>
<hr />
<div>= Measure microformat =<br />
<br />
Currently this microformat is in exploratory stage. Contributions should focus on real examples from the Web, existing formats/encoding of measures.<br />
<br />
== The problem ==<br />
<br />
Measures (e.g. weights, sizes, temperatures) occur frequently on the Web, but they differ from locale to locale (e.g. Fahrenheit vs. Celsius, pound versus Kilogram) making comparison and matching of offerings difficult.<br />
<br />
The Measurement Unit microformat will enable unambiguous description of measures and as a result easier comparison and matching of offerings.<br />
<br />
== Related microformats ==<br />
<br />
* [[job-listing]] can use time measure for specify per what period of time the salary is for.<br />
* [[hlisting]] product dimensions; weight/mass; time period (as above). <br />
* [[directions-examples]] can use length measure for mileage and time to go from one point to the next.<br />
* [[recipe-examples]] can use weight, volume and time measure for ingredients and preparation time.<br />
* [[currency]] can be viewed as a measurement unit, or as a component of a measurement unit, as in $ per hour.<br />
<br />
== Measurement Classification ==<br />
<br />
Because it is easier to provide examples, I will first list examples.<br />
<br />
=== Categorical Data ===<br />
<br />
* Various measurements may produce '''NON-Numerical''' values<br />
** a pain scale: '''most severe''', '''very severe''', '''severe''', ...<br />
<br />
=== A Single Value / Data Point ===<br />
<br />
* the distance between 2 cities is '''40 km'''<br />
* the velocity is '''62 mph'''<br />
* ...<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 />
=== 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 />
<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 />
== Contributors ==<br />
* Guillaume Lebleu<br />
* [[User:AndyMabbett|Andy Mabbett]]<br />
<br />
==References==<br />
*[http://www.bipm.org/en/si/ International System of Units (SI)]<br />
**[http://en.wikipedia.org/wiki/International_System_of_Units (Wikipedia)]<br />
<br />
==See also==<br />
* [[currency]]<br />
* [[measure-formats]]<br />
* [[measure-examples]]<br />
* [[measure-brainstorming]]</div>Discoleohttp://microformats.org/wiki/index.php?title=measure&diff=10435measure2006-11-22T18:00:38Z<p>Discoleo: /* An Interval Measurement */</p>
<hr />
<div>= Measure microformat =<br />
<br />
Currently this microformat is in exploratory stage. Contributions should focus on real examples from the Web, existing formats/encoding of measures.<br />
<br />
== The problem ==<br />
<br />
Measures (e.g. weights, sizes, temperatures) occur frequently on the Web, but they differ from locale to locale (e.g. Fahrenheit vs. Celsius, pound versus Kilogram) making comparison and matching of offerings difficult.<br />
<br />
The Measurement Unit microformat will enable unambiguous description of measures and as a result easier comparison and matching of offerings.<br />
<br />
== Related microformats ==<br />
<br />
* [[job-listing]] can use time measure for specify per what period of time the salary is for.<br />
* [[hlisting]] product dimensions; weight/mass; time period (as above). <br />
* [[directions-examples]] can use length measure for mileage and time to go from one point to the next.<br />
* [[recipe-examples]] can use weight, volume and time measure for ingredients and preparation time.<br />
* [[currency]] can be viewed as a measurement unit, or as a component of a measurement unit, as in $ per hour.<br />
<br />
== Measurement Classification ==<br />
<br />
Because it is easier to provide examples, I will first list examples.<br />
<br />
=== Categorical Data ===<br />
<br />
* Various measurements may produce '''NON-Numerical''' values<br />
** a pain scale: '''most severe''', '''very severe''', '''severe''', ...<br />
<br />
=== A Single Value / Data Point ===<br />
<br />
* the distance between 2 cities is '''40 km'''<br />
* the velocity is '''62 mph'''<br />
* ...<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 level 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 />
=== 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 />
<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 />
== Contributors ==<br />
* Guillaume Lebleu<br />
* [[User:AndyMabbett|Andy Mabbett]]<br />
<br />
==References==<br />
*[http://www.bipm.org/en/si/ International System of Units (SI)]<br />
**[http://en.wikipedia.org/wiki/International_System_of_Units (Wikipedia)]<br />
<br />
==See also==<br />
* [[currency]]<br />
* [[measure-formats]]<br />
* [[measure-examples]]<br />
* [[measure-brainstorming]]</div>Discoleohttp://microformats.org/wiki/index.php?title=Main_Page&diff=29336Main Page2006-11-22T17:40:20Z<p>Discoleo: /* Exploratory Discussions */</p>
<hr />
<div>__NOTOC__<br />
=Microformats Wiki=<br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. <br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]] {{NewMarker}}<br />
* [[hresume|hResume]] {{NewMarker}}<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* '''bloated format''':<br />
** some of the markup is really bloated<br />
** instead of a number, we end sometimes with a whole '''new paragraph''' of markup<br />
** however, in order to be complete, the markup might need to be so<br />
** nevertheless, having a page with 1000 data points will be a horror scenario<br />
** I propose to open a new brainstorming session/page on how to efficiently implement the microformats in web pages, e.g.:<br />
*** define the classes in the page header<br />
*** define '''abbreviations''' to those classes<br />
*** use actually only the abbrevioations inside the web page, instead of the '''whole paragraph''' of markup<br />
** another interseting implementation idea would be:<br />
*** define the microformat classes inside a '''separate file''' (similarly to the css)<br />
*** this file needs NOT to be downloaded automatically<br />
**** you do NOT need it for displaying the data<br />
**** it is only needed when wanting to import the data somewhere<br />
**** most viewers, however, only view the data<br />
*** let the browser automatically download this file, only IF:<br />
**** there is enough bandwidth<br />
**** the user wants to copy that data<br />
**** the user wants to explicitly save the whole page<br />
*** when the user wants to copy an item<br />
**** the web browser should acces that ''microformats'' additional page and<br />
**** download only the relevant class (NO need to actually download the whole page)<br />
**** '''EXTEND html protocol to be able to download ''web-file/class-defined-inside-file'' '''without beeing necessary to download the whole file<br />
** discussion opened by [[discoleo|Leonard Mada]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}<br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] {{NewMarker}}<br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[hproduct|hProduct]] - [[hproduct-brainstorming|hProduct brainstorming]] | [[hproduct-feedback|hProduct discussion]] | [[hproduct-examples|hProduct examples]] {{NewMarker}}<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]] {{NewMarker}}<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{NewMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]]. {{NewMarker}}<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] {{NewMarker}}<br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
<br />
== Tools & Test Cases & Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]] {{NewMarker}}<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 50 articles<br />
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
* languages with over 2 articles<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
** [[Main_Page-es|Español (Spanish)]]<br />
* languages with 2 articles<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are offsite pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])</div>Discoleohttp://microformats.org/wiki/index.php?title=Main_Page&diff=29335Main Page2006-11-22T17:38:03Z<p>Discoleo: /* Exploratory Discussions */</p>
<hr />
<div>__NOTOC__<br />
=Microformats Wiki=<br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. <br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]] {{NewMarker}}<br />
* [[hresume|hResume]] {{NewMarker}}<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* '''bloated format''':<br />
** some of the markup is really bloated<br />
** instead of a number, we end sometimes with a whole '''new paragraph''' of markup<br />
** however, in order to be complete, the markup might need to be so<br />
** nevertheless, having a page with 1000 data points will be a horror scenario<br />
** I propose to open a new brainstorming session/page on how to efficiently implement the microformats in web pages, e.g.:<br />
*** define the classes in the page header<br />
*** define '''abbreviations''' to those classes<br />
*** use actually only the abbrevioations inside the web page, instead of the '''whole paragraph''' of markup<br />
** another interseting implementation idea would be:<br />
*** define the microformat classes inside a '''separate file''' (similarly to the css)<br />
*** this file needs NOT to be downloaded automatically<br />
**** you do NOT need it for displaying the data<br />
**** it is only needed when wanting to import the data somewhere<br />
**** most viewers, however, only view the data<br />
*** let the browser automatically download this file, only IF:<br />
**** there is enough bandwidth<br />
**** the user wants to copy that data<br />
**** the user wants to explicitly save the whole page<br />
*** when the user wants to copy an item<br />
**** the web browser should acces that ''microformats'' additional page and<br />
**** download only the relevant class (NO need to actually download the whole page)<br />
**** '''EXTEND html protocol to be able to download ''web-file/class-defined-inside-file'' '''without beeing necessary to download the whole file<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}<br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] {{NewMarker}}<br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[hproduct|hProduct]] - [[hproduct-brainstorming|hProduct brainstorming]] | [[hproduct-feedback|hProduct discussion]] | [[hproduct-examples|hProduct examples]] {{NewMarker}}<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]] {{NewMarker}}<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{NewMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]]. {{NewMarker}}<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] {{NewMarker}}<br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
<br />
== Tools & Test Cases & Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]] {{NewMarker}}<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 50 articles<br />
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
* languages with over 2 articles<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
** [[Main_Page-es|Español (Spanish)]]<br />
* languages with 2 articles<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are offsite pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])</div>Discoleohttp://microformats.org/wiki/index.php?title=Main_Page&diff=29334Main Page2006-11-22T17:25:42Z<p>Discoleo: /* Exploratory Discussions */</p>
<hr />
<div>__NOTOC__<br />
=Microformats Wiki=<br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. <br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]] {{NewMarker}}<br />
* [[hresume|hResume]] {{NewMarker}}<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* '''bloated format''':<br />
** some of the markup is really bloated<br />
** instead of a number, we end sometimes with a whole '''new paragraph''' of markup<br />
** however, in order to be complete, the markup might need to be so<br />
** nevertheless, having a page with 1000 data points will be a horror scenario<br />
** I propose to open a new brainstorming session/page on how to efficiently implement the microformats in web pages, e.g.:<br />
*** define the classes in the page header<br />
*** define '''abbreviations''' to those classes<br />
*** use actually only the abbrevioations inside the web page, instead of the '''whole paragraph''' of markup<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}<br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] {{NewMarker}}<br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[hproduct|hProduct]] - [[hproduct-brainstorming|hProduct brainstorming]] | [[hproduct-feedback|hProduct discussion]] | [[hproduct-examples|hProduct examples]] {{NewMarker}}<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]] {{NewMarker}}<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{NewMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]]. {{NewMarker}}<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] {{NewMarker}}<br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
<br />
== Tools & Test Cases & Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]] {{NewMarker}}<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 50 articles<br />
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
* languages with over 2 articles<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
** [[Main_Page-es|Español (Spanish)]]<br />
* languages with 2 articles<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are offsite pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])</div>Discoleohttp://microformats.org/wiki/index.php?title=measure&diff=10425measure2006-11-22T17:00:12Z<p>Discoleo: /* Measurment Classification */</p>
<hr />
<div>= Measure microformat =<br />
<br />
Currently this microformat is in exploratory stage. Contributions should focus on real examples from the Web, existing formats/encoding of measures.<br />
<br />
== The problem ==<br />
<br />
Measures (e.g. weights, sizes, temperatures) occur frequently on the Web, but they differ from locale to locale (e.g. Fahrenheit vs. Celsius, pound versus Kilogram) making comparison and matching of offerings difficult.<br />
<br />
The Measurement Unit microformat will enable unambiguous description of measures and as a result easier comparison and matching of offerings.<br />
<br />
== Related microformats ==<br />
<br />
* [[job-listing]] can use time measure for specify per what period of time the salary is for.<br />
* [[hlisting]] same as for job listing.<br />
* [[directions-examples]] can use length measure for mileage and time to go from one point to the next.<br />
* [[recipe-examples]] can use weight, volume and time measure for ingredients and preparation time.<br />
* [[currency]] can be viewed as a measurement unit, or as a component of a measurement unit, as in $ per hour.<br />
<br />
<br />
== Measurment Classification ==<br />
<br />
Because it is easier to provide examples, I will first list examples.<br />
<br />
=== Categorical Data ===<br />
<br />
* Various measuremnts may produce '''NON-Numerical''' values<br />
** a pain scale: '''most severe''', '''very severe''', '''severe''', ...<br />
<br />
=== A Single Value / Data Point ===<br />
<br />
* the distance between 2 cities is '''40 km'''<br />
* the velocity is '''62 mph'''<br />
* ...<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 />
<br />
=== Matrices ===<br />
<br />
* the GPS coordinates are '''12°14' N and 25°55' E'''<br />
* the dimension of the box is '''3m x 2m x 0.55m'''<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 Precission ====<br />
<br />
'''QUESTIONS'''<br />
* How detailed should a measuremnt be stored?<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 measurment 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 />
== Contributors ==<br />
* Guillaume Lebleu<br />
* [[User:AndyMabbett|Andy Mabbett]]<br />
<br />
==References==<br />
*[http://www.bipm.org/en/si/ International System of Units (SI)]<br />
**[http://en.wikipedia.org/wiki/International_System_of_Units (Wikipedia)]<br />
<br />
==See also==<br />
* [[currency]]<br />
* [[measure-formats]]<br />
* [[measure-examples]]<br />
* [[measure-brainstorming]]</div>Discoleohttp://microformats.org/wiki/index.php?title=measure&diff=10423measure2006-11-22T16:00:33Z<p>Discoleo: /* Related microformats */</p>
<hr />
<div>= Measure microformat =<br />
<br />
Currently this microformat is in exploratory stage. Contributions should focus on real examples from the Web, existing formats/encoding of measures.<br />
<br />
== The problem ==<br />
<br />
Measures (e.g. weights, sizes, temperatures) occur frequently on the Web, but they differ from locale to locale (e.g. Fahrenheit vs. Celsius, pound versus Kilogram) making comparison and matching of offerings difficult.<br />
<br />
The Measurement Unit microformat will enable unambiguous description of measures and as a result easier comparison and matching of offerings.<br />
<br />
== Related microformats ==<br />
<br />
* [[job-listing]] can use time measure for specify per what period of time the salary is for.<br />
* [[hlisting]] same as for job listing.<br />
* [[directions-examples]] can use length measure for mileage and time to go from one point to the next.<br />
* [[recipe-examples]] can use weight, volume and time measure for ingredients and preparation time.<br />
* [[currency]] can be viewed as a measurement unit, or as a component of a measurement unit, as in $ per hour.<br />
<br />
<br />
== Measurment Classification ==<br />
<br />
Because it is easier to provide examples, I will first list examples.<br />
<br />
=== Categorical Data ===<br />
<br />
* Various measuremnts may produce '''NON-Numerical''' values<br />
** a pain scale: '''most severe''', '''very severe''', '''severe''', ...<br />
<br />
=== A Single Value / Data Point ===<br />
<br />
* the distance between 2 cities is '''40 km'''<br />
* the velocity is '''62 mph'''<br />
* ...<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 />
<br />
=== Matrices ===<br />
<br />
* the GPS coordinates are '''12°14' N and 25°55' E'''<br />
* the dimension of the box is '''3m x 2m x 0.55m'''<br />
<br />
=== Measurement Scales ===<br />
<br />
==== Accuracy vs Precission ====<br />
<br />
'''QUESTIONS'''<br />
* How detailed should a measuremnt be stored?<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 />
<br />
== Contributors ==<br />
* Guillaume Lebleu<br />
* [[User:AndyMabbett|Andy Mabbett]]<br />
<br />
==References==<br />
*[http://www.bipm.org/en/si/ International System of Units (SI)]<br />
**[http://en.wikipedia.org/wiki/International_System_of_Units (Wikipedia)]<br />
<br />
==See also==<br />
* [[currency]]<br />
* [[measure-formats]]<br />
* [[measure-examples]]<br />
* [[measure-brainstorming]]</div>Discoleohttp://microformats.org/wiki/index.php?title=currency-examples&diff=9542currency-examples2006-10-17T20:09:50Z<p>Discoleo: /* The Problem */</p>
<hr />
<div>= Currency Examples =<br />
The following are real-world examples and brainstorming for marking up '''[[currency]]'''..<br />
<br />
== The Problem ==<br />
<br />
<p>The problem: how to explicitly specify a) that a figure/number relates to money; and b) the currency of a stated figure.</p><br />
<br />
<ul><br />
<li>The currency sign cannot be used reliably since the same sign (or symbol) may represent more than one currency. eg. $ is used for many different dollars (USD, AUD, CAD...) and even [http://en.wikipedia.org/wiki/Currency_sign#Examples other units like pesos].</li><br />
<li>The language of the page is not sufficient to define the currency of prices in the page:<br />
<ul><br />
<li>More than one currency may be used by people who speak the same language.</li><br />
<li>The page may be written in one language and still quote prices/figures in a different country's currency.</li><br />
<li>Even if a country can be identified, more than one currency may be used in that country.</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<p>Converting currency figures is a reasonably easy problem to solve as indicated by the [[#Existing_Practices]]. However many automated conversion tools must make assumptions about the original figure's currency - eg. assuming a USD for all uses of $, or British Pounds for £ (which is also [http://en.wikipedia.org/wiki/Lira sometimes used to denote Lira]).</p><br />
<br />
<br />
=== Currency Changes ===<br />
I wish to expand on one of the points mentioned above: there might be two or more currencies in the same country: e.g. in Romania<br />
* ROL Romania, Lei [being phased out]<br />
* RON Romania, New Lei<br />
* after Romania will join the EU, the RON will be replaced by Euro, too (not imediately, probably in 2-3 years)<br />
<br />
Although the three letter code is different in this case, the currency is often given as ''Lei''. There are other countries, where similar examples exist/existed. The two currencies might have an identical name, yet they have 2 very different meanings. Usually there is a difference of 3-4 orders of magnitude between the old currency and the new currency.<br />
[[discoleo]]<br />
<br />
<br />
===Related problems===<br />
<p>"Amounts" in arbitrary units is a bit harder and necessary for several applications.</p><br />
<br />
<p>For example, consider the work that has been done on a recipe microformat.</p><br />
<br />
[[recipe-examples]]<br />
<br />
<p>Though we haven't reached this problem yet in the research, I can see it<br />
coming:</p><br />
<br />
<p>Say you wanted to create a "shopping list" application which you could tell which recipes you wanted to cook, and have it automatically total up all the various amounts of ingredients and give you the net amount of stuff you wanted to pick up.</p><br />
<br />
<p>It would need to be able to determine precise amounts/units of each ingredient. This might turn out to be like the currency problem, or it might be more complex, given the variety of units used in recipes, English vs. metric etc. That's a case that might need a microformat. We need more research and analysis to really justify it, but I can see it within the realm of probable possibility.</p><br />
<br />
===Use of currency amounts in tables===<br />
<br />
Representing currency amounts in a table format is very common. For instance, see [http://investor.google.com/fin_data.html Google Financials].<br />
<br />
In this table representation, it does not make sense to provide the currency information for each cell. Instead, it should be provided once at the table, thead, tr, or th, level, and then a td may override the default value. This is very similar to the common practice of indicating the currency and formatting in plain english: "Numbers in thousands of dollars" in the table title/subtitle or legend.<br />
<br />
The microformat for currency amounts should provide a way to represent a default currency for all children of a table, thead, tr, or th nodes. <br />
The currency symbol/abbreviation should be optional in for elements defined as containing currency values/amounts, if a default currency has been defined in one of the ancestor elements.<br />
<br />
==Contributors==<br />
* [http://weblog.200ok.com.au/ Ben Buchanan] (proponent)<br />
* Arve Bersvendsen<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* [http://steve.ganz.name/ Steve Ganz]<br />
* Charles Iliya Krempeaux <br />
*[[User:AndyMabbett|Andy Mabbett]] (2nd proponent)<br />
* Ciaran McNulty<br />
* Mike Stickel<br />
* Ben Ward<br />
* Guillaume Lebleu<br />
<br />
== Real-World Examples ==<br />
''Links to public web pages, either popular or insightful''<br />
<br />
=== [http://enterpriseforum.mit.edu/mindshare/startingup/dilution.html MIT Enterprise Forum ] ===<br />
<br />
<pre>$1 million in equity</pre><br />
<br />
<pre>$2.50 a share</pre><br />
<br />
See also [[measure]]<br />
<br />
=== [http://tonto.eia.doe.gov/oog/info/ngw/historical/2004/06_24/ngupdate.asp Energy Information Administration] ===<br />
<br />
<pre>23 cents per barrel</pre><br />
<br />
Also in this [http://www.eia.doe.gov/emeu/international/oilprice.html page]:<br />
<br />
<pre>(U.S. Cents per Gallon)</pre><br />
<br />
<pre>(Euros per Thousand Liters)</pre><br />
<br />
<pre>(U.S. Dollars per Gallon)</pre><br />
<br />
See also [[measure]]<br />
<br />
=== [http://www.cbc.ca/money/story/2005/08/08/oil-050808.html CBCNews] ===<br />
<br />
<pre>$63.94 US per barrel, up $1.63 US</pre><br />
<br />
=== [http://finance.google.com/finance?q=google&hl=en Google Finance] ===<br />
<br />
The current price of a stock:<br />
<br />
<pre><span class="pr">401.90</span></pre><br />
<br />
=== [http://www.ebay.com eBay] ===<br />
<br />
eBay marks prices as "ebcPr". eBay c? Price.<br />
<br />
<pre><br />
<td class="ebcPr"><span class="bold">$11.70</span><br/><span>$12.95</span><br/></td><br />
</pre><br />
<br />
=== [http://code.google.com/webstats/2005-12/classes.html Google] ===<br />
<br />
The Google Web Authoring Statistics mentions that "price" is the 40th most used class name.<br />
<br />
Something like:<br />
<br />
<pre><br />
<span class="price">$39.99</span><br />
</pre><br />
<br />
=== [http://us.mcafee.com/root/package.asp?pkgid=100 McAfee] ===<br />
<pre><br />
<span class="price">$39.99 <span class="currency">(USD)</span></span><br />
</pre><br />
<br />
=== [http://www.amazon.com/gp/product/0764597582/sr=8-9/qid=1153301402/ref=sr_1_9/002-9103678-0608852?ie=UTF8 Amazon] ===<br />
<br />
<pre><td class="price">$34.85</td></pre><br />
<br />
=== [https://secure.vmp.com/signup/adv_signup.php?locale=fr_CA Bell Canada in French Canadian] ===<br />
<br />
<pre><b>Niveau de service Premium - 125 $*</b></pre><br />
<br />
Note the placement of the dollar sign AFTER the number.<br />
<br />
=== [https://secure.vmp.com/signup/adv_signup.php?locale=en_US Bell Canada in US English] ===<br />
<br />
<pre><b>Premium Service Level - $125*</b></pre><br />
<br />
===Historic prices===<br />
*[http://www.westmidlandbirdclub.com/biblio/worcs.htm#MalvernHand West Midland Bird Club Bibliography] (Published prices of old books)<br />
*[http://www.westmidlandbirdclub.com/reviews/rarer.htm West Midland Bird Club CD-ROM review] (price at time of review; since reduced)<br />
*[http://en.wikipedia.org/wiki/Bleak_House#Original_publication Wikipedia: Bleak House]<br />
**"Like most Dickens novels, Bleak House was published in 19 monthly instalments, each containing 32 pages of text and two illustrations by Phiz. Each cost one shilling, except for the last, which was a double issue and cost two." Dates in the subsequent table range monthly from March 1852 - September 1853<br />
*[http://en.wikipedia.org/wiki/1922_in_Germany#Inflation_and_Repercussions Wikpedia: 1922 in Germany]<br />
**"Despite the ending of cash payments for the rest of 1922, the main cause of Germany's inability to pay, the steady depreciation of the mark, was ongoing. Towards the end of the year it assumed a disastrous rapidity. On August 1, the US Dollar still stood at 643 Marks to the Dollar and the British Pound at 2,850 Marks to the Pound. But on September 5 the dollar had already risen to 1,440 Marks and the pound to 6,525 Marks, and in December the pound was worth between 30,000 and 40,000 marks and the dollar between 7,000 and 9,000."<br />
*[http://news.bbc.co.uk/1/hi/business/1096916.stm BBC News story dated 2 January, 2001]<br />
**"A barrel of Brent crude for February delivery came within range of $25 a barrel on Tuesday before slipping to $24.35, a closing price 48 cents above Friday's closing price of $23.87. In New York, the price of Nymex (New York Merchantile Exchange) crude reached $27.40 a barrel before settling at $27.40, a gain of 41 cents or 1.5% on the day. Nymex oil prices in 2000 averaged $30.20 a barrel, the highest level since 1983, and well above the 1999 average of $19.25. Traders also saw support for the oil price from the Opec basket of seven crude oils which stood at $21.75 a barrell on 29 December 2000. That was the seventh day the price stayed below a preferred range of $22-$28 a barrell. Under an Opec price stability measure, output will be cut by 500,000 barrels a day if the basket price stay below $22 for more than 10 days."<br />
*[http://news.bbc.co.uk/1/hi/uk/911569.stm BBC News story dated 5 September, 2000]<br />
**"The Millennium Commission's decision to grant an extra £47m to the Dome has been widely condemned by MPs on various political hues."<br />
*[http://www.jamaica-gleaner.com/pages/history/story0014.html Jamaica and the Great War]<br />
**"in 1917 [...] unemployment was high and wages were low - men received 9 pence a day to cut cane."<br />
*[http://www.wilkiecollins.demon.co.uk/coinage/coins.htm Money and Coinage in Victorian Britain]<br />
*[http://www.margaretmorgan.com/wesley/state.html Macaulay on the State of England in 1685]<br />
**"In 1661 the justices at Chelmsford had fixed the wages of the Essex labourer, who was not boarded, at six shillings in winter and seven in summer."<br />
*[http://www.bbc.co.uk/ww2peopleswar/stories/74/a4095074.shtml BBC - WW2 People's War]<br />
**"I left [school] at Easter 1938. As soon as I had left school, my Father insisted that I went to work for my Uncle. My wages were 5 shillings per week plus board & lodgings"<br />
*[http://privatewww.essex.ac.uk/~alan/family/N-Money.html Relative Value of Sums of Money]<br />
<br />
== Existing Practices ==<br />
<br />
===Firefox Extension===<br />
[http://viewmycurrency.wordpress.com/about/ Firefox Currency Converter - ViewMyCurrency]<br />
<br />
<p>Note: the [http://viewmycurrency.backpackit.com/pub/403081 current bug list] illustrates some problems of identifying currencies based on page content alone:</p><br />
<blockquote><br />
<ul><br />
<li>All $ symbols are treated as USD Very annoying if you are Australian, Canadian etc. (Needs a new feature)</li><br />
<li>‘Euro 2006 Championship’ should not be converted.</li><br />
<li>...</li><br />
<li>Don’t convert CVS keywords . $Revision: 1.3 $ should not be treated as dollars.</li><br />
</ul><br />
</blockquote><br />
<br />
===Greasemonkey Scripts ===<br />
[http://nybblelabs.org.uk/projects/exchequer Exchequer]<br />
<br />
[http://6v8.gamboni.org/Greasemonkey-Yahoo-Finance.html Yahoo! Finance Currency Converter]<br />
<br />
===Relevant Standards ===<br />
[http://www.xe.com/iso4217.htm ISO 4217 Codes]<br />
<br />
<br />
<br />
== See Also ==<br />
* [[currency-brainstorming]]<br />
**[[currency-brainstorming#Straw man proposal]]<br />
* [[abbr-design-pattern]]</div>Discoleohttp://microformats.org/wiki/index.php?title=currency-examples&diff=9541currency-examples2006-10-17T20:09:00Z<p>Discoleo: /* The Problem */</p>
<hr />
<div>= Currency Examples =<br />
The following are real-world examples and brainstorming for marking up '''[[currency]]'''..<br />
<br />
== The Problem ==<br />
<br />
<p>The problem: how to explicitly specify a) that a figure/number relates to money; and b) the currency of a stated figure.</p><br />
<br />
<ul><br />
<li>The currency sign cannot be used reliably since the same sign (or symbol) may represent more than one currency. eg. $ is used for many different dollars (USD, AUD, CAD...) and even [http://en.wikipedia.org/wiki/Currency_sign#Examples other units like pesos].</li><br />
<li>The language of the page is not sufficient to define the currency of prices in the page:<br />
<ul><br />
<li>More than one currency may be used by people who speak the same language.</li><br />
<li>The page may be written in one language and still quote prices/figures in a different country's currency.</li><br />
<li>Even if a country can be identified, more than one currency may be used in that country.</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<p>Converting currency figures is a reasonably easy problem to solve as indicated by the [[#Existing_Practices]]. However many automated conversion tools must make assumptions about the original figure's currency - eg. assuming a USD for all uses of $, or British Pounds for £ (which is also [http://en.wikipedia.org/wiki/Lira sometimes used to denote Lira]).</p><br />
<br />
I wish to expand on one of the points mentioned above: there might be two or more currencies in the same country: e.g. in Romania<br />
* ROL Romania, Lei [being phased out]<br />
* RON Romania, New Lei<br />
* after Romania will join the EU, the RON will be replaced by Euro, too (not imediately, probably in 2-3 years)<br />
<br />
Although the three letter code is different in this case, the currency is often given as ''Lei''. There are other countries, where similar examples exist/existed. The two currencies might have an identical name, yet they have 2 very different meanings. Usually there is a difference of 3-4 orders of magnitude between the old currency and the new currency.<br />
<br />
===Related problems===<br />
<p>"Amounts" in arbitrary units is a bit harder and necessary for several applications.</p><br />
<br />
<p>For example, consider the work that has been done on a recipe microformat.</p><br />
<br />
[[recipe-examples]]<br />
<br />
<p>Though we haven't reached this problem yet in the research, I can see it<br />
coming:</p><br />
<br />
<p>Say you wanted to create a "shopping list" application which you could tell which recipes you wanted to cook, and have it automatically total up all the various amounts of ingredients and give you the net amount of stuff you wanted to pick up.</p><br />
<br />
<p>It would need to be able to determine precise amounts/units of each ingredient. This might turn out to be like the currency problem, or it might be more complex, given the variety of units used in recipes, English vs. metric etc. That's a case that might need a microformat. We need more research and analysis to really justify it, but I can see it within the realm of probable possibility.</p><br />
<br />
===Use of currency amounts in tables===<br />
<br />
Representing currency amounts in a table format is very common. For instance, see [http://investor.google.com/fin_data.html Google Financials].<br />
<br />
In this table representation, it does not make sense to provide the currency information for each cell. Instead, it should be provided once at the table, thead, tr, or th, level, and then a td may override the default value. This is very similar to the common practice of indicating the currency and formatting in plain english: "Numbers in thousands of dollars" in the table title/subtitle or legend.<br />
<br />
The microformat for currency amounts should provide a way to represent a default currency for all children of a table, thead, tr, or th nodes. <br />
The currency symbol/abbreviation should be optional in for elements defined as containing currency values/amounts, if a default currency has been defined in one of the ancestor elements.<br />
<br />
==Contributors==<br />
* [http://weblog.200ok.com.au/ Ben Buchanan] (proponent)<br />
* Arve Bersvendsen<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* [http://steve.ganz.name/ Steve Ganz]<br />
* Charles Iliya Krempeaux <br />
*[[User:AndyMabbett|Andy Mabbett]] (2nd proponent)<br />
* Ciaran McNulty<br />
* Mike Stickel<br />
* Ben Ward<br />
* Guillaume Lebleu<br />
<br />
== Real-World Examples ==<br />
''Links to public web pages, either popular or insightful''<br />
<br />
=== [http://enterpriseforum.mit.edu/mindshare/startingup/dilution.html MIT Enterprise Forum ] ===<br />
<br />
<pre>$1 million in equity</pre><br />
<br />
<pre>$2.50 a share</pre><br />
<br />
See also [[measure]]<br />
<br />
=== [http://tonto.eia.doe.gov/oog/info/ngw/historical/2004/06_24/ngupdate.asp Energy Information Administration] ===<br />
<br />
<pre>23 cents per barrel</pre><br />
<br />
Also in this [http://www.eia.doe.gov/emeu/international/oilprice.html page]:<br />
<br />
<pre>(U.S. Cents per Gallon)</pre><br />
<br />
<pre>(Euros per Thousand Liters)</pre><br />
<br />
<pre>(U.S. Dollars per Gallon)</pre><br />
<br />
See also [[measure]]<br />
<br />
=== [http://www.cbc.ca/money/story/2005/08/08/oil-050808.html CBCNews] ===<br />
<br />
<pre>$63.94 US per barrel, up $1.63 US</pre><br />
<br />
=== [http://finance.google.com/finance?q=google&hl=en Google Finance] ===<br />
<br />
The current price of a stock:<br />
<br />
<pre><span class="pr">401.90</span></pre><br />
<br />
=== [http://www.ebay.com eBay] ===<br />
<br />
eBay marks prices as "ebcPr". eBay c? Price.<br />
<br />
<pre><br />
<td class="ebcPr"><span class="bold">$11.70</span><br/><span>$12.95</span><br/></td><br />
</pre><br />
<br />
=== [http://code.google.com/webstats/2005-12/classes.html Google] ===<br />
<br />
The Google Web Authoring Statistics mentions that "price" is the 40th most used class name.<br />
<br />
Something like:<br />
<br />
<pre><br />
<span class="price">$39.99</span><br />
</pre><br />
<br />
=== [http://us.mcafee.com/root/package.asp?pkgid=100 McAfee] ===<br />
<pre><br />
<span class="price">$39.99 <span class="currency">(USD)</span></span><br />
</pre><br />
<br />
=== [http://www.amazon.com/gp/product/0764597582/sr=8-9/qid=1153301402/ref=sr_1_9/002-9103678-0608852?ie=UTF8 Amazon] ===<br />
<br />
<pre><td class="price">$34.85</td></pre><br />
<br />
=== [https://secure.vmp.com/signup/adv_signup.php?locale=fr_CA Bell Canada in French Canadian] ===<br />
<br />
<pre><b>Niveau de service Premium - 125 $*</b></pre><br />
<br />
Note the placement of the dollar sign AFTER the number.<br />
<br />
=== [https://secure.vmp.com/signup/adv_signup.php?locale=en_US Bell Canada in US English] ===<br />
<br />
<pre><b>Premium Service Level - $125*</b></pre><br />
<br />
===Historic prices===<br />
*[http://www.westmidlandbirdclub.com/biblio/worcs.htm#MalvernHand West Midland Bird Club Bibliography] (Published prices of old books)<br />
*[http://www.westmidlandbirdclub.com/reviews/rarer.htm West Midland Bird Club CD-ROM review] (price at time of review; since reduced)<br />
*[http://en.wikipedia.org/wiki/Bleak_House#Original_publication Wikipedia: Bleak House]<br />
**"Like most Dickens novels, Bleak House was published in 19 monthly instalments, each containing 32 pages of text and two illustrations by Phiz. Each cost one shilling, except for the last, which was a double issue and cost two." Dates in the subsequent table range monthly from March 1852 - September 1853<br />
*[http://en.wikipedia.org/wiki/1922_in_Germany#Inflation_and_Repercussions Wikpedia: 1922 in Germany]<br />
**"Despite the ending of cash payments for the rest of 1922, the main cause of Germany's inability to pay, the steady depreciation of the mark, was ongoing. Towards the end of the year it assumed a disastrous rapidity. On August 1, the US Dollar still stood at 643 Marks to the Dollar and the British Pound at 2,850 Marks to the Pound. But on September 5 the dollar had already risen to 1,440 Marks and the pound to 6,525 Marks, and in December the pound was worth between 30,000 and 40,000 marks and the dollar between 7,000 and 9,000."<br />
*[http://news.bbc.co.uk/1/hi/business/1096916.stm BBC News story dated 2 January, 2001]<br />
**"A barrel of Brent crude for February delivery came within range of $25 a barrel on Tuesday before slipping to $24.35, a closing price 48 cents above Friday's closing price of $23.87. In New York, the price of Nymex (New York Merchantile Exchange) crude reached $27.40 a barrel before settling at $27.40, a gain of 41 cents or 1.5% on the day. Nymex oil prices in 2000 averaged $30.20 a barrel, the highest level since 1983, and well above the 1999 average of $19.25. Traders also saw support for the oil price from the Opec basket of seven crude oils which stood at $21.75 a barrell on 29 December 2000. That was the seventh day the price stayed below a preferred range of $22-$28 a barrell. Under an Opec price stability measure, output will be cut by 500,000 barrels a day if the basket price stay below $22 for more than 10 days."<br />
*[http://news.bbc.co.uk/1/hi/uk/911569.stm BBC News story dated 5 September, 2000]<br />
**"The Millennium Commission's decision to grant an extra £47m to the Dome has been widely condemned by MPs on various political hues."<br />
*[http://www.jamaica-gleaner.com/pages/history/story0014.html Jamaica and the Great War]<br />
**"in 1917 [...] unemployment was high and wages were low - men received 9 pence a day to cut cane."<br />
*[http://www.wilkiecollins.demon.co.uk/coinage/coins.htm Money and Coinage in Victorian Britain]<br />
*[http://www.margaretmorgan.com/wesley/state.html Macaulay on the State of England in 1685]<br />
**"In 1661 the justices at Chelmsford had fixed the wages of the Essex labourer, who was not boarded, at six shillings in winter and seven in summer."<br />
*[http://www.bbc.co.uk/ww2peopleswar/stories/74/a4095074.shtml BBC - WW2 People's War]<br />
**"I left [school] at Easter 1938. As soon as I had left school, my Father insisted that I went to work for my Uncle. My wages were 5 shillings per week plus board & lodgings"<br />
*[http://privatewww.essex.ac.uk/~alan/family/N-Money.html Relative Value of Sums of Money]<br />
<br />
== Existing Practices ==<br />
<br />
===Firefox Extension===<br />
[http://viewmycurrency.wordpress.com/about/ Firefox Currency Converter - ViewMyCurrency]<br />
<br />
<p>Note: the [http://viewmycurrency.backpackit.com/pub/403081 current bug list] illustrates some problems of identifying currencies based on page content alone:</p><br />
<blockquote><br />
<ul><br />
<li>All $ symbols are treated as USD Very annoying if you are Australian, Canadian etc. (Needs a new feature)</li><br />
<li>‘Euro 2006 Championship’ should not be converted.</li><br />
<li>...</li><br />
<li>Don’t convert CVS keywords . $Revision: 1.3 $ should not be treated as dollars.</li><br />
</ul><br />
</blockquote><br />
<br />
===Greasemonkey Scripts ===<br />
[http://nybblelabs.org.uk/projects/exchequer Exchequer]<br />
<br />
[http://6v8.gamboni.org/Greasemonkey-Yahoo-Finance.html Yahoo! Finance Currency Converter]<br />
<br />
===Relevant Standards ===<br />
[http://www.xe.com/iso4217.htm ISO 4217 Codes]<br />
<br />
<br />
<br />
== See Also ==<br />
* [[currency-brainstorming]]<br />
**[[currency-brainstorming#Straw man proposal]]<br />
* [[abbr-design-pattern]]</div>Discoleohttp://microformats.org/wiki/index.php?title=citation-brainstorming&diff=9256citation-brainstorming2006-09-26T15:00:43Z<p>Discoleo: /* Citing a conference publication */</p>
<hr />
<div><h1> Citation Brainstroming </h1><br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* ...<br />
* ... (a bunch of good folks!)<br />
* Tantek Çelik<br />
* Tim White<br />
* Michael McCracken<br />
<br />
== See also ==<br />
* [[citation]]<br />
* [[citation-examples]]<br />
* [[citation-formats]]<br />
* [[citation-faq]]<br />
<br />
== Use Cases ==<br />
<br />
To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving.<br />
<br />
I've included two, focusing on consuming information - I've assumed that use cases for generating microformatted content would just involve the desire to enable your content to be consumed better, but I'm interested to see if there's something I'm missing here -Mike<br />
<br />
=== Acquiring reference information from the web ===<br />
<br />
A user either finds an author's papers page, or is viewing the results of a search and would like to import the information about the displayed papers into their local reference database, for the purposes of cataloging things they've read, adding notes, and using the information to generate later citations, potentially in other forms, such as BibTeX or Docbook, for inclusion in a publication of their own.<br />
<br />
Notes: In this case, it isn't important to the user what format the citation takes as displayed on the page where they find it. What *is* important is that it contains enough information to allow generation of the format they will ultimately re-publish it in. This implies that it may be worthwhile to err a little on the side of verbosity.<br />
<br />
Also, links to downloadable full representations of the cited work are very important - e.g. a link to the PDF of a journal article, or to a music file.<br />
<br />
=== Subscribing to reading lists, periodicals, etc ===<br />
<br />
I would like to be able to leverage my news aggregator with hAtom to subscribe to a remote source for citation information, for example:<br />
<br />
* a reading list for a seminar<br />
* The publication list for a conference (e.g., subscribe to SIGGRAPH and see the updated conference proceedings every year)<br />
* the issues of a journal<br />
* a particular research group or researcher's publications<br />
* Not just research: a popular author's publications (e.g., [http://www.gladwell.com/archive.html Malcolm Gladwell's Archive])<br />
<br />
=== Aggregating reading lists and reviews ===<br />
<br />
A citation microformat-specific aggregator could provide a decentralized version of [http://citeulike.org/ CiteULike]. Libraries, authors, research groups, and publishers could mark up their collections, while other people on weblogs or review sites could add tags and reviews.<br />
<br />
At least, having a well-adopted microformat would make writing tools like CiteULike much better, since it relies in some cases on screen-scraping publisher web-sites.<br />
<br />
== Original hBib Discussion ==<br />
<br />
During the WWW2005 Developer's Day [[microformats]] track, Rohit Khare gave a [[presentations|presentation]] where he discussed the microformats [[process]], and then did a quick demonstration wherein a bunch of us got on a shared Subethaedit document, and brainstormed some thoughts on what an "hBib" bibliography citation microformat would look like. Rohit placed the [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document on his Commercenet site].<br />
<br />
* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html<br />
<br />
''An attempt to summarize and inline the linked document follows. -Mike''<br />
<br />
Two major goals were outlined by the group:<br />
<br />
* Avoid re-keying references<br />
* Adapt to new journal styles by changing CSS<br />
<br />
The fundamental problem was discussed in terms of display - the ability to transform XHTML+hBib into the many journal-specific formats. For example, how to display "et.al" when all authors are present in the source, and how to re-order the elements if a style defines a set order of elements that conflicts with the ordering in the source. Using hCard for authors was agreed on, and the beginnings of an example were shown.<br />
<br />
== XHTML Structure ==<br />
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.<br />
<br />
* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.<br />
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.<br />
* Perhaps class="hcite" with <code>&lt;cite&gt;</code> recommended as the root element. E.g. <code>&lt;cite class="hcite"&gt;</code><br />
<br />
== Citation vs. [[media-info]] ==<br />
<br />
What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.<br />
<br />
== Semantic Meaning ==<br />
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)<br />
<br />
The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference. ''Does this sentence make sense only historically? -Mike''<br />
<br />
== OCLC's WorldCat for titles == <br />
Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White<br />
<br />
== This and That ==<br />
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)<br />
<br />
The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.<br />
<br />
This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]<br />
<br />
== More on This and That ==<br />
<br />
Citation microformats are being explored as a possibility for citing genealogical information at [http://eatslikeahuman.blogspot.com Dan Lawyer's blog].<br />
<br />
This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as ''venue''?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?<br />
<br />
== Date Formatting ==<br />
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types. <br />
<br />
These are all the different fields from various citation formats that are of temporal nature:<br />
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)<br />
* originInfo/dateIssued<br />
* originInfo/dateCreated<br />
* originInfo/dateCaptured<br />
* originInfo/dateOther<br />
* month<br />
* year<br />
* Copyright Year<br />
* Date - Generic<br />
* Date of Confernce<br />
* Date of Publication<br />
* Date of update/revisou/issuance of database record<br />
* Former Date<br />
* Entry Date for Database Record<br />
* Database Update<br />
* Year of Publication<br />
<br />
There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities. <br />
<br />
There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.<br />
<br />
...<br />
<br />
It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek<br />
<br />
<br />
'''Important'''<br />
Sometimes we need a date range and not simply a date (e.g. 4-6 May 2006). See ''Conference Citation'' examples later on this page. - Discoleo<br />
<br />
== Tags ==<br />
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.<br />
<br />
<br />
== MARC / MODS / Dublin Core ==<br />
<br />
The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.<br />
<br />
Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):<br />
<br />
<pre><nowiki><br />
<div class="book" lang="en"><br />
<h3 class="fn">Arithmetic /</h3><br />
<p>By <span class="creator"><span class="fn">Sandburg, Carl</span>,<br />
<span class="date">1878-1967</span></span>,<br />
and <span class="illustrator">Rand, Ted</span></p><br />
<p>Publisher: <span class="publisher"><span class="fn">Harcourt Brace Jovanovich</span>,<br />
<span class="locality">San Diego</span></span></p><br />
<p>Published: <span class="issued">1993</span></p><br />
<p class="description">A poem about numbers and their characteristics. Features<br />
anamorphic, or distorted, drawings which can be restored to normal by viewing<br />
from a particular angle or by viewing the image's reflection in the provided<br />
Mylar cone.</p><br />
<p class="note">One Mylar sheet included in pocket.</p><br />
<p>Subjects:</p><br />
<ul><br />
<li class="subject">Arithmetic</li><br />
<li class="subject">Children's poetry, American.</li><br />
<li class="subject">Arithmetic</li><br />
<li class="subject">American poetry</li><br />
<li class="subject">Visual perception</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
== Basic Citation Stuctures ==<br />
There are basic structures to any citation, this is an overview of some of the types<br />
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]<br />
<br />
<br />
== Concerns not addressed by existing formats ==<br />
<br />
There are some aspects '''NOT adequately''' covered by existing formats. I have addressed this issue on the OpenOffice.org wiki page, too. [see http://wiki.services.openoffice.org/wiki/Bibliographic_Database for an extending discussion, the paragraph on ''Reference Types'']<br />
<br />
<br />
These issues pertain mainly to '''Errata''', '''Comments and Authors Reply''' and '''Article Retractions'''.<br />
* a bidirectional link could be necessary to implement these features (original article <=> eratum, reply, retraction letter)<br />
* '''IMPORTANT: Errata'''<br />
** Erata: one or more Corrections might be posted in various issues of the journal<br />
** this is usually cited as: Orininal Article Citation Data (Correction available in ''Journal, Issue Nr, Year, Pages'') (repeat for more than one correction)<br />
** it is possibly never cited alone<br />
** there should be a link to the original article, while the original article should contain a link to this ''Errata''<br />
* '''IMPORTANT: Commentary and Author Reply'''<br />
** similar to Errata, there might be one or more Comments and Author Replys; this should be stored, too<br />
** however, it is usually not included in the original citation<br />
** it might be used however in a citation, but I do not know exaclty how to cite it optimally (original article should be provided as well) <br />
* '''IMPORTANT: Article Retraction'''<br />
** an article may be retracted because of plagiarism or some other flaw<br />
** this should not be used any further in the research<br />
** however, it might be used e.g. for an article on plagiarism or flawed research<br />
** there should be therefore one field storing this information, too, and a link to:<br />
** the published withdrawal letter (which explains why the article was retracted)<br />
<br />
* this issue may need a time-controlled event<br />
* '''IMPORTANT: electronic publishing ahead of print (EPUB)'''<br />
** more and more articles are initially posted online, before the published article gets actually printed<br />
** How should this be used/cited?<br />
** Is this changed, after the print version becomes available?<br />
<br />
<br />
== Outstanding Issues ==<br />
The 3 main points i (Brian) came across so far are:<br />
1) IDENTIFIERS<br />
2) FORMAT TYPES<br />
3) NESTING<br />
<br />
1) In hCard/hCalendar there is a UID field. Added with URL it makes for a great unique identifier. There are loads of other identifers besides URL, ISBN, LOC call number, SKU, ISSN, etc. Many of these are unique in their domain, but not globally unique. So how to they get marked-up? Much like the hCard TEL/ADR properties, we can use something like:<br />
<pre><br />
<nowiki><br />
<div class="uid"><span class="type">ISBN</span>: <span<br />
class="value">123456</span></div><br />
</nowiki><br />
</pre><br />
This makes the encoding the most extensible... if we start use class="isbn" then it is an enumerated list, with class="type" it is open ended.<br />
<br />
2) I keep mis-using "format", format is the medium - hardback, softback. The TYPE (there probably is a better word - container?) is book, article, conference, manifesto, etc. Much like the identifers we can make an enumerated list of values, class="book", class="article", but that boxes us in, whereas something like: <pre><nowiki><span class="type">article</span></nowiki></pre> leaves things more open.<br />
<br />
3) Nesting citation data in a citation. The ability to nest the same microformat inside itself is something that other microformats don't explicitly handle.<br />
<br />
The two options are:<br />
i) Using class="book"<br />
<pre><br />
<nowiki><br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn">Book Title</span><br />
<div class="chapter"><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</div><br />
</div><br />
</nowiki><br />
</pre><br />
<br />
This makes things easy to nest and to figure out exactly what is<br />
associated with what, but the downside is that we have enumerated<br />
lists of values for the class properties.<br />
<br />
ii) using the TYPE for book<br />
<pre><br />
<nowiki><br />
<div class="hcite"><br />
<div class="type">book</div><br />
<span class="fn">Book Title</span><br />
<div class="type">chapter</div><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</nowiki><br />
</pre><br />
<br />
now the class="fn" is not nested inside the class="book" or<br />
class="chapter" so there would have to be some other mechanism to<br />
associate the data with the type.<br />
<br />
== Brian's Straw format ==<br />
<br />
=== implied schema (examples) ===<br />
+ publisher<br />
+ language<br />
+ description<br />
+ title<br />
+ creator<br />
+ journal<br />
+ volume<br />
+ issue<br />
+ page <br />
+ edition<br />
+ identifier<br />
+ tags<br />
+ format<br />
+ date published<br />
+ copyright<br />
- audience<br />
<br />
=== implied schema (formats) ===<br />
+ publisher<br />
+ language<br />
+ description<br />
+ title<br />
+ creator<br />
+ volume<br />
+ pages<br />
+ edition<br />
+ issue<br />
+ identifier<br />
+ tags<br />
+ format<br />
+ date published<br />
+ date copyrighted<br />
- subtitle<br />
- image <br />
- excerpt<br />
- index terms<br />
- series title<br />
- publication<br />
- journal<br />
- part (1 of X)<br />
<br />
UNION of the two schemas<br />
+ (PLUS) means common properties<br />
- (MINUS) means unique to the schema<br />
<br />
=== Example ===<br />
<pre><br />
<nowiki><br />
<ul class="bibliography"><br />
<li class="citation" xml:lang="en-gb"><br />
<br />
<!-- publisher data as hCard--><br />
<div class="publisher vcard"><br />
<span class="fn org">ABC Publishing Co.</span><br />
<span class="country-name">United Kingdom</span><br />
...<br />
</div><br />
<br />
<!-- author(s) data as hCard --><br />
<div class="creator vcard"><br />
<span class="fn n"><span class="given-name">John <span class="family-name">Doe</span></span><br />
...<br />
</div><br />
<br />
<!-- location data --><br />
<span class="title">Foobar!</span><br />
<span class="description">World Class Book about foobar</span><br />
<span class="volume">1</span><br />
<span class="issue">1</span><br />
<span class="edition">1</span><br />
<span class="pages">1-10</span><br />
<span class="format">article</span><br />
<br />
<!-- differed to the UID debate --><br />
<span class="identifier">12345678</span><br />
<br />
<!-- keywords --><br />
<span class="keyword">foo</span><br />
<span class="keyword">bar</span><br />
<br />
<!-- date properties --><br />
Published <abbr class="dtpublished" title="20060101">January 1st 1006</abbr><br />
Copyright <abbr class="copyright" title="20060101">2006</abbr><br />
</li><br />
...<br />
</ul><br />
<br />
<p class="citation">Have you read <span class="title"><abbr title="book" class="format">Foo Bar</abbr></span>? <br />
It was written by <span class="author vcard"><span class="fn">John Doe</span></span>. <br />
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr></p><br />
</nowiki><br />
</pre><br />
<br />
Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce<br />
<br />
Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?<br />
<br />
'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)<br />
<br />
== Mike straw format suggestion ==<br />
<br />
In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike<br />
<br />
=== In General ===<br />
<br />
The ''citation'' format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.<br />
<br />
=== Schema ===<br />
<br />
The citation schema consists of the following:<br />
<br />
* cite <br />
** title: required, text (class = fn)<br />
** subtitle: optional, text<br />
** authors: optional, use hCard<br />
** publication date: optional<br />
** link(s) to instantiations, optional, url or use rel-enclosure? (class=url)<br />
** UID, optional (for ISBN, DOI - use existing uid class) | permalink<br />
** series (aka volume/issuenum) , optional (''not as sure how to handle these - suggestions?'')<br />
** pages: startpage & endpage, optional, text<br />
** venue, optional (hCard)<br />
** publisher, optional (hCard)<br />
** container: optional (nested hCite)<br />
** abstract, optional (blockquote + class="abstract" ?)<br />
** notes, optional (blockquote + class="notes" ?)<br />
** keywords, optional (rel-tag)<br />
** image, optional (for inclusion inline, unlike the url)<br />
** copyright, optional (rel-license)<br />
** ''what else am I missing?''<br />
*** language, optional<br />
<br />
''Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html the need for a root element]. We should extract the N optimization of hCard like we did with adr, in order to ease this problem.'' --[[User:RCanine|Ryan Cannon]]<br />
<br />
Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html <br />
you see citations like this<nowiki>:</nowiki><br />
<blockquote><br />
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.<br />
</blockquote><br />
--[[User:JoeAndrieu|Joe Andrieu]]<br />
<br />
=== Examples ===<br />
<br />
The following are translations into the ''citation'' format.<br />
<br />
Note: some of these are just placeholders right now. Please feel free to fill them in!<br />
<br />
==== Citing Private Communication ====<br />
* published-date seems a weird fit, but it works...<br />
private communication, Michael Jordan, May 2004<br />
<br />
Needs a formatted example.<br />
<br />
==== Citing Legal Cases ====<br />
Needs an example. Here's some info I found about citing law:<br />
<br />
I'm not a lawyer, so I'm relying on the published [http://www.legalbluebook.com "blue book" standard], at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?<br />
<br />
From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:<br />
<pre><nowiki><br />
<h1>The Betamax Case</h1><br />
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2><br />
</nowiki></pre><br />
<br />
From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf<br />
5 basic components:<br />
*1 name of the case (citation title)<br />
*2 published source in which case may be found (citation containing publication?)<br />
*3 a parenthetical indicating the court and year of decision (citation venue?)<br />
*4 other parenthetical information, if any (citation notes?)<br />
*5 subsequent history of the case, if any (citation notes?)<br />
<br />
Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!<br />
<br />
Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).<br />
<br />
Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).<br />
<br />
==== Citing a Book ====<br />
<br />
needs an example<br />
<br />
==== Citing a journal article ====<br />
<br />
needs an example <br />
<br />
==== Citing a magazine article ====<br />
<br />
needs an example<br />
<br />
==== Citing a Patent ====<br />
<br />
Patents are often just cited by number. Here's a citation that accomplishes the same thing with some extra information:<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<a class="fn url" href="http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=/netahtml/search-bool.html&r=3&f=G&l=50&co1=AND&d=ptxt&s1=tevanian&OS=tevanian&RS=tevanian">US Patent #6,704,928</a><br />
<span class="author vcard">Richard Shann</span><br />
<abbr class="dtpublished" title="20000828T0000-0500">August 28, 2000</abbr><br />
<blockquote class="abstract"><br />
An executable program is prepared from a plurality of object code modules, at least one of the object code modules including section data specifying a plurality of code sequences each associated with relocation instructions identifying condition parameters. Only one of the code sequences is selected for inclusion in the executable program, determined by whether the condition for that parameter is satisfied. A linker for preparing the executable program includes a stack, a relocation module for reading the relocations, carrying out the relocation operations and selecting code sequences for inclusion in the executable program in dependence on values taken from the stack, a section data module for holding section data which is subject to the relocation operations, and a program forming module for preparing executable programs. Also disclosed is a method of assembling an object code module such that the assembled object code module includes the conditional code sequences.</blockquote><br />
</cite><br />
</nowiki></pre><br />
<br />
==== Citing a conference publication====<br />
<br />
Based on the following reference, plus some more information from the ACM site and a little of my own input (the tags)<br />
<br />
L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<span class="author vcard">Lorin Hochstein</span>,<br />
<span class="author vcard"> Jeff Carver </span>,<br />
<span class="author vcard"> Forrest Shull </span>,<br />
<span class="author vcard"> Sima Asgari</span>,<br />
<span class="author vcard"> Victor Basili</span>,<br />
<span class="author vcard"> Jeffrey K. Hollingsworth</span>, and <br />
<span class="author vcard"> Marv Zelkowitz</span>,<br />
<a class="fn url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.<br />
<cite class="container citation"><br />
<a class="fn url" href="">Proceedings of ACM/IEEE Supercomputing Conference</a><br />
<abbr class="dtpublished" title="20051126T0000-0800">2005</abbr><br />
</cite><br />
page <span class="startpage">35</span><br />
<div class="publisher vcard"><br />
<span class=" fn">IEEE Computer Society<br />
</span><br />
<div class="adr"><br />
<span class="locality">Washington</span>,<br />
<span class="region">DC</span><br />
</div><br />
</div><br />
<a class="url instantiation" href="http://portal.acm.org/ft_gateway.cfm?id=1105800&type=pdf&coll=portal&dl=ACM&CFID=68330711&CFTOKEN=39187329">PDF of full text from ACM</a><br />
<br />
DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a><br />
Tags: <a href="http://citeulike.org/tag/productivity" rel="tag">productivity</a>, <a href="http://citeulike.org/tag/hpc" rel="tag">hpc</a>, <a href="http://citeulike.org/tag/performance" rel="tag">performance</a><br />
<blockquote class="abstract">In developing High-Performance Computing (HPC) software, time to solution is an important metric. This metric is comprised of two main components: the human effort required developing the software, plus the amount of machine time required to execute it. To date, little empirical work has been done to study the first component: the human effort required and the effects of approaches and practices that may be used to reduce it. In this paper, we describe a series of studies that address this problem. We instrumented the development process used in multiple HPC classroom environments. We analyzed data within and across such studies, varying factors such as the parallel programming model used and the application being developed, to understand their impact on the development process.<br />
</blockquote><br />
</cite><br />
</nowiki></pre><br />
<br />
<br />
'''IMPORTANT'''<br />
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.<br />
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.<br />
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.<br />
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.<br />
<br />
==== Citing an external website ====<br />
<br />
This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:<br />
<br />
[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a><br />
<span class="author vcard"><br />
<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a><br />
</span> <br />
<abbr class="dtpublished" title="19990125T0000-0500"><br />
Jan 25, 1999<br />
</abbr><br />
</cite><br />
</nowiki></pre><br />
<br />
== discussions ==<br />
<br />
* [[citation-irc-notes-2006-04-09]]</div>Discoleohttp://microformats.org/wiki/index.php?title=citation-brainstorming&diff=9007citation-brainstorming2006-09-26T14:59:07Z<p>Discoleo: /* Date Formatting */</p>
<hr />
<div><h1> Citation Brainstroming </h1><br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* ...<br />
* ... (a bunch of good folks!)<br />
* Tantek Çelik<br />
* Tim White<br />
* Michael McCracken<br />
<br />
== See also ==<br />
* [[citation]]<br />
* [[citation-examples]]<br />
* [[citation-formats]]<br />
* [[citation-faq]]<br />
<br />
== Use Cases ==<br />
<br />
To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving.<br />
<br />
I've included two, focusing on consuming information - I've assumed that use cases for generating microformatted content would just involve the desire to enable your content to be consumed better, but I'm interested to see if there's something I'm missing here -Mike<br />
<br />
=== Acquiring reference information from the web ===<br />
<br />
A user either finds an author's papers page, or is viewing the results of a search and would like to import the information about the displayed papers into their local reference database, for the purposes of cataloging things they've read, adding notes, and using the information to generate later citations, potentially in other forms, such as BibTeX or Docbook, for inclusion in a publication of their own.<br />
<br />
Notes: In this case, it isn't important to the user what format the citation takes as displayed on the page where they find it. What *is* important is that it contains enough information to allow generation of the format they will ultimately re-publish it in. This implies that it may be worthwhile to err a little on the side of verbosity.<br />
<br />
Also, links to downloadable full representations of the cited work are very important - e.g. a link to the PDF of a journal article, or to a music file.<br />
<br />
=== Subscribing to reading lists, periodicals, etc ===<br />
<br />
I would like to be able to leverage my news aggregator with hAtom to subscribe to a remote source for citation information, for example:<br />
<br />
* a reading list for a seminar<br />
* The publication list for a conference (e.g., subscribe to SIGGRAPH and see the updated conference proceedings every year)<br />
* the issues of a journal<br />
* a particular research group or researcher's publications<br />
* Not just research: a popular author's publications (e.g., [http://www.gladwell.com/archive.html Malcolm Gladwell's Archive])<br />
<br />
=== Aggregating reading lists and reviews ===<br />
<br />
A citation microformat-specific aggregator could provide a decentralized version of [http://citeulike.org/ CiteULike]. Libraries, authors, research groups, and publishers could mark up their collections, while other people on weblogs or review sites could add tags and reviews.<br />
<br />
At least, having a well-adopted microformat would make writing tools like CiteULike much better, since it relies in some cases on screen-scraping publisher web-sites.<br />
<br />
== Original hBib Discussion ==<br />
<br />
During the WWW2005 Developer's Day [[microformats]] track, Rohit Khare gave a [[presentations|presentation]] where he discussed the microformats [[process]], and then did a quick demonstration wherein a bunch of us got on a shared Subethaedit document, and brainstormed some thoughts on what an "hBib" bibliography citation microformat would look like. Rohit placed the [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document on his Commercenet site].<br />
<br />
* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html<br />
<br />
''An attempt to summarize and inline the linked document follows. -Mike''<br />
<br />
Two major goals were outlined by the group:<br />
<br />
* Avoid re-keying references<br />
* Adapt to new journal styles by changing CSS<br />
<br />
The fundamental problem was discussed in terms of display - the ability to transform XHTML+hBib into the many journal-specific formats. For example, how to display "et.al" when all authors are present in the source, and how to re-order the elements if a style defines a set order of elements that conflicts with the ordering in the source. Using hCard for authors was agreed on, and the beginnings of an example were shown.<br />
<br />
== XHTML Structure ==<br />
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.<br />
<br />
* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.<br />
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.<br />
* Perhaps class="hcite" with <code>&lt;cite&gt;</code> recommended as the root element. E.g. <code>&lt;cite class="hcite"&gt;</code><br />
<br />
== Citation vs. [[media-info]] ==<br />
<br />
What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.<br />
<br />
== Semantic Meaning ==<br />
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)<br />
<br />
The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference. ''Does this sentence make sense only historically? -Mike''<br />
<br />
== OCLC's WorldCat for titles == <br />
Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White<br />
<br />
== This and That ==<br />
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)<br />
<br />
The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.<br />
<br />
This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]<br />
<br />
== More on This and That ==<br />
<br />
Citation microformats are being explored as a possibility for citing genealogical information at [http://eatslikeahuman.blogspot.com Dan Lawyer's blog].<br />
<br />
This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as ''venue''?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?<br />
<br />
== Date Formatting ==<br />
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types. <br />
<br />
These are all the different fields from various citation formats that are of temporal nature:<br />
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)<br />
* originInfo/dateIssued<br />
* originInfo/dateCreated<br />
* originInfo/dateCaptured<br />
* originInfo/dateOther<br />
* month<br />
* year<br />
* Copyright Year<br />
* Date - Generic<br />
* Date of Confernce<br />
* Date of Publication<br />
* Date of update/revisou/issuance of database record<br />
* Former Date<br />
* Entry Date for Database Record<br />
* Database Update<br />
* Year of Publication<br />
<br />
There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities. <br />
<br />
There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.<br />
<br />
...<br />
<br />
It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek<br />
<br />
<br />
'''Important'''<br />
Sometimes we need a date range and not simply a date (e.g. 4-6 May 2006). See ''Conference Citation'' examples later on this page. - Discoleo<br />
<br />
== Tags ==<br />
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.<br />
<br />
<br />
== MARC / MODS / Dublin Core ==<br />
<br />
The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.<br />
<br />
Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):<br />
<br />
<pre><nowiki><br />
<div class="book" lang="en"><br />
<h3 class="fn">Arithmetic /</h3><br />
<p>By <span class="creator"><span class="fn">Sandburg, Carl</span>,<br />
<span class="date">1878-1967</span></span>,<br />
and <span class="illustrator">Rand, Ted</span></p><br />
<p>Publisher: <span class="publisher"><span class="fn">Harcourt Brace Jovanovich</span>,<br />
<span class="locality">San Diego</span></span></p><br />
<p>Published: <span class="issued">1993</span></p><br />
<p class="description">A poem about numbers and their characteristics. Features<br />
anamorphic, or distorted, drawings which can be restored to normal by viewing<br />
from a particular angle or by viewing the image's reflection in the provided<br />
Mylar cone.</p><br />
<p class="note">One Mylar sheet included in pocket.</p><br />
<p>Subjects:</p><br />
<ul><br />
<li class="subject">Arithmetic</li><br />
<li class="subject">Children's poetry, American.</li><br />
<li class="subject">Arithmetic</li><br />
<li class="subject">American poetry</li><br />
<li class="subject">Visual perception</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
== Basic Citation Stuctures ==<br />
There are basic structures to any citation, this is an overview of some of the types<br />
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]<br />
<br />
<br />
== Concerns not addressed by existing formats ==<br />
<br />
There are some aspects '''NOT adequately''' covered by existing formats. I have addressed this issue on the OpenOffice.org wiki page, too. [see http://wiki.services.openoffice.org/wiki/Bibliographic_Database for an extending discussion, the paragraph on ''Reference Types'']<br />
<br />
<br />
These issues pertain mainly to '''Errata''', '''Comments and Authors Reply''' and '''Article Retractions'''.<br />
* a bidirectional link could be necessary to implement these features (original article <=> eratum, reply, retraction letter)<br />
* '''IMPORTANT: Errata'''<br />
** Erata: one or more Corrections might be posted in various issues of the journal<br />
** this is usually cited as: Orininal Article Citation Data (Correction available in ''Journal, Issue Nr, Year, Pages'') (repeat for more than one correction)<br />
** it is possibly never cited alone<br />
** there should be a link to the original article, while the original article should contain a link to this ''Errata''<br />
* '''IMPORTANT: Commentary and Author Reply'''<br />
** similar to Errata, there might be one or more Comments and Author Replys; this should be stored, too<br />
** however, it is usually not included in the original citation<br />
** it might be used however in a citation, but I do not know exaclty how to cite it optimally (original article should be provided as well) <br />
* '''IMPORTANT: Article Retraction'''<br />
** an article may be retracted because of plagiarism or some other flaw<br />
** this should not be used any further in the research<br />
** however, it might be used e.g. for an article on plagiarism or flawed research<br />
** there should be therefore one field storing this information, too, and a link to:<br />
** the published withdrawal letter (which explains why the article was retracted)<br />
<br />
* this issue may need a time-controlled event<br />
* '''IMPORTANT: electronic publishing ahead of print (EPUB)'''<br />
** more and more articles are initially posted online, before the published article gets actually printed<br />
** How should this be used/cited?<br />
** Is this changed, after the print version becomes available?<br />
<br />
<br />
== Outstanding Issues ==<br />
The 3 main points i (Brian) came across so far are:<br />
1) IDENTIFIERS<br />
2) FORMAT TYPES<br />
3) NESTING<br />
<br />
1) In hCard/hCalendar there is a UID field. Added with URL it makes for a great unique identifier. There are loads of other identifers besides URL, ISBN, LOC call number, SKU, ISSN, etc. Many of these are unique in their domain, but not globally unique. So how to they get marked-up? Much like the hCard TEL/ADR properties, we can use something like:<br />
<pre><br />
<nowiki><br />
<div class="uid"><span class="type">ISBN</span>: <span<br />
class="value">123456</span></div><br />
</nowiki><br />
</pre><br />
This makes the encoding the most extensible... if we start use class="isbn" then it is an enumerated list, with class="type" it is open ended.<br />
<br />
2) I keep mis-using "format", format is the medium - hardback, softback. The TYPE (there probably is a better word - container?) is book, article, conference, manifesto, etc. Much like the identifers we can make an enumerated list of values, class="book", class="article", but that boxes us in, whereas something like: <pre><nowiki><span class="type">article</span></nowiki></pre> leaves things more open.<br />
<br />
3) Nesting citation data in a citation. The ability to nest the same microformat inside itself is something that other microformats don't explicitly handle.<br />
<br />
The two options are:<br />
i) Using class="book"<br />
<pre><br />
<nowiki><br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn">Book Title</span><br />
<div class="chapter"><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</div><br />
</div><br />
</nowiki><br />
</pre><br />
<br />
This makes things easy to nest and to figure out exactly what is<br />
associated with what, but the downside is that we have enumerated<br />
lists of values for the class properties.<br />
<br />
ii) using the TYPE for book<br />
<pre><br />
<nowiki><br />
<div class="hcite"><br />
<div class="type">book</div><br />
<span class="fn">Book Title</span><br />
<div class="type">chapter</div><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</nowiki><br />
</pre><br />
<br />
now the class="fn" is not nested inside the class="book" or<br />
class="chapter" so there would have to be some other mechanism to<br />
associate the data with the type.<br />
<br />
== Brian's Straw format ==<br />
<br />
=== implied schema (examples) ===<br />
+ publisher<br />
+ language<br />
+ description<br />
+ title<br />
+ creator<br />
+ journal<br />
+ volume<br />
+ issue<br />
+ page <br />
+ edition<br />
+ identifier<br />
+ tags<br />
+ format<br />
+ date published<br />
+ copyright<br />
- audience<br />
<br />
=== implied schema (formats) ===<br />
+ publisher<br />
+ language<br />
+ description<br />
+ title<br />
+ creator<br />
+ volume<br />
+ pages<br />
+ edition<br />
+ issue<br />
+ identifier<br />
+ tags<br />
+ format<br />
+ date published<br />
+ date copyrighted<br />
- subtitle<br />
- image <br />
- excerpt<br />
- index terms<br />
- series title<br />
- publication<br />
- journal<br />
- part (1 of X)<br />
<br />
UNION of the two schemas<br />
+ (PLUS) means common properties<br />
- (MINUS) means unique to the schema<br />
<br />
=== Example ===<br />
<pre><br />
<nowiki><br />
<ul class="bibliography"><br />
<li class="citation" xml:lang="en-gb"><br />
<br />
<!-- publisher data as hCard--><br />
<div class="publisher vcard"><br />
<span class="fn org">ABC Publishing Co.</span><br />
<span class="country-name">United Kingdom</span><br />
...<br />
</div><br />
<br />
<!-- author(s) data as hCard --><br />
<div class="creator vcard"><br />
<span class="fn n"><span class="given-name">John <span class="family-name">Doe</span></span><br />
...<br />
</div><br />
<br />
<!-- location data --><br />
<span class="title">Foobar!</span><br />
<span class="description">World Class Book about foobar</span><br />
<span class="volume">1</span><br />
<span class="issue">1</span><br />
<span class="edition">1</span><br />
<span class="pages">1-10</span><br />
<span class="format">article</span><br />
<br />
<!-- differed to the UID debate --><br />
<span class="identifier">12345678</span><br />
<br />
<!-- keywords --><br />
<span class="keyword">foo</span><br />
<span class="keyword">bar</span><br />
<br />
<!-- date properties --><br />
Published <abbr class="dtpublished" title="20060101">January 1st 1006</abbr><br />
Copyright <abbr class="copyright" title="20060101">2006</abbr><br />
</li><br />
...<br />
</ul><br />
<br />
<p class="citation">Have you read <span class="title"><abbr title="book" class="format">Foo Bar</abbr></span>? <br />
It was written by <span class="author vcard"><span class="fn">John Doe</span></span>. <br />
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr></p><br />
</nowiki><br />
</pre><br />
<br />
Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce<br />
<br />
Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?<br />
<br />
'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)<br />
<br />
== Mike straw format suggestion ==<br />
<br />
In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike<br />
<br />
=== In General ===<br />
<br />
The ''citation'' format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.<br />
<br />
=== Schema ===<br />
<br />
The citation schema consists of the following:<br />
<br />
* cite <br />
** title: required, text (class = fn)<br />
** subtitle: optional, text<br />
** authors: optional, use hCard<br />
** publication date: optional<br />
** link(s) to instantiations, optional, url or use rel-enclosure? (class=url)<br />
** UID, optional (for ISBN, DOI - use existing uid class) | permalink<br />
** series (aka volume/issuenum) , optional (''not as sure how to handle these - suggestions?'')<br />
** pages: startpage & endpage, optional, text<br />
** venue, optional (hCard)<br />
** publisher, optional (hCard)<br />
** container: optional (nested hCite)<br />
** abstract, optional (blockquote + class="abstract" ?)<br />
** notes, optional (blockquote + class="notes" ?)<br />
** keywords, optional (rel-tag)<br />
** image, optional (for inclusion inline, unlike the url)<br />
** copyright, optional (rel-license)<br />
** ''what else am I missing?''<br />
*** language, optional<br />
<br />
''Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html the need for a root element]. We should extract the N optimization of hCard like we did with adr, in order to ease this problem.'' --[[User:RCanine|Ryan Cannon]]<br />
<br />
Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html <br />
you see citations like this<nowiki>:</nowiki><br />
<blockquote><br />
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.<br />
</blockquote><br />
--[[User:JoeAndrieu|Joe Andrieu]]<br />
<br />
=== Examples ===<br />
<br />
The following are translations into the ''citation'' format.<br />
<br />
Note: some of these are just placeholders right now. Please feel free to fill them in!<br />
<br />
==== Citing Private Communication ====<br />
* published-date seems a weird fit, but it works...<br />
private communication, Michael Jordan, May 2004<br />
<br />
Needs a formatted example.<br />
<br />
==== Citing Legal Cases ====<br />
Needs an example. Here's some info I found about citing law:<br />
<br />
I'm not a lawyer, so I'm relying on the published [http://www.legalbluebook.com "blue book" standard], at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?<br />
<br />
From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:<br />
<pre><nowiki><br />
<h1>The Betamax Case</h1><br />
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2><br />
</nowiki></pre><br />
<br />
From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf<br />
5 basic components:<br />
*1 name of the case (citation title)<br />
*2 published source in which case may be found (citation containing publication?)<br />
*3 a parenthetical indicating the court and year of decision (citation venue?)<br />
*4 other parenthetical information, if any (citation notes?)<br />
*5 subsequent history of the case, if any (citation notes?)<br />
<br />
Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!<br />
<br />
Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).<br />
<br />
Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).<br />
<br />
==== Citing a Book ====<br />
<br />
needs an example<br />
<br />
==== Citing a journal article ====<br />
<br />
needs an example <br />
<br />
==== Citing a magazine article ====<br />
<br />
needs an example<br />
<br />
==== Citing a Patent ====<br />
<br />
Patents are often just cited by number. Here's a citation that accomplishes the same thing with some extra information:<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<a class="fn url" href="http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=/netahtml/search-bool.html&r=3&f=G&l=50&co1=AND&d=ptxt&s1=tevanian&OS=tevanian&RS=tevanian">US Patent #6,704,928</a><br />
<span class="author vcard">Richard Shann</span><br />
<abbr class="dtpublished" title="20000828T0000-0500">August 28, 2000</abbr><br />
<blockquote class="abstract"><br />
An executable program is prepared from a plurality of object code modules, at least one of the object code modules including section data specifying a plurality of code sequences each associated with relocation instructions identifying condition parameters. Only one of the code sequences is selected for inclusion in the executable program, determined by whether the condition for that parameter is satisfied. A linker for preparing the executable program includes a stack, a relocation module for reading the relocations, carrying out the relocation operations and selecting code sequences for inclusion in the executable program in dependence on values taken from the stack, a section data module for holding section data which is subject to the relocation operations, and a program forming module for preparing executable programs. Also disclosed is a method of assembling an object code module such that the assembled object code module includes the conditional code sequences.</blockquote><br />
</cite><br />
</nowiki></pre><br />
<br />
==== Citing a conference publication====<br />
<br />
Based on the following reference, plus some more information from the ACM site and a little of my own input (the tags)<br />
<br />
L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.<br />
<br />
'''IMPORTANT'''<br />
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.<br />
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.<br />
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.<br />
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<span class="author vcard">Lorin Hochstein</span>,<br />
<span class="author vcard"> Jeff Carver </span>,<br />
<span class="author vcard"> Forrest Shull </span>,<br />
<span class="author vcard"> Sima Asgari</span>,<br />
<span class="author vcard"> Victor Basili</span>,<br />
<span class="author vcard"> Jeffrey K. Hollingsworth</span>, and <br />
<span class="author vcard"> Marv Zelkowitz</span>,<br />
<a class="fn url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.<br />
<cite class="container citation"><br />
<a class="fn url" href="">Proceedings of ACM/IEEE Supercomputing Conference</a><br />
<abbr class="dtpublished" title="20051126T0000-0800">2005</abbr><br />
</cite><br />
page <span class="startpage">35</span><br />
<div class="publisher vcard"><br />
<span class=" fn">IEEE Computer Society<br />
</span><br />
<div class="adr"><br />
<span class="locality">Washington</span>,<br />
<span class="region">DC</span><br />
</div><br />
</div><br />
<a class="url instantiation" href="http://portal.acm.org/ft_gateway.cfm?id=1105800&type=pdf&coll=portal&dl=ACM&CFID=68330711&CFTOKEN=39187329">PDF of full text from ACM</a><br />
<br />
DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a><br />
Tags: <a href="http://citeulike.org/tag/productivity" rel="tag">productivity</a>, <a href="http://citeulike.org/tag/hpc" rel="tag">hpc</a>, <a href="http://citeulike.org/tag/performance" rel="tag">performance</a><br />
<blockquote class="abstract">In developing High-Performance Computing (HPC) software, time to solution is an important metric. This metric is comprised of two main components: the human effort required developing the software, plus the amount of machine time required to execute it. To date, little empirical work has been done to study the first component: the human effort required and the effects of approaches and practices that may be used to reduce it. In this paper, we describe a series of studies that address this problem. We instrumented the development process used in multiple HPC classroom environments. We analyzed data within and across such studies, varying factors such as the parallel programming model used and the application being developed, to understand their impact on the development process.<br />
</blockquote><br />
</cite><br />
</nowiki></pre><br />
<br />
==== Citing an external website ====<br />
<br />
This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:<br />
<br />
[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a><br />
<span class="author vcard"><br />
<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a><br />
</span> <br />
<abbr class="dtpublished" title="19990125T0000-0500"><br />
Jan 25, 1999<br />
</abbr><br />
</cite><br />
</nowiki></pre><br />
<br />
== discussions ==<br />
<br />
* [[citation-irc-notes-2006-04-09]]</div>Discoleohttp://microformats.org/wiki/index.php?title=citation-examples&diff=8967citation-examples2006-09-24T21:18:20Z<p>Discoleo: /* Citation Mark Up in the Wild */</p>
<hr />
<div><h1> Citation Examples </h1><br />
<br />
The following examples are real world examples of citations found on the web. Please add to this list. The idea is that we get a solid sample of examples and see what commonalities there are amonst them and try to build this microformat so that it can meet 80% of typical uses.<br />
<br />
See also:<br />
* [[citation]]<br />
* [[citation-formats]]<br />
* [[citation-brainstorming]]<br />
* [[citation-faq]]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
* ...<br />
* [http://suda.co.uk/ Brian Suda]<br />
* Tantek Çelik<br />
* [http://michael-mccracken.net/wp/ Michael McCracken]<br />
* Tim White<br />
* [http://inkdroid.org Ed Summers]<br />
<br />
== Citation Mark Up in the Wild ==<br />
Mark up examples from reference publisher's websites (online catalogs), including ABC-CLIO, Greenwood Press, Marshall Cavendish, Oxford University Press (USA) and Thomson Gale. Examples are broken down and organized by element. <br />
<br />
(For a cleaner version, see [http://www.tjameswhite.com/citation-examples.htm]) -- ''is this link now out of date?''--[[User:Mike|Mike]] 18:19, 30 Aug 2006 (PDT)<br />
<br />
=== Important ===<br />
<br />
There are some aspects '''NOT adequately''' covered by existing formats. I have addressed this issue on the OpenOffice.org wiki page, too. [see http://wiki.services.openoffice.org/wiki/Bibliographic_Database for an extending discussion, the paragraph on ''Reference Types'']<br />
<br />
<br />
These issues pertain mainly to '''Errata''', '''Comments and Authors Reply''' and '''Article Retractions'''.<br />
* a bidirectional link could be necessary to implement these features (original article <=> eratum, reply, retraction letter)<br />
* '''IMPORTANT: Errata'''<br />
** Erata: one or more Corrections might be posted in various issues of the journal<br />
** this is usually cited as: Orininal Article Citation Data (Correction available in ''Journal, Issue Nr, Year, Pages'') (repeat for more than one correction)<br />
** it is possibly never cited alone<br />
** there should be a link to the original article, while the original article should contain a link to this ''Errata''<br />
* '''IMPORTANT: Commentary and Author Reply'''<br />
** similar to Errata, there might be one or more Comments and Author Replys; this should be stored, too<br />
** however, it is usually not included in the original citation<br />
** it might be used however in a citation, but I do not know exaclty how to cite it optimally (original article should be provided as well) <br />
* '''IMPORTANT: Article Retraction'''<br />
** an article may be retracted because of plagiarism or some other flaw<br />
** this should not be used any further in the research<br />
** however, it might be used e.g. for an article on plagiarism or flawed research<br />
** there should be therefore one field storing this information, too, and a link to:<br />
** the published withdrawal letter (which explains why the article was retracted)<br />
<br />
* this issue may need a time-controlled event<br />
* '''IMPORTANT: electronic publishing ahead of print (EPUB)'''<br />
** more and more articles are initially posted online, before the published article gets actually printed<br />
** How should this be used/cited?<br />
** Is this changed, after the print version becomes available?<br />
<br />
<br />
<br />
<br />
=== ABC-CLIO Product detail page ===<br />
[http://www.abc-clio.com/products/overview.aspx?productid=109327 example] <br />
[http://microformats.org/wiki/citation-examples-markup#ABC-CLIO_Product_detail_page.C2.A0.28http:.2F.2Fwww.abc-clio.com.2Fproducts.2Foverview.aspx.3Fproductid.3D109327.29 Original Markup]<br />
<br />
* title<br />
* subtitle<br />
* author<br />
* image<br />
* publication date<br />
* pages<br />
* volumes<br />
* specifications (book dimentions 8.5x11, weight, etc)<br />
* Format - (Hardback, softback)<br />
* Price<br />
* ISBN<br />
<br />
=== Greenwood Press featured book ===<br />
[http://www.greenwood.com/ greenwood press home page]<br />
[http://microformats.org/wiki/citation-examples-markup#Greenwood_Press_home_page.C2.A0.28http:.2F.2Fwww.greenwood.com.2F.29_featured_book Original Markup]<br />
* title<br />
* subtitle<br />
* author<br />
* ISBN<br />
* Price<br />
* Description<br />
<br />
=== Greenwood Press product detail page ===<br />
[http://www.greenwood.com/catalog/GR2847.aspx Product detail page]<br />
[http://microformats.org/wiki/citation-examples-markup#Greenwood_Press_Product_detail_page.C2.A0.28http:.2F.2Fwww.greenwood.com.2Fcatalog.2FGR2847.aspx.29 Original Markup]<br />
<br />
* Title<br />
* subtitle<br />
* authors<br />
* AuthorsNote<br />
* BookCode (internal code system)<br />
* ISBN<br />
* Page<br />
* Publisher<br />
* Publication Date<br />
* Price<br />
* Availability<br />
* MediaType<br />
* categories<br />
* LC Card Number<br />
* LCC Class<br />
* Dewey Class<br />
<br />
=== Marshall Cavendish product page===<br />
[http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page] <br />
[http://microformats.org/wiki/citation-examples-markup#Marshall_Cavendish_product_page.C2.A0.28http:.2F.2Fwww.marshallcavendish.com.2Fmarshallcavendish.2Facademic.2Fredirector.xml.3Furl.3D.2Fmarshallcavendish.2Facademic.2Fcatalogue.2Fbooks.2Fregionalism_n_regional_security.2F9812102108.xml.29 Original Markup]<br />
<br />
* ISBN<br />
* Series<br />
* Title<br />
* publisher<br />
* Specifications (dimentions/weight)<br />
* Authors<br />
* Target Audience<br />
* Price<br />
* description<br />
<br />
=== Oxford University Press (USA) home page ===<br />
[http://www.us.oup.com/us/?view=usa homepage]<br />
[http://microformats.org/wiki/citation-examples-markup#Oxford_University_Press_.28USA.29_homepage.C2.A0.28http:.2F.2Fwww.us.oup.com.2Fus.2F.3Fview.3Dusa.29 Original Markup]<br />
<br />
* title<br />
* subTitle<br />
* edition<br />
* byline<br />
* ISBN<br />
* format - hardback<br />
* publication Date<br />
* price<br />
* description<br />
* related<br />
<br />
=== Oxford University Press (USA) product detail page ===<br />
[http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&amp;ci=0195162471#Product_Details Product page]<br />
[http://microformats.org/wiki/citation-examples-markup#Oxford_University_Press_.28USA.29_Product_page.C2.A0.28http:.2F.2Fwww.us.oup.com.2Fus.2Fcatalog.2Fgeneral.2Fsubject.2FHistoryAmerican.2FColonialRevolutionary.2F.3Fview.3Dusa.26ci.3D0195162471.23Product_Details.29 Original Markup]<br />
<br />
* title<br />
* subTitle<br />
* edition<br />
* byline<br />
* image<br />
* isbnNumber<br />
* format - hardback<br />
* pages<br />
* publication Date<br />
* availability<br />
* price<br />
<br />
=== Thomson Gale product detail page ===<br />
[http://microformats.org/wiki/citation-examples-markup#Thomson_Gale_product_detail_page Original Markup]<br />
<br />
* title<br />
* excerp<br />
* Volume<br />
* Publisher<br />
* description<br />
* Published date<br />
* ISBN<br />
* Product number (internal code system)<br />
* Pages<br />
* Shipping Weight<br />
* price<br />
<br />
=== RFC vCard Example ===<br />
[http://microformats.org/wiki/citation-examples-markup#RFC_vCard_Example Original Markup]<br />
<br />
* refID (HTML @ID)<br />
* title<br />
* publication<br />
* title<br />
* Journal<br />
* Volume<br />
* Issue<br />
* page<br />
* pubdate<br />
* RFC ID<br />
<br />
=== W3C XHTML Spec Example ===<br />
[http://microformats.org/wiki/citation-examples-markup#W3C_XHTML_Spec_Example Original Markup]<br />
<br />
* refID (HTML @ID)<br />
* URL<br />
* title<br />
* subtitle<br />
* part (1 of X)<br />
* journal<br />
* authors<br />
* pubdate<br />
* language<br />
* ISO/IEC ID<br />
* RFC ID<br />
<br />
[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]<br />
<br />
=== CiteProc XHTML Output ===<br />
[http://microformats.org/wiki/citation-examples-markup#CiteProc_XHTML_Output Original Markup]<br />
<br />
The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc/] wasn't designed per se as a microformat, but is probably not a bad place to start. It is desgined to handle a wide range of content. Here is the APA output:<br />
<br />
* refID (HTML @ID)<br />
* creator<br />
* role (to indicate editors and translators)<br />
* date<br />
* title<br />
* volume<br />
* issue<br />
* page<br />
* issue<br />
* container (a book serves as container for a chapter)<br />
* type (book, newspaper, proceedings)<br />
* edition<br />
* publisher<br />
* place<br />
* location (for urls and physical locations)<br />
* access date (for online items)<br />
<br />
=== ACM Digital Library Search Result Examples ===<br />
<br />
The [http://www.acm.org/dl/ ACM Digital Library] is a heavily used computer science literature database.<br />
[http://microformats.org/wiki/citation-examples-markup#ACM_Digital_Library_Search_Result_Examples Original Markup]<br />
<br />
* title<br />
* authors<br />
* Pages<br />
* format (PDF)<br />
* Additional Information<br />
* abstract<br />
* index terms<br />
* journal<br />
* issue<br />
* volume<br />
* pubdate<br />
* DOI<br />
<br />
=== IEEE IEEExplore Search Results Markup ===<br />
[http://microformats.org/wiki/citation-examples-markup#IEEE_IEEExplore_Search_Results_Markup Original Markup]<br />
<br />
* title<br />
* authors<br />
* journal<br />
* issue<br />
* volume<br />
* issue<br />
* pubdate<br />
* page<br />
* Digital Object Identifier (DOI)<br />
* summary<br />
<br />
=== CiteSeer database search results ===<br />
<br />
The [http://citeseer.ist.psu.edu CiteSeer] database has been another heavily used Computer Science online resource, and it has minimal markup:<br />
[http://microformats.org/wiki/citation-examples-markup#CiteSeer_database_search_results Original Markup]<br />
<br />
* author <br />
* title<br />
* journal<br />
* pages <br />
* publication date<br />
* URL<br />
<br />
=== CiteULike.org citation listing ===<br />
<br />
[http://www.citeulike.org/ CiteULike]<br />
[http://microformats.org/wiki/citation-examples-markup#CiteULike.org_citation_listing Original Markup]<br />
<br />
* title<br />
* author<br />
* subjects<br />
* image<br />
* Volume<br />
* Number<br />
* publication date <br />
* page<br />
<br />
Links to services with the following IDs embedded in the link<br />
* Z3988<br />
* DOI<br />
* Pubmed<br />
* Hubmed<br />
<br />
=== Amazon.com citation info ===<br />
<br />
This is from a detail page on Amazon.com for a book.<br />
[http://microformats.org/wiki/citation-examples-markup#Amazon.com_citation_info Original Markup]<br />
<br />
* title<br />
* author<br />
* series title<br />
* page<br />
<br />
=== PubMed Medical Journal Example ===<br />
[http://microformats.org/wiki/citation-examples-markup#PubMed_Medical_Journal_Example Original Markup]<br />
<br />
* abstract<br />
* title<br />
* publisher<br />
* journal<br />
* date/time published <br />
* Review (BOOLEAN YES/NO)<br />
* PubMedID<br />
<br />
=== BibDesk Default Template ===<br />
[[citation-examples-markup#BibDesk_default_HTML_export_example|Original Markup]]<br />
<br />
This is a pretty simplistic template for a very general app, but it seems to be OK for most BD users. <br />
<br />
* Title<br />
* Author<br />
* Journal<br />
* Volume<br />
* Pages<br />
* Date<br />
* Url<br />
* Abstract<br />
<br />
=== Wikipedia ===<br />
[http://wikpedia.org Wikipedia] makes extensive use of bibliographic citations, in particular to point readers to further information sources. There are differing formats depending on Wikipedia's language:<br />
<br />
==== English Wikipdia ====<br />
The kinds of citations used on the site run the full gamut. Here are breakdowns of four categories previously mentioned:<br />
<br />
===== Book =====<br />
[http://en.wikipedia.org/wiki/Richard_feynman#_note-8 Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Book Example Markup]<br />
<br />
* title<br />
* author<br />
* publisher<br />
* year<br />
* ISBN<br />
* url (indirectly via special wikipedia ISBN page)<br />
<br />
===== Journal Articles =====<br />
[http://en.wikipedia.org/wiki/DNA#Citations Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Journal_Article Example Markup]<br />
<br />
* author (truncated list)<br />
* year<br />
* title<br />
* journal title<br />
* journal number<br />
* page range<br />
* [http://doi.org DOI]<br />
<br />
===== Court cases =====<br />
[http://en.wikipedia.org/wiki/List_of_leading_legal_cases_in_copyright_law Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Example Markup]<br />
<br />
* title<br />
* case number <br />
** ''note that legal standards for referring to cases include some inscrutable abbreviations that are probably more detailed than just "case number"''<br />
* court name<br />
* year<br />
* description/abstract<br />
<br />
===== U.S. Law =====<br />
[http://en.wikipedia.org/wiki/Foreign_Intelligence_Surveillance_Act#endnote_FISA Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_US_Law Example Markup]<br />
<br />
* title (title number, for example "50" in "50 U.S.C. chapter 36."<br />
* chapter title (name, for example "Foreign Intelligence Surveillance" )<br />
* chapter number<br />
* section, paragraph, subparagraph numbers (optionally)<br />
<br />
===== Conference presentations ===== <br />
[http://en.wikipedia.org/wiki/Paul_R._Pillar#Conference_presentation_by_Pillar Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Conference_Presentation Example Markup]<br />
<br />
* title<br />
* location<br />
* date<br />
* author (implied - the page is about this person)<br />
<br />
<br />
===== Historical Sources =====<br />
[http://en.wikipedia.org/wiki/American_Civil_War#Primary_sources Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Primary_Historical_Source Example Markup]<br />
<br />
* source / location<br />
* title<br />
* publisher<br />
* year<br />
* description<br />
* url<br />
<br />
==== German Wikipedia ====<br />
* [http://de.wikipedia.org/wiki/Wikipedia:Literatur citing styles]<br />
<br />
=== EPrints.org ===<br />
<br />
[http://eprints.ecs.soton.ac.uk/12070/ example]<br />
[http://microformats.org/wiki/citation-examples-markup#EPrints.org_generated_output example markup]<br />
<br />
Based on [http://dublincore.org/documents/dcq-html/ Expressing Dublin Core in HTML/XHTML meta and link elements] and [http://www.ietf.org/rfc/rfc2731.txt rfc2731], Eprints.org uses the following Dublin Core terms in meta tags in the HTML HEAD of each paper's page: <br />
<br />
* title<br />
* creator (author)<br />
* description (abstract)<br />
* date<br />
* type<br />
* identifier (a url)<br />
* format <br />
** a strange syntax for the meta content:"pdf http://eprints.ecs.soton.ac.uk/12070/01/Alani-final.pdf"" for the format term...<br />
* fulltext <br />
** this is in a rel-alternate link element. The class is 'fulltext', and the href is the same link as in format, only a valid URL this time.<br />
<br />
In the body of the page, they use the following classes, now no longer DC terms:<br />
* title<br />
* authors (a flat list with abbreviated names)<br />
* year<br />
* conference<br />
* conference location<br />
<br />
=== Self-Citation Example ===<br />
[http://cbio.mskcc.org/~hoffmann/lifecycles/olv/index.html One example] of an article that includes a statement "please cite as" (a self-description):<br />
<br />
* title<br />
* author<br />
* periodical (journal) title<br />
* volume<br />
* issue<br />
* pages<br />
* year<br />
<br />
=== Citation of an Online Resource ===<br />
At University of Michigan's [http://www.crlt.umich.edu/publinks/facment_biblio.html Center for Research on Learning and Teaching] you see citations like this:<br />
<br />
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Wed: http://www.k-state.edu/provost/academic/big12/big12guide.htm.<br />
<br />
* title<br />
* publication year<br />
* department/author<br />
* retrieval date<br />
* URL<br />
<br />
== Implied schema ==<br />
<br />
=== List of all properties ===<br />
This are a summation of all the properties in the examples, I have tried to logically group them together.<br />
<br />
* title<br />
* subtitle<br />
* author<br />
* editor<br />
* translator<br />
* image<br />
* date (issued, copyrighted, accessed)<br />
* language<br />
* description/Summary/abstract<br />
* excerpt<br />
* index terms<br />
* categories (keywords, tags, labels, etc.)<br />
<br />
RELATIONS<br />
* container (publication; periodicals, books, etc.)<br />
* collection (series and so forth)<br />
* event (conference, etc.)<br />
* original (for republished material)<br />
<br />
LOCATION INFORMATION<br />
* pages<br />
* volume<br />
* series title<br />
* Series<br />
* edition<br />
* issue<br />
* publication<br />
* journal<br />
* part (1 of X)<br />
<br />
PHYSICAL ATTRIBUTES<br />
* Specifications (dimentions/weight)<br />
* Format/type (book, newspaper, proceedings)<br />
<br />
IDENTIFIERS<br />
* ISBN<br />
* LC Card Number<br />
* LCC Class<br />
* Dewey Class<br />
* URL<br />
* RFC ID<br />
* ISO/IEC ID<br />
* DOI<br />
* PubMedID<br />
<br />
PUBLISHER<br />
* publisher<br />
<br />
<br />
These are sort of left overs, the are not really about citations, but more about commerce or other things. If they are important we can move them to the above list.<br />
* refID (HTML @ID)<br />
* Reviewed (BOOLEAN YES/NO)<br />
* Availability<br />
* Price<br />
* Shipping Weight<br />
* related<br />
* Product number (internal system code)<br />
* BookCode (internal system code)<br />
* AuthorsNote<br />
* Additional Information<br />
* Target Audience<br />
<br />
=== Analysis of Examples ===<br />
With exception of just a few properties, all of the above appeared in atleast two different examples. The following properties were very common in most the example formats:<br />
* title<br />
* subtitle<br />
* author<br />
* publication date<br />
* description<br />
* pages<br />
* ISBN<br />
* publisher<br />
<br />
== Styles ==<br />
This does NOT define a format, but instead shows how the format should be displayed. This is something out of the direct scope of this project. CSS styles will handle the look-and-feel of the text, and the author can put it in any order they choose. These links are mentioned for two reasons, one is informative, the other is so we know at least meet the minimum properties that are used in the styles.<br />
<br />
* [http://www.liu.edu/cwis/cwp/library/workshop/citmla.htm MLA Style]<br />
* [http://www.bu.edu/library/guides/citation.html Chicago, MLA, and APA styles]<br />
* [http://www.english.uiuc.edu/cws/wworkshop/writer_resources/citation_styles/citation_styles.htm Writer's Workshop citation style page] (detailed citation style info)<br />
* [http://www.legalbluebook.com/ Blue Book] for legal citations<br />
* [http://www.columbia.edu/cu/cup/cgos/idx_basic.html Columbia University Citation Style] developed for modern internet citations</div>Discoleohttp://microformats.org/wiki/index.php?title=citation-brainstorming&diff=8966citation-brainstorming2006-09-22T23:12:49Z<p>Discoleo: /* Citing a conference publication */</p>
<hr />
<div><h1> Citation Brainstroming </h1><br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* ...<br />
* ... (a bunch of good folks!)<br />
* Tantek Çelik<br />
* Tim White<br />
* Michael McCracken<br />
<br />
== See also ==<br />
* [[citation]]<br />
* [[citation-examples]]<br />
* [[citation-formats]]<br />
* [[citation-faq]]<br />
<br />
== Use Cases ==<br />
<br />
To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving.<br />
<br />
I've included two, focusing on consuming information - I've assumed that use cases for generating microformatted content would just involve the desire to enable your content to be consumed better, but I'm interested to see if there's something I'm missing here -Mike<br />
<br />
=== Acquiring reference information from the web ===<br />
<br />
A user either finds an author's papers page, or is viewing the results of a search and would like to import the information about the displayed papers into their local reference database, for the purposes of cataloging things they've read, adding notes, and using the information to generate later citations, potentially in other forms, such as BibTeX or Docbook, for inclusion in a publication of their own.<br />
<br />
Notes: In this case, it isn't important to the user what format the citation takes as displayed on the page where they find it. What *is* important is that it contains enough information to allow generation of the format they will ultimately re-publish it in. This implies that it may be worthwhile to err a little on the side of verbosity.<br />
<br />
Also, links to downloadable full representations of the cited work are very important - e.g. a link to the PDF of a journal article, or to a music file.<br />
<br />
=== Subscribing to reading lists, periodicals, etc ===<br />
<br />
I would like to be able to leverage my news aggregator with hAtom to subscribe to a remote source for citation information, for example:<br />
<br />
* a reading list for a seminar<br />
* The publication list for a conference (e.g., subscribe to SIGGRAPH and see the updated conference proceedings every year)<br />
* the issues of a journal<br />
* a particular research group or researcher's publications<br />
* Not just research: a popular author's publications (e.g., [http://www.gladwell.com/archive.html Malcolm Gladwell's Archive])<br />
<br />
=== Aggregating reading lists and reviews ===<br />
<br />
A citation microformat-specific aggregator could provide a decentralized version of [http://citeulike.org/ CiteULike]. Libraries, authors, research groups, and publishers could mark up their collections, while other people on weblogs or review sites could add tags and reviews.<br />
<br />
At least, having a well-adopted microformat would make writing tools like CiteULike much better, since it relies in some cases on screen-scraping publisher web-sites.<br />
<br />
== Original hBib Discussion ==<br />
<br />
During the WWW2005 Developer's Day [[microformats]] track, Rohit Khare gave a [[presentations|presentation]] where he discussed the microformats [[process]], and then did a quick demonstration wherein a bunch of us got on a shared Subethaedit document, and brainstormed some thoughts on what an "hBib" bibliography citation microformat would look like. Rohit placed the [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document on his Commercenet site].<br />
<br />
* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html<br />
<br />
''An attempt to summarize and inline the linked document follows. -Mike''<br />
<br />
Two major goals were outlined by the group:<br />
<br />
* Avoid re-keying references<br />
* Adapt to new journal styles by changing CSS<br />
<br />
The fundamental problem was discussed in terms of display - the ability to transform XHTML+hBib into the many journal-specific formats. For example, how to display "et.al" when all authors are present in the source, and how to re-order the elements if a style defines a set order of elements that conflicts with the ordering in the source. Using hCard for authors was agreed on, and the beginnings of an example were shown.<br />
<br />
== XHTML Structure ==<br />
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.<br />
<br />
* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.<br />
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.<br />
* Perhaps class="hcite" with <code>&lt;cite&gt;</code> recommended as the root element. E.g. <code>&lt;cite class="hcite"&gt;</code><br />
<br />
== Citation vs. [[media-info]] ==<br />
<br />
What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.<br />
<br />
== Semantic Meaning ==<br />
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)<br />
<br />
The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference. ''Does this sentence make sense only historically? -Mike''<br />
<br />
== OCLC's WorldCat for titles == <br />
Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White<br />
<br />
== This and That ==<br />
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)<br />
<br />
The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.<br />
<br />
This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]<br />
<br />
== More on This and That ==<br />
<br />
Citation microformats are being explored as a possibility for citing genealogical information at [http://eatslikeahuman.blogspot.com Dan Lawyer's blog].<br />
<br />
This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as ''venue''?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?<br />
<br />
== Date Formatting ==<br />
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types. <br />
<br />
These are all the different fields from various citation formats that are of temporal nature:<br />
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)<br />
* originInfo/dateIssued<br />
* originInfo/dateCreated<br />
* originInfo/dateCaptured<br />
* originInfo/dateOther<br />
* month<br />
* year<br />
* Copyright Year<br />
* Date - Generic<br />
* Date of Confernce<br />
* Date of Publication<br />
* Date of update/revisou/issuance of database record<br />
* Former Date<br />
* Entry Date for Database Record<br />
* Database Update<br />
* Year of Publication<br />
<br />
There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities. <br />
<br />
There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.<br />
<br />
...<br />
<br />
It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek<br />
<br />
<br />
<br />
<br />
== Tags ==<br />
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.<br />
<br />
<br />
== MARC / MODS / Dublin Core ==<br />
<br />
The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.<br />
<br />
Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):<br />
<br />
<pre><nowiki><br />
<div class="book" lang="en"><br />
<h3 class="fn">Arithmetic /</h3><br />
<p>By <span class="creator"><span class="fn">Sandburg, Carl</span>,<br />
<span class="date">1878-1967</span></span>,<br />
and <span class="illustrator">Rand, Ted</span></p><br />
<p>Publisher: <span class="publisher"><span class="fn">Harcourt Brace Jovanovich</span>,<br />
<span class="locality">San Diego</span></span></p><br />
<p>Published: <span class="issued">1993</span></p><br />
<p class="description">A poem about numbers and their characteristics. Features<br />
anamorphic, or distorted, drawings which can be restored to normal by viewing<br />
from a particular angle or by viewing the image's reflection in the provided<br />
Mylar cone.</p><br />
<p class="note">One Mylar sheet included in pocket.</p><br />
<p>Subjects:</p><br />
<ul><br />
<li class="subject">Arithmetic</li><br />
<li class="subject">Children's poetry, American.</li><br />
<li class="subject">Arithmetic</li><br />
<li class="subject">American poetry</li><br />
<li class="subject">Visual perception</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
== Basic Citation Stuctures ==<br />
There are basic structures to any citation, this is an overview of some of the types<br />
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]<br />
<br />
== Outstanding Issues ==<br />
The 3 main points i (Brian) came across so far are:<br />
1) IDENTIFIERS<br />
2) FORMAT TYPES<br />
3) NESTING<br />
<br />
1) In hCard/hCalendar there is a UID field. Added with URL it makes for a great unique identifier. There are loads of other identifers besides URL, ISBN, LOC call number, SKU, ISSN, etc. Many of these are unique in their domain, but not globally unique. So how to they get marked-up? Much like the hCard TEL/ADR properties, we can use something like:<br />
<pre><br />
<nowiki><br />
<div class="uid"><span class="type">ISBN</span>: <span<br />
class="value">123456</span></div><br />
</nowiki><br />
</pre><br />
This makes the encoding the most extensible... if we start use class="isbn" then it is an enumerated list, with class="type" it is open ended.<br />
<br />
2) I keep mis-using "format", format is the medium - hardback, softback. The TYPE (there probably is a better word - container?) is book, article, conference, manifesto, etc. Much like the identifers we can make an enumerated list of values, class="book", class="article", but that boxes us in, whereas something like: <span class="type">article</span> leaves things more open.<br />
<br />
3) Nesting citation data in a citation. The ability to nest the same microformat inside itself is something that other microformats don't explicitly handle.<br />
<br />
The two options are:<br />
i) Using class="book"<br />
<pre><br />
<nowiki><br />
<div class="hcite"><br />
<div class="book"><br />
<span class="fn">Book Title</span><br />
<div class="chapter"><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</div><br />
</div><br />
</nowiki><br />
</pre><br />
<br />
This makes things easy to nest and to figure out exactly what is<br />
associated with what, but the downside is that we have enumerated<br />
lists of values for the class properties.<br />
<br />
ii) using the TYPE for book<br />
<pre><br />
<nowiki><br />
<div class="hcite"><br />
<div class="type">book</div><br />
<span class="fn">Book Title</span><br />
<div class="type">chapter</div><br />
<span class="fn">Chapter Title</span><br />
</div><br />
</nowiki><br />
</pre><br />
<br />
now the class="fn" is not nested inside the class="book" or<br />
class="chapter" so there would have to be some other mechanism to<br />
associate the data with the type.<br />
<br />
== Brian's Straw format ==<br />
<br />
=== implied schema (examples) ===<br />
+ publisher<br />
+ language<br />
+ description<br />
+ title<br />
+ creator<br />
+ journal<br />
+ volume<br />
+ issue<br />
+ page <br />
+ edition<br />
+ identifier<br />
+ tags<br />
+ format<br />
+ date published<br />
+ copyright<br />
- audience<br />
<br />
=== implied schema (formats) ===<br />
+ publisher<br />
+ language<br />
+ description<br />
+ title<br />
+ creator<br />
+ volume<br />
+ pages<br />
+ edition<br />
+ issue<br />
+ identifier<br />
+ tags<br />
+ format<br />
+ date published<br />
+ date copyrighted<br />
- subtitle<br />
- image <br />
- excerpt<br />
- index terms<br />
- series title<br />
- publication<br />
- journal<br />
- part (1 of X)<br />
<br />
UNION of the two schemas<br />
+ (PLUS) means common properties<br />
- (MINUS) means unique to the schema<br />
<br />
=== Example ===<br />
<pre><br />
<nowiki><br />
<ul class="bibliography"><br />
<li class="citation" xml:lang="en-gb"><br />
<br />
<!-- publisher data as hCard--><br />
<div class="publisher vcard"><br />
<span class="fn org">ABC Publishing Co.</span><br />
<span class="country-name">United Kingdom</span><br />
...<br />
</div><br />
<br />
<!-- author(s) data as hCard --><br />
<div class="creator vcard"><br />
<span class="fn n"><span class="given-name">John <span class="family-name">Doe</span></span><br />
...<br />
</div><br />
<br />
<!-- location data --><br />
<span class="title">Foobar!</span><br />
<span class="description">World Class Book about foobar</span><br />
<span class="volume">1</span><br />
<span class="issue">1</span><br />
<span class="edition">1</span><br />
<span class="pages">1-10</span><br />
<span class="format">article</span><br />
<br />
<!-- differed to the UID debate --><br />
<span class="identifier">12345678</span><br />
<br />
<!-- keywords --><br />
<span class="keyword">foo</span><br />
<span class="keyword">bar</span><br />
<br />
<!-- date properties --><br />
Published <abbr class="dtpublished" title="20060101">January 1st 1006</abbr><br />
Copyright <abbr class="copyright" title="20060101">2006</abbr><br />
</li><br />
...<br />
</ul><br />
<br />
<p class="citation">Have you read <span class="title"><abbr title="book" class="format">Foo Bar</abbr></span>? <br />
It was written by <span class="author vcard"><span class="fn">John Doe</span></span>. <br />
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr></p><br />
</nowiki><br />
</pre><br />
<br />
Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce<br />
<br />
Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?<br />
<br />
'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)<br />
<br />
== Mike straw format suggestion ==<br />
<br />
In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike<br />
<br />
=== In General ===<br />
<br />
The ''citation'' format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.<br />
<br />
=== Schema ===<br />
<br />
The citation schema consists of the following:<br />
<br />
* cite <br />
** title: required, text (class = fn)<br />
** subtitle: optional, text<br />
** authors: optional, use hCard<br />
** publication date: optional<br />
** link(s) to instantiations, optional, url or use rel-enclosure? (class=url)<br />
** UID, optional (for ISBN, DOI - use existing uid class) | permalink<br />
** series (aka volume/issuenum) , optional (''not as sure how to handle these - suggestions?'')<br />
** pages: startpage & endpage, optional, text<br />
** venue, optional (hCard)<br />
** publisher, optional (hCard)<br />
** container: optional (nested hCite)<br />
** abstract, optional (blockquote + class="abstract" ?)<br />
** notes, optional (blockquote + class="notes" ?)<br />
** keywords, optional (rel-tag)<br />
** image, optional (for inclusion inline, unlike the url)<br />
** copyright, optional (rel-license)<br />
** ''what else am I missing?''<br />
*** language, optional<br />
<br />
''Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html the need for a root element]. We should extract the N optimization of hCard like we did with adr, in order to ease this problem.'' --[[User:RCanine|Ryan Cannon]]<br />
<br />
Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html <br />
you see citations like this<nowiki>:</nowiki><br />
<blockquote><br />
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.<br />
</blockquote><br />
--[[User:JoeAndrieu|Joe Andrieu]]<br />
<br />
=== Examples ===<br />
<br />
The following are translations into the ''citation'' format.<br />
<br />
Note: some of these are just placeholders right now. Please feel free to fill them in!<br />
<br />
==== Citing Private Communication ====<br />
* published-date seems a weird fit, but it works...<br />
private communication, Michael Jordan, May 2004<br />
<br />
Needs a formatted example.<br />
<br />
==== Citing Legal Cases ====<br />
Needs an example. Here's some info I found about citing law:<br />
<br />
I'm not a lawyer, so I'm relying on the published [http://www.legalbluebook.com "blue book" standard], at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?<br />
<br />
From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:<br />
<pre><nowiki><br />
<h1>The Betamax Case</h1><br />
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2><br />
</nowiki></pre><br />
<br />
From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf<br />
5 basic components:<br />
*1 name of the case (citation title)<br />
*2 published source in which case may be found (citation containing publication?)<br />
*3 a parenthetical indicating the court and year of decision (citation venue?)<br />
*4 other parenthetical information, if any (citation notes?)<br />
*5 subsequent history of the case, if any (citation notes?)<br />
<br />
Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!<br />
<br />
Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).<br />
<br />
Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).<br />
<br />
==== Citing a Book ====<br />
<br />
needs an example<br />
<br />
==== Citing a journal article ====<br />
<br />
needs an example <br />
<br />
==== Citing a magazine article ====<br />
<br />
needs an example<br />
<br />
==== Citing a Patent ====<br />
<br />
Patents are often just cited by number. Here's a citation that accomplishes the same thing with some extra information:<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<a class="fn url" href="http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=/netahtml/search-bool.html&r=3&f=G&l=50&co1=AND&d=ptxt&s1=tevanian&OS=tevanian&RS=tevanian">US Patent #6,704,928</a><br />
<span class="author vcard">Richard Shann</span><br />
<abbr class="dtpublished" title="20000828T0000-0500">August 28, 2000</abbr><br />
<blockquote class="abstract"><br />
An executable program is prepared from a plurality of object code modules, at least one of the object code modules including section data specifying a plurality of code sequences each associated with relocation instructions identifying condition parameters. Only one of the code sequences is selected for inclusion in the executable program, determined by whether the condition for that parameter is satisfied. A linker for preparing the executable program includes a stack, a relocation module for reading the relocations, carrying out the relocation operations and selecting code sequences for inclusion in the executable program in dependence on values taken from the stack, a section data module for holding section data which is subject to the relocation operations, and a program forming module for preparing executable programs. Also disclosed is a method of assembling an object code module such that the assembled object code module includes the conditional code sequences.</blockquote><br />
</cite><br />
</nowiki></pre><br />
<br />
==== Citing a conference publication====<br />
<br />
Based on the following reference, plus some more information from the ACM site and a little of my own input (the tags)<br />
<br />
L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.<br />
<br />
'''IMPORTANT'''<br />
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.<br />
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.<br />
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.<br />
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<span class="author vcard">Lorin Hochstein</span>,<br />
<span class="author vcard"> Jeff Carver </span>,<br />
<span class="author vcard"> Forrest Shull </span>,<br />
<span class="author vcard"> Sima Asgari</span>,<br />
<span class="author vcard"> Victor Basili</span>,<br />
<span class="author vcard"> Jeffrey K. Hollingsworth</span>, and <br />
<span class="author vcard"> Marv Zelkowitz</span>,<br />
<a class="fn url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.<br />
<cite class="container citation"><br />
<a class="fn url" href="">Proceedings of ACM/IEEE Supercomputing Conference</a><br />
<abbr class="dtpublished" title="20051126T0000-0800">2005</abbr><br />
</cite><br />
page <span class="startpage">35</span><br />
<div class="publisher vcard"><br />
<span class=" fn">IEEE Computer Society<br />
</span><br />
<div class="adr"><br />
<span class="locality">Washington</span>,<br />
<span class="region">DC</span><br />
</div><br />
</div><br />
<a class="url instantiation" href="http://portal.acm.org/ft_gateway.cfm?id=1105800&type=pdf&coll=portal&dl=ACM&CFID=68330711&CFTOKEN=39187329">PDF of full text from ACM</a><br />
<br />
DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a><br />
Tags: <a href="http://citeulike.org/tag/productivity" rel="tag">productivity</a>, <a href="http://citeulike.org/tag/hpc" rel="tag">hpc</a>, <a href="http://citeulike.org/tag/performance" rel="tag">performance</a><br />
<blockquote class="abstract">In developing High-Performance Computing (HPC) software, time to solution is an important metric. This metric is comprised of two main components: the human effort required developing the software, plus the amount of machine time required to execute it. To date, little empirical work has been done to study the first component: the human effort required and the effects of approaches and practices that may be used to reduce it. In this paper, we describe a series of studies that address this problem. We instrumented the development process used in multiple HPC classroom environments. We analyzed data within and across such studies, varying factors such as the parallel programming model used and the application being developed, to understand their impact on the development process.<br />
</blockquote><br />
</cite><br />
</nowiki></pre><br />
<br />
==== Citing an external website ====<br />
<br />
This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:<br />
<br />
[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)<br />
<br />
<pre><nowiki><br />
<cite class="citation"><br />
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a><br />
<span class="author vcard"><br />
<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a><br />
</span> <br />
<abbr class="dtpublished" title="19990125T0000-0500"><br />
Jan 25, 1999<br />
</abbr><br />
</cite><br />
</nowiki></pre><br />
<br />
== discussions ==<br />
<br />
* [[citation-irc-notes-2006-04-09]]</div>Discoleohttp://microformats.org/wiki/index.php?title=citation-examples&diff=8906citation-examples2006-09-22T21:47:44Z<p>Discoleo: /* Citation Mark Up in the Wild */</p>
<hr />
<div><h1> Citation Examples </h1><br />
<br />
The following examples are real world examples of citations found on the web. Please add to this list. The idea is that we get a solid sample of examples and see what commonalities there are amonst them and try to build this microformat so that it can meet 80% of typical uses.<br />
<br />
See also:<br />
* [[citation]]<br />
* [[citation-formats]]<br />
* [[citation-brainstorming]]<br />
* [[citation-faq]]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
* ...<br />
* [http://suda.co.uk/ Brian Suda]<br />
* Tantek Çelik<br />
* [http://michael-mccracken.net/wp/ Michael McCracken]<br />
* Tim White<br />
* [http://inkdroid.org Ed Summers]<br />
<br />
== Citation Mark Up in the Wild ==<br />
Mark up examples from reference publisher's websites (online catalogs), including ABC-CLIO, Greenwood Press, Marshall Cavendish, Oxford University Press (USA) and Thomson Gale. Examples are broken down and organized by element. <br />
<br />
(For a cleaner version, see [http://www.tjameswhite.com/citation-examples.htm]) -- ''is this link now out of date?''--[[User:Mike|Mike]] 18:19, 30 Aug 2006 (PDT)<br />
<br />
=== Important ===<br />
<br />
There are some aspects '''NOT adequately''' covered by existing formats. I have addressed this issue on the OpenOffice.org wiki page, too. [see http://wiki.services.openoffice.org/wiki/Bibliographic_Database for an extending discussion, the paragraph on ''Reference Types'']<br />
<br />
These issues pertain mainly to '''Errata''', '''Comments and Authors Reply''' and '''Article Retractions'''.<br />
* '''IMPORTANT: Errata'''<br />
** Erata: one or more Corrections might be posted in various issues of the journal<br />
** this is usually cited as: Orininal Article Citation Data (Correction available in ''Journal, Issue Nr, Year, Pages'') (repeat for more than one correction)<br />
** it is possibly never cited alone<br />
** there should be a link to the original article, while the original article should contain a link to this Errata <br />
* '''IMPORTANT: Commentary and Author Reply'''<br />
** similar to Errata, there might be one or more Comments and Author Replys; this should be stored, too<br />
** however, it is usually not included in the original citation<br />
** it might be used however in a citation, but I do not know exaclty how to cite it optimally (original article should be provided as well) <br />
* '''IMPORTANT: Article Retraction'''<br />
** an article may be retracted because of plagiarism or some other flaw<br />
** this should not be used any further in the research<br />
** however, it might be used e.g. for an article on plagiarism or flawed research<br />
** there should be therefore one field storing this information, too, and a link to:<br />
** the published withdrawal letter (which explains why the article was retracted)<br />
<br />
<br />
<br />
=== ABC-CLIO Product detail page ===<br />
[http://www.abc-clio.com/products/overview.aspx?productid=109327 example] <br />
[http://microformats.org/wiki/citation-examples-markup#ABC-CLIO_Product_detail_page.C2.A0.28http:.2F.2Fwww.abc-clio.com.2Fproducts.2Foverview.aspx.3Fproductid.3D109327.29 Original Markup]<br />
<br />
* title<br />
* subtitle<br />
* author<br />
* image<br />
* publication date<br />
* pages<br />
* volumes<br />
* specifications (book dimentions 8.5x11, weight, etc)<br />
* Format - (Hardback, softback)<br />
* Price<br />
* ISBN<br />
<br />
=== Greenwood Press featured book ===<br />
[http://www.greenwood.com/ greenwood press home page]<br />
[http://microformats.org/wiki/citation-examples-markup#Greenwood_Press_home_page.C2.A0.28http:.2F.2Fwww.greenwood.com.2F.29_featured_book Original Markup]<br />
* title<br />
* subtitle<br />
* author<br />
* ISBN<br />
* Price<br />
* Description<br />
<br />
=== Greenwood Press product detail page ===<br />
[http://www.greenwood.com/catalog/GR2847.aspx Product detail page]<br />
[http://microformats.org/wiki/citation-examples-markup#Greenwood_Press_Product_detail_page.C2.A0.28http:.2F.2Fwww.greenwood.com.2Fcatalog.2FGR2847.aspx.29 Original Markup]<br />
<br />
* Title<br />
* subtitle<br />
* authors<br />
* AuthorsNote<br />
* BookCode (internal code system)<br />
* ISBN<br />
* Page<br />
* Publisher<br />
* Publication Date<br />
* Price<br />
* Availability<br />
* MediaType<br />
* categories<br />
* LC Card Number<br />
* LCC Class<br />
* Dewey Class<br />
<br />
=== Marshall Cavendish product page===<br />
[http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page] <br />
[http://microformats.org/wiki/citation-examples-markup#Marshall_Cavendish_product_page.C2.A0.28http:.2F.2Fwww.marshallcavendish.com.2Fmarshallcavendish.2Facademic.2Fredirector.xml.3Furl.3D.2Fmarshallcavendish.2Facademic.2Fcatalogue.2Fbooks.2Fregionalism_n_regional_security.2F9812102108.xml.29 Original Markup]<br />
<br />
* ISBN<br />
* Series<br />
* Title<br />
* publisher<br />
* Specifications (dimentions/weight)<br />
* Authors<br />
* Target Audience<br />
* Price<br />
* description<br />
<br />
=== Oxford University Press (USA) home page ===<br />
[http://www.us.oup.com/us/?view=usa homepage]<br />
[http://microformats.org/wiki/citation-examples-markup#Oxford_University_Press_.28USA.29_homepage.C2.A0.28http:.2F.2Fwww.us.oup.com.2Fus.2F.3Fview.3Dusa.29 Original Markup]<br />
<br />
* title<br />
* subTitle<br />
* edition<br />
* byline<br />
* ISBN<br />
* format - hardback<br />
* publication Date<br />
* price<br />
* description<br />
* related<br />
<br />
=== Oxford University Press (USA) product detail page ===<br />
[http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&amp;ci=0195162471#Product_Details Product page]<br />
[http://microformats.org/wiki/citation-examples-markup#Oxford_University_Press_.28USA.29_Product_page.C2.A0.28http:.2F.2Fwww.us.oup.com.2Fus.2Fcatalog.2Fgeneral.2Fsubject.2FHistoryAmerican.2FColonialRevolutionary.2F.3Fview.3Dusa.26ci.3D0195162471.23Product_Details.29 Original Markup]<br />
<br />
* title<br />
* subTitle<br />
* edition<br />
* byline<br />
* image<br />
* isbnNumber<br />
* format - hardback<br />
* pages<br />
* publication Date<br />
* availability<br />
* price<br />
<br />
=== Thomson Gale product detail page ===<br />
[http://microformats.org/wiki/citation-examples-markup#Thomson_Gale_product_detail_page Original Markup]<br />
<br />
* title<br />
* excerp<br />
* Volume<br />
* Publisher<br />
* description<br />
* Published date<br />
* ISBN<br />
* Product number (internal code system)<br />
* Pages<br />
* Shipping Weight<br />
* price<br />
<br />
=== RFC vCard Example ===<br />
[http://microformats.org/wiki/citation-examples-markup#RFC_vCard_Example Original Markup]<br />
<br />
* refID (HTML @ID)<br />
* title<br />
* publication<br />
* title<br />
* Journal<br />
* Volume<br />
* Issue<br />
* page<br />
* pubdate<br />
* RFC ID<br />
<br />
=== W3C XHTML Spec Example ===<br />
[http://microformats.org/wiki/citation-examples-markup#W3C_XHTML_Spec_Example Original Markup]<br />
<br />
* refID (HTML @ID)<br />
* URL<br />
* title<br />
* subtitle<br />
* part (1 of X)<br />
* journal<br />
* authors<br />
* pubdate<br />
* language<br />
* ISO/IEC ID<br />
* RFC ID<br />
<br />
[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]<br />
<br />
=== CiteProc XHTML Output ===<br />
[http://microformats.org/wiki/citation-examples-markup#CiteProc_XHTML_Output Original Markup]<br />
<br />
The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc/] wasn't designed per se as a microformat, but is probably not a bad place to start. It is desgined to handle a wide range of content. Here is the APA output:<br />
<br />
* refID (HTML @ID)<br />
* creator<br />
* role (to indicate editors and translators)<br />
* date<br />
* title<br />
* volume<br />
* issue<br />
* page<br />
* issue<br />
* container (a book serves as container for a chapter)<br />
* type (book, newspaper, proceedings)<br />
* edition<br />
* publisher<br />
* place<br />
* location (for urls and physical locations)<br />
* access date (for online items)<br />
<br />
=== ACM Digital Library Search Result Examples ===<br />
<br />
The [http://www.acm.org/dl/ ACM Digital Library] is a heavily used computer science literature database.<br />
[http://microformats.org/wiki/citation-examples-markup#ACM_Digital_Library_Search_Result_Examples Original Markup]<br />
<br />
* title<br />
* authors<br />
* Pages<br />
* format (PDF)<br />
* Additional Information<br />
* abstract<br />
* index terms<br />
* journal<br />
* issue<br />
* volume<br />
* pubdate<br />
* DOI<br />
<br />
=== IEEE IEEExplore Search Results Markup ===<br />
[http://microformats.org/wiki/citation-examples-markup#IEEE_IEEExplore_Search_Results_Markup Original Markup]<br />
<br />
* title<br />
* authors<br />
* journal<br />
* issue<br />
* volume<br />
* issue<br />
* pubdate<br />
* page<br />
* Digital Object Identifier (DOI)<br />
* summary<br />
<br />
=== CiteSeer database search results ===<br />
<br />
The [http://citeseer.ist.psu.edu CiteSeer] database has been another heavily used Computer Science online resource, and it has minimal markup:<br />
[http://microformats.org/wiki/citation-examples-markup#CiteSeer_database_search_results Original Markup]<br />
<br />
* author <br />
* title<br />
* journal<br />
* pages <br />
* publication date<br />
* URL<br />
<br />
=== CiteULike.org citation listing ===<br />
<br />
[http://www.citeulike.org/ CiteULike]<br />
[http://microformats.org/wiki/citation-examples-markup#CiteULike.org_citation_listing Original Markup]<br />
<br />
* title<br />
* author<br />
* subjects<br />
* image<br />
* Volume<br />
* Number<br />
* publication date <br />
* page<br />
<br />
Links to services with the following IDs embedded in the link<br />
* Z3988<br />
* DOI<br />
* Pubmed<br />
* Hubmed<br />
<br />
=== Amazon.com citation info ===<br />
<br />
This is from a detail page on Amazon.com for a book.<br />
[http://microformats.org/wiki/citation-examples-markup#Amazon.com_citation_info Original Markup]<br />
<br />
* title<br />
* author<br />
* series title<br />
* page<br />
<br />
=== PubMed Medical Journal Example ===<br />
[http://microformats.org/wiki/citation-examples-markup#PubMed_Medical_Journal_Example Original Markup]<br />
<br />
* abstract<br />
* title<br />
* publisher<br />
* journal<br />
* date/time published <br />
* Review (BOOLEAN YES/NO)<br />
* PubMedID<br />
<br />
=== BibDesk Default Template ===<br />
[[citation-examples-markup#BibDesk_default_HTML_export_example|Original Markup]]<br />
<br />
This is a pretty simplistic template for a very general app, but it seems to be OK for most BD users. <br />
<br />
* Title<br />
* Author<br />
* Journal<br />
* Volume<br />
* Pages<br />
* Date<br />
* Url<br />
* Abstract<br />
<br />
=== Wikipedia ===<br />
[http://wikpedia.org Wikipedia] makes extensive use of bibliographic citations, in particular to point readers to further information sources. There are differing formats depending on Wikipedia's language:<br />
<br />
==== English Wikipdia ====<br />
The kinds of citations used on the site run the full gamut. Here are breakdowns of four categories previously mentioned:<br />
<br />
===== Book =====<br />
[http://en.wikipedia.org/wiki/Richard_feynman#_note-8 Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Book Example Markup]<br />
<br />
* title<br />
* author<br />
* publisher<br />
* year<br />
* ISBN<br />
* url (indirectly via special wikipedia ISBN page)<br />
<br />
===== Journal Articles =====<br />
[http://en.wikipedia.org/wiki/DNA#Citations Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Journal_Article Example Markup]<br />
<br />
* author (truncated list)<br />
* year<br />
* title<br />
* journal title<br />
* journal number<br />
* page range<br />
* [http://doi.org DOI]<br />
<br />
===== Court cases =====<br />
[http://en.wikipedia.org/wiki/List_of_leading_legal_cases_in_copyright_law Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Example Markup]<br />
<br />
* title<br />
* case number <br />
** ''note that legal standards for referring to cases include some inscrutable abbreviations that are probably more detailed than just "case number"''<br />
* court name<br />
* year<br />
* description/abstract<br />
<br />
===== U.S. Law =====<br />
[http://en.wikipedia.org/wiki/Foreign_Intelligence_Surveillance_Act#endnote_FISA Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_US_Law Example Markup]<br />
<br />
* title (title number, for example "50" in "50 U.S.C. chapter 36."<br />
* chapter title (name, for example "Foreign Intelligence Surveillance" )<br />
* chapter number<br />
* section, paragraph, subparagraph numbers (optionally)<br />
<br />
===== Conference presentations ===== <br />
[http://en.wikipedia.org/wiki/Paul_R._Pillar#Conference_presentation_by_Pillar Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Conference_Presentation Example Markup]<br />
<br />
* title<br />
* location<br />
* date<br />
* author (implied - the page is about this person)<br />
<br />
<br />
===== Historical Sources =====<br />
[http://en.wikipedia.org/wiki/American_Civil_War#Primary_sources Example]<br />
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Primary_Historical_Source Example Markup]<br />
<br />
* source / location<br />
* title<br />
* publisher<br />
* year<br />
* description<br />
* url<br />
<br />
==== German Wikipedia ====<br />
* [http://de.wikipedia.org/wiki/Wikipedia:Literatur citing styles]<br />
<br />
=== EPrints.org ===<br />
<br />
[http://eprints.ecs.soton.ac.uk/12070/ example]<br />
[http://microformats.org/wiki/citation-examples-markup#EPrints.org_generated_output example markup]<br />
<br />
Based on [http://dublincore.org/documents/dcq-html/ Expressing Dublin Core in HTML/XHTML meta and link elements] and [http://www.ietf.org/rfc/rfc2731.txt rfc2731], Eprints.org uses the following Dublin Core terms in meta tags in the HTML HEAD of each paper's page: <br />
<br />
* title<br />
* creator (author)<br />
* description (abstract)<br />
* date<br />
* type<br />
* identifier (a url)<br />
* format <br />
** a strange syntax for the meta content:"pdf http://eprints.ecs.soton.ac.uk/12070/01/Alani-final.pdf"" for the format term...<br />
* fulltext <br />
** this is in a rel-alternate link element. The class is 'fulltext', and the href is the same link as in format, only a valid URL this time.<br />
<br />
In the body of the page, they use the following classes, now no longer DC terms:<br />
* title<br />
* authors (a flat list with abbreviated names)<br />
* year<br />
* conference<br />
* conference location<br />
<br />
=== Self-Citation Example ===<br />
[http://cbio.mskcc.org/~hoffmann/lifecycles/olv/index.html One example] of an article that includes a statement "please cite as" (a self-description):<br />
<br />
* title<br />
* author<br />
* periodical (journal) title<br />
* volume<br />
* issue<br />
* pages<br />
* year<br />
<br />
=== Citation of an Online Resource ===<br />
At University of Michigan's [http://www.crlt.umich.edu/publinks/facment_biblio.html Center for Research on Learning and Teaching] you see citations like this:<br />
<br />
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Wed: http://www.k-state.edu/provost/academic/big12/big12guide.htm.<br />
<br />
* title<br />
* publication year<br />
* department/author<br />
* retrieval date<br />
* URL<br />
<br />
== Implied schema ==<br />
<br />
=== List of all properties ===<br />
This are a summation of all the properties in the examples, I have tried to logically group them together.<br />
<br />
* title<br />
* subtitle<br />
* author<br />
* editor<br />
* translator<br />
* image<br />
* date (issued, copyrighted, accessed)<br />
* language<br />
* description/Summary/abstract<br />
* excerpt<br />
* index terms<br />
* categories (keywords, tags, labels, etc.)<br />
<br />
RELATIONS<br />
* container (publication; periodicals, books, etc.)<br />
* collection (series and so forth)<br />
* event (conference, etc.)<br />
* original (for republished material)<br />
<br />
LOCATION INFORMATION<br />
* pages<br />
* volume<br />
* series title<br />
* Series<br />
* edition<br />
* issue<br />
* publication<br />
* journal<br />
* part (1 of X)<br />
<br />
PHYSICAL ATTRIBUTES<br />
* Specifications (dimentions/weight)<br />
* Format/type (book, newspaper, proceedings)<br />
<br />
IDENTIFIERS<br />
* ISBN<br />
* LC Card Number<br />
* LCC Class<br />
* Dewey Class<br />
* URL<br />
* RFC ID<br />
* ISO/IEC ID<br />
* DOI<br />
* PubMedID<br />
<br />
PUBLISHER<br />
* publisher<br />
<br />
<br />
These are sort of left overs, the are not really about citations, but more about commerce or other things. If they are important we can move them to the above list.<br />
* refID (HTML @ID)<br />
* Reviewed (BOOLEAN YES/NO)<br />
* Availability<br />
* Price<br />
* Shipping Weight<br />
* related<br />
* Product number (internal system code)<br />
* BookCode (internal system code)<br />
* AuthorsNote<br />
* Additional Information<br />
* Target Audience<br />
<br />
=== Analysis of Examples ===<br />
With exception of just a few properties, all of the above appeared in atleast two different examples. The following properties were very common in most the example formats:<br />
* title<br />
* subtitle<br />
* author<br />
* publication date<br />
* description<br />
* pages<br />
* ISBN<br />
* publisher<br />
<br />
== Styles ==<br />
This does NOT define a format, but instead shows how the format should be displayed. This is something out of the direct scope of this project. CSS styles will handle the look-and-feel of the text, and the author can put it in any order they choose. These links are mentioned for two reasons, one is informative, the other is so we know at least meet the minimum properties that are used in the styles.<br />
<br />
* [http://www.liu.edu/cwis/cwp/library/workshop/citmla.htm MLA Style]<br />
* [http://www.bu.edu/library/guides/citation.html Chicago, MLA, and APA styles]<br />
* [http://www.english.uiuc.edu/cws/wworkshop/writer_resources/citation_styles/citation_styles.htm Writer's Workshop citation style page] (detailed citation style info)<br />
* [http://www.legalbluebook.com/ Blue Book] for legal citations<br />
* [http://www.columbia.edu/cu/cup/cgos/idx_basic.html Columbia University Citation Style] developed for modern internet citations</div>Discoleo