Network Working Group H. Schulzrinne
Request for Comments: 4589 Columbia U.
Category: Standards Track H. Tschofenig
Siemens
July 2006
Network Working Group H. Schulzrinne
Request for Comments: 4589 Columbia U.
Category: Standards Track H. Tschofenig
Siemens
July 2006
Location Types Registry
位置类型注册表
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This document creates a registry for describing the types of places a human or end system might be found. The registry is then referenced by other protocols that need a common set of location terms as protocol constants. Examples of location terms defined in this document include aircraft, office, and train station.
本文档创建了一个注册表，用于描述可能找到人工或终端系统的位置类型。然后，需要一组公共位置术语作为协议常量的其他协议引用注册表。本文件中定义的位置术语示例包括飞机、办公室和火车站。
Table of Contents
目录
1. Introduction ....................................................2
2. Terminology .....................................................3
3. Location Types ..................................................3
4. Schema ..........................................................6
5. IANA Considerations .............................................7
5.1. Registering Tokens .........................................7
5.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:location-type .......................8
5.3. Schema Registration for Schema
urn:ietf:params:xml:ns:location-type .......................9
6. Internationalization Considerations .............................9
7. Security Considerations .........................................9
8. Acknowledgements ................................................9
9. References .....................................................10
9.1. Normative References ......................................10
9.2. Informative References ....................................10
1. Introduction ....................................................2
2. Terminology .....................................................3
3. Location Types ..................................................3
4. Schema ..........................................................6
5. IANA Considerations .............................................7
5.1. Registering Tokens .........................................7
5.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:location-type .......................8
5.3. Schema Registration for Schema
urn:ietf:params:xml:ns:location-type .......................9
6. Internationalization Considerations .............................9
7. Security Considerations .........................................9
8. Acknowledgements ................................................9
9. References .....................................................10
9.1. Normative References ......................................10
9.2. Informative References ....................................10
This document creates a registry for location type tokens. We anticipate that the network, through configuration or management protocols, tells a mobile device what kind of location it finds itself in. The device and associated software can then tailor its behavior to the environment. For example, this document defines the terms "classroom", "place-of-worship", and "theater". A considerate owner of a cell phone might program the device to switch from ringer to vibrate mode in such environments. Just knowing the geographic location, be it as civic (street address) or geospatial coordinates, would generally not allow the device to make a similar decision.
本文档为位置类型标记创建一个注册表。我们期望网络通过配置或管理协议告诉移动设备它所处的位置。然后，设备和相关软件可以根据环境调整其行为。例如，本文件定义了“教室”、“礼拜场所”和“剧院”等术语。在这样的环境下，一位体贴的手机用户可能会对手机进行编程，使其从振铃模式切换到振动模式。仅仅知道地理位置，不管是城市（街道地址）还是地理空间坐标，通常都不允许设备做出类似的决定。
Naturally, the number of descriptive terms for physical environments is almost unbounded. This registry tries to identify common terms that are likely to be useful for communications devices and for controlling and guiding communications behavior. The terms roughly correspond to the level of details of location descriptions and icons found on geographic maps, for example, and are meant to be in common use across a variety of cultures and countries. The registration process described in the IANA Considerations section allows this list to be extended as needed, while aiming to prevent an unnecessary explosion in the registry.
自然，物理环境的描述性术语的数量几乎是无限的。此注册表试图识别可能对通信设备以及控制和指导通信行为有用的通用术语。例如，这些术语大致对应于地理地图上的位置描述和图标的详细程度，并且在各种文化和国家中普遍使用。IANA注意事项部分中描述的注册过程允许根据需要扩展此列表，同时旨在防止注册表中出现不必要的爆炸。
The use of tokens (i.e., protocol constants) makes it easier to build systems across multiple languages. A user interface can readily translate a finite set of tokens to user-appropriate textual or iconic representations. Protocols using this registry are encouraged to provide additional mechanisms to accommodate location types not currently registered via free-text fields with appropriate language and character set labeling.
令牌（即协议常量）的使用使得跨多种语言构建系统变得更加容易。用户界面可以很容易地将有限的标记集转换为用户适当的文本或图标表示。鼓励使用此注册表的协议提供其他机制，以适应当前未通过具有适当语言和字符集标签的自由文本字段注册的位置类型。
The terms defined in this registry do not attempt to provide a hierarchy of location descriptions, except in certain special cases. For example, the term "restaurant" is defined to include the term "cafe", and the term "public" encompasses a range of descriptors, as noted below. The registry makes these more generic terms available as often the more detailed distinctions may not be available, or privacy concerns suggest the use of less precise terms that are still sufficient to guide communications behavior or evaluate the source of a phone call or message, say.
除某些特殊情况外，此注册表中定义的术语不会试图提供位置描述的层次结构。例如，术语“餐厅”被定义为包括术语“咖啡厅”，术语“公共”包括一系列描述符，如下所述。注册中心提供这些更通用的术语，因为通常可能无法获得更详细的区分，或者出于隐私考虑，建议使用不太精确的术语，这些术语仍然足以指导通信行为或评估电话或消息的来源。
In many cases, a location might be described by multiple terms that apply at the same time. For example, the combination of "restaurant" and "airport" is immediately recognizable. This registry makes no attempt to limit the number of terms that can be used to describe a single place or to restrict what combinations are allowed, given that there are few combinations that are physically impossible. Common
在许多情况下，一个位置可能由同时适用的多个术语描述。例如，“餐厅”和“机场”的组合可以立即识别。本注册中心不试图限制可用于描述单个位置的术语数量，也不试图限制允许的组合，因为很少有物理上不可能的组合。常见的
sense is probably a better guide here; the authors would not want to rule out creative business models such as combinations of "parking" and "restaurant" or "bar" and "hospital". The number of terms that can be used within the same protocol element is left to the protocol description.
在这里，理智可能是更好的向导；作者不想排除创造性的商业模式，如“停车场”和“餐厅”或“酒吧”和“医院”的组合。可在同一协议元素中使用的术语数量由协议描述决定。
This document does not describe how the values of the registry are to be used, as this description is provided by other documents. For example, [5] describes options for carrying civic address information, including the place type attributes listed in this document, using the Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6). A usage for Remote Authentication Dial-In User Service (RADIUS) is described in [6], where this information is conveyed from the RADIUS client to the RADIUS server. Rich presence (RPID [4]) also utilizes the values of the location types registry.
本文档不描述如何使用注册表的值，因为本说明由其他文档提供。例如，[5]描述了使用动态主机配置协议（DHCPv4和DHCPv6）承载公民地址信息的选项，包括本文档中列出的地点类型属性。[6]中描述了远程身份验证拨入用户服务（RADIUS）的用法，其中该信息从RADIUS客户端传输到RADIUS服务器。Rich presence（RPID[4]）还利用位置类型注册表的值。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [1].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[1]中所述进行解释。
This section describes types of locations where an entity is located. The entity is not further specified and can be a person or an object such as a network access point or end system.
本节描述实体所在位置的类型。实体未进一步指定，可以是个人或对象，例如网络接入点或终端系统。
aircraft: A device that is used or intended to be used for flight in the air, such as an airplane, helicopter, gyroplane, glider, or lighter-than-air devices like a balloon.
飞机：用于或打算用于空中飞行的装置，如飞机、直升机、旋翼机、滑翔机或比空气轻的装置，如气球。
airport: A place from which aircrafts operate, such as an airport or heliport.
机场：飞机运行的地方，如机场或直升机场。
arena: Enclosed area used for sports events.
竞技场：用于体育活动的封闭区域。
automobile: An automotive vehicle, usually four-wheeled, designed for passenger transportation, such as a car.
汽车：设计用于客运的汽车，通常为四轮，如汽车。
bank: Business establishment in which money is kept for saving, commercial purposes, is invested, supplied for loans, or exchanged.
银行：为储蓄、商业目的、投资、提供贷款或交换而存钱的商业机构。
bar: A bar or saloon.
酒吧：酒吧或酒馆。
bicycle: A vehicle with two wheels tandem, a steering handle, a saddle seat, and pedals by which it is propelled.
自行车：一种两轮串联的车辆，有一个转向手柄、一个鞍座和用来推动它的踏板。
bus: A large motor vehicle designed to carry passengers.
公共汽车：设计用来载客的大型机动车辆。
bus-station: Terminal that serves bus passengers, such as a bus depot or bus terminal.
公共汽车站：为公共汽车乘客服务的终点站，如公共汽车站或公共汽车站。
cafe: Usually a small and informal establishment that serves various refreshments (such as coffee); coffee shop.
咖啡馆：通常是提供各种茶点（如咖啡）的小型非正式场所；咖啡厅
classroom: Academic classroom or lecture hall.
教室：学术教室或演讲厅。
club: Dance club, nightclub, or discotheque.
俱乐部：舞蹈俱乐部、夜总会或迪斯科舞厅。
construction: Construction site.
施工：施工现场。
convention-center: Convention center or exhibition hall.
会议中心：会议中心或展览厅。
government: Government building, such as those used by the legislative, executive, or judicial branches of governments, including court houses, police stations, and military installations.
政府：政府建筑，如政府立法、行政或司法部门使用的建筑，包括法院、警察局和军事设施。
hospital: Hospital, hospice, medical clinic, mental institution, or doctor's office.
医院：医院、临终关怀、医疗诊所、精神病院或医生办公室。
hotel: Hotel, motel, inn, or other lodging establishment.
酒店：酒店、汽车旅馆、客栈或其他住宿设施。
industrial: Industrial setting, such as a manufacturing floor or power plant.
工业：工业环境，如生产车间或发电厂。
library: Library or other public place in which literary and artistic materials, such as books, music, periodicals, newspapers, pamphlets, prints, records, and tapes, are kept for reading, reference, or lending.
图书馆：保存文学和艺术资料（如书籍、音乐、期刊、报纸、小册子、印刷品、唱片和磁带）以供阅读、参考或借阅的图书馆或其他公共场所。
motorcycle: A two-wheeled automotive vehicle, including a scooter.
摩托车：一种两轮汽车，包括小型摩托车。
office: Business setting, such as an office.
办公室：业务设置，如办公室。
other: A place without a registered place type representation.
其他：没有注册地点类型表示的地点。
outdoors: Outside a building, in or into the open air, such as a park or city streets.
户外：建筑物外，在户外，如公园或城市街道。
parking: A parking lot or parking garage.
停车场：停车场或停车场。
place-of-worship: A religious site where congregations gather for religious observances, such as a church, chapel, meetinghouse, mosque, shrine, synagogue, or temple.
礼拜场所：会众聚集进行宗教仪式的宗教场所，如教堂、礼拜堂、会议室、清真寺、神龛、犹太教堂或寺庙。
prison: Correctional institution where persons are confined while on trial or for punishment, such as a prison, penitentiary, jail, brig.
监狱：犯人在受审或受刑期间被监禁的教养机构，如监狱、感化所、监狱、禁闭所。
public: Public area such as a shopping mall, street, park, public building, train station, or airport or in public conveyance such as a bus, train, plane, or ship. This general description encompasses the more precise descriptors 'street', 'public-transport', 'aircraft', 'bus', 'bus-station', 'train', 'train-station', 'airport', 'shopping-area', 'outdoors', and 'watercraft'.
公共：公共区域，如购物中心、街道、公园、公共建筑、火车站或机场，或公共交通工具，如公共汽车、火车、飞机或轮船。该一般描述包括更精确的描述词“街道”、“公共交通”、“飞机”、“公共汽车”、“公共汽车站”、“火车站”、“火车站”、“机场”、“购物区”、“户外”和“船艇”。
public-transport: Any form of public transport, including aircraft, bus, train, or ship.
公共交通：任何形式的公共交通，包括飞机、公共汽车、火车或轮船。
residence: A private or residential setting, not necessarily the personal residence of the entity, e.g., including a friend's home.
住所：私人或住宅环境，不一定是实体的个人住所，例如，包括朋友的家。
restaurant: Restaurant, coffee shop, or other public dining establishment.
餐厅：餐厅、咖啡厅或其他公共餐厅。
school: School or university property, but not necessarily a classroom or library.
学校：学校或大学财产，但不一定是教室或图书馆。
shopping-area: Shopping mall or shopping area. This area is a large, often enclosed, shopping complex containing various stores, businesses, and restaurants usually accessible by common passageways.
购物区：购物中心或购物区。该区域是一个大型的、通常封闭的购物中心，包含各种商店、企业和餐厅，通常通过公共通道进入。
stadium: Large, usually open structure for sports events, including a racetrack.
体育场：大型开放式建筑，用于体育赛事，包括赛马场。
store: Place where merchandise is offered for sale, such as a shop.
商店：出售商品的地方，如商店。
street: A public thoroughfare, such as an avenue, street, alley, lane, or road, including any sidewalks.
街道：公共通道，如大道、街道、小巷、小巷或道路，包括人行道。
theater: Theater, lecture hall, auditorium, classroom, movie theater, or similar facility designed for presentations, talks, plays, music performances, and other events involving an audience.
剧院：剧院、演讲厅、礼堂、教室、电影院或类似设施，用于演讲、演讲、戏剧、音乐表演和其他涉及观众的活动。
train: Train, monorail, maglev, cable car, or similar conveyance.
火车：火车、单轨、磁悬浮、缆车或类似运输工具。
train-station: Terminal where trains load or unload passengers or goods; railway station, railroad station, railroad terminal, train depot.
火车站：火车装卸乘客或货物的终点站；火车站，火车站，火车站，火车站。
truck: An automotive vehicle suitable for hauling, used primarily to carry goods rather than people.
卡车：一种适于运输的汽车，主要用于运输货物而非人员。
underway: In a land-, water-, or aircraft that is underway (in motion).
正在进行中：在陆地、水上或正在进行（运动中）的飞机上。
unknown: The type of place is unknown.
未知：位置类型未知。
warehouse: Place in which goods or merchandise are stored, such as a storehouse or self-storage facility.
仓库：储存货物或商品的地方，如仓库或自储设施。
water: In, on, or above bodies of water, such as an ocean, lake, river, canal, or other waterway.
水：在水体中、之上或之上，如海洋、湖泊、河流、运河或其他水道。
watercraft: On a vessel for travel on water such as a boat or ship.
船艇：在船上航行的船只，如小船或轮船。
This registry can be used in two ways, first, as a list of tokens, to be referenced by appropriate protocols that accept textual tokens, and second, as a schema, with its own namespace, referenced by other schema, either explicitly or via namespace="##other".
此注册表可通过两种方式使用，第一种是作为令牌列表，由接受文本令牌的适当协议引用；第二种是作为模式，具有自己的命名空间，由其他模式显式或通过namespace=“##other”引用。
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:location-type"
xmlns="urn:ietf:params:xml:ns:location-type"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:location-type"
xmlns="urn:ietf:params:xml:ns:location-type"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:complexType name="empty"/>
<xs:complexType name="empty"/>
<xs:complexType name="Note_t">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute ref="xml:lang"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="Note_t">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute ref="xml:lang"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:element name="aircraft" type="empty" />
<xs:element name="airport" type="empty" />
<xs:element name="arena" type="empty" />
<xs:element name="automobile" type="empty" />
<xs:element name="bank" type="empty" />
<xs:element name="bar" type="empty" />
<xs:element name="bicyle" type="empty" />
<xs:element name="bus" type="empty" />
<xs:element name="aircraft" type="empty" />
<xs:element name="airport" type="empty" />
<xs:element name="arena" type="empty" />
<xs:element name="automobile" type="empty" />
<xs:element name="bank" type="empty" />
<xs:element name="bar" type="empty" />
<xs:element name="bicyle" type="empty" />
<xs:element name="bus" type="empty" />
<xs:element name="bus-station" type="empty" />
<xs:element name="cafe" type="empty" />
<xs:element name="classroom" type="empty" />
<xs:element name="club" type="empty" />
<xs:element name="construction" type="empty" />
<xs:element name="convention-center" type="empty" />
<xs:element name="government" type="empty" />
<xs:element name="hospital" type="empty" />
<xs:element name="hotel" type="empty" />
<xs:element name="industrial" type="empty" />
<xs:element name="library" type="empty" />
<xs:element name="motorcycle" type="empty" />
<xs:element name="office" type="empty" />
<xs:element name="other" type="Note_t"/>
<xs:element name="outdoors" type="empty" />
<xs:element name="parking" type="empty" />
<xs:element name="place-of-worship" type="empty" />
<xs:element name="prison" type="empty" />
<xs:element name="public" type="empty" />
<xs:element name="public-transport" type="empty" />
<xs:element name="residence" type="empty" />
<xs:element name="restaurant" type="empty" />
<xs:element name="school" type="empty" />
<xs:element name="shopping-area" type="empty" />
<xs:element name="stadium" type="empty" />
<xs:element name="store" type="empty" />
<xs:element name="street" type="empty" />
<xs:element name="theater" type="empty" />
<xs:element name="train" type="empty" />
<xs:element name="train-station" type="empty" />
<xs:element name="truck" type="empty" />
<xs:element name="underway" type="empty" />
<xs:element name="unknown" type="empty" />
<xs:element name="warehouse" type="empty" />
<xs:element name="water" type="empty" />
<xs:element name="watercraft" type="empty" />
</xs:schema>
<xs:element name="bus-station" type="empty" />
<xs:element name="cafe" type="empty" />
<xs:element name="classroom" type="empty" />
<xs:element name="club" type="empty" />
<xs:element name="construction" type="empty" />
<xs:element name="convention-center" type="empty" />
<xs:element name="government" type="empty" />
<xs:element name="hospital" type="empty" />
<xs:element name="hotel" type="empty" />
<xs:element name="industrial" type="empty" />
<xs:element name="library" type="empty" />
<xs:element name="motorcycle" type="empty" />
<xs:element name="office" type="empty" />
<xs:element name="other" type="Note_t"/>
<xs:element name="outdoors" type="empty" />
<xs:element name="parking" type="empty" />
<xs:element name="place-of-worship" type="empty" />
<xs:element name="prison" type="empty" />
<xs:element name="public" type="empty" />
<xs:element name="public-transport" type="empty" />
<xs:element name="residence" type="empty" />
<xs:element name="restaurant" type="empty" />
<xs:element name="school" type="empty" />
<xs:element name="shopping-area" type="empty" />
<xs:element name="stadium" type="empty" />
<xs:element name="store" type="empty" />
<xs:element name="street" type="empty" />
<xs:element name="theater" type="empty" />
<xs:element name="train" type="empty" />
<xs:element name="train-station" type="empty" />
<xs:element name="truck" type="empty" />
<xs:element name="underway" type="empty" />
<xs:element name="unknown" type="empty" />
<xs:element name="warehouse" type="empty" />
<xs:element name="water" type="empty" />
<xs:element name="watercraft" type="empty" />
</xs:schema>
This document creates new IANA registries for location types as listed in Section 3, starting with 'aircraft' and finishing with 'watercraft'.
本文件为第3节中列出的位置类型创建新的IANA登记册，以“飞机”开始，以“船艇”结束。
IANA will maintain this registry both in the form of an XML schema and a list of tokens, with the same content.
IANA将以XML模式和具有相同内容的令牌列表的形式维护此注册表。
Following the policies outline in RFC 2434 [2], new tokens are assigned after Expert Review. The Expert Reviewer will generally consult the IETF GeoPRIV working group mailing list or its designated successor. Updates or deletions of tokens from the registration follow the same procedures.
按照RFC 2434[2]中的政策大纲，在专家审查后分配新令牌。专家评审员通常会参考IETF GeoPRIV工作组邮件列表或其指定的继任者。从注册中更新或删除令牌遵循相同的过程。
The expert review should be guided by a few common sense considerations. For example, tokens should not be specific to a country, region, organization, or company; they should be well-defined and widely recognized. The expert's support of IANA will include providing IANA with the new token(s) when the update is provided only in the form of a schema, and providing IANA with the new schema element(s) when the update is provided only in the form of a token.
专家审评应以一些常识性考虑为指导。例如，代币不应特定于某个国家、地区、组织或公司；它们应该得到明确定义和广泛承认。专家对IANA的支持包括：当更新仅以模式的形式提供时，向IANA提供新的令牌；当更新仅以令牌的形式提供时，向IANA提供新的模式元素。
To ensure widespread usability across protocols, tokens MUST follow the character set restrictions for XML Names [3].
为了确保跨协议的广泛可用性，令牌必须遵循XML名称的字符集限制[3]。
Each registration must include the name of the token and a brief description similar to the ones offered herein for the initial registrations contained this document:
每次注册必须包括代币的名称和与本文件中包含的初始注册类似的简要说明：
Token Identifier: Identifier of the token.
令牌标识符：令牌的标识符。
Description: Brief description indicating the meaning of the token, including one or more examples where the term encompasses several more precise terms.
描述：指示标记含义的简要描述，包括一个或多个示例，其中该术语包含多个更精确的术语。
XML namespace: Tokens MAY be used as elements within other appropriate XML documents. Each token lists the namespace it is part of, typically urn:ietf:params:xml:ns:location-type:ext, where 'ext' is the name of the extension.
XML名称空间：标记可以用作其他适当XML文档中的元素。每个令牌都列出了它所属的名称空间，通常是urn:ietf:params:xml:ns:location-type:ext，其中“ext”是扩展名。
Note that the usage of these tokens is not limited to XML and the 'Token Identifier' is the XML element content and not the XML element name.
请注意，这些标记的使用不限于XML，“标记标识符”是XML元素内容，而不是XML元素名称。
5.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:location-type
5.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:location-type
URI: urn:ietf:params:xml:ns:location-type
URI: urn:ietf:params:xml:ns:location-type
Description: This is the XML namespace for XML elements defined by RFC4589 to describe location types within XML documents.
描述：这是RFC4589定义的XML元素的XML名称空间，用于描述XML文档中的位置类型。
Registrant Contact: IETF, GEOPRIV working group, geopriv@ietf.org, Henning Schulzrinne, hgs@cs.columbia.edu
注册人联系人：IETF、GEOPRIV工作组、，geopriv@ietf.org，Henning Schulzrinne，hgs@cs.columbia.edu
XML:
XML:
BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>Location Types Registry</title>
</head>
<body>
<h1>Namespace for Location Types</h1>
<h2>urn:ietf:params:xml:ns:location-type</h2>
<p>See <a href="ftp://ftp.rfc-editor.org/in-notes/rfc4589.txt">
RFC4589</a>.</p>
</body>
</html>
END
BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>Location Types Registry</title>
</head>
<body>
<h1>Namespace for Location Types</h1>
<h2>urn:ietf:params:xml:ns:location-type</h2>
<p>See <a href="ftp://ftp.rfc-editor.org/in-notes/rfc4589.txt">
RFC4589</a>.</p>
</body>
</html>
END
5.3. Schema Registration for Schema
urn:ietf:params:xml:ns:location-type
5.3. Schema Registration for Schema
urn:ietf:params:xml:ns:location-type
URI: urn:ietf:params:xml:ns:location-type
URI: urn:ietf:params:xml:ns:location-type
Registrant Contact: IESG
注册联系人：IESG
XML: See Section 4
XML：参见第4节
The location type values listed in this document MUST NOT be presented to the user. The values therefore have the characteristic of tokens or tags and no internationalization support is required.
不得向用户显示本文档中列出的位置类型值。因此，这些值具有令牌或标记的特征，不需要国际化支持。
This document defines a registry for location types and as such does not raise security issues.
本文档定义了位置类型的注册表，因此不会引起安全问题。
Vijay Gurbani, Paul Kyzivat, and Jonathan Rosenberg contributed to RPID [4], which led to the location types listed in this document. Many thanks to Harald Alvestrand, Frank Ellermann, Bill Fenner, Ted Hardie, David Kessens, Allison Mankin, Jon Peterson, and Sam Hartman for their suggestions. Rick Jones pointed us to the Global Justice
Vijay Gurbani、Paul Kyzivat和Jonathan Rosenberg对RPID[4]做出了贡献，这导致了本文中列出的位置类型。非常感谢Harald Alvestrand、Frank Ellermann、Bill Fenner、Ted Hardie、David Kessens、Allison Mankin、Jon Peterson和Sam Hartman的建议。里克·琼斯向我们指出了全球正义
XML work (see http://it.ojp.gov/jxdm/) that helped us to add more values to the location registry.
XML工作（参见http://it.ojp.gov/jxdm/)这有助于我们向位置注册表添加更多值。
Some of the definitions are derived from the Merriam-Webster Online Dictionary.
其中一些定义源自韦氏在线词典。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[2] Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[3] Sperberg-McQueen, C., Maler, E., Bray, T., Paoli, J., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium Recommendation http://www.w3.org/TR/2004/REC-xml-20040204, February 2004.
[3] Sperberg McQueen，C.，Maler，E.，Bray，T.，Paoli，J.，和F.Yergeau，“可扩展标记语言（XML）1.0（第三版）”，万维网联盟建议http://www.w3.org/TR/2004/REC-xml-20040204，2004年2月。
[4] Schulzrinne, H., "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)", Work in Progress, December 2005.
[4] Schulzrinne，H.，“RPID：状态信息数据格式（PIDF）的丰富状态扩展”，正在进行的工作，2005年12月。
[5] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information", Work in Progress, January 2006.
[5] Schulzrinne，H.，“Civic地址配置信息的动态主机配置协议（DHCPv4和DHCPv6）选项”，正在进行的工作，2006年1月。
[6] Tschofenig, H., "Carrying Location Objects in RADIUS", Work in Progress, March 2006.
[6] Tschofenig，H.，“在半径内携带定位物体”，正在进行的工作，2006年3月。
Authors' Addresses
作者地址
Henning Schulzrinne Columbia University Department of Computer Science 450 Computer Science Building New York, NY 10027 USA
美国纽约州纽约市哥伦比亚大学计算机科学系计算机科学大楼450号
Phone: +1 212 939 7042
EMail: schulzrinne@cs.columbia.edu
URI: http://www.cs.columbia.edu/~hgs
Phone: +1 212 939 7042
EMail: schulzrinne@cs.columbia.edu
URI: http://www.cs.columbia.edu/~hgs
Hannes Tschofenig Siemens Otto-Hahn-Ring 6 Munich, Bavaria 81739 Germany
德国巴伐利亚州慕尼黑第6环汉内斯·茨霍芬尼西门子奥托·哈恩81739
EMail: Hannes.Tschofenig@siemens.com
URI: http://www.tschofenig.com
EMail: Hannes.Tschofenig@siemens.com
URI: http://www.tschofenig.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。