GEOPRIV K. Wolf
Internet-Draft A. Mayrhofer
Expires: May 12, 2008 nic.at
Nov 09, 2007
Civic Address Considerations for Austria
draft-wolf-civicaddresses-austria-00
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 12, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
Providing civic address considerations for individual countries is
proposed in RFC4119. This documents provides such considerations for
Austria, and proposes a mapping of Austrian address elements to the
PIDF Location Object (PIDF-LO).
Wolf & Mayrhofer Expires May 12, 2008 [Page 1]
Internet-Draft Austrian Civic Addresses Nov 2007
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Civic Addresses in Austria . . . . . . . . . . . . . . . . . . 4
4. Sample Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
5. Address Codes in Austria . . . . . . . . . . . . . . . . . . . 9
6. Austrian Addresses in PIDF-LO . . . . . . . . . . . . . . . . 9
6.1. Mapping Austrian Addresses to existing PIDF-LO elements . 9
6.2. Additional PIDF-LO elements for Austria . . . . . . . . . 11
6.3. PIDF-LO elements not to be used in Austria . . . . . . . . 12
6.4. Country Element . . . . . . . . . . . . . . . . . . . . . 13
6.5. A1 Element . . . . . . . . . . . . . . . . . . . . . . . . 13
6.6. A2 Element . . . . . . . . . . . . . . . . . . . . . . . . 13
6.7. Additional Code Element . . . . . . . . . . . . . . . . . 14
7. Location by Reference with the Austrian Address Code . . . . . 14
8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Security & Privacy Considerations . . . . . . . . . . . . . . 15
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
12.1. Normative References . . . . . . . . . . . . . . . . . . . 16
12.2. Informative References . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 18
Wolf & Mayrhofer Expires May 12, 2008 [Page 2]
Internet-Draft Austrian Civic Addresses Nov 2007
1. Introduction
The "Presence Information Data Format Location Object" (PIDF-LO) [2]
is an an object format for carrying geographical information on the
Internet. PIDF-LO can be used to carry civic address information,
and supports a range of "civic address types" (CATypes) to describe
individual attributes of an civic address (see Section 2.2.1 of RFC
4119). The list of CATypes is currently under revision (see Secion
3.1 of draft-ietf-geopriv-revised-civic-lo [8]. This document is
based on the revised set of CATypes.
The Austrian "Gebaeude- und Wohnungsregistergesetz" (building and
habitation registry law) is the legal basis for the obligation to
provide a registry of civic addresses, buildings and their usable
units (subdivisions of buildings). The registry is operated by
"Statistik Austria GmbH", a fully governmental owned company.
Responsibility for keeping records in the registry up to date is an
obligation to the local administration of the individual townships.
The data format definition for the individual records is publicly
available (data access itself is however restricted). Hence, an
uniform address data base for whole Austria is available.
Unfortunately, Austrian civic addresses use a much more complex
format compared to civic addresses in PIDF-LO. A detailed
description of the Austrian civic address data format is contained in
section Section 3.
A guideline of how to use PIDF-LO for Austrian addresses is necessary
in order to avoid misinterpretations. This is especially important
if the PIDF-LO is conveyed during an emergency call to a Public
Safety Answering Point (PSAP). A precise location information is
needed in case of emergency to send out responders without any delay
to the correct location of the caller. If every data-provider uses
its own address mapping to PIDF-LO, confusion and misunderstandings
are bound to happen. However, ideally any PSAP should have full
access to the data by Statistik Austria. PSAPs must be able to rely
that location information is always provided the same way by all
data-providers. To address the idiosyncrasies in Austria, the civic
address elements are discussed subsequently.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [1].
Wolf & Mayrhofer Expires May 12, 2008 [Page 3]
Internet-Draft Austrian Civic Addresses Nov 2007
3. Civic Addresses in Austria
Statistik Austria data describes estates, buildings and usable units
[4]. On a single estate there may be any number of buildings.
Apartment houses that have more than one staircase, are split up in
separate buildings at every staircase. In every building, there may
be several usable units. For example, an apartment house may have
several apartments, counting as separate usable units. Moreover, one
building may have more than one address, but at least one address.
Below, the address elements for estates (Table 1), buildings
(Table 2) and usable units (Table 3) are shown.
Wolf & Mayrhofer Expires May 12, 2008 [Page 4]
Internet-Draft Austrian Civic Addresses Nov 2007
+-------------------------+-----------------------------------------+
| Statistik Austria name | Explaination |
+-------------------------+-----------------------------------------+
| Adresscode | address identifier |
| | |
| Gemeindename, | commune name and identifier |
| Gemeindekennziffer | |
| | |
| Ortschaftsname, | village name and identifier |
| Ortschaftskennziffer | |
| | |
| Strassenname, | street name and identifier |
| Strassenkennziffer | |
| | |
| Katastralgemeindename, | commune subdivision name and identifier |
| Katastralgemeindenummer | |
| | |
| Hausnummerntext | text in front of the house number |
| | |
| Hausnummer - 1. Teil - | first part of the house number, numeric |
| Nummer | |
| | |
| Hausnummer - 1. Teil - | first part of the house number, |
| Buchstabe | character |
| | |
| Hausnummer - | links first and Bis part of house |
| Verbindungszeichen Teil | number |
| 1 -> Bis | |
| | |
| Hausnummer - Bis-Nummer | number of bis part of house number |
| | |
| Hausnummer - | character of bis part of house number |
| Bis-Buchstabe | |
| | |
| Hausnummernbereich | indicates if all house numbers |
| | specified or just odd or even numbers |
| | are stated |
| | |
| Grundstuecksnummer | estate identifier |
| | |
| Postleitzahl | postal code |
| | |
| Postleitzahlengebiet | postal community code |
| | |
| Vulgoname | local name |
| | |
| Hofname | farm name |
+-------------------------+-----------------------------------------+
Wolf & Mayrhofer Expires May 12, 2008 [Page 5]
Internet-Draft Austrian Civic Addresses Nov 2007
Table 1: Civic Address Elements for Estates
+------------------------+------------------------------------------+
| Statistik Austria name | Explaination |
+------------------------+------------------------------------------+
| Adressubcode | address subcode |
| | |
| Objektnummer | object code |
| | |
| Hausnummer - | links Bis and second part of house |
| Verbindungszeichen | number |
| Teil Bis -> Teil 2 | |
| | |
| Hausnummer - 2. Teil - | second part of the house number, numeric |
| Nummer | |
| | |
| Hausnummer - 2. Teil - | second part of the house number, |
| Buchstabe | character |
| | |
| Hausnummer - | links second and third part of house |
| Verbindungszeichen | number |
| Teil 2-> Teil 3 | |
| | |
| Hausnummer - 3. Teil - | third part of the house number, numeric |
| Nummer | |
| | |
| Hausnummer - 3. Teil - | third part of the house number, |
| Buchstabe | character |
| | |
| Gebaeudeunterscheidung | for differentiation of buildings, e.g. |
| | Maierweg 27 Hotel vers. Maierweg 27 |
| | Appartmenthaus |
| | |
+------------------------+------------------------------------------+
Table 2: Additional Civic Address Elements for Buildings
Wolf & Mayrhofer Expires May 12, 2008 [Page 6]
Internet-Draft Austrian Civic Addresses Nov 2007
+-----------------------------+-------------------------------------+
| Statistik Austria name | Explaination |
+-----------------------------+-------------------------------------+
| Nutzungseinheitenlaufnummer | usable unit code |
| | |
| Tuernummer | door number |
| | |
| Topnummer | unit number |
| | |
| Lagebeschreibung | for verbal description |
| | |
| Lage | describes if the usable unit is in |
| | the basement, mezzanine, attic |
| | floor, ... (but not the floor |
| | number) |
| | |
| Stockwerk | floor |
| | |
+-----------------------------+-------------------------------------+
Table 3: Additional Civic Address Elements for usable units
Note: "Floors" in Austria (as in most parts of Europe) are counted
differently compared to the US. The "1st floor" in Austria is
actually the floor above the floor at street level (2nd floor in US),
not considering the fact that in old buildings there might be even
more floors between street level and 1st floor, like "mezzanine",
"2nd mezzanine". So, an Austrian "1st floor" could well be the "4th
floor" according to US nomenclature.
According to Statistik Austria [3], 81.5% of Austrian addresses are
of the simple type Musterstrasse 1 (Musterstrasse is an example
street name). 5% of all addresses have an additional character, like
Musterstrasse 1b. 1% of Austrian addresses look like Musterstrasse
21a-23a. For 8% of addresses, an additional separator is necessary,
like Musterstrasse 10 Haus 1 Stiege 2 or Musterstrasse 20 Gruppe A
Reihe 1 Parzelle 13 or Musterstrasse 30 Weg 1 Parzelle 10. Very
seldom, there are so called special addresses (0.03%), for example
Musterstrasse gegenueber 3a, meaning this address is actually vis-a-
vis of house number 3a. Rather surprisingly, 4.47% of Austrian
addresses contain the identifier of the estate since no house number
is assigned at all, for example: Musterstrasse GNR 1234, or
Musterstrasse GNR .12/4 Kirche (this type of addresses is common for
churches) or a real example in Stockerau: Kolomaniwoerth GNR 1583.
This identifier is stored by Statistik Austria as Hausnummerntext.
Otherwise one could misinterpret this number as a house number, what
would be definitely wrong.
Wolf & Mayrhofer Expires May 12, 2008 [Page 7]
Internet-Draft Austrian Civic Addresses Nov 2007
4. Sample Addresses
In order to clarify the Austrian civic address format, this section
provides some exemplary addresses:
1234 Musterstadt, Hauptstrasse 1a - 5a Block 1b Haus 2c Stiege 1
Postleitzahl: 1234
Stadt: Musterstadt
Strasse: Hauptstrasse
Hausnummer - 1. Teil - Nummer: 1
Hausnummer - 1. Teil - Buchstabe: a
Hausnummer - Verbindungszeichen Teil 1 -> Bis: -
Hausnummer - 2. Teil - Nummer: 5
Hausnummer - 2. Teil - Buchstabe: a
Hausnummer - Verbindungszeichen Teil Bis -> Teil 2: Block
Hausnummer - 2. Teil - Nummer: 1
Hausnummer - 2. Teil - Buchstabe: b
Hausnummer - Verbindungszeichen Teil 2-> Teil 3: Haus
Hausnummer - 3. Teil - Nummer: 2
Hausnummer - 3. Teil - Buchstabe: c
Gebaeudeunterscheidung: Stiege 1
1234 Musterstadt, Musterstrasse 13 Hotel
Postleitzahl: 1234
Stadt: Musterstadt
Strasse: Musterstrasse
Hausnummer - 1. Teil - Nummer: 13
Gebaeudeunterscheidung: Hotel
6020 Innsbruck, Anichstrasse vor 35
Postleitzahl: 6020
Stadt: Innsbruck
Strasse: Anichstrasse
Hausnummerntext: vor ("in front of")
Hausnummer: 35
6173 Oberperfuss, Riedl 3097 (Pfarrkirche)
Postleitzahl: 6173
Stadt: Oberperfuss
Strasse: Riedl
Hausnummerntext: 3097
(since the estate identifier is 81305 3097 where 81305 is the
Katastralgemeindenummer (commune subdivision name) and no house
number is assigned)
Vulgoname: Pfarrkirche
Wolf & Mayrhofer Expires May 12, 2008 [Page 8]
Internet-Draft Austrian Civic Addresses Nov 2007
5. Address Codes in Austria
Statistik Austria registers 4 codes: Adresscode, Adresssubcode,
Objektnummer and the Nutzungseinheitenlaufnummer. The Adresscode (7
digits) is a unique code for an address in Austria. The
Adressregister maps the Adresscode to the civic address. If there is
a building located at an address, there is also an Adresssubcode (3
digits) assigned. Every building at an address has its own
Adresssubcode (assigned sequentially starting with 001, 002, 003 and
so on) in order to distinguish between buildings at the same address.
Furthermore, every building located in Austria has its own unique
code, the Objektnummer (7 digits). This code identifies the building
independent of the Adresscode. That's because addresses are subject
to change while the building may persist. To differ multiple usable
units inside a building, the Nutzungseinheitenlaufnummer (4 digits)
is used. This code is also assigned in sequential order for each
building.
Besides, every address and building is geocoded by Statistik Austria.
Hence, if every PIDF-LO location object would carry data in the
format of Statistik Austria and every PSAP would use the database of
Statistik Austria for mapping, a time saving, definite mapping
without irregularities could be achieved.
Besides these codes, Statistik Austria maintains reference numbers
for communes, localities or streets, to mention just a few.
6. Austrian Addresses in PIDF-LO
A good number of Austrian addresses do not fit into the PIDF-LO
format, as described in the previous section. There are several
options to map Austrian addresses to PIDF-LO. First, one could merge
all the Austrian address fields to the existing PIDF-LO elements (by
violating the intended purpose of the element and loss of precision).
Another way is to define other civic address elements for use by
Austrian addresses. An unacceptable option would be to just omit all
the address data that does not fit into PIDF-LO. However, that
certainly causes wrong addresses (instead of Hauptstrasse 1a - 5a
Block 1b Haus 2c Stiege 1 just Hauptstrasse 1a).
6.1. Mapping Austrian Addresses to existing PIDF-LO elements
First, there are some common data elements, that can be mapped
directly without any problems. The following elements are:
Wolf & Mayrhofer Expires May 12, 2008 [Page 9]
Internet-Draft Austrian Civic Addresses Nov 2007
country see Section 6.4
A1 see Section 6.5
A2 political district (politscher Bezirk), see Section 6.6
A3 city (Stadt, Gemeinde)
A4 Ortschaft (see exception for Vienna below)
A6 Strasse
LMK Hofname
LOC
FLR
NAM Vulgoname
PC
BLD
UNIT
ROOM
PLC
PCN
POBOX
SEAT
Unfortunately, there are elements, that can not unambiguously be
entered. PIDF-LO only defines a single house number element (HNO,
numeric part only) and a house number suffix element (HNS). This is
unsuitable for the situation in Austria and far too less fields.
Statistik Austria knows 14 data fields related to the house number of
a building plus another 6 fields for distinction of different usable
units inside a building (including the floor, which has a separate
field in PIDF-LO). By violating the rules of PIDF-LO, one could
simply concatenate all the house number information into the HNO
element, even though it is expected to hold numeric part only.
Consequently this may cause troubles at the side of the receiver of
the location object. Moreover, the price is a loss in precision
since the different house number parts cannot be easily separated
again. It is recommended, not to use the HNS element for Austrian
addresses, since there are addresses that do not have just one
suffix. For example, the address Lazarettgasse 13A could be mapped
by:
<HNO>13</HNO> <HNS>A</HNS>
However, the building at Lazarettgasse has the house number 13A-13C.
Consequently, just the HNO element should be used:
<HNO>13A-13C</HNO>
And even for addresses with a house number consisting of a single
number and a single prefix, just HNO should be use because of
uniformity:
Wolf & Mayrhofer Expires May 12, 2008 [Page 10]
Internet-Draft Austrian Civic Addresses Nov 2007
<HNO>13A</HNO>
Addresses with a house number text would look like:
<HNO>vor 1-1A</HNO>
with no HNS element. Last, there is another exception to mention
concerning the Austrian capital Vienna (Wien). The city of Vienna is
equal to its political district and even the state is called Vienna.
Nevertheless, Vienna is separated in 23 districts within the same
political district. Consequently, an address in Vienna would look
like:
<country>AT</country>
<a1>Wien</a1>
<a2>Wien</a2>
<a3>Wien</a3>
<a4>Innere Stadt</a4> or <a4>1<a4>
The element A4, holding the city division, must hold the name or the
number of the district.
6.2. Additional PIDF-LO elements for Austria
In order to create a PIDF-LO document holding all available data from
Statistik Austria separately, new elements are necessary. Table 4
lists the additional elements needed for Austrian addresses.
Wolf & Mayrhofer Expires May 12, 2008 [Page 11]
Internet-Draft Austrian Civic Addresses Nov 2007
+----------------------------------------------------+
| Statistik Austria name |
+----------------------------------------------------+
| Katastralgemeindename, Katastralgemeindenummer |
| Hausnummerntext |
| Hausnummer - 1. Teil - Nummer |
| Hausnummer - 1. Teil - Buchstabe |
| Hausnummer - Verbindungszeichen Teil 1 -> Bis |
| Hausnummer - Bis-Nummer |
| Hausnummer - Bis-Buchstabe |
| Hausnummernbereich |
| Grundstuecksnummer |
| Vulgoname |
| Hofname |
| Hausnummer - Verbindungszeichen Teil Bis -> Teil 2 |
| Hausnummer - 2. Teil - Nummer |
| Hausnummer - 2. Teil - Buchstabe |
| Hausnummer - Verbindungszeichen Teil 2-> Teil 3 |
| Hausnummer - 3. Teil - Nummer |
| Hausnummer - 3. Teil - Buchstabe |
| Gebaeudeunterscheidung |
| Tuernummer |
| Topnummer |
| Lagebeschreibung |
| Lage |
+----------------------------------------------------+
Table 4: Additional PIDF-LO elements for Austria
6.3. PIDF-LO elements not to be used in Austria
The street suffix STS is not used in the data format of Statistik
Austria. Consequently, this element can be omitted, since it is
always included in the A6 element. This is a common practice in
Austria. The following listing shows all PIDF-LO elements that
should not be used for representing Austrian addresses:
A5
STS
HNS
PRD
POD
RD
RDBR
RDSUBBR
PRM
POM
Wolf & Mayrhofer Expires May 12, 2008 [Page 12]
Internet-Draft Austrian Civic Addresses Nov 2007
6.4. Country Element
The country element for Austria must be set to AT, since this is the
ISO 3166-1 [5] alpha-2 code for Austria.
<country>AT</country>
The usage of the ISO 3166 code is demanded by RFC 4119 [2] and
I-D.ietf-geopriv-revised-civic-lo [8] proposes to use upper case
characters only.
6.5. A1 Element
As proposed in I-D.ietf-geopriv-revised-civic-lo [8], for the PIDF-LO
element A1, the second part of ISO 3166-2 [6] can be used. However,
in Austria it is also common to write out the names of the states.
Table 5 shows the possible values of the A1 element for Austrian
states.
+-------------------+--------------------------------+
| Bundesland | second part of ISO 3166-2 code |
+-------------------+--------------------------------+
| Burgenland | 1 |
| | |
| Kaernten | 2 |
| | |
| Niederoesterreich | 3 |
| | |
| Oberoesterreich | 4 |
| | |
| Salzburg | 5 |
| | |
| Steiermark | 6 |
| | |
| Tirol | 7 |
| | |
| Vorarlberg | 8 |
| | |
| Wien | 9 |
+-------------------+--------------------------------+
Table 5: A1 element format for Austria
6.6. A2 Element
Names of the Austrian political districts are available at Statistik
Austria [7]. These names can be used for the A2 element. Statistik
Austria also has a unique code for each political district, which
Wolf & Mayrhofer Expires May 12, 2008 [Page 13]
Internet-Draft Austrian Civic Addresses Nov 2007
could be used to identify the political district in the A2 element.
The district Bruck an der Leitha could be represented by:
<A2>Bruck an der Leitha<A2> or <A2>307</A2>
6.7. Additional Code Element
The element additional code could be used to hold the codes provided
by Statistik Austria. There is an Adresscode, Adressubcode,
Objektnummer and a Nutzungseinheitenlaufnummer. These unique codes
identify the location. Actually, these codes alone would be enough,
which leads to location by reference with address codes, for Austria
described in Section 7.
If the additional code in a PIDF-LO document is going to hold the
codes from Statistik Austria, the following format should be used:
<addcode>AdrCD=1234567;AdrsubCD=123;ObjNr=2333211;NtzLnr=0001</addcode>
By setting the country element to AT (see Section 6.4), indicating an
Austrian address, the Additional Code element is expected to hold
codes from Statistik Austria only. When creating PIDF-LO documents
using address codes by Statistik Austria, the country and addcode
elements are mandatory.
7. Location by Reference with the Austrian Address Code
As explained in the previous section, the codes of Statistik Austria
alone are enough to describe a location. A PIDF-LO document could
therefore just contain the country and the appropriate codes.
Consequently it would be possible to just convey an identifier as key
to the location information. Therefore, it would be necessary that
all potential location recipients have access to the database to
resolve the identifier to the location. One way to put this idea to
an international and consistent way is to request an URN space for
that purpose. Each country may register its own URN for their codes
with different meaning.
An proposed URN space for the addresscodes provided by Statistik
Austria could look like:
urn:addresscode:at:statistikaustria.AdrCD.AdrsubCD.ObjNr.NtzLnr
For example:
urn:addresscode:at:statistikaustria.1234567.004.2333211.0017
Wolf & Mayrhofer Expires May 12, 2008 [Page 14]
Internet-Draft Austrian Civic Addresses Nov 2007
8. Example
This section shows an example mapping of an Austrian address mapping
to the existing PIDF-LO elements. This example is of a simple type,
so that no additional elements are used for this case. However, if
the civic address elements are needed separately at the side of the
receiver, a distinct mapping to separate field would be desirable.
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:cl=" urn:ietf:params:xml:ns:pidf:geopriv10:civicLoc"
entity="pres:123@localhost">
<tuple id="123456">
<status>
<gp:geopriv>
<gp:location-info>
<cl:civicAddress>
<cl:country>AT</country>
<cl:a1>Wien</a1>
<cl:a2>Wien</a2>
<cl:a3>Wien</a3>
<cl:a4>9</a4>
<cl:a6>Lazarettgasse</a6>
<cl:HNO>13A-13C</HNO>
<cl:PC>1090<PC>
</cl:civicAddress>
</gp:location-info>
<gp:usage-rules>
<gp:retransmission-allowed>yes</gp:retransmission-allowed>
<gp:retention-expiry>2007-11-10T12:00:00Z</gp:retention-expiry>
</gp:usage-rules>
</gp:geopriv>
</status>
<timestamp>2007-11-09T12:00:00Z</timestamp>
</tuple>
</presence>
9. Security & Privacy Considerations
RFC 4119 contains general security considerations for handling PIDF-
LOs. In addition to that, it has to be considered that data from the
Austrian building and habitation unit registry are generally not
public, so restrictions as imposed on the original data set MUST also
be imposed on the resulting PIDF-LO document.
Wolf & Mayrhofer Expires May 12, 2008 [Page 15]
Internet-Draft Austrian Civic Addresses Nov 2007
10. IANA Considerations
At this stage, this document contains no considerations for IANA.
However, if a definition of an "civic address URN" as sketeched out
in section Section 7 is to be used, the respective URN namespaces
need to be registered with IANA.
11. Acknowledgements
The authors wish to thank Gregor Jaenin for contributing insights
about the Austrian civic address data format.
12. References
12.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] Peterson, J., "A Presence-based GEOPRIV Location Object Format",
RFC 4119, December 2005.
12.2. Informative References
[3] Statistik Austria, "Handbuch Adress-GWR-Online Teil A
Theoretisches Handbuch Kapitel 2 Warten von Adressen im Adress-
GWR-Online", Jan 2005.
[4] Statistik Austria, "Handbuch Adress-GWR-Online Teil C Anhang 2
Merkmalskatalog", Sept 2004.
[5] International Organization for Standardization, "Codes for the
representation of names of countries and their subdivisions -
Part 1: Country codes", ISO Standard 3166-1:1997, 1997.
[6] International Organization for Standardization, "Codes for the
representation of names of countries and their subdivisions -
Part 2: Country subdivision code", ISO Standard 3166-2:1998,
1998.
[7] Statistik Austria, "Politische Bezirke, Gebietsstand 2007",
Oct 2007.
[8] Thomson, M. and J. Winterbottom, "Revised Civic Location Format
for PIDF-LO", draft-ietf-geopriv-revised-civic-lo-06 (work in
progress), October 2007.
Wolf & Mayrhofer Expires May 12, 2008 [Page 16]
Internet-Draft Austrian Civic Addresses Nov 2007
Authors' Addresses
Karl Heinz Wolf
nic.at GmbH
Karlsplatz 1/2/9
Wien A-1010
Austria
Phone: +43 1 5056416 37
Email: karlheinz.wolf@nic.at
URI: http://www.nic.at/
Alexander Mayrhofer
nic.at GmbH
Karlsplatz 1/2/9
Wien A-1010
Austria
Phone: +43 1 5056416 34
Email: alexander.mayrhofer@nic.at
URI: http://www.nic.at/
Wolf & Mayrhofer Expires May 12, 2008 [Page 17]
Internet-Draft Austrian Civic Addresses Nov 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Wolf & Mayrhofer Expires May 12, 2008 [Page 18]