| 1 |
<pre>Internet Engineering Task Force (IETF) K. Wolf |
| 2 |
Request for Comments: 5774 A. Mayrhofer |
| 3 |
BCP: 154 nic.at |
| 4 |
Updates: <a href="./rfc4776">4776</a> March 2010 |
| 5 |
Category: Best Current Practice |
| 6 |
ISSN: 2070-1721 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">Considerations for Civic Addresses in the</span> |
| 10 |
<span class="h1">Presence Information Data Format Location Object (PIDF-LO):</span> |
| 11 |
<span class="h1">Guidelines and IANA Registry Definition</span> |
| 12 |
|
| 13 |
Abstract |
| 14 |
|
| 15 |
This document provides a guideline for creating civic address |
| 16 |
considerations documents for individual countries, as required by <a href="./rfc4776">RFC</a> |
| 17 |
<a href="./rfc4776">4776</a>. Furthermore, this document also creates an IANA Registry |
| 18 |
referring to such address considerations documents and registers such |
| 19 |
address considerations for Austria. |
| 20 |
|
| 21 |
Status of This Memo |
| 22 |
|
| 23 |
This memo documents an Internet Best Current Practice. |
| 24 |
|
| 25 |
This document is a product of the Internet Engineering Task Force |
| 26 |
(IETF). It represents the consensus of the IETF community. It has |
| 27 |
received public review and has been approved for publication by the |
| 28 |
Internet Engineering Steering Group (IESG). Further information on |
| 29 |
BCPs is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 30 |
|
| 31 |
Information about the current status of this document, any errata, |
| 32 |
and how to provide feedback on it may be obtained at |
| 33 |
<a href="http://www.rfc-editor.org/info/rfc5774">http://www.rfc-editor.org/info/rfc5774</a>. |
| 34 |
|
| 35 |
Copyright Notice |
| 36 |
|
| 37 |
Copyright (c) 2010 IETF Trust and the persons identified as the |
| 38 |
document authors. All rights reserved. |
| 39 |
|
| 40 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 41 |
Provisions Relating to IETF Documents |
| 42 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 43 |
publication of this document. Please review these documents |
| 44 |
carefully, as they describe your rights and restrictions with respect |
| 45 |
to this document. Code Components extracted from this document must |
| 46 |
include Simplified BSD License text as described in Section 4.e of |
| 47 |
the Trust Legal Provisions and are provided without warranty as |
| 48 |
described in the Simplified BSD License. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 60 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-4">4</a> |
| 61 |
<a href="#section-3">3</a>. Requirements ....................................................<a href="#page-4">4</a> |
| 62 |
<a href="#section-4">4</a>. Specifying PIDF-LO Element Usage ................................<a href="#page-5">5</a> |
| 63 |
<a href="#section-4.1">4.1</a>. General Considerations and Workflow ........................<a href="#page-5">5</a> |
| 64 |
<a href="#section-4.2">4.2</a>. Guidelines for Individual Elements .........................<a href="#page-7">7</a> |
| 65 |
<a href="#section-4.2.1">4.2.1</a>. Country .............................................<a href="#page-7">7</a> |
| 66 |
<a href="#section-4.2.2">4.2.2</a>. Country Subdivisions A1-A6 ..........................<a href="#page-7">7</a> |
| 67 |
<a href="#section-4.2.3">4.2.3</a>. Road and Street Names ...............................<a href="#page-8">8</a> |
| 68 |
<a href="#section-4.2.4">4.2.4</a>. House Numbers .......................................<a href="#page-8">8</a> |
| 69 |
<a href="#section-4.2.5">4.2.5</a>. Local Names .........................................<a href="#page-9">9</a> |
| 70 |
<a href="#section-4.2.6">4.2.6</a>. Floors .............................................<a href="#page-10">10</a> |
| 71 |
<a href="#section-4.2.7">4.2.7</a>. Address Codes ......................................<a href="#page-10">10</a> |
| 72 |
<a href="#section-4.2.8">4.2.8</a>. Other Elements .....................................<a href="#page-11">11</a> |
| 73 |
<a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-12">12</a> |
| 74 |
<a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-12">12</a> |
| 75 |
<a href="#section-6.1">6.1</a>. PIDF-LO Civic Address Considerations Registry .............<a href="#page-12">12</a> |
| 76 |
<a href="#section-6.1.1">6.1.1</a>. Structure ..........................................<a href="#page-12">12</a> |
| 77 |
<a href="#section-6.1.2">6.1.2</a>. Registration Template ..............................<a href="#page-13">13</a> |
| 78 |
<a href="#section-6.1.3">6.1.3</a>. Registry Location ..................................<a href="#page-14">14</a> |
| 79 |
<a href="#section-6.1.4">6.1.4</a>. Registration Procedure .............................<a href="#page-14">14</a> |
| 80 |
<a href="#section-6.2">6.2</a>. Registration Request for Austria ..........................<a href="#page-14">14</a> |
| 81 |
6.3. Registration of the Considerations in <a href="./rfc4776">RFC 4776</a> as |
| 82 |
Obsolete ..................................................<a href="#page-14">14</a> |
| 83 |
<a href="#section-7">7</a>. Acknowledgements ...............................................<a href="#page-17">17</a> |
| 84 |
<a href="#appendix-A">Appendix A</a>. Civic Address Considerations Registration for |
| 85 |
the Austrian Building and Habitation Registry .............<a href="#page-18">18</a> |
| 86 |
<a href="#appendix-A.1">A.1</a>. Civic Address Format in Austria ...........................<a href="#page-18">18</a> |
| 87 |
<a href="#appendix-A.2">A.2</a>. Sample Addresses ..........................................<a href="#page-22">22</a> |
| 88 |
<a href="#appendix-A.3">A.3</a>. Address Codes in Austria ..................................<a href="#page-23">23</a> |
| 89 |
<a href="#appendix-A.4">A.4</a>. Austrian Addresses in PIDF-LO .............................<a href="#page-23">23</a> |
| 90 |
<a href="#appendix-A.4.1">A.4.1</a>. Country ............................................<a href="#page-23">23</a> |
| 91 |
<a href="#appendix-A.4.2">A.4.2</a>. Country Subdivisions A1-A6 .........................<a href="#page-24">24</a> |
| 92 |
<a href="#appendix-A.4.3">A.4.3</a>. Road and Street Names ..............................<a href="#page-27">27</a> |
| 93 |
<a href="#appendix-A.4.4">A.4.4</a>. House Numbers ......................................<a href="#page-27">27</a> |
| 94 |
<a href="#appendix-A.4.5">A.4.5</a>. Local Names ........................................<a href="#page-28">28</a> |
| 95 |
<a href="#appendix-A.4.6">A.4.6</a>. Floors .............................................<a href="#page-28">28</a> |
| 96 |
<a href="#appendix-A.4.7">A.4.7</a>. Additional Code Element ............................<a href="#page-28">28</a> |
| 97 |
<a href="#appendix-A.4.8">A.4.8</a>. Other Elements .....................................<a href="#page-29">29</a> |
| 98 |
<a href="#appendix-A.4.9">A.4.9</a>. Elements Not to Be Used ............................<a href="#page-29">29</a> |
| 99 |
<a href="#appendix-A.5">A.5</a>. Example ...................................................<a href="#page-29">29</a> |
| 100 |
<a href="#appendix-A.6">A.6</a>. IANA Registration Record ..................................<a href="#page-30">30</a> |
| 101 |
Normative References ..............................................<a href="#page-31">31</a> |
| 102 |
Informative References ............................................<a href="#page-32">32</a> |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
The Presence Information Data Format Location Object (PIDF-LO) |
| 116 |
[<a href="./rfc4119" title=""A Presence-based GEOPRIV Location Object Format"">RFC4119</a>] is an object format for carrying geographical information |
| 117 |
on the Internet. PIDF-LO can contain civic address information and |
| 118 |
supports a range of "civic address types" (CAtypes) to hold the |
| 119 |
individual attributes of such addresses (see <a href="./rfc4119#section-2.2.1">Section 2.2.1 of |
| 120 |
[RFC4119]</a> and <a href="./rfc5139#section-3.1">Section 3.1 of [RFC5139]</a>). |
| 121 |
|
| 122 |
In many use cases, PIDF-LOs are populated with data from long- |
| 123 |
established sources, like postal and governmental building registers, |
| 124 |
line information databases and yellow/white pages of infrastructure |
| 125 |
providers, or official residents registers. The structure and format |
| 126 |
of data from such sources is almost always different from PIDF-LO's |
| 127 |
CAtypes definition -- additionally, the structure and format of those |
| 128 |
sources differ from country to country. |
| 129 |
|
| 130 |
To make use of such existing data sources, transposing that data into |
| 131 |
PIDF-LO format is required. With no guidelines available on how to |
| 132 |
map source Fields into CAtype Elements, different creators of PIDF-LO |
| 133 |
documents might end up with different results, even when using the |
| 134 |
same data source, which reduces interoperability and increases the |
| 135 |
risk of misinterpretation by recipients. |
| 136 |
|
| 137 |
Therefore, civic address considerations are necessary to ensure |
| 138 |
uniform usage of PIDF-LO Elements for such data sources. [<a href="./rfc4776" title=""Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information"">RFC4776</a>] |
| 139 |
explicitly requests such documents to be provided, but defines |
| 140 |
neither their structure nor a way to publish them. This memo |
| 141 |
provides documentation on how to create such civic address |
| 142 |
considerations, and IANA has created a registry to store references |
| 143 |
to such documents. Furthermore, civic address considerations for |
| 144 |
Austria are provided in <a href="#appendix-A">Appendix A</a> and have been registered in the |
| 145 |
IANA registry. |
| 146 |
|
| 147 |
<a href="./rfc4776#section-3.4">Section 3.4 of [RFC4776]</a> contains some example considerations |
| 148 |
regarding the use of administrative subdivision Elements for Canada, |
| 149 |
Germany, Japan, Korea, and the United States. This document |
| 150 |
registers these examples with IANA as "obsolete" (see <a href="#section-6.3">Section 6.3</a>). |
| 151 |
|
| 152 |
<a href="./rfc4776#section-3.4">Section 3.4 of [RFC4776]</a> also contains instructions on the creation |
| 153 |
of civic address considerations documents on page 8. This document |
| 154 |
updates that section and replaces said instructions with Sections <a href="#section-4">4</a> |
| 155 |
and 5 of this memo. |
| 156 |
|
| 157 |
The guidelines in this document have been created with a focus on |
| 158 |
formal application of PIDF-LO (such as conveying location during an |
| 159 |
emergency call). It is not intended to forbid other, more informal |
| 160 |
uses of PIDF-LO that may not follow any formal mapping |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 167 |
|
| 168 |
|
| 169 |
specifications. An example use case of such informal usage may be |
| 170 |
the transmission of PIDF-LO documents during an instant-messaging |
| 171 |
session between humans. Such use may, however, imply some drawbacks, |
| 172 |
like prohibiting automatic processing of civic addresses from such a |
| 173 |
PIDF-LO. |
| 174 |
|
| 175 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 176 |
|
| 177 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 178 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 179 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 180 |
|
| 181 |
In addition, this document uses "Field" to refer to a field of a |
| 182 |
civic address data source, and "Element" to refer to a CAtype Element |
| 183 |
of a PIDF-LO. |
| 184 |
|
| 185 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Requirements</span> |
| 186 |
|
| 187 |
The following requirements apply to defining civic-address mapping |
| 188 |
considerations: |
| 189 |
|
| 190 |
o The considerations document MUST identify the data source to which |
| 191 |
the definitions apply. A brief description of its structure |
| 192 |
SHOULD be provided as well. |
| 193 |
|
| 194 |
o For any data source, just one active mapping definition should |
| 195 |
exist in order to reduce the risk of ambiguous interpretation. |
| 196 |
|
| 197 |
o The document MUST include instructions for any Field that occurs |
| 198 |
in the data. For any of the Fields, the document MUST describe |
| 199 |
whether the Field is required, optional, or must not be used in |
| 200 |
the mapping procedure. |
| 201 |
|
| 202 |
o Instructions MUST be included for any CAtype Element that is |
| 203 |
registered by the time the document is created. Those |
| 204 |
instructions MUST include information regarding whether an Element |
| 205 |
is required, optional, or must not be used in that mapping. In |
| 206 |
case the set of CAtypes is revised by the IETF, the address |
| 207 |
considerations document SHOULD be updated. Until an update is |
| 208 |
approved, the existing mapping procedure MUST be used. |
| 209 |
|
| 210 |
o Address mapping procedures SHOULD be reversible so that location |
| 211 |
recipients can identify the corresponding record in the original |
| 212 |
data source (given they have access to that source). |
| 213 |
|
| 214 |
o For any source data Field that is required or optional, at least |
| 215 |
one example mapping MUST be provided. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 223 |
|
| 224 |
|
| 225 |
o In many cases, data sources used in the mapping process might be |
| 226 |
subject to access restrictions. Such restrictions (as imposed on |
| 227 |
the original data) MUST also be imposed on the resulting PIDF-LO |
| 228 |
documents. The considerations document SHOULD note such |
| 229 |
restrictions in its Security Considerations section. |
| 230 |
|
| 231 |
Although the mapping is defined in a national way and the actual |
| 232 |
meaning of several PIDF-LO Elements may not be clear to an outsider, |
| 233 |
at least the country Element tells in what context this PIDF-LO was |
| 234 |
created. In case of emergency calls, a PIDF-LO would just be passed |
| 235 |
to a Public Safety Answering Point (PSAP) in the same country as the |
| 236 |
location generator anyway. However, in a border region there might |
| 237 |
be exceptions and the PIDF-LO could be sent to a neighboring country. |
| 238 |
The PIDF-LO can still be passed on to a PSAP in the right country |
| 239 |
(based on the country Element), or the PSAP might be aware of the |
| 240 |
mapping scheme used in the neighboring country. |
| 241 |
|
| 242 |
A consistent mapping is also very important for checking if two PIDF- |
| 243 |
LO documents describe the same location. When civic address Fields |
| 244 |
are put into different PIDF-LO Elements, it may be difficult to |
| 245 |
identify whether or not two PIDF-LOs describe identical addresses. |
| 246 |
|
| 247 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Specifying PIDF-LO Element Usage</span> |
| 248 |
|
| 249 |
The purpose of the civic address considerations for an individual |
| 250 |
data source is to create interoperability by specifying a common list |
| 251 |
of PIDF-LO Elements to be used and by defining the mapping between |
| 252 |
these Elements and the Fields of the respective data source. |
| 253 |
|
| 254 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. General Considerations and Workflow</span> |
| 255 |
|
| 256 |
The workflow for creating an address considerations document is as |
| 257 |
follows: |
| 258 |
|
| 259 |
1. Describe the data source to which the address considerations |
| 260 |
document applies. |
| 261 |
|
| 262 |
2. Identify all Fields from the data source and decide, for each of |
| 263 |
the Fields, whether or not it is to be used for the purpose of |
| 264 |
creating PIDF-LO documents. The considerations document must |
| 265 |
list all Fields (or at least state which Fields are considered in |
| 266 |
the mapping and clearly state that the other Fields MUST NOT be |
| 267 |
used). |
| 268 |
|
| 269 |
3. For each of the Fields that are required or optional, specify a |
| 270 |
clear mapping instruction according to the guidelines below. |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 279 |
|
| 280 |
|
| 281 |
4. Provide a list of all CAtypes registered and describe their level |
| 282 |
of usage in this mapping (or combine it with the list of Fields |
| 283 |
above and clearly list which Elements are not used for the |
| 284 |
mapping procedure). For Elements that are not described in |
| 285 |
detail, state whether they MUST NOT be used at all or whether |
| 286 |
they may be used without further restriction. |
| 287 |
|
| 288 |
5. Provide examples of source data and mapping results. |
| 289 |
|
| 290 |
Civic address Elements are designed to be generic containers. In |
| 291 |
some cases, Fields clearly correspond to such a container; however, |
| 292 |
in some other cases, identifying the correct container might require |
| 293 |
some approximation. For example, in some countries the RD (road) |
| 294 |
Element might also be appropriate for other thoroughfares, like |
| 295 |
waterways or tunnels. |
| 296 |
|
| 297 |
Fields that are identified to have the same meaning as one of the |
| 298 |
CAtypes SHOULD be directly mapped to that CAtype Element. |
| 299 |
|
| 300 |
Where CAtype usage diverges from the original specification, the |
| 301 |
mapping definition of Fields that are mapped to that Element SHOULD |
| 302 |
include a discussion of the differences. |
| 303 |
|
| 304 |
Fields that do not fit into an existing CAtype: |
| 305 |
|
| 306 |
Even though the list of CAtypes could be extended, it is not |
| 307 |
feasible to add new Elements for every new Field in every data |
| 308 |
source in every country. Therefore, unless new generic CAtypes |
| 309 |
are specified by the IETF, only existing Elements can be used, |
| 310 |
which leaves the following options: |
| 311 |
|
| 312 |
1. Concatenate several civic address Fields into a single PIDF-LO |
| 313 |
Element (define delimiters if applicable and make sure the |
| 314 |
separate civic address parts can be retrieved again). |
| 315 |
|
| 316 |
2. Use a PIDF-LO Element that is unused so far. |
| 317 |
|
| 318 |
Note: Obviously, the first option is required if the number of |
| 319 |
Fields that are used in the mapping procedure is greater than the |
| 320 |
number of existing CAtype Elements. |
| 321 |
|
| 322 |
Note that the xml:lang attribute should be present in PIDF-LO XML |
| 323 |
[<a href="#ref-W3C.REC-xml-20060816">W3C.REC-xml-20060816</a>] documents, according to <a href="./rfc5139">RFC 5139</a>. |
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Guidelines for Individual Elements</span> |
| 338 |
|
| 339 |
The following sections discuss individual PIDF-LO Elements and |
| 340 |
describe what to consider for each Element when defining civic |
| 341 |
address considerations. It is RECOMMENDED to follow a similar |
| 342 |
structure for considerations documents. |
| 343 |
|
| 344 |
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Country</span> |
| 345 |
|
| 346 |
The country Element must hold the alpha-2 codes from ISO 3166-1 |
| 347 |
[<a href="#ref-ISO3166-1" title=""Codes for the representation of names of countries and their subdivisions - Part 1: Country codes"">ISO3166-1</a>] in uppercase characters, as clarified in <a href="./rfc5139#section-3.3">Section 3.3 of |
| 348 |
RFC 5139</a> [<a href="./rfc5139" title=""Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)"">RFC5139</a>]. |
| 349 |
|
| 350 |
This Element cannot be redefined on a national basis since it |
| 351 |
identifies the country itself. This Element is used to identify |
| 352 |
which national mapping for civic addresses has been used in a |
| 353 |
specific PIDF-LO. |
| 354 |
|
| 355 |
Example for Austria: <country>AT</country> |
| 356 |
|
| 357 |
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Country Subdivisions A1-A6</span> |
| 358 |
|
| 359 |
The Elements A1 to A6 are used to hold national subdivision |
| 360 |
identifiers, with A1 holding the top-level subdivision identifier. |
| 361 |
A1 may either contain the second part of ISO 3166-2 [<a href="#ref-ISO3166-2" title=""Codes for the representation of names of countries and their subdivisions - Part 2: Country subdivision code"">ISO3166-2</a>] (see |
| 362 |
<a href="./rfc5139#section-3.4">Section 3.4 of RFC 5139</a> [<a href="./rfc5139" title=""Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)"">RFC5139</a>]) or other values as described in |
| 363 |
the particular address considerations document. Elements "A2" to |
| 364 |
"A6" may contain additional levels of subdivisions (see <a href="./rfc4119#section-2.2.1">Section 2.2.1 |
| 365 |
of RFC 4119</a>). |
| 366 |
|
| 367 |
For A1, an address considerations document MUST state whether ISO |
| 368 |
3166-2 codes are to be used exclusively; alternatively, it should |
| 369 |
define a list of values to be used (for example, subdivision names). |
| 370 |
In either case, A1 MUST NOT be redefined for any other use than |
| 371 |
describing top-level subdivisions. |
| 372 |
|
| 373 |
For each of the A2 - A6 Elements that are required or optional, the |
| 374 |
document SHOULD define the set of allowed values, either by listing |
| 375 |
them or by referring to such a list. |
| 376 |
|
| 377 |
Example for Austria: |
| 378 |
|
| 379 |
A1 province (Bundesland) |
| 380 |
A2 political district (politischer Bezirk) name or identifier |
| 381 |
A3 commune (Gemeinde) name or identifier |
| 382 |
A4 village (Ortschaft) name or identifier |
| 383 |
A5 cadastral municipality (Katastralgemeinde) name or identifier |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 391 |
|
| 392 |
|
| 393 |
A6 must not be used. For more details, see the example in <a href="#appendix-A.4.2">Appendix</a> |
| 394 |
<a href="#appendix-A.4.2">A.4.2</a>. |
| 395 |
|
| 396 |
<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>. Road and Street Names</span> |
| 397 |
|
| 398 |
PIDF-LO contains the following Elements related to road names: RD, |
| 399 |
RDSEC, RDBR, RDSUBADDR, PRM, POM (Sections <a href="#section-3.1">3.1</a> and <a href="#section-3.2">3.2</a> of <a href="./rfc5139">RFC 5139</a> |
| 400 |
[<a href="./rfc5139" title=""Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)"">RFC5139</a>]) and PRD, POD, STS (Sections <a href="#section-3.4">3.4</a> of [<a href="./rfc4776" title=""Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information"">RFC4776</a>]). Note: the |
| 401 |
use of the A6 Element for street names is not valid any more (<a href="./rfc5139#section-3.2">Section</a> |
| 402 |
<a href="./rfc5139#section-3.2">3.2 of RFC 5139</a> [<a href="./rfc5139" title=""Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)"">RFC5139</a>]). |
| 403 |
|
| 404 |
Besides the basic specification of which of those Elements are |
| 405 |
required, optional, or not to be used, an address considerations |
| 406 |
document may also describe more complicated dependencies (for |
| 407 |
example, "RD is optional, but required if any other road name Element |
| 408 |
is used"). |
| 409 |
|
| 410 |
For any required or optional Element, the relation of those Elements |
| 411 |
to Fields of the data source used MUST be described, as should |
| 412 |
special considerations (like concatenation of Fields into an |
| 413 |
Element), if they apply. The usage of the Element STS (street |
| 414 |
suffix) SHOULD be consistent. In case no suffixes are known in a |
| 415 |
data source, or it is common to write the street name and the suffix |
| 416 |
together, the STS Element SHOULD be left out completely. If suffixes |
| 417 |
may be abbreviated, the common abbreviations SHOULD be defined. |
| 418 |
|
| 419 |
Example for Austria: |
| 420 |
|
| 421 |
RD: street name |
| 422 |
|
| 423 |
All other road Elements must not be used. Street suffixes are |
| 424 |
already included in the "street name" Field and must not be |
| 425 |
abbreviated. |
| 426 |
|
| 427 |
<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>. House Numbers</span> |
| 428 |
|
| 429 |
PIDF-LO specifies two Elements related to house numbers: HNO ("house |
| 430 |
number", numeric part only) and HNS ("house number suffix") (see |
| 431 |
<a href="./rfc4776#section-3.4">Section 3.4 of RFC 4776</a>). However, in many countries house numbers |
| 432 |
have a more complex format. In any case, a clear definition is |
| 433 |
REQUIRED to minimize the potential for confusion. |
| 434 |
|
| 435 |
An address considerations document should provide the following |
| 436 |
information with regards to house numbers: if the structure of house |
| 437 |
numbers fits the HNO/HNS structure, the document MUST mandate to use |
| 438 |
those Elements as described in <a href="./rfc4776">RFC 4776</a>. If the structure of house |
| 439 |
numbers does not directly fit into those two Elements, the document |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 447 |
|
| 448 |
|
| 449 |
MUST define strategies on how to map source Fields into Elements. |
| 450 |
Besides HNO and HNS, LOC and BLD could be considered for carrying |
| 451 |
house number information. |
| 452 |
|
| 453 |
The document SHOULD describe whether or not abbreviations of house |
| 454 |
number information is valid. If abbreviations are used, they MUST be |
| 455 |
clearly defined. If house numbers consist of more than one number, |
| 456 |
or if multiple prefixes and suffixes may coexist, a delimiter symbol |
| 457 |
and a clear rule on how to concatenate all this data into the HNO and |
| 458 |
HNS Element might be necessary. Whenever concatenating data into one |
| 459 |
Element, keep in mind that the location recipient might want to |
| 460 |
separate the data again. |
| 461 |
|
| 462 |
Example from Austria: |
| 463 |
|
| 464 |
HNO: concatenate all the data Fields of Austrian house numbers into |
| 465 |
this single PIDF-LO Element in a defined order with delimiter |
| 466 |
symbols (see <a href="#appendix-A.4.4">Appendix A.4.4</a> for the complete definition). |
| 467 |
|
| 468 |
HNS: usage not allowed since there may be multiple suffixes for the |
| 469 |
different parts of the house number. |
| 470 |
|
| 471 |
LOC and BLD are not to be used to reflect house number information. |
| 472 |
|
| 473 |
<span class="h4"><a class="selflink" id="section-4.2.5" href="#section-4.2.5">4.2.5</a>. Local Names</span> |
| 474 |
|
| 475 |
PIDF-LO contains three Elements to reflect local names: LMK, LOC, and |
| 476 |
NAM (<a href="./rfc4776#section-3.4">Section 3.4 of RFC 4776</a>). Such local names may be of importance |
| 477 |
for the identification of a location and may either coexist with a |
| 478 |
valid civic address or (in some cases) have no address assigned, in |
| 479 |
which case the local name, itself, identifies the location. In rural |
| 480 |
regions, for example, a farm name may be more common than a street |
| 481 |
address to identify a location. Landmarks typically don't have any |
| 482 |
civic address information assigned. Therefore, local names may |
| 483 |
assist in finding a "street name" type address, but they might also |
| 484 |
be the authoritative (and only) civic location information. |
| 485 |
|
| 486 |
For any required or optional Element out of LMK, LOC, or NAM, the |
| 487 |
considerations document should state potential values (source data) |
| 488 |
for the Element. In the case that multiple values for an Element may |
| 489 |
occur, a concatenation/selection strategy should be described. |
| 490 |
Concatenation using ";" as a separator is recommended, unless this |
| 491 |
character also appears in the source Fields. |
| 492 |
|
| 493 |
If local name information and "common" address information is both |
| 494 |
available and used, the document SHOULD discuss the relationship |
| 495 |
between those two address information types and the expected behavior |
| 496 |
of location recipients. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 503 |
|
| 504 |
|
| 505 |
Example from Austria: |
| 506 |
|
| 507 |
NAM: contains the "Vulgoname" (local name); multiple local names are |
| 508 |
separated by a semicolon (if applicable). |
| 509 |
|
| 510 |
LMK: contains the farm name (just one name possible) (if applicable). |
| 511 |
|
| 512 |
LOC: can be used without restriction for additional location |
| 513 |
information (as per <a href="./rfc4119">RFC 4119</a>). |
| 514 |
|
| 515 |
The "Vulgoname" is useful to identify the location within its |
| 516 |
locality, since official addresses (especially in rural regions) |
| 517 |
might not be well known. |
| 518 |
|
| 519 |
<span class="h4"><a class="selflink" id="section-4.2.6" href="#section-4.2.6">4.2.6</a>. Floors</span> |
| 520 |
|
| 521 |
PIDF-LO defines the Element FLR to hold floor information but does |
| 522 |
not further specify its content. <a href="./rfc3825#section-2.1">Section 2.1 of RFC 3825</a> provides |
| 523 |
guidance about floor numbering but is not directly related to PIDF- |
| 524 |
LO. |
| 525 |
|
| 526 |
An address considerations document SHOULD clearly specify how to |
| 527 |
express floors using the FLR Element. Following the above-mentioned |
| 528 |
guidance is RECOMMENDED; however, local nomenclature might require a |
| 529 |
completely different system. The document SHOULD specify whether |
| 530 |
only numbers, text, or both are allowed in the FLR Element. If there |
| 531 |
are standard values for certain floors, they SHOULD be listed. |
| 532 |
Abbreviations SHOULD be avoided, unless they are the primary (well- |
| 533 |
known) way of identifying floors. |
| 534 |
|
| 535 |
Example from Austria: |
| 536 |
|
| 537 |
If floor numbers are to be mapped, the FLR Element MUST be used. |
| 538 |
Numbers and text are both allowed. The first floor (<FLR>1</FLR>) is |
| 539 |
the first "full" floor above the floor at street level. The floor at |
| 540 |
street level is <FLR>EG</FLR> or <FLR>0</FLR>. There might be |
| 541 |
intermediate floors, especially between the floor at street level and |
| 542 |
the "first floor". Such intermediate floors have names like |
| 543 |
"Mezzanine", "Erster Halbstock" ("first half floor"), or "Zweiter |
| 544 |
Halbstock" ("second half floor"), and have local meanings. |
| 545 |
|
| 546 |
<span class="h4"><a class="selflink" id="section-4.2.7" href="#section-4.2.7">4.2.7</a>. Address Codes</span> |
| 547 |
|
| 548 |
Address codes are available in several countries in different forms |
| 549 |
(for estates, buildings, or usable units for example). These codes |
| 550 |
identify an address record and MAY be placed in the ADDCODE Element |
| 551 |
in PIDF-LO. Address codes can help the location recipient to |
| 552 |
determine the location and to identify the original record in the |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 559 |
|
| 560 |
|
| 561 |
data source. Depending on the type of code, the code alone (without |
| 562 |
any other Elements) may even be sufficient to fully identify an |
| 563 |
address within a country. |
| 564 |
|
| 565 |
In such cases, a PIDF-LO containing just the country and ADDCODE |
| 566 |
Elements might provide enough information to retrieve a civic |
| 567 |
address, given the location recipient has access to the respective |
| 568 |
source database. |
| 569 |
|
| 570 |
A civic address considerations document SHOULD specify whether and in |
| 571 |
which applications the use of the ADDCODE Element is allowed. If |
| 572 |
ADDCODE is used, its relation to the remaining Elements MUST be |
| 573 |
clearly stated. If several namespaces for address codes exist in a |
| 574 |
country, a mechanism to distinguish the different code spaces MUST be |
| 575 |
described. |
| 576 |
|
| 577 |
Examples from Austria: |
| 578 |
|
| 579 |
Statistik Austria provides 4 codes: Adresscode (AdrCD), Adresssubcode |
| 580 |
(AdrsubCD), Objektnummer (ObjNr), and Nutzungseinheitenlaufnummer |
| 581 |
(NtzLnr). |
| 582 |
|
| 583 |
The following format SHOULD be used: |
| 584 |
|
| 585 |
<ADDCODE>AdrCD=1234567;AdrsubCD=123; |
| 586 |
ObjNr=2333211;NtzLnr=0001</ADDCODE> |
| 587 |
|
| 588 |
<span class="h4"><a class="selflink" id="section-4.2.8" href="#section-4.2.8">4.2.8</a>. Other Elements</span> |
| 589 |
|
| 590 |
This section lists all PIDF-LO Elements that have not been discussed |
| 591 |
so far. |
| 592 |
|
| 593 |
To specify the location inside a building, the following Elements can |
| 594 |
be useful: |
| 595 |
|
| 596 |
o UNIT |
| 597 |
o ROOM |
| 598 |
o SEAT |
| 599 |
|
| 600 |
The following Elements are to be used for the representation of |
| 601 |
postal codes: |
| 602 |
|
| 603 |
o PC |
| 604 |
o PCN |
| 605 |
o POBOX |
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 615 |
|
| 616 |
|
| 617 |
To describe the place-type or the building, the following Elements |
| 618 |
are available: |
| 619 |
|
| 620 |
o PLC - Place-type (for allowed values, refer to the IANA registry |
| 621 |
defined in [<a href="./rfc4589" title=""Location Types Registry"">RFC4589</a>]) |
| 622 |
|
| 623 |
o BLD - Building (structure) |
| 624 |
|
| 625 |
For any of those Elements that are required or optional in a mapping, |
| 626 |
the semantics of its contents must be described if it differs from |
| 627 |
the definition in the PIDF-LO base documents. |
| 628 |
|
| 629 |
It is RECOMMENDED that the Elements SEAT, UNIT, and ROOM remain to be |
| 630 |
used for identifying a location inside a building. They MAY be used |
| 631 |
by the owner of the respective building if a considerations document |
| 632 |
does not restrict their use. For example, an airport could decide to |
| 633 |
place the gate number in the UNIT Element and a location recipient |
| 634 |
could identify that PIDF-LO by the value of the PLC Element. The |
| 635 |
name of the airport could be placed in NAM. |
| 636 |
|
| 637 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 638 |
|
| 639 |
<a href="./rfc4119">RFC 4119</a> contains general security considerations for handling PIDF- |
| 640 |
LOs. |
| 641 |
|
| 642 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 643 |
|
| 644 |
IANA has created the registry "PIDF-LO Civic Address Considerations |
| 645 |
Registry", according to the following definitions. Furthermore, this |
| 646 |
document registers a civic address considerations document for |
| 647 |
Austrian addresses, as provided in the Appendix of this document, and |
| 648 |
also registers the considerations of <a href="./rfc4776">RFC 4776</a> as obsolete. |
| 649 |
|
| 650 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. PIDF-LO Civic Address Considerations Registry</span> |
| 651 |
|
| 652 |
<span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. Structure</span> |
| 653 |
|
| 654 |
The IANA registry contains the following fields: |
| 655 |
|
| 656 |
o Country-Code: either the ISO 3166 alpha-two code of the country to |
| 657 |
which the consideration applies or "other" in case the |
| 658 |
considerations document is not specific to a particular country. |
| 659 |
This field is to be defined by the requestor. |
| 660 |
|
| 661 |
o Serial Number: a number that uniquely identifies a considerations |
| 662 |
document within a certain "Country-Code" field value. Serial |
| 663 |
Numbers are sequentially assigned by IANA per Country-Code value, |
| 664 |
start at zero, and are never reused. |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 671 |
|
| 672 |
|
| 673 |
o Reference to specification: this field contains a reference to the |
| 674 |
considerations document. The xref type "rfc" should be used for |
| 675 |
referencing to RFCs, while other documents should use the "uri" |
| 676 |
type. |
| 677 |
|
| 678 |
o Requestor: the author of the document. |
| 679 |
|
| 680 |
o Status: one of either "active" or "obsolete". When the document |
| 681 |
is registered by IANA, the status is first set to "active" by |
| 682 |
IANA. Experts may later request changing the status to |
| 683 |
"obsolete", especially if there is an updated version of the |
| 684 |
considerations document available. Authors of considerations |
| 685 |
documents must contact the experts if they wish to change the |
| 686 |
status of the document. |
| 687 |
|
| 688 |
Note: the combination of Country-Code and Serial Number fields |
| 689 |
uniquely identifies a considerations document in the registry (for |
| 690 |
example, "AT-0", "US-0", "US-1", or "other-0"). |
| 691 |
|
| 692 |
<span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. Registration Template</span> |
| 693 |
|
| 694 |
For registration of address considerations documents in the registry, |
| 695 |
requesters SHOULD use the following template. The template SHOULD be |
| 696 |
contained in the considerations document itself. |
| 697 |
|
| 698 |
<record> |
| 699 |
<country> <!-- Country-Code --> </country> |
| 700 |
<serial> <!-- assigned by IANA --> </serial> |
| 701 |
|
| 702 |
<!-- reference to document --> |
| 703 |
<xref type="uri" data="http://www.example.org/civicaddr/"/> |
| 704 |
|
| 705 |
<!-- record requesters --> |
| 706 |
<xref type="person" data="John_Doe"/> |
| 707 |
<xref type="person" data="Jane_Dale"/> |
| 708 |
|
| 709 |
<status> <!-- assigned by IANA --> </status> |
| 710 |
</record> |
| 711 |
|
| 712 |
<people> |
| 713 |
<person id="John_Doe"> |
| 714 |
<name> <!-- Firstname Lastname --> </name> |
| 715 |
<org> <!-- Organization Name --> </org> |
| 716 |
<uri> <!-- mailto: or http: URI --> </uri> |
| 717 |
<updated> <!-- date format YYYY-MM-DD --> </updated> |
| 718 |
</person> |
| 719 |
<!-- repeat person section for each person --> |
| 720 |
</people> |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h4"><a class="selflink" id="section-6.1.3" href="#section-6.1.3">6.1.3</a>. Registry Location</span> |
| 730 |
|
| 731 |
Approved registrations are published in the IANA registry named |
| 732 |
"PIDF-LO Civic Address Considerations Registry", which is available |
| 733 |
from <a href="http://www.iana.org">http://www.iana.org</a>. |
| 734 |
|
| 735 |
Registrations are sorted by ascending order by the Country-Code and |
| 736 |
by Serial Number within Country-Code values. Registrations with |
| 737 |
Country-Code of "other" are put at the end of the list. |
| 738 |
|
| 739 |
<span class="h4"><a class="selflink" id="section-6.1.4" href="#section-6.1.4">6.1.4</a>. Registration Procedure</span> |
| 740 |
|
| 741 |
Following the policies outlined in [<a href="./rfc5226" title="">RFC5226</a>], new address |
| 742 |
considerations are added to the registry after Expert Review (see |
| 743 |
<a href="./rfc5226#section-4.1">Section 4.1 in RFC 5226</a>). The Expert will generally check if the |
| 744 |
submitted address considerations conform to the civic address |
| 745 |
guidelines in this document (see <a href="#section-4">Section 4</a>). If in doubt, the Expert |
| 746 |
SHOULD consult the GEOPRIV mailing list or its dedicated successor. |
| 747 |
If possible, the Experts SHOULD check the available documentation on |
| 748 |
which the address consideration is based. |
| 749 |
|
| 750 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Registration Request for Austria</span> |
| 751 |
|
| 752 |
This document registers the civic address considerations for |
| 753 |
addresses from the official Austrian Building and Habitation |
| 754 |
registry, according to the registration procedure described above. |
| 755 |
The required information is contained in <a href="#appendix-A">Appendix A</a>. |
| 756 |
|
| 757 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Registration of the Considerations in <a href="./rfc4776">RFC 4776</a> as Obsolete</span> |
| 758 |
|
| 759 |
Since this document updates <a href="./rfc4776">RFC 4776</a>, the considerations on the |
| 760 |
subdivision Elements in <a href="./rfc4776#section-3.4">Section 3.4 of RFC 4776</a> for Canada, Germany, |
| 761 |
Japan, Korea, and the United States are obsolete. The following IANA |
| 762 |
registration records register them in the IANA registry as obsolete. |
| 763 |
|
| 764 |
|
| 765 |
|
| 766 |
|
| 767 |
|
| 768 |
|
| 769 |
|
| 770 |
|
| 771 |
|
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 783 |
|
| 784 |
|
| 785 |
Canada: |
| 786 |
<record> |
| 787 |
<country>CA</country> |
| 788 |
<serial>0</serial> |
| 789 |
<xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/> |
| 790 |
<xref type="person" data="Henning_Schulzrinne"/> |
| 791 |
<status>obsolete</status> |
| 792 |
</record> |
| 793 |
|
| 794 |
<people> |
| 795 |
<person id="Henning_Schulzrinne"> |
| 796 |
<name>Henning Schulzrinne</name> |
| 797 |
<org>Columbia University</org> |
| 798 |
<uri>mailto:[email protected]</uri> |
| 799 |
<updated>2009-01-09</updated> |
| 800 |
</person> |
| 801 |
</people> |
| 802 |
|
| 803 |
Germany: |
| 804 |
<record> |
| 805 |
<country>DE</country> |
| 806 |
<serial>0</serial> |
| 807 |
<xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/> |
| 808 |
<xref type="person" data="Henning_Schulzrinne"/> |
| 809 |
<status>obsolete</status> |
| 810 |
</record> |
| 811 |
|
| 812 |
<people> |
| 813 |
<person id="Henning_Schulzrinne"> |
| 814 |
<name>Henning Schulzrinne</name> |
| 815 |
<org>Columbia University</org> |
| 816 |
<uri>mailto:[email protected]</uri> |
| 817 |
<updated>2009-01-09</updated> |
| 818 |
</person> |
| 819 |
</people> |
| 820 |
|
| 821 |
|
| 822 |
|
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 839 |
|
| 840 |
|
| 841 |
Japan: |
| 842 |
<record> |
| 843 |
<country>JP</country> |
| 844 |
<serial>0</serial> |
| 845 |
<xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/> |
| 846 |
<xref type="person" data="Henning_Schulzrinne"/> |
| 847 |
<status>obsolete</status> |
| 848 |
</record> |
| 849 |
|
| 850 |
<people> |
| 851 |
<person id="Henning_Schulzrinne"> |
| 852 |
<name>Henning Schulzrinne</name> |
| 853 |
<org>Columbia University</org> |
| 854 |
<uri>mailto:[email protected]</uri> |
| 855 |
<updated>2009-01-09</updated> |
| 856 |
</person> |
| 857 |
</people> |
| 858 |
|
| 859 |
Korea: |
| 860 |
<record> |
| 861 |
<country>KR</country> |
| 862 |
<serial>0</serial> |
| 863 |
<xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/> |
| 864 |
<xref type="person" data="Henning_Schulzrinne"/> |
| 865 |
<status>obsolete</status> |
| 866 |
</record> |
| 867 |
|
| 868 |
<people> |
| 869 |
<person id="Henning_Schulzrinne"> |
| 870 |
<name>Henning Schulzrinne</name> |
| 871 |
<org>Columbia University</org> |
| 872 |
<uri>mailto:[email protected]</uri> |
| 873 |
<updated>2009-01-09</updated> |
| 874 |
</person> |
| 875 |
</people> |
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 895 |
|
| 896 |
|
| 897 |
United States: |
| 898 |
<record> |
| 899 |
<country>US</country> |
| 900 |
<serial>0</serial> |
| 901 |
<xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/> |
| 902 |
<xref type="person" data="Henning_Schulzrinne"/> |
| 903 |
<status>obsolete</status> |
| 904 |
</record> |
| 905 |
|
| 906 |
<people> |
| 907 |
<person id="Henning_Schulzrinne"> |
| 908 |
<name>Henning Schulzrinne</name> |
| 909 |
<org>Columbia University</org> |
| 910 |
<uri>mailto:[email protected]</uri> |
| 911 |
<updated>2009-01-09</updated> |
| 912 |
</person> |
| 913 |
</people> |
| 914 |
|
| 915 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span> |
| 916 |
|
| 917 |
The authors would like to thank Martin Thomson and Richard Barnes for |
| 918 |
reviewing the document, and Gregor Jaenin for contributing insights |
| 919 |
into the Austrian civic address data format. |
| 920 |
|
| 921 |
|
| 922 |
|
| 923 |
|
| 924 |
|
| 925 |
|
| 926 |
|
| 927 |
|
| 928 |
|
| 929 |
|
| 930 |
|
| 931 |
|
| 932 |
|
| 933 |
|
| 934 |
|
| 935 |
|
| 936 |
|
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Civic Address Considerations Registration for the Austrian</span> |
| 954 |
Building and Habitation Registry |
| 955 |
|
| 956 |
The Austrian "Gebaeude- und Wohnungsregistergesetz" (building and |
| 957 |
habitation registry law) is the legal basis for the obligation to |
| 958 |
provide a registry of civic addresses, buildings, and their usable |
| 959 |
units (subdivisions of buildings). The registry is operated by |
| 960 |
"Statistik Austria GmbH", a fully governmentally owned company. The |
| 961 |
local administrations of individual townships are responsible for |
| 962 |
keeping records in the registry up to date. |
| 963 |
|
| 964 |
The data format definition for the individual records is publicly |
| 965 |
available (data access itself is, however, restricted). Hence, a |
| 966 |
uniform address database for the whole of Austria is available. A |
| 967 |
detailed description of the Statistik Austria civic address data |
| 968 |
format is contained in <a href="#appendix-A.1">Appendix A.1</a>. |
| 969 |
|
| 970 |
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. Civic Address Format in Austria</span> |
| 971 |
|
| 972 |
Statistik Austria data describes estates, buildings, and usable units |
| 973 |
[<a href="#ref-merkmalskatalog">merkmalskatalog</a>]. On a single estate there may be any number of |
| 974 |
buildings. Apartment houses that have more than one staircase are |
| 975 |
split up in separate buildings at every staircase. In every |
| 976 |
building, there may be several usable units. For example, an |
| 977 |
apartment house may have several apartments, counting as separate |
| 978 |
usable units. Moreover, one building may have more than one address |
| 979 |
but will have at least one address. Below, the address Fields for |
| 980 |
estates (Table 1), buildings (Table 2), and usable units (Table 3) |
| 981 |
are shown. |
| 982 |
|
| 983 |
The ADDCODE, A5, and PCN Elements are optional, and the other |
| 984 |
Elements MUST be used if the data source contains their corresponding |
| 985 |
Fields. The Elements A1 and A2 (not listed in the tables) SHOULD |
| 986 |
also be used if data is available. Exception: when using the address |
| 987 |
codes only (access to the codes is necessary for the creator and |
| 988 |
recipient of the location information), just the ADDCODE and country |
| 989 |
Elements are mandatory; the other Elements can be used optionally, of |
| 990 |
course. |
| 991 |
|
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
+-------------------------+-------------------------------+---------+ |
| 1010 |
| Statistik Austria name | Explanation | PIDF-LO | |
| 1011 |
| | | Element | |
| 1012 |
+-------------------------+-------------------------------+---------+ |
| 1013 |
| Adresscode | address identifier | ADDCODE | |
| 1014 |
| | | | |
| 1015 |
| Gemeindename, | commune name and identifier | A3 | |
| 1016 |
| Gemeindekennziffer | | | |
| 1017 |
| | | | |
| 1018 |
| Ortschaftsname, | village name and identifier | A4 | |
| 1019 |
| Ortschaftskennziffer | | | |
| 1020 |
| | | | |
| 1021 |
| Strassenname, | street name and identifier | RD | |
| 1022 |
| Strassenkennziffer | | | |
| 1023 |
| | | | |
| 1024 |
| Katastralgemeindename, | cadastral municipality and | A5 | |
| 1025 |
| Katastralgemeindenummer | identifier | | |
| 1026 |
| | | | |
| 1027 |
| Hausnummerntext | text in front of the house | HNO | |
| 1028 |
| | number | | |
| 1029 |
| | | | |
| 1030 |
| Hausnummer - 1. Teil - | first part of the house | HNO | |
| 1031 |
| Nummer | number, numeric | | |
| 1032 |
| | | | |
| 1033 |
| Hausnummer - 1. Teil - | first part of the house | HNO | |
| 1034 |
| Buchstabe | number, character | | |
| 1035 |
| | | | |
| 1036 |
| Hausnummer - | links first and Bis part of | HNO | |
| 1037 |
| Verbindungszeichen Teil | house number | | |
| 1038 |
| 1 -> Bis | | | |
| 1039 |
| | | | |
| 1040 |
| Hausnummer - Bis-Nummer | number of Bis part of house | HNO | |
| 1041 |
| | number | | |
| 1042 |
| | | | |
| 1043 |
| Hausnummer - | character of Bis part of | HNO | |
| 1044 |
| Bis-Buchstabe | house number | | |
| 1045 |
| | | | |
| 1046 |
| Hausnummernbereich | indicates if all house | HNO | |
| 1047 |
| | numbers specified or just odd | | |
| 1048 |
| | or even numbers are stated | | |
| 1049 |
| | | | |
| 1050 |
| Postleitzahl | postal code | PC | |
| 1051 |
| | | | |
| 1052 |
| Postleitzahlengebiet | postal community code | PCN | |
| 1053 |
| | | | |
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
| Vulgoname | local name | NAM | |
| 1066 |
| | | | |
| 1067 |
| Hofname | farm name | LMK | |
| 1068 |
+-------------------------+-------------------------------+---------+ |
| 1069 |
|
| 1070 |
Table 1: Civic Address Fields for Estates |
| 1071 |
|
| 1072 |
+------------------------+--------------------------------+---------+ |
| 1073 |
| Statistik Austria name | Explanation | PIDF-LO | |
| 1074 |
| | | Element | |
| 1075 |
+------------------------+--------------------------------+---------+ |
| 1076 |
| Adresssubcode | address subcode | ADDCODE | |
| 1077 |
| | | | |
| 1078 |
| Objektnummer | object code | ADDCODE | |
| 1079 |
| | | | |
| 1080 |
| Hausnummer - | links Bis and second part of | HNO | |
| 1081 |
| Verbindungszeichen | house number | | |
| 1082 |
| Teil Bis -> Teil 2 | | | |
| 1083 |
| | | | |
| 1084 |
| Hausnummer - 2. Teil | second part of the house | HNO | |
| 1085 |
| - Nummer | number, numeric | | |
| 1086 |
| | | | |
| 1087 |
| Hausnummer - 2. Teil | second part of the house | HNO | |
| 1088 |
| - Buchstabe | number, character | | |
| 1089 |
| | | | |
| 1090 |
| Hausnummer - | links second and third part of | HNO | |
| 1091 |
| Verbindungszeichen | house number | | |
| 1092 |
| Teil 2-> Teil 3 | | | |
| 1093 |
| | | | |
| 1094 |
| Hausnummer - 3. Teil | third part of the house | HNO | |
| 1095 |
| - Nummer | number, numeric | | |
| 1096 |
| | | | |
| 1097 |
| Hausnummer - 3. Teil | third part of the house | HNO | |
| 1098 |
| - Buchstabe | number, character | | |
| 1099 |
| | | | |
| 1100 |
| Gebaeudeunterscheidung | for differentiation of | HNO | |
| 1101 |
| | buildings, e.g. Maierweg 27 | | |
| 1102 |
| | Hotel vs. Maierweg 27 | | |
| 1103 |
| | Appartmenthaus | | |
| 1104 |
| | | | |
| 1105 |
+------------------------+--------------------------------+---------+ |
| 1106 |
|
| 1107 |
Table 2: Additional Civic Address Fields for Buildings |
| 1108 |
|
| 1109 |
|
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
+-----------------------------+---------------------------+---------+ |
| 1122 |
| Statistik Austria name | Explanation | PIDF-LO | |
| 1123 |
| | | Element | |
| 1124 |
+-----------------------------+---------------------------+---------+ |
| 1125 |
| Nutzungseinheitenlaufnummer | usable unit code | ADDCODE | |
| 1126 |
| | | | |
| 1127 |
| Tuernummer | door number | HNO | |
| 1128 |
| | | | |
| 1129 |
| Topnummer | unit number | HNO | |
| 1130 |
| | | | |
| 1131 |
| Lagebeschreibung | for verbal description | HNO | |
| 1132 |
| | | | |
| 1133 |
| Lage | describes if the usable | FLR | |
| 1134 |
| | unit is in the basement, | | |
| 1135 |
| | mezzanine, attic floor, | | |
| 1136 |
| | ... (but not the floor | | |
| 1137 |
| | number) | | |
| 1138 |
| | | | |
| 1139 |
| Stockwerk | floor | FLR | |
| 1140 |
| | | | |
| 1141 |
+-----------------------------+---------------------------+---------+ |
| 1142 |
|
| 1143 |
Table 3: Additional Civic Address Fields for Usable Units |
| 1144 |
|
| 1145 |
Note: "floors" in Austria (as in most parts of Europe) are counted |
| 1146 |
differently compared to the US. The "1st floor" in Austria is |
| 1147 |
actually the floor above the floor at street level (2nd floor in US) |
| 1148 |
-- not considering the fact that, in old buildings, there might be |
| 1149 |
even more floors between street level and 1st floor, like "mezzanine" |
| 1150 |
and "2nd mezzanine". So, an Austrian "1st floor" could well be the |
| 1151 |
"4th floor" according to US nomenclature. |
| 1152 |
|
| 1153 |
According to Statistik Austria [<a href="#ref-adrwarten" title=""Handbuch Adress-GWR-Online Teil A Theoretisches Handbuch Kapitel 2 Warten von Adressen im Adress-GWR-Online"">adrwarten</a>], 81.5% of Austrian |
| 1154 |
addresses are of the simple type Musterstrasse 1 (Musterstrasse is an |
| 1155 |
example street name). 5% of all addresses have an additional |
| 1156 |
character, like Musterstrasse 1b. 1% of Austrian addresses look like |
| 1157 |
Musterstrasse 21A - 23A. For 8% of addresses, an additional |
| 1158 |
separator is necessary -- like Musterstrasse 10 Haus 1 Stiege 2, or |
| 1159 |
Musterstrasse 20 Gruppe A Reihe 1 Parzelle 13, or Musterstrasse 30 |
| 1160 |
Weg 1 Parzelle 10. Very seldom, there are so-called special |
| 1161 |
addresses (0.03%) -- for example, Musterstrasse gegenueber 3A, |
| 1162 |
meaning this address is actually opposite of house number 3A. Rather |
| 1163 |
surprisingly, 4.47% of Austrian addresses contain the identifier of |
| 1164 |
the estate since no house number is assigned at all -- for example, |
| 1165 |
Musterstrasse GNR 1234, or Musterstrasse GNR .12/4 Kirche (this type |
| 1166 |
of addresses is common for churches), or a real example in Stockerau: |
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
Kolomaniwoerth GNR 1583. This identifier is stored by Statistik |
| 1178 |
Austria as Hausnummerntext. Otherwise, one could misinterpret this |
| 1179 |
number as a house number, which would be definitely wrong. |
| 1180 |
|
| 1181 |
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Sample Addresses</span> |
| 1182 |
|
| 1183 |
In order to clarify the Austrian civic address format, this section |
| 1184 |
provides some exemplary addresses: |
| 1185 |
|
| 1186 |
1234 Musterstadt, Hauptstrasse 1a - 5a Block 1b Haus 2c Stiege 1 |
| 1187 |
Postleitzahl: 1234 |
| 1188 |
Stadt: Musterstadt |
| 1189 |
Strasse: Hauptstrasse |
| 1190 |
Hausnummer - 1. Teil - Nummer: 1 |
| 1191 |
Hausnummer - 1. Teil - Buchstabe: a |
| 1192 |
Hausnummer - Verbindungszeichen Teil 1 -> Bis: - |
| 1193 |
Hausnummer - 2. Teil - Nummer: 5 |
| 1194 |
Hausnummer - 2. Teil - Buchstabe: a |
| 1195 |
Hausnummer - Verbindungszeichen Teil Bis -> Teil 2: Block |
| 1196 |
Hausnummer - 2. Teil - Nummer: 1 |
| 1197 |
Hausnummer - 2. Teil - Buchstabe: b |
| 1198 |
Hausnummer - Verbindungszeichen Teil 2-> Teil 3: Haus |
| 1199 |
Hausnummer - 3. Teil - Nummer: 2 |
| 1200 |
Hausnummer - 3. Teil - Buchstabe: c |
| 1201 |
Gebaeudeunterscheidung: Stiege 1 |
| 1202 |
|
| 1203 |
1234 Musterstadt, Musterstrasse 13 Hotel |
| 1204 |
Postleitzahl: 1234 |
| 1205 |
Stadt: Musterstadt |
| 1206 |
Strasse: Musterstrasse |
| 1207 |
Hausnummer - 1. Teil - Nummer: 13 |
| 1208 |
Gebaeudeunterscheidung: Hotel |
| 1209 |
|
| 1210 |
6020 Innsbruck, Anichstrasse vor 35 |
| 1211 |
Postleitzahl: 6020 |
| 1212 |
Stadt: Innsbruck |
| 1213 |
Strasse: Anichstrasse |
| 1214 |
Hausnummerntext: vor ("in front of") |
| 1215 |
Hausnummer: 35 |
| 1216 |
|
| 1217 |
6173 Oberperfuss, Riedl 3097 (Pfarrkirche) |
| 1218 |
Postleitzahl: 6173 |
| 1219 |
Stadt: Oberperfuss |
| 1220 |
Strasse: Riedl |
| 1221 |
Hausnummerntext: 3097 |
| 1222 |
(since the estate identifier is 81305 3097, where 81305 is the |
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
Katastralgemeindenummer (cadastral municipality), and no house |
| 1234 |
number is assigned) |
| 1235 |
Vulgoname: Pfarrkirche |
| 1236 |
|
| 1237 |
<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>. Address Codes in Austria</span> |
| 1238 |
|
| 1239 |
Statistik Austria registers 4 codes: Adresscode, Adresssubcode, |
| 1240 |
Objektnummer, and the Nutzungseinheitenlaufnummer. The Adresscode (7 |
| 1241 |
digits) is a unique code for an address in Austria. The |
| 1242 |
Adressregister maps the Adresscode to the civic address. If there is |
| 1243 |
a building located at an address, there is also an Adresssubcode (3 |
| 1244 |
digits) assigned. Every building at an address has its own |
| 1245 |
Adresssubcode (assigned sequentially starting with 001, 002, 003, and |
| 1246 |
so on) in order to distinguish between buildings at the same address. |
| 1247 |
Furthermore, every building located in Austria has its own unique |
| 1248 |
code, the Objektnummer (7 digits). This code identifies the building |
| 1249 |
independent of the Adresscode. That's because addresses are subject |
| 1250 |
to change while the building may persist. To differentiate multiple |
| 1251 |
usable units inside a building, the Nutzungseinheitenlaufnummer (4 |
| 1252 |
digits) is used. This code is also assigned in sequential order for |
| 1253 |
each building. |
| 1254 |
|
| 1255 |
Besides, every address and building is geocoded by Statistik Austria. |
| 1256 |
Hence, if every PIDF-LO would carry data in the format of Statistik |
| 1257 |
Austria and if every PSAP would use the database of Statistik Austria |
| 1258 |
for mapping, a time-saving, definite mapping without irregularities |
| 1259 |
could be achieved. |
| 1260 |
|
| 1261 |
Besides these codes, Statistik Austria maintains reference numbers |
| 1262 |
for communes, localities, or streets, to mention just a few. |
| 1263 |
|
| 1264 |
<span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a>. Austrian Addresses in PIDF-LO</span> |
| 1265 |
|
| 1266 |
The following subsections define the mapping procedure. |
| 1267 |
|
| 1268 |
<span class="h4"><a class="selflink" id="appendix-A.4.1" href="#appendix-A.4.1">A.4.1</a>. Country</span> |
| 1269 |
|
| 1270 |
The country Element for Austria must be set to AT, since this is the |
| 1271 |
ISO 3166-1 [<a href="#ref-ISO3166-1" title=""Codes for the representation of names of countries and their subdivisions - Part 1: Country codes"">ISO3166-1</a>] alpha-2 code for Austria. |
| 1272 |
|
| 1273 |
<country>AT</country> |
| 1274 |
|
| 1275 |
The usage of the ISO 3166 code is demanded by <a href="./rfc4119">RFC 4119</a> [<a href="./rfc4119" title=""A Presence-based GEOPRIV Location Object Format"">RFC4119</a>], and |
| 1276 |
<a href="./rfc5139">RFC 5139</a> [<a href="./rfc5139" title=""Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)"">RFC5139</a>] proposes to use uppercase characters only. |
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
<span class="h4"><a class="selflink" id="appendix-A.4.2" href="#appendix-A.4.2">A.4.2</a>. Country Subdivisions A1-A6</span> |
| 1290 |
|
| 1291 |
A1 province (Bundesland), Section A.4.2.1 |
| 1292 |
A2 political district name or identifier (politischer Bezirk), |
| 1293 |
Section A.4.2.2 |
| 1294 |
A3 commune name or identifier (Gemeinde), Section A.4.2.3 |
| 1295 |
A4 village name or identifier (Ortschaft), Section A.4.2.4 |
| 1296 |
A5 cadastral municipality name or identifier (Katastralgemeindename |
| 1297 |
or Katastralgemeindenummer), Section A.4.2.5 |
| 1298 |
|
| 1299 |
Element A6 must not be used. |
| 1300 |
|
| 1301 |
Last, there is an exception to mention that concerns the Austrian |
| 1302 |
capital, Vienna (Wien). The city of Vienna is equal to its political |
| 1303 |
district and even the province is called Vienna. Nevertheless, |
| 1304 |
Vienna is separated in 23 districts within the same political |
| 1305 |
district. Consequently, an address in Vienna would look like: |
| 1306 |
|
| 1307 |
<country>AT</country> |
| 1308 |
<A1>Wien</A1> |
| 1309 |
<A2>Wien</A2> |
| 1310 |
<A3>Wien</A3> |
| 1311 |
<A4>Favoriten</A4> or <A4>10<A4> |
| 1312 |
<A5>Inzersdorf Stadt<A5> |
| 1313 |
|
| 1314 |
The Element A4, holding the city division, can hold the name or the |
| 1315 |
number of the district. |
| 1316 |
|
| 1317 |
<span class="h5"><a class="selflink" id="appendix-A.4.2.1" href="#appendix-A.4.2.1">A.4.2.1</a>. A1 Element</span> |
| 1318 |
|
| 1319 |
As proposed in <a href="./rfc5139">RFC 5139</a> [<a href="./rfc5139" title=""Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)"">RFC5139</a>], for the PIDF-LO Element A1, the |
| 1320 |
second part of ISO 3166-2 [<a href="#ref-ISO3166-2" title=""Codes for the representation of names of countries and their subdivisions - Part 2: Country subdivision code"">ISO3166-2</a>] can be used. However, in |
| 1321 |
Austria it is also common to write out the names of the states. |
| 1322 |
Table 4 shows the possible values of the A1 Element for Austrian |
| 1323 |
states. |
| 1324 |
|
| 1325 |
|
| 1326 |
|
| 1327 |
|
| 1328 |
|
| 1329 |
|
| 1330 |
|
| 1331 |
|
| 1332 |
|
| 1333 |
|
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
+------------------------+--------------------------------+ |
| 1346 |
| Bundesland | second part of ISO 3166-2 code | |
| 1347 |
+------------------------+--------------------------------+ |
| 1348 |
| Burgenland | 1 | |
| 1349 |
| | | |
| 1350 |
| K=U+00E4rnten | 2 | |
| 1351 |
| | | |
| 1352 |
| Nieder=U+00F6sterreich | 3 | |
| 1353 |
| | | |
| 1354 |
| Ober=U+00F6sterreich | 4 | |
| 1355 |
| | | |
| 1356 |
| Salzburg | 5 | |
| 1357 |
| | | |
| 1358 |
| Steiermark | 6 | |
| 1359 |
| | | |
| 1360 |
| Tirol | 7 | |
| 1361 |
| | | |
| 1362 |
| Vorarlberg | 8 | |
| 1363 |
| | | |
| 1364 |
| Wien | 9 | |
| 1365 |
+------------------------+--------------------------------+ |
| 1366 |
|
| 1367 |
Table 4: A1 Element Format for Austria |
| 1368 |
(Note: values are shown in UTF-8, which is recommended to be used for |
| 1369 |
PIDF-LO.) |
| 1370 |
|
| 1371 |
<span class="h5"><a class="selflink" id="appendix-A.4.2.2" href="#appendix-A.4.2.2">A.4.2.2</a>. A2 Element</span> |
| 1372 |
|
| 1373 |
Names of the Austrian political districts are available at Statistik |
| 1374 |
Austria [<a href="#ref-bezirke" title=""Politische Bezirke, Gebietsstand 2008"">bezirke</a>]. These names, the unique code for the political |
| 1375 |
district, or both can be used for the A2 Element. If the content of |
| 1376 |
the A2 Element is numeric, obviously the code is provided (there is |
| 1377 |
no political district in Austria with a number in its name). In case |
| 1378 |
both the name and the code are provided, they are separated by a |
| 1379 |
semicolon and the name must be listed first. |
| 1380 |
|
| 1381 |
The district of "Bruck an der Leitha" could be represented by: |
| 1382 |
|
| 1383 |
<A2>Bruck an der Leitha<A2> |
| 1384 |
|
| 1385 |
or |
| 1386 |
<A2>307</A2> |
| 1387 |
|
| 1388 |
or |
| 1389 |
<A2>Bruck an der Leitha;307</A2> |
| 1390 |
|
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
<span class="h5"><a class="selflink" id="appendix-A.4.2.3" href="#appendix-A.4.2.3">A.4.2.3</a>. A3 Element</span> |
| 1402 |
|
| 1403 |
The Element A3 holds the Gemeindename (commune name), the identifier |
| 1404 |
of the Gemeinde, or both separated by a semicolon (the name must be |
| 1405 |
listed first). If the content of the A3 Element consists of a number |
| 1406 |
only, it is obvious that just the identifier is provided. Statistik |
| 1407 |
Austria maintains a table with the Gemeindenamen and identifiers |
| 1408 |
[<a href="#ref-gemeinden" title=""Gemeindeliste sortiert nach Gemeindekennziffer, Gebietsstand 2008"">gemeinden</a>], which must be used as the content for the A3 Element; no |
| 1409 |
other spelling is allowed. |
| 1410 |
|
| 1411 |
Sample: |
| 1412 |
|
| 1413 |
<A3>Neusiedl am See</A3> |
| 1414 |
|
| 1415 |
or |
| 1416 |
<A3>10713</A3> |
| 1417 |
|
| 1418 |
or |
| 1419 |
<A3>Neusiedl am See;10713</A3> |
| 1420 |
|
| 1421 |
<span class="h5"><a class="selflink" id="appendix-A.4.2.4" href="#appendix-A.4.2.4">A.4.2.4</a>. A4 Element</span> |
| 1422 |
|
| 1423 |
The Element A4 holds the Ortschaftsname (village name), the |
| 1424 |
Ortschaftskennziffer (the identifier), or both separated by a |
| 1425 |
semicolon (the name must be listed first). If the content of the A4 |
| 1426 |
Element consists of a number only, it is obvious that just the |
| 1427 |
identifier is provided, since there are no Ortschaftsnamen in Austria |
| 1428 |
that contain a number. Statistik Austria maintains a table with the |
| 1429 |
Ortschaftsnamen and identifiers [<a href="#ref-ortschaften" title=""Gemeinden mit Ortschaften und Postleitzahlen, Gebietsstand 2008"">ortschaften</a>], which must be used as |
| 1430 |
the content for the A4 Element; no other spelling is allowed. |
| 1431 |
|
| 1432 |
Sample: |
| 1433 |
|
| 1434 |
<A4>Wilfleinsdorf</A4> |
| 1435 |
|
| 1436 |
or |
| 1437 |
<A4>03448</A4> |
| 1438 |
|
| 1439 |
or |
| 1440 |
<A4>Wilfleinsdorf;03448</A4> |
| 1441 |
|
| 1442 |
<span class="h5"><a class="selflink" id="appendix-A.4.2.5" href="#appendix-A.4.2.5">A.4.2.5</a>. A5 Element</span> |
| 1443 |
|
| 1444 |
The Element A5 holds the Katastralgemeindename (cadastral |
| 1445 |
municipality), the Katastralgemeindenummer (the identifier), or both |
| 1446 |
separated by a semicolon (the name must be listed first). If the |
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
content of the A5 Element consists of a number only, it is obvious |
| 1458 |
that just the identifier is provided, since there are no |
| 1459 |
Katastralgemeindenamen in Austria that contain a number. |
| 1460 |
|
| 1461 |
Sample (Vienna, Fuenfhaus): |
| 1462 |
|
| 1463 |
<A5>Oberbaumgarten</A5> |
| 1464 |
|
| 1465 |
or |
| 1466 |
<A5>1208</A5> |
| 1467 |
|
| 1468 |
or |
| 1469 |
<A5>Oberbaumgarten;1208</A5> |
| 1470 |
|
| 1471 |
<span class="h4"><a class="selflink" id="appendix-A.4.3" href="#appendix-A.4.3">A.4.3</a>. Road and Street Names</span> |
| 1472 |
|
| 1473 |
The PIDF-LO Element RD holds the complete street name, including the |
| 1474 |
street suffix. No abbreviations are allowed. No other Elements are |
| 1475 |
needed for streets and must not be used. |
| 1476 |
|
| 1477 |
<span class="h4"><a class="selflink" id="appendix-A.4.4" href="#appendix-A.4.4">A.4.4</a>. House Numbers</span> |
| 1478 |
|
| 1479 |
Statistik Austria lists 14 data Fields related to the house number of |
| 1480 |
a building plus another 5 Fields for distinction of different usable |
| 1481 |
units inside a building (including the floor, which has a separate |
| 1482 |
Element in PIDF-LO). Unfortunately, PIDF-LO only defines a single |
| 1483 |
house number Element (HNO, numeric part only) and house number suffix |
| 1484 |
Element (HNS). Therefore, this section defines a mapping in order to |
| 1485 |
accommodate all data: all house number data is concatenated into a |
| 1486 |
single HNO Element, even though it is expected to hold numeric part |
| 1487 |
only. |
| 1488 |
|
| 1489 |
In order to allow automatic procession of the HNO Element, it is |
| 1490 |
necessary to use a semicolon as a delimiter symbol (Austrian house |
| 1491 |
numbers do not contain semicolons). The house number parts MUST be |
| 1492 |
provided in the order in which they are listed by the Statistik |
| 1493 |
Austria document [<a href="#ref-merkmalskatalog">merkmalskatalog</a>]. For user-interface |
| 1494 |
representation, the semicolon-separated format can be transformed by |
| 1495 |
replacing semicolons by spaces (multiple spaces should be combined) |
| 1496 |
and no space should be present between a numeric part of a house |
| 1497 |
number and its related character. |
| 1498 |
|
| 1499 |
It is not allowed to use the HNS Element for Austrian addresses, |
| 1500 |
since there are addresses that do not have just a single suffix. |
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
The house number "vor 1 - 1A" (consisting of a house number text |
| 1514 |
"vor", first part of the house number numeric "1", "-" as the link of |
| 1515 |
the first and Bis part, "1" as house number Bis part numeric, "A" as |
| 1516 |
character of the Bis part) would be mapped to: |
| 1517 |
|
| 1518 |
<HNO>vor;1;;-;1;A;;;;;;;;;;;</HNO> |
| 1519 |
|
| 1520 |
<span class="h4"><a class="selflink" id="appendix-A.4.5" href="#appendix-A.4.5">A.4.5</a>. Local Names</span> |
| 1521 |
|
| 1522 |
NAM: contains the Vulgoname (local name); multiple local names are |
| 1523 |
separated by a semicolon (if applicable). |
| 1524 |
|
| 1525 |
LMK: contains the farm name (just one name possible) (if applicable). |
| 1526 |
|
| 1527 |
LOC: can be used without restriction for additional location |
| 1528 |
information (as per <a href="./rfc4119">RFC 4119</a>). |
| 1529 |
|
| 1530 |
<span class="h4"><a class="selflink" id="appendix-A.4.6" href="#appendix-A.4.6">A.4.6</a>. Floors</span> |
| 1531 |
|
| 1532 |
The floor Element may contain numbers or text describing the floor. |
| 1533 |
The first floor (<FLR>1</FLR>) is the floor above the floor at street |
| 1534 |
level. The floor at street level is <FLR>EG</FLR> or <FLR>0</FLR>. |
| 1535 |
Other floors may have names like mezzanine, for example. The |
| 1536 |
Statistik Austria data Fields Lage and Stockwerk are concatenated if |
| 1537 |
necessary. |
| 1538 |
|
| 1539 |
<span class="h4"><a class="selflink" id="appendix-A.4.7" href="#appendix-A.4.7">A.4.7</a>. Additional Code Element</span> |
| 1540 |
|
| 1541 |
The Element additional code may be used to hold the codes provided by |
| 1542 |
Statistik Austria. There is an Adresscode, Adresssubcode, |
| 1543 |
Objektnummer, and a Nutzungseinheitenlaufnummer. These unique codes |
| 1544 |
identify the location. Actually, these codes alone would be enough |
| 1545 |
but require that the location recipient has access to the database of |
| 1546 |
Statistik Austria. |
| 1547 |
|
| 1548 |
If the additional code in a PIDF-LO document is going to hold the |
| 1549 |
codes from Statistik Austria, the following format should be used: |
| 1550 |
|
| 1551 |
<ADDCODE>AdrCD=1234567;AdrsubCD=123; |
| 1552 |
ObjNr=2333211;NtzLnr=0001</ADDCODE> |
| 1553 |
|
| 1554 |
It is not necessary to provide all codes, but there are some |
| 1555 |
restrictions: the Adresssubcode cannot be used without an Adresscode. |
| 1556 |
More restrictions are defined by Statistik Austria. By setting the |
| 1557 |
country Element to AT (see <a href="#section-4.2.1">Section 4.2.1</a>), indicating an Austrian |
| 1558 |
address, the Additional Code Element is expected to hold codes from |
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
Statistik Austria only. When creating PIDF-LO documents using |
| 1570 |
address codes by Statistik Austria, the country and ADDCODE Elements |
| 1571 |
are mandatory. |
| 1572 |
|
| 1573 |
<span class="h4"><a class="selflink" id="appendix-A.4.8" href="#appendix-A.4.8">A.4.8</a>. Other Elements</span> |
| 1574 |
|
| 1575 |
The Elements PC and PCN can hold the data form Statistik Austria, the |
| 1576 |
POBOX can be used if the post assigned a post office box. At least |
| 1577 |
the PC Element should be present. |
| 1578 |
|
| 1579 |
PC: Postleitzahl (postal code) |
| 1580 |
|
| 1581 |
PCN: Postleitzahlengebiet (postal community name) |
| 1582 |
|
| 1583 |
POBOX: Postfach |
| 1584 |
|
| 1585 |
The Elements UNIT, ROOM, SEAT, PLC, and BLD may be used without |
| 1586 |
further restriction. |
| 1587 |
|
| 1588 |
<span class="h4"><a class="selflink" id="appendix-A.4.9" href="#appendix-A.4.9">A.4.9</a>. Elements Not to Be Used</span> |
| 1589 |
|
| 1590 |
A6 |
| 1591 |
STS |
| 1592 |
HNS |
| 1593 |
PRD |
| 1594 |
POD |
| 1595 |
RDBR |
| 1596 |
RDSUBBR |
| 1597 |
PRM |
| 1598 |
POM |
| 1599 |
|
| 1600 |
<span class="h3"><a class="selflink" id="appendix-A.5" href="#appendix-A.5">A.5</a>. Example</span> |
| 1601 |
|
| 1602 |
This section shows an example mapping of an Austrian address to |
| 1603 |
PIDF-LO. |
| 1604 |
|
| 1605 |
Address: |
| 1606 |
|
| 1607 |
Bundesland: Wien |
| 1608 |
Politischer Bezirk: Wien |
| 1609 |
Gemeindename: Wien |
| 1610 |
9. Bezirk |
| 1611 |
Strasse: Lazarettgasse |
| 1612 |
Hausnummer - 1. Teil - Nummer: 13 |
| 1613 |
Hausnummer - 1. Teil - Buchstabe: A |
| 1614 |
Hausnummer - Verbindungszeichen Teil 1-Bis: - |
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
Hausnummer - Bis-Nummer: 13 |
| 1626 |
Hausnummer - Bis-Buchstabe: C |
| 1627 |
Postleitzahl: 1090 |
| 1628 |
|
| 1629 |
PIDF-LO: |
| 1630 |
|
| 1631 |
<?xml version="1.0" encoding="UTF-8" ?> |
| 1632 |
<presence xmlns="urn:ietf:params:xml:ns:pidf" |
| 1633 |
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" |
| 1634 |
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" |
| 1635 |
entity="pres:123@examplehost"> |
| 1636 |
<tuple id="abcd123456"> |
| 1637 |
<status> |
| 1638 |
<gp:geopriv> |
| 1639 |
<gp:location-info> |
| 1640 |
<cl:civicAddress xml:lang="de"> |
| 1641 |
<cl:country>AT</cl:country> |
| 1642 |
<cl:A1>Wien</cl:A1> |
| 1643 |
<cl:A2>Wien</cl:A2> |
| 1644 |
<cl:A3>Wien</cl:A3> |
| 1645 |
<cl:A4>9</cl:A4> |
| 1646 |
<cl:RD>Lazarettgasse</cl:RD> |
| 1647 |
<cl:HNO>;13;A;-;13;C;;;;;;;;;;;;</cl:HNO> |
| 1648 |
<cl:PC>1090</cl:PC> |
| 1649 |
</cl:civicAddress> |
| 1650 |
</gp:location-info> |
| 1651 |
<gp:usage-rules> |
| 1652 |
<gp:retransmission-allowed>yes</gp:retransmission-allowed> |
| 1653 |
<gp:retention-expiry>2009-11-10T12:00:00Z</gp:retention-expiry> |
| 1654 |
</gp:usage-rules> |
| 1655 |
</gp:geopriv> |
| 1656 |
</status> |
| 1657 |
<timestamp>2009-02-09T12:00:00Z</timestamp> |
| 1658 |
</tuple> |
| 1659 |
</presence> |
| 1660 |
|
| 1661 |
<span class="h3"><a class="selflink" id="appendix-A.6" href="#appendix-A.6">A.6</a>. IANA Registration Record</span> |
| 1662 |
|
| 1663 |
<record> |
| 1664 |
<country>AT</country> |
| 1665 |
<serial>0</serial> |
| 1666 |
|
| 1667 |
<!-- reference to document --> |
| 1668 |
<xref type="rfc" data="<a href="./rfc5774">rfc5774</a>"/> |
| 1669 |
|
| 1670 |
<!-- record requesters --> |
| 1671 |
<xref type="person" data="Alexander_Mayrhofer"/> |
| 1672 |
<xref type="person" data="Karl_Heinz_Wolf"/> |
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
<status>active</status> |
| 1682 |
</record> |
| 1683 |
|
| 1684 |
<people> |
| 1685 |
<person id="Alexander_Mayrhofer"> |
| 1686 |
<name>Alexander Mayrhofer</name> |
| 1687 |
<org>nic.at GmbH</org> |
| 1688 |
<uri>mailto:[email protected]</uri> |
| 1689 |
<updated>2009-01-09</updated> |
| 1690 |
</person> |
| 1691 |
<person id="Karl_Heinz_Wolf"> |
| 1692 |
<name>Karl Heinz Wolf</name> |
| 1693 |
<org>nic.at GmbH</org> |
| 1694 |
<uri>mailto:[email protected]</uri> |
| 1695 |
<updated>2009-01-09</updated> |
| 1696 |
</person> |
| 1697 |
</people> |
| 1698 |
|
| 1699 |
Normative References |
| 1700 |
|
| 1701 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1702 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1703 |
|
| 1704 |
[<a id="ref-RFC4119">RFC4119</a>] Peterson, J., "A Presence-based GEOPRIV Location Object |
| 1705 |
Format", <a href="./rfc4119">RFC 4119</a>, December 2005. |
| 1706 |
|
| 1707 |
[<a id="ref-RFC4589">RFC4589</a>] Schulzrinne, H. and H. Tschofenig, "Location Types |
| 1708 |
Registry", <a href="./rfc4589">RFC 4589</a>, July 2006. |
| 1709 |
|
| 1710 |
[<a id="ref-RFC4776">RFC4776</a>] Schulzrinne, H., "Dynamic Host Configuration Protocol |
| 1711 |
(DHCPv4 and DHCPv6) Option for Civic Addresses |
| 1712 |
Configuration Information", <a href="./rfc4776">RFC 4776</a>, November 2006. |
| 1713 |
|
| 1714 |
[<a id="ref-RFC5139">RFC5139</a>] Thomson, M. and J. Winterbottom, "Revised Civic |
| 1715 |
Location Format for Presence Information Data Format |
| 1716 |
Location Object (PIDF-LO)", <a href="./rfc5139">RFC 5139</a>, February 2008. |
| 1717 |
|
| 1718 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing |
| 1719 |
an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC</a> |
| 1720 |
<a href="./rfc5226">5226</a>, May 2008. |
| 1721 |
|
| 1722 |
[<a id="ref-W3C.REC-xml-20060816">W3C.REC-xml-20060816</a>] |
| 1723 |
W3C, "Extensible Markup Language (XML) 1.0 (Fourth |
| 1724 |
Edition)", Recommendation REC-xml-20060816, August |
| 1725 |
2006, <<a href="http://www.w3.org/TR/2006/REC-xml-20060816">http://www.w3.org/TR/2006/REC-xml-20060816</a>>. |
| 1726 |
|
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
Informative References |
| 1738 |
|
| 1739 |
[<a id="ref-adrwarten">adrwarten</a>] Statistik Austria, "Handbuch Adress-GWR-Online Teil A |
| 1740 |
Theoretisches Handbuch Kapitel 2 Warten von Adressen im |
| 1741 |
Adress-GWR-Online", Jan 2005. |
| 1742 |
|
| 1743 |
[<a id="ref-merkmalskatalog">merkmalskatalog</a>] |
| 1744 |
Statistik Austria, "Handbuch Adress-GWR-Online Teil C |
| 1745 |
Anhang 2 Merkmalskatalog", Sept 2004. |
| 1746 |
|
| 1747 |
[<a id="ref-ISO3166-1">ISO3166-1</a>] International Organization for Standardization, "Codes |
| 1748 |
for the representation of names of countries and their |
| 1749 |
subdivisions - Part 1: Country codes", ISO Standard |
| 1750 |
3166-1:1997, 1997. |
| 1751 |
|
| 1752 |
[<a id="ref-ISO3166-2">ISO3166-2</a>] International Organization for Standardization, "Codes |
| 1753 |
for the representation of names of countries and their |
| 1754 |
subdivisions - Part 2: Country subdivision code", ISO |
| 1755 |
Standard 3166-2:1998, 1998. |
| 1756 |
|
| 1757 |
[<a id="ref-bezirke">bezirke</a>] Statistik Austria, "Politische Bezirke, Gebietsstand |
| 1758 |
2008", Feb 2008. |
| 1759 |
|
| 1760 |
[<a id="ref-gemeinden">gemeinden</a>] Statistik Austria, "Gemeindeliste sortiert nach |
| 1761 |
Gemeindekennziffer, Gebietsstand 2008", Feb 2008. |
| 1762 |
|
| 1763 |
[<a id="ref-ortschaften">ortschaften</a>] Statistik Austria, "Gemeinden mit Ortschaften und |
| 1764 |
Postleitzahlen, Gebietsstand 2008", Feb 2008. |
| 1765 |
|
| 1766 |
|
| 1767 |
|
| 1768 |
|
| 1769 |
|
| 1770 |
|
| 1771 |
|
| 1772 |
|
| 1773 |
|
| 1774 |
|
| 1775 |
|
| 1776 |
|
| 1777 |
|
| 1778 |
|
| 1779 |
|
| 1780 |
|
| 1781 |
|
| 1782 |
|
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Wolf & Mayrhofer Best Current Practice [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc5774">RFC 5774</a> Civic Address Considerations March 2010</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
Authors' Addresses |
| 1794 |
|
| 1795 |
Karl Heinz Wolf |
| 1796 |
nic.at GmbH |
| 1797 |
Karlsplatz 1/2/9 |
| 1798 |
Wien A-1010 |
| 1799 |
Austria |
| 1800 |
|
| 1801 |
Phone: +43 1 5056416 37 |
| 1802 |
EMail: [email protected] |
| 1803 |
URI: <a href="http://www.nic.at/">http://www.nic.at/</a> |
| 1804 |
|
| 1805 |
|
| 1806 |
Alexander Mayrhofer |
| 1807 |
nic.at GmbH |
| 1808 |
Karlsplatz 1/2/9 |
| 1809 |
Wien A-1010 |
| 1810 |
Austria |
| 1811 |
|
| 1812 |
Phone: +43 1 5056416 34 |
| 1813 |
EMail: [email protected] |
| 1814 |
URI: <a href="http://www.nic.at/">http://www.nic.at/</a> |
| 1815 |
|
| 1816 |
|
| 1817 |
|
| 1818 |
|
| 1819 |
|
| 1820 |
|
| 1821 |
|
| 1822 |
|
| 1823 |
|
| 1824 |
|
| 1825 |
|
| 1826 |
|
| 1827 |
|
| 1828 |
|
| 1829 |
|
| 1830 |
|
| 1831 |
|
| 1832 |
|
| 1833 |
|
| 1834 |
|
| 1835 |
|
| 1836 |
|
| 1837 |
|
| 1838 |
|
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
Wolf & Mayrhofer Best Current Practice [Page 33] |
| 1845 |
</pre> |