One document matched: draft-rosen-geopriv-pidf-interior-01.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc3688 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml">
<!ENTITY rfc4119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4119.xml">
<!ENTITY rfc4776 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4776.xml">
<!ENTITY rfc5139 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5139.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc compact="yes"?>
<rfc category="std" docName="draft-rosen-geopriv-pidf-interior-01" ipr="trust200902">
<front>
<title abbrev="Interior Location">
Interior Location in the Presence Information Data Format - Location Object
</title>
<author fullname="Brian Rosen" initials="B." surname="Rosen">
<organization abbrev="NeuStar">NeuStar, Inc.</organization>
<address>
<postal>
<street>470 Conrad Dr</street>
<city>Mars</city>
<region>PA</region>
<code>16046</code>
<country>US</country>
</postal>
<email>br@brianrosen.net</email>
</address>
</author>
<date year="2010"/>
<area>RAI</area>
<workgroup>geopriv</workgroup>
<abstract>
<t>RFC5139 defines explicit tags for interior building location such as "BLD" (building), "UNIT", "ROOM".
There is wide variation in how interior spaces are named, and the rigid element names provided do not allow accurate representation
of interior spaces that don't use the element tags defined. This memo provides an alternative mechanism that provides an extensible
flexible way to name spaces in any kind of addressable location.</t>
</abstract></front><middle>
<section title="Terminology">
<t>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 <xref
target="RFC2119"></xref>.</t>
</section><section title="Introduction">
<t><xref target="RFC4119"/> provides a way to specify an addressable civic location, naming the country, region, city, street name, etc.
Within that document is an element FLR (floor) which specifies location within the addressable location. <xref target="RFC5139"/>
extends the ability to locate interior spaces by defining BLD (Building), UNIT, ROOM, and SEAT. The problem with these elements is
that there is very wide variation in how interior spaces are named, and these fixed elements don't allow one to specify interior
location that matches signage, drawings or other conventions that are needed to properly locate targets within an addressable location.
An example of where the BLD/FLR/UNIT/ROOM doesn't work is an airport. Interior location may be given as Terminal 2, Concourse A,
Gate 27.</t>
<t>Additionally, since interior location may vary within a structure (Terminal 2, Food Court, Store 13), and every building could have
different conventions, it is essential that a way to parse a sign, drawing, or other representation of interior space to the elements
needed to specify that space in a PIDF, or the reverse: creating a human readable string from a PIDF matching signage or drawings,
it must be possible to specify how the conversion from human readable to PIDF and vice versa can be accomplished.</t>
</section>
<section title="INT element">
<t>This memo introduces a new CAtype for PIDF-LO called "INT" (for interior) which has two new attributes:
<list style="hanging" hangIndent='5'>
<t hangText =" N">The locally significant name of a "level" of interior space. Examples include "Floor", "Concourse" and "Suite".</t>
<t hangText =" R">An enumeration of how the name and value are represented in a human readable form.</t>
</list></t>
<t>A PIDF-LO may have multiple INT elements. If there are more than one, the order in which they appear in the PIDF can be significant.</t>
<t>The R attribute has the following values:
<list style="hanging" hangIndent='5'>
<t hangText =" B">The name is expressed before the value as in "Concourse A".</t>
<t hangText =" A">The name is expressed after the value as in "Presidential Suite".</t>
</list></t>
<t>If the R subelement is not present, the default value "B" is assumed.</t>
<t>An IANA registry of N values is established by this document. As the names are only required to be locally significant, adding new values to the registry should be simple.</t>
<t>While the existing BLD/FLR/UNIT/ROOM/SEAT elements are not deprecated by this document, their use should be restricted to existing implementations. New implementations SHOULD use INT. As always, recipients of PIDF-LO should be liberal in what they accept, which would mean both INT and BLD/FLR/UNIT/ROOM/SEAT.</t>
</section>
<section title="Examples">
<figure><artwork>
<civicAddress xml:lang="en-AU"
xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
<country>AU</country>
<A1>NSW</A1>
<A3>Wollongong</A3>
<A4>North Wollongong</A4>
<RD>Flinders</RD><STS>Street</STS>
<NAM> Video Rental Store </NAM>
<PC>2500</PC>
<INT N='Room' R='A'>Westerns and Classics</INT>
</civicAddress>
<civicAddress xml:lang="en-US"
xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
<country>US</country>
<A1>PA</A1>
<A3>Findlay</A3>
<RD>Airport</RD><STS>RD</STS>
<INT N='Terminal'>1</INT>
<INT N='Concourse'>A</INT>
<INT N='Gate'>37</INT>
</civicAddress>
</artwork></figure>
</section>
<section anchor="schema" title="Civic Address Schema">
<figure><artwork><![CDATA[
<?xml version="1.0"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:simpleType name="iso3166a2">
<xs:restriction base="xs:token">
<xs:pattern value="[A-Z]{2}"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="caType">
<xs:simpleContent>
<xs:extension base="xs:token">
<xs:attribute ref="xml:lang" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="intType">
<xs:simpleContent>
<xs;attribute name="N" type="xs:string" use="optional"/>
<xs:attribute name="R" use="optional", default="B"
<xs:restriction base="xs:string">
<xs:pattern value="[AB]"/>
</xs:restriction>
<xs:extension base="xs:token">
<xs:attribute ref="xml:lang" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:element name="civicAddress" type="ca:civicAddress"/>
<xs:complexType name="civicAddress">
<xs:sequence>
<xs:element name="country" type="ca:iso3166a2" minOccurs="0"/>
<xs:element name="A1" type="ca:caType" minOccurs="0"/>
<xs:element name="A2" type="ca:caType" minOccurs="0"/>
<xs:element name="A3" type="ca:caType" minOccurs="0"/>
<xs:element name="A4" type="ca:caType" minOccurs="0"/>
<xs:element name="A5" type="ca:caType" minOccurs="0"/>
<xs:element name="A6" type="ca:caType" minOccurs="0"/>
<xs:element name="PRM" type="ca:caType" minOccurs="0"/>
<xs:element name="PRD" type="ca:caType" minOccurs="0"/>
<xs:element name="RD" type="ca:caType" minOccurs="0"/>
<xs:element name="STS" type="ca:caType" minOccurs="0"/>
<xs:element name="POD" type="ca:caType" minOccurs="0"/>
<xs:element name="POM" type="ca:caType" minOccurs="0"/>
<xs:element name="RDSEC" type="ca:caType" minOccurs="0"/>
<xs:element name="RDBR" type="ca:caType" minOccurs="0"/>
<xs:element name="RDSUBBR" type="ca:caType" minOccurs="0"/>
<xs:element name="HNO" type="ca:caType" minOccurs="0"/>
<xs:element name="HNS" type="ca:caType" minOccurs="0"/>
<xs:element name="LMK" type="ca:caType" minOccurs="0"/>
<xs:element name="LOC" type="ca:caType" minOccurs="0"/>
<xs:element name="FLR" type="ca:caType" minOccurs="0"/>
<xs:element name="NAM" type="ca:caType" minOccurs="0"/>
<xs:element name="PC" type="ca:caType" minOccurs="0"/>
<xs:element name="BLD" 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="SEAT" type="ca:caType" minOccurs="0"/>
<xs:element name="PLC" type="xs:token" minOccurs="0"/>
<xs:element name="PCN" type="ca:caType" minOccurs="0"/>
<xs:element name="POBOX" type="ca:caType" minOccurs="0"/>
<xs:element name="STP" type="ca:caType" minOccurs="0"/>
<xs:element name="HNP" type="ca:caType" minOccurs="0"/>
<xs:element name="INT" type="ca:intType minOccurs="0"/>
<xs:element name="ADDCODE" type="ca:caType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
</xs:schema>
]]></artwork></figure></section>
<section title="Security Considerations">
<t>The XML representation described in this document is designed for
inclusion in a PIDF-LO document. As such, it is subject to the same
security considerations as are described in <xref target="RFC4119"/>.
Considerations relating to the inclusion of this representation in
other XML documents are outside the scope of this document.</t>
<t>This extension may make it possible to more precisely locate a target, and thus raise more privacy concerns. However, since
<xref target="RFC5139"/> already can locate to a seat in a room, this concern does not seem to be significant.</t>
</section>
<section title="IANA Considerations">
<section title="XML Schema Registration">
<t>This section registers an XML schema as per the procedures in <xref target="RFC3688"/>.</t>
<figure><artwork>
URI: urn:ietf:params:xml:schema:pidf:geopriv10:civicAddr
Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org),
Brian Rosen (brian.rosen@neustar.biz).
The XML for this schema can be found as the entirety of Section 5.
of this document.
</artwork></figure></section>
<section title="CAtype Registry Update">
<t>
This document updates the civic address type registry established by
<xref target="RFC4776"/>. One additional value is added:</t>
<figure><artwork>
40 INT Interior Location
</artwork></figure>
</section>
<section title="INT Name Registry">
<t>This document creates a new registry managed by IANA for the values that may appear in an "N" attribute in an INT element.</t>
<t>The name of this registry is "INT Names"</t>
<t>Each entry in the registry includes the Name which can appear in the N attribute (a text string).</t>
<t>The policy for this registry is "first come, first served"</t>
<t>The initial values for this registry are "Building", "Floor", "Suite", "Room", "Seat", "Terminal", "Concourse" and "Gate".</t>
</section></section>
<section title="Acknowledgements">
<t>The authors would like to acknowledge James Polk and Marc Linsner for their contributions to this document.
</t></section>
</middle>
<back>
<references title="Normative References">
&rfc2119;
&rfc4119;
&rfc5139;
</references>
<references title="Informative References">
&rfc3688;
&rfc4776;
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-21 00:28:24 |