draft-ietf-geopriv-revised-civic-lo-05.txt   draft-ietf-geopriv-revised-civic-lo-06.txt 
GEOPRIV WG M. Thomson GEOPRIV WG M. Thomson
Internet-Draft J. Winterbottom Internet-Draft J. Winterbottom
Updates: 4119 (if approved) Andrew Updates: 4119 (if approved) Andrew
Intended status: Standards Track February 15, 2007 Intended status: Standards Track October 17, 2007
Expires: August 19, 2007 Expires: April 19, 2008
Revised Civic Location Format for PIDF-LO Revised Civic Location Format for PIDF-LO
draft-ietf-geopriv-revised-civic-lo-05.txt draft-ietf-geopriv-revised-civic-lo-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 19, 2007. This Internet-Draft will expire on April 19, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines an XML format for the representation of civic This document defines an XML format for the representation of civic
location. This format is designed for use with PIDF Location Object location. This format is designed for use with PIDF Location Object
(PIDF-LO) documents. The format is based on the civic address (PIDF-LO) documents and replaces the civic location format in RFC
definition in PIDF-LO, but adds several new elements based on the 4119. The format is based on the civic address definition in
civic types defined for DHCP, and adds a hierarchy to address complex PIDF-LO, but adds several new elements based on the civic types
road identity schemes. The format also includes support for the defined for DHCP, and adds a hierarchy to address complex road
xml:lang language tag and restricts the types of elements where identity schemes. The format also includes support for the xml:lang
appropriate. language tag and restricts the types of elements where appropriate.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Changes from PIDF-LO . . . . . . . . . . . . . . . . . . . . . 5 3. Changes from PIDF-LO . . . . . . . . . . . . . . . . . . . . . 5
3.1. Additional Civic Address Types . . . . . . . . . . . . . . 5 3.1. Additional Civic Address Types . . . . . . . . . . . . . . 5
3.2. New Thoroughfare Elements . . . . . . . . . . . . . . . . 6 3.2. New Thoroughfare Elements . . . . . . . . . . . . . . . . 6
3.2.1. Street Numbering . . . . . . . . . . . . . . . . . . . 7 3.2.1. Street Numbering . . . . . . . . . . . . . . . . . . . 7
3.2.2. Directionals and other Qualifiers . . . . . . . . . . 7 3.2.2. Directionals and other Qualifiers . . . . . . . . . . 7
skipping to change at page 5, line 18 skipping to change at page 5, line 18
[RFC4776] provides a full set of parameters that may be used to [RFC4776] provides a full set of parameters that may be used to
describe a civic location. Specifically [RFC4776] lists several describe a civic location. Specifically [RFC4776] lists several
civic address types (CAtypes) that require support in the formal civic address types (CAtypes) that require support in the formal
PIDF-LO definition that are not in [RFC4119]. PIDF-LO definition that are not in [RFC4119].
These changes include and new elements that are required to support These changes include and new elements that are required to support
more complex structures for naming street addresses, this is more complex structures for naming street addresses, this is
described in more detail in Section 3.2. described in more detail in Section 3.2.
+---------------+--------+----------------------------+-------------+ +-----------+--------+-------------------------------+--------------+
| New Civic | CAtype | Description | Example | | New Field | CAtype | Description | Example |
| Field | | | | +-----------+--------+-------------------------------+--------------+
+---------------+--------+----------------------------+-------------+ | BLD | 25 | Building (structure) | Hope Theatre |
| BLD | 25 | Building (structure) | Hope |
| | | | Theatre |
| | | | | | | | | |
| UNIT | 26 | Unit (apartment, suite) | 12a | | UNIT | 26 | Unit (apartment, suite) | 12a |
| | | | | | | | | |
| ROOM | 28 | Room | 450F | | ROOM | 28 | Room | 450F |
| | | | | | | | | |
| PLC | 29 | Place-type | office | | PLC | 29 | Place-type | office |
| | | | | | | | | |
| PCN | 30 | Postal community name | Leonia | | PCN | 30 | Postal community name | Leonia |
| | | | | | | | | |
| POBOX | 31 | Post office box (P.O. box) | U40 | | POBOX | 31 | Post office box (P.O. box) | U40 |
skipping to change at page 5, line 51 skipping to change at page 5, line 49
| | | | | | | | | |
| RDSEC | 35 | Road section | 14 | | RDSEC | 35 | Road section | 14 |
| | | | | | | | | |
| RDBR | 36 | Road branch | Lane 7 | | RDBR | 36 | Road branch | Lane 7 |
| | | | | | | | | |
| RDSUBBR | 37 | Road sub-branch | Alley 8 | | RDSUBBR | 37 | Road sub-branch | Alley 8 |
| | | | | | | | | |
| PRM | 38 | Road pre-modifier | Old | | PRM | 38 | Road pre-modifier | Old |
| | | | | | | | | |
| POM | 39 | Road post-modifier | Extended | | POM | 39 | Road post-modifier | Extended |
+---------------+--------+----------------------------+-------------+ +-----------+--------+-------------------------------+--------------+
Table 1: New Civic PIDF-LO Types
Table 1: New Civic PIDF-LO Types
A complete description of these types is included in [RFC4776]. A complete description of these types is included in [RFC4776].
3.2. New Thoroughfare Elements 3.2. New Thoroughfare Elements
In some countries a thoroughfare can be broken up into sections, and In some countries a thoroughfare can be broken up into sections, and
it is not uncommon for street numbers to be repeated between it is not uncommon for street numbers to be repeated between
sections. A road section identifier is required to ensure that an sections. A road section identifier is required to ensure that an
address is unique. For example, "West Alice Parade" has 5 sections, address is unique. For example, "West Alice Parade" has 5 sections,
each numbered from 1; unless the section is specified "7 West Alice each numbered from 1; unless the section is specified "7 West Alice
Parade" could exist in 5 different places. The "RDSEC" element is Parade" could exist in 5 different places. The "RDSEC" element is
skipping to change at page 8, line 4 skipping to change at page 7, line 49
LU-L; Australia uses both two and three character codes: AU-ACT, AU- LU-L; Australia uses both two and three character codes: AU-ACT, AU-
NSW, AU-NT; France uses numerical codes for mainland France and NSW, AU-NT; France uses numerical codes for mainland France and
letters for territories: FR-75, FR-NC. This results in the following letters for territories: FR-75, FR-NC. This results in the following
fragments: fragments:
<country>CA</country><A1>ON</A1> <country>CA</country><A1>ON</A1>
<country>LU</country><A1>L</A1> <country>LU</country><A1>L</A1>
<country>AU</country><A1>ACT</A1> <country>AU</country><A1>ACT</A1>
<country>FR</country><A1>75</A1> <country>FR</country><A1>75</A1>
3.5. Languages and Scripts 3.5. Languages and Scripts
The XML schema defined for civic addresses allows for the addition of The XML schema defined for civic addresses allows for the addition of
the "xml:lang" attribute to all elements except "country" and "PLC", the "xml:lang" attribute to all elements except "country" and "PLC",
which both contain enumerated values. which both contain language-neutral values. The range of allowed
values for "country" are defined in [ISO.3166-1]; the range of
allowed values for "PLC" are defined in the IANA registry defined by
[RFC4589].
The "script" field defined in [RFC4776] is omitted in favour of using The "script" field defined in [RFC4776] is omitted in favour of using
the "xml:lang" attribute. the "xml:lang" attribute.
It is RECOMMENDED that each "civicAddress" element use one language It is RECOMMENDED that each "civicAddress" element use one language
only, or a combination of languages that is consistent. Where a only, or a combination of languages that is consistent. Where a
civic location is represented in multiple languages multiple civic location is represented in multiple languages multiple
"civicAddress" elements SHOULD be included in the PIDF-LO document. "civicAddress" elements SHOULD be included in the PIDF-LO document.
For civic addresses that form a complex to describe the same For civic addresses that form a complex to describe the same
location, these SHOULD be inserted into the same tuple. location, these SHOULD be inserted into the same tuple.
skipping to change at page 11, line 20 skipping to change at page 11, line 20
<xs:element name="UNIT" type="ca:caType" minOccurs="0"/> <xs:element name="UNIT" type="ca:caType" minOccurs="0"/>
<xs:element name="ROOM" type="ca:caType" minOccurs="0"/> <xs:element name="ROOM" type="ca:caType" minOccurs="0"/>
<xs:element name="SEAT" type="ca:caType" minOccurs="0"/> <xs:element name="SEAT" type="ca:caType" minOccurs="0"/>
<xs:element name="PLC" type="xs:token" minOccurs="0"/> <xs:element name="PLC" type="xs:token" minOccurs="0"/>
<xs:element name="PCN" type="ca:caType" minOccurs="0"/> <xs:element name="PCN" type="ca:caType" minOccurs="0"/>
<xs:element name="POBOX" type="ca:caType" minOccurs="0"/> <xs:element name="POBOX" type="ca:caType" minOccurs="0"/>
<xs:element name="ADDCODE" type="ca:caType" minOccurs="0"/> <xs:element name="ADDCODE" type="ca:caType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute ref="xml:lang" use="optional"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
5. Example 5. Example
<?xml version="1.0"?>
<civicAddress xml:lang="en-AU" <civicAddress xml:lang="en-AU"
xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
<country>AU</country> <country>AU</country>
<A1>NSW</A1> <A1>NSW</A1>
<A3> Wollongong <A3> Wollongong
</A3><A4>North Wollongong </A3><A4>North Wollongong
</A4> </A4>
<RD>Flinders</RD><STS>Street</STS> <RD>Flinders</RD><STS>Street</STS>
<RDBR>Campbell Street</RDBR> <RDBR>Campbell Street</RDBR>
<LMK> <LMK>
skipping to change at page 16, line 13 skipping to change at page 16, line 13
to include the types shown in the first column of Table 1. to include the types shown in the first column of Table 1.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[W3C.REC-xmlschema-2-20041028] [W3C.REC-xmlschema-2-20041028]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes
Second Edition", World Wide Web Consortium Second Edition", World Wide Web Consortium
Recommendation REC-xmlschema-2-20041028, October 2004, Recommendation REC-xmlschema-2-20041028, October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005.
[RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types
Registry", RFC 4589, July 2006.
[RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol
(DHCPv4 and DHCPv6) Option for Civic Addresses (DHCPv4 and DHCPv6) Option for Civic Addresses
Configuration Information", RFC 4776, November 2006. Configuration Information", RFC 4776, November 2006.
[ISO.3166-1] [ISO.3166-1]
International Organization for Standardization, "Codes for International Organization for Standardization, "Codes for
the representation of names of countries and their the representation of names of countries and their
subdivisions - Part 1: Country codes", ISO Standard 3166- subdivisions - Part 1: Country codes", ISO Standard 3166-
1:1997, 1997, 1:1997, 1997.
<http://www.iso.org/iso/en/prods-services/iso3166ma/>.
[ISO.3166-2] [ISO.3166-2]
International Organization for Standardization, "Codes for International Organization for Standardization, "Codes for
the representation of names of countries and their the representation of names of countries and their
subdivisions - Part 2: Country subdivision code", subdivisions - Part 2: Country subdivision code",
ISO Standard 3166-2:1998, 1998, ISO Standard 3166-2:1998, 1998.
<http://www.iso.org/iso/en/prods-services/iso3166ma/>.
8.2. Informative References 8.2. Informative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005.
[UPU-S42] Universal Postal Union (UPU), "International Postal [UPU-S42] Universal Postal Union (UPU), "International Postal
Address Components and Templates", UPS SB42-4, July 2004. Address Components and Templates", UPS SB42-4, July 2004.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors would like to thank Henning Schulzrinne for his The authors would like to thank Henning Schulzrinne for his
assistance in defining the additional civic address types, assistance in defining the additional civic address types,
particularly his research into different addressing schemes that lead particularly his research into different addressing schemes that lead
to the introduction of the thoroughfare elements. Rohan Mahy to the introduction of the thoroughfare elements. Rohan Mahy
suggested the ISO 3166-2 recommendation for A1. In addition we would suggested the ISO 3166-2 recommendation for A1. In addition we would
 End of changes. 16 change blocks. 
29 lines changed or deleted 31 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/