h-adr: Difference between revisions
(editorial, move backcompat to its own section at the bottom) |
(Category:Draft Specifications) |
||
Line 81: | Line 81: | ||
* [[h-geo]] can be nested in h-adr | * [[h-geo]] can be nested in h-adr | ||
* [[h-card]] and [[h-event]] often contain h-adr | * [[h-card]] and [[h-event]] often contain h-adr | ||
[[Category:Draft Specifications]] |
Revision as of 23:45, 14 June 2013
<entry-title>h-adr</entry-title> Tantek Çelik (Editor)
h-adr is a simple, open format for publishing structured locations such as addresses, physical and/or postal. h-adr is one of several open microformat draft standards suitable for embedding data in HTML/HTML5 on the web.
h-adr is the microformats-2 update to adr. It is most commonly used as part of an h-card or h-event.
Example
Here is a simple postal address example:
<p class="h-adr">
<span class="p-street-address">17 Austerstræti</span>
<span class="p-locality">Reykjavík</span>
<span class="p-country-name">Iceland</span>
<span class="p-postal-code">107</span>
</p>
Get started
The class h-adr
is a root class name that indicates the presence of an h-adr.
p-street-address, p-locality, p-country-name, p-postal-code and all the other h-adr property class names listed below define properties of the h-adr.
See microformats-2-parsing to learn more about property class names.
Properties
Inside an element with class h-adr:
p-street-address
- house/apartment number, floor, street namep-extended-address
- additional street detailsp-post-office-box
p-locality
- city/town/villagep-region
- state/county/provincep-postal-code
- postal code, e.g. ZIP in the USp-country-name
- country namep-label
- new in vCard4 (RFC6350)p-geo
(or u-geo with a RFC 5870 geo: URL), optionally a nested h-geop-latitude
- metric latitudep-longitude
- metric longitudep-altitude
- metric altitude
Status
h-adr is a microformats.org draft specification. Public discussion on h-adr takes place on h-adr-feedback, the #microformats irc channel on irc.freenode.net, and microformats-new mailing list.
h-adr is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-adrs up with classic adr classnames.
Property Details
(stub, add any property explanations here)
Examples in the Wild
- … add any h-adr examples you find in the wild
Backward Compatiblity
Publisher Compatibility
For backward compatibility, you may wish to use classic adr classnames in addition to the more future-proof h-adr properties, for example:
<span class="p-street-address street-address">123 Main St.</span>
Parser Compatibility
Microformats parsers should detect classic properties and parse them as microformats 2 properties. If an "h-adr" is found, don't look for an "adr" on the same element.
Compatibility root class name: adr
Properties: (parsed as p- plain text unless otherwise specified)
- post-office-box
- extended-address
- street-address
- locality
- region
- postal-code
- country-name
Background
h-adr is based on the existing adr specification, which was extracted from hCard in order to allow it to be used for applications other than contact information.
See Also
- microformats-2
- h-geo can be nested in h-adr
- h-card and h-event often contain h-adr