draft-ietf-geopriv-revised-civic-lo-06.txt   draft-ietf-geopriv-revised-civic-lo-07.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 October 17, 2007 Intended status: Standards Track December 7, 2007
Expires: April 19, 2008 Expires: June 9, 2008
Revised Civic Location Format for PIDF-LO Revised Civic Location Format for PIDF-LO
draft-ietf-geopriv-revised-civic-lo-06.txt draft-ietf-geopriv-revised-civic-lo-07.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 April 19, 2008. This Internet-Draft will expire on June 9, 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 and replaces the civic location format in RFC (PIDF-LO) documents and replaces the civic location format in RFC
skipping to change at page 6, line 31 skipping to change at page 6, line 31
uniquely identify the road. Road branches MAY also be used where a uniquely identify the road. Road branches MAY also be used where a
major thoroughfare is split into sections. major thoroughfare is split into sections.
Similar to the way that a road branch is associated with a road, a Similar to the way that a road branch is associated with a road, a
road sub-branch is associated with a road branch. The "RDSUBBR" road sub-branch is associated with a road branch. The "RDSUBBR"
element is used to identify road sub-branches. element is used to identify road sub-branches.
The "A6" element is retained for use in those countries that require The "A6" element is retained for use in those countries that require
this level of detail. Where "A6" was previously used for street this level of detail. Where "A6" was previously used for street
names in [RFC4119], it MUST NOT be used, the "RD" element MUST be names in [RFC4119], it MUST NOT be used, the "RD" element MUST be
used for thoroughfare data. However, without additional information used for thoroughfare data.
these fields MUST not be interchanged when converting between
different civic formats. Where civic address information is obtained
from another format, such as the DHCP form [RFC4776], the "A6"
element MUST be copied directly from the source format.
The following example figure shows a fictional arrangement of roads The following example figure shows a fictional arrangement of roads
where these new thoroughfare elements are applicable. where these new thoroughfare elements are applicable.
| || | ||
| ---------------|| | ---------------||
| Carol La. Carol La. || Bob | Carol La. Carol La. || Bob
| || St. | || St.
| West Alice Pde. || | West Alice Pde. ||
==========/=================/===============/==========||=========== ==========/=================/===============/==========||===========
skipping to change at page 8, line 15 skipping to change at page 8, line 15
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 language-neutral values. The range of allowed which both contain language-neutral values. The range of allowed
values for "country" are defined in [ISO.3166-1]; the range of values for "country" are defined in [ISO.3166-1]; the range of
allowed values for "PLC" are defined in the IANA registry defined by allowed values for "PLC" are defined in the IANA registry defined by
[RFC4589]. [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 with a script subtag [RFC4646].
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.
3.5.1. Converting from the DHCP Format 3.5.1. Converting from the DHCP Format
skipping to change at page 16, line 24 skipping to change at page 16, line 24
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 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005. Format", RFC 4119, December 2005.
[RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types
Registry", RFC 4589, July 2006. Registry", RFC 4589, July 2006.
[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 4646, September 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.
 End of changes. 6 change blocks. 
10 lines changed or deleted 9 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/