|
| |
|
Meta Tags-Geo Placename
|
Example:
<meta name="geo.placename" content="Seattle,
Washington"> |
Recommendation:
Optional |
Complete Syntax:
|
|
Length: |
Minimum n/a |
Maximum n/a
|
Recommended n/a |
Usage:
|
Description:
The
geo.placename tag is provided
primarily for resource recognition; it is anticipated
that this field be harvested by automated agents and
presented to the user in search engine results in a
similar manner to the description META
tag.
|
Comments:
This field is free-text, and typically would be
used for city, county and state names. It could,
however, be used for resource discovery, particularly if
names from some controlled vocabulary such as the
Getty Thesaurus of Geographic Names is used. |
Examples:
|
<meta name="geo.placename"
content="<placename>"> |
|
<META name="geo.placename" content="Boca Raton,
FL"> |
|
<meta name="geo.placename" content="Bracknell">
... |
|
<meta name="geo.placename" content="Eugene"> |
|
<meta name="geo.placename" content="Hamburg,
Germany"> |
|
<META NAME="geo.placename" CONTENT="Houston,
Texas, USA"><!-- The "geo.placename" tag is
provided primarily for resource recognition;
and typically would be used for city, state
and country names. -->
|
|
<meta name="geo.placename" content="Kazan,
Russian Federation"> |
|
<META NAME="geo.placename" content="London"> |
|
<META NAME="geo.placename" content="London,
Ont"> |
|
<META NAME="geo.placename" content="London,
Ont"><META NAME="geo.region" |
|
<META NAME="geo.placename" CONTENT="London,
Ontario"> |
|
<meta name="geo.placename" content="Northville"> |
|
<meta name="geo.placename" content="Paseo del
Prado"> |
<!--[if !vml]--><!--[endif]--><!--[if
!vml]--><!--[endif]-->
|
<META NAME="geo.placename"
CONTENT="Place Name"> |
|
|
<META NAME="geo.placename" CONTENT="Place
Name"><META NAME="geo.region" |
|
<meta name="geo.placename" content="Sackville"> |
|
<meta name="geo.placename" content="Seattle,
Washington"> |
|
<meta name="geo.placename" content="Your city,
Your Country"> |
|
<meta name="geo.placename” content="Eugene"> |
|
|
Google-Comments: |
|
Yahoo-Comments: |
|
MSN-Comments: |
|
AOL-Comments: |
|
Ask Jeeves-Comments: |
|
AltaVista-Comments: |
|
Excite-Comments: |
|
HotBot-Comments: |
|
Itomi-Comments: |
|
InfoSeek-Comments: |
| Lycos-Comments: |
|
NorthernLight-Comments: |
| |
| USA
Usage/Comments: |
| UK
Usage/Comments: |
| CDN Usage/Comments: |
| DCMI
Usage/Comments: |
| Other
International/Comments: |
| |
| Commercial
Usage/Comments: |
| Governmental
Usage/Comments: |
| Education
Usage/Comments: |
| Non-profit
Usage/Comments: |
| |
| HTML 1.0 |
| HTML 2.0 |
| HTML 3.2 |
| HTML 4.0 |
| XHTML |
| DHTML |
| eGMS |
| PICS |
| DCMI |
| W3C |
| ASP |
| Java |
| |
| |
| Internet Explorer
Browser: |
| Netscape Browser: |
| Firefox Browser: |
| AOL Browser: |
| Other Browser: |
| |
| |
| |
| |
Implementation
HTML markup should be added to the document in the form of a META
statement. This should be placed in the document head in accordance
with the HTML 4 specification [1]. The identifier "geo.position" is
used for Latitude and Longitude data. The identifier
"geo.placename" is used for a free text representation of the
position, for example "city, province" or "town, county, state". The
identifier "geo.region" is used for the country subdivision code from
ISO 3166-2 [10].
For resources within the United States and Canada, the "geo.region"
identifier as given by ISO 3166-2 is typically constructed from the
2-character country code [5] as used in Internet domain names, and
the common 2-character State/Province codes [8][9], joined with an
underscore, for example "CA_BC" for British Columbia, Canada.
Where the official subdivision code is unknown, the 2-character
country code alone may be used in "geo.region", for example "DE" for
Germany.
It is anticipated that the "geo.placename" tag be used for resource
recognition, rather than resource discovery, due to possible
ambiguities in naming convention, language, word ordering and
placename duplicates.
Although the HTML specification [1] states that the name field is in
general case-sensitive, these "geo" tags should be recognized by
compliant agents regardless of case. Coordinates should be ordered
(Latitude ; Longitude) as for RFC 2426, RFC 2445 (vCard and iCal
specifications) [6][7]. This is at variance with common GIS practice,
but better matches the intended audience of this Draft.
Examples
<META NAME="geo.position" content="48.54;-123.84">
describes a resource at position 48.54 degrees North, 123.84 degrees
West, while
<META NAME="geo.position" content="-10;60">
describes a resource at position 10 degrees South, 60 degrees West.
<META NAME="geo.placename" content="London, Ont">
<META NAME="geo.region" content="ca_on">
describes a resource in London, Ontario, Canada while
<META NAME="geo.placename" content="London">
<META NAME="geo.region" content="gb">
describes a resource in London, England (Great Britain).
Internationalization considerations
The "geo.placename" tag content is free text, and should obey the
internationalization rules of HTML 4. "lang" and "dir" modifiers may
be used to specify the language of the content. Multiple instances of
geo.placename may be used with different "lang" modifiers.
Geo.placename content is coded using the character set of the
containing document.
|
| |
|
| |
|