h-adr - Revision history

GRegorLove: s///

2023-07-26T21:13:15Z

s/<source>/<syntaxhighlight>/

← Older revision		Revision as of 21:13, 26 July 2023
Line 18:		Line 18:
	Here is a simple postal address example:		Here is a simple postal address example:

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<p class="h-adr">		<p class="h-adr">
	<span class="p-street-address">17 Austerstræti</span>		<span class="p-street-address">17 Austerstræti</span>
Line 25:		Line 25:
	<span class="p-postal-code">107</span>		<span class="p-postal-code">107</span>
	</p>		</p>
	</~~source~~>		</syntaxhighlight>

	Parsed JSON:		Parsed JSON:

	<~~source~~ lang=~~javascript~~>		<syntaxhighlight lang="json">
	{		{
	"items": [		"items": [
Line 56:		Line 56:
	]		]
	}		}
	</~~source~~>		</syntaxhighlight>

	The implicit "name" property that is generated from parsing an h-adr is there for consuming applications to have a simple flattened string representation of an h-adr.		The implicit "name" property that is generated from parsing an h-adr is there for consuming applications to have a simple flattened string representation of an h-adr.
Line 106:		Line 106:
	For backward compatibility, you may wish to use classic [[adr]] classnames in addition to the more future-proof h-adr properties, for example:		For backward compatibility, you may wish to use classic [[adr]] classnames in addition to the more future-proof h-adr properties, for example:

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<p class="h-adr adr">		<p class="h-adr adr">
	<span class="p-street-address street-address">123 Main St.</span>,		<span class="p-street-address street-address">123 Main St.</span>,
Line 112:		Line 112:
	...		...
	</p>		</p>
	</~~source~~>		</syntaxhighlight>

	The class '''<code>adr</code>''' is a ''backward compatible root class name'' that indicates the presence of an [[adr]].		The class '''<code>adr</code>''' is a ''backward compatible root class name'' that indicates the presence of an [[adr]].
Line 140:		Line 140:

	A: In short yes. You can do:		A: In short yes. You can do:
	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<span class="p-country-name">UK</span>		<span class="p-country-name">UK</span>
	</~~source~~>		</syntaxhighlight>
	However it's better if you mark it up with the <code>abbr</code> element and provide the full name as well, e.g.		However it's better if you mark it up with the <code>abbr</code> element and provide the full name as well, e.g.
	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<abbr class="p-country-name" title="United Kingdom">UK</abbr>		<abbr class="p-country-name" title="United Kingdom">UK</abbr>
	</~~source~~>		</syntaxhighlight>

	Consuming applications may interpret any 2-3 character country-name per the table of 2-3 character [http://en.wikipedia.org/wiki/ISO_3166-1#Officially_assigned_code_elements country codes in ISO3166].		Consuming applications may interpret any 2-3 character country-name per the table of 2-3 character [http://en.wikipedia.org/wiki/ISO_3166-1#Officially_assigned_code_elements country codes in ISO3166].

GRegorLove: set up status/editor/participate section, remove redundant DisplayTitle:h-adr

2022-10-01T18:41:01Z

set up status/editor/participate section, remove redundant DisplayTitle:h-adr

← Older revision		Revision as of 18:41, 1 October 2022
Line 1:		Line 1:
	~~{{DISPLAYTITLE:h-adr}}~~
	~~<span class="h-card vcard"><span class="p-name fn">[[User:Tantek\|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>~~
	~~----~~
	<dfn style="font-style:normal;font-weight:bold">h-adr</dfn> is a simple, open format for publishing structured locations such as addresses, physical and/or postal. h-adr is one of several open [[microformats\|microformat]] draft standards suitable for embedding data in HTML.		<dfn style="font-style:normal;font-weight:bold">h-adr</dfn> is a simple, open format for publishing structured locations such as addresses, physical and/or postal. h-adr is one of several open [[microformats\|microformat]] draft standards suitable for embedding data in HTML.

Line 8:		Line 5:
	For named addresses, e.g. people or venues, use [[h-card]].		For named addresses, e.g. people or venues, use [[h-card]].

	{{cc0-owfa-license}}		;<span id="Status">Status</span>
			:This is a '''Draft Specification'''
			;Participate
			:[[IRC]]: [irc://irc.libera.chat/microformats #microformats on Libera]
			;Editor
			:<span class="h-card vcard"><span class="p-name fn">[[User:Tantek\|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
			;License
			:{{cc0-owfa-license}}
			__TOC__

	== Example ==		== Example ==

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:23:09Z

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

← Older revision		Revision as of 16:23, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~h-adr~~</entry-title>~~		{{DISPLAYTITLE:h-adr}}
	<span class="h-card vcard"><span class="p-name fn">[[User:Tantek\|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>		<span class="h-card vcard"><span class="p-name fn">[[User:Tantek\|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
	----		----

Tantek: /* See Also */ address formats

2017-08-14T21:21:39Z

Tantek: editorial: drop explicit HTML5 on the web from dfn, unnecessary

2017-08-03T21:35:32Z

editorial: drop explicit HTML5 on the web from dfn, unnecessary

← Older revision		Revision as of 21:35, 3 August 2017
Line 2:		Line 2:
	<span class="h-card vcard"><span class="p-name fn">[[User:Tantek\|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>		<span class="h-card vcard"><span class="p-name fn">[[User:Tantek\|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
	----		----
	<dfn style="font-style:normal;font-weight:bold">h-adr</dfn> is a simple, open format for publishing structured locations such as addresses, physical and/or postal. h-adr is one of several open [[microformats\|microformat]] draft standards suitable for embedding data in HTML~~/HTML5 on the web~~.		<dfn style="font-style:normal;font-weight:bold">h-adr</dfn> is a simple, open format for publishing structured locations such as addresses, physical and/or postal. h-adr is one of several open [[microformats\|microformat]] draft standards suitable for embedding data in HTML.

	h-adr is the [[microformats-2]] update to [[adr]]. It is most commonly used as part of an [[h-card]] or [[h-event]].		h-adr is the [[microformats-2]] update to [[adr]]. It is most commonly used as part of an [[h-card]] or [[h-event]].

Benthatmustbeme: /* Backward Compatiblity */ typo

2017-05-01T13:31:52Z

Backward Compatiblity: typo

← Older revision		Revision as of 13:31, 1 May 2017
Line 97:		Line 97:
	{{h-spec-section-validating}}		{{h-spec-section-validating}}

	== Backward ~~Compatiblity~~ ==		== Backward Compatibility ==
	=== Publisher Compatibility ===		=== 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:		For backward compatibility, you may wish to use classic [[adr]] classnames in addition to the more future-proof h-adr properties, for example:

Tantek: /* Status */ -mailinglist

2015-05-25T04:26:28Z

Status: -mailinglist

← Older revision		Revision as of 04:26, 25 May 2015
Line 84:		Line 84:

	== Status ==		== 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 [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list]~~.		'''h-adr''' is a microformats.org draft specification. Public discussion on h-adr takes place on [[h-adr-feedback]] and the #microformats [[irc]] channel on irc.freenode.net.

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

Tantek: /* Example */ note why implicit name, use h-card for an explicitly named address

2015-05-16T23:21:53Z

Example: note why implicit name, use h-card for an explicitly named address

← Older revision		Revision as of 23:21, 16 May 2015
Line 53:		Line 53:
	</source>		</source>

	For a mailing address ~~with~~ a ~~name~~, use [[h-card]].		The implicit "name" property that is generated from parsing an h-adr is there for consuming applications to have a simple flattened string representation of an h-adr.

			For an explicitly named address (such as a mailing address to a specific person), use [[h-card]].

	=== Get started ===		=== Get started ===

Tantek: /* Properties */ explicitly note lack of p-name and should use h-card instead

2015-05-16T23:18:17Z

Properties: explicitly note lack of p-name and should use h-card instead

← Older revision		Revision as of 23:18, 16 May 2015
Line 78:		Line 78:

	All properties are optional.		All properties are optional.

			* '''<code>p-name</code>''' - there is no "p-name" property in h-adr. If your address has an explicit name, it's likely a venue, and you should use [[h-card]] instead.

	== Status ==		== Status ==

Tantek: note vcard was the basis

2015-05-14T22:01:31Z

note vcard was the basis

← Older revision		Revision as of 22:01, 14 May 2015
Line 148:		Line 148:
	* [[h-geo]] can be embedded in h-adr		* [[h-geo]] can be embedded in h-adr
	* [[h-card]] and [[h-event]] often contain h-adr		* [[h-card]] and [[h-event]] often contain h-adr
			* [[vcard]] (most recently vCard4 RFC6350) vocabulary is re-used by h-adr.

	[[Category:Draft Specifications]]		[[Category:Draft Specifications]]

← Older revision		Revision as of 21:21, 14 August 2017
Line 153:		Line 153:
	* [[h-card]] and [[h-event]] often contain h-adr		* [[h-card]] and [[h-event]] often contain h-adr
	* [[vcard]] (most recently vCard4 RFC6350) vocabulary is re-used by h-adr.		* [[vcard]] (most recently vCard4 RFC6350) vocabulary is re-used by h-adr.
			* [[address-formats]]

	[[Category:Draft Specifications]]		[[Category:Draft Specifications]]