One document matched: draft-rosen-geopriv-pidf-interior-00.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="info" docName="draft-rosen-geopriv-pidf-interior-00" ipr="trust200902">
  <front>
    <title >
      Interior Location in PIDF-LO
    </title>

    <author fullname="Brian Rosen" initials="B.R." 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 day="3" month="July" year="2009" />

    <area>app</area>

<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 addressible 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 readible string from a PIDF matching signage or drawings, 
it must be possible to specify how the conversion from human readible 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 readible 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 signficant.</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>Editor's note: Should FLR, BLD, ROOM, ... be deprecated?  I think we should.</t>
</section>
<section title="Civic Address Schema">

<t>TBD</t>
</section>
<section anchor="schema" 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 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>
</section>
<section title="IANA Considerations">
<section title="XML Schema Registration">

<t>This section replaces the existing XML namespace per the procedures of <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 4
      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>
  </middle>

  <back>
     <references title="Normative References">
      &rfc2119;
      &rfc4119;
      &rfc5139;
    </references>
   <references title="Informative References">
      &rfc3688;
      &rfc4776;
    </references>
  </back>
</rfc>