[Cache from http://www.w3.org/1999/06/NOTE-poix-19990624/; please use this canonical URL/source if possible.]

W3C

POIX: Point Of Interest eXchange Language Specification

W3C Note - 24 June 1999

This version:: http://www.w3.org/1999/06/NOTE-poix-19990624
Latest version:: http://www.w3.org/TR/poix
Editors:: Hiroyuki Kanemitsu,
TOYOTA MOTOR CORPORATION
kanemitu@fantasia.ml.toyota.co.jp

Tomihisa Kamada,
ACCESS Co.,Ltd.
tomy@access.co.jp

*This document was created in cooperation with the POI Working Group in MOSTEC(MObile Information Standard TEchnical Committee).

Status of this Document

This document is a NOTE made available by the W3 Consortium for discussion only. This indicates no endorsement of its content, nor that the Consortium has had any editorial control in it preparation, nor that the Consortium has, is, or will be allocating any resources to the issues addressed by the NOTE.

Abstract

The Internet is rapidly growing toward wireless and mobile environment beyond the wired world. Nowadays, various types of mobile devices including PDAs and car navigation systems can access to the Internet. These devices are required to exchange the location-related information such as position data on the map. The "POIX" proposed here defines a general-purpose specification language for describing location information, which is an application of XML (Extensible Markup Language). POIX is a common baseline for exchanging location data via e-mail and embedding location data in HTML and XML documents. This specification can be used by mobile device developers, location-related service providers, and server software developers.

1. PURPOSE OF THIS SPECIFICATION

2. VERSION NUMBER AND DOCUMENT REVISION

3. REVISION HISTORY

4. SUMMARY

5. INTRODUCTION
    5.1. Study Organization
    5.2. Purpose of Use and Design Policy
    5.3. Language Specification and Operational Specification

6. LANGUAGE SPECIFICATION
    6.1. Document Type Definition POIX.DTD
    6.2. Terminology
    6.3. Common Items
    6.4. Abbreviations
    6.5. Description of Elements and Attributes
        6.5.1. poix
        6.5.2. format
        6.5.3. datum
        6.5.4. unit
        6.5.5. type
        6.5.6. author
        6.5.7. time
        6.5.8. poi
        6.5.9. point
        6.5.10. pos
        6.5.11. lat
        6.5.12. lon
        6.5.13. herror
        6.5.14. alt
        6.5.15. verror
        6.5.16. move
        6.5.17. method
        6.5.18. speed
        6.5.19. dir
        6.5.20. locus
        6.5.21. name
        6.5.22. nb
        6.5.23. rt
        6.5.24. access
        6.5.25. method
        6.5.26. ipoint
        6.5.27. iclass
        6.5.28. tpoint
        6.5.29. tclass
        6.5.30. route
        6.5.31. pol
        6.5.32. contact
        6.5.33. mate
    6.6. POIX file type
        6.6.1. POIX file extension
        6.6.2. POIX media type

7. OPERATIONAL SPECIFICATION
    7.1. Geodetic datum
    7.2. Angle Units
        7.2.1. Unit of degrees
        7.2.2. Unit of Degrees, Minutes, and Second
    7.3. Altitude
    7.4. Horizontal and Vertical Errors
    7.5. Moving Method
    7.6. Moving Speed
    7.7. Moving Direction
    7.8. Introductory Point Class
    7.9. Terminal Point Class
    7.10. Route Coordinate Point String
    7.11. Locus Coordinate Point String
    7.12. Contact
        7.12.1. Contact Hyper Reference
        7.12.2. Note for Contact
    7.13. Relevant POIX
        7.13.1. Relevant POIX Hyper Reference
        7.13.2. Note for Relevant

8 EXAMPLES OF DESCRIPTIONS
    8.1. Example of Simple Description for Notifying the Location
    8.2. Example of Description with Access Method Appended
    8.3. Example of Description for Location-related information on Mobile Entity

9 APPENDIX
    9.1. MOSTEC Members

10. REFERENCES

1. PURPOSE OF THIS SPECIFICATION

This document specifies the data format for exchange of location-related information over the Internet, as discussed at the MOSTEC (MObile Information Standard TEchnical Committee). This data format is called POIX (Point Of Interest eXchange language).

This document is intended to present the POIX data format and promote its use, and may be distributed freely for that purpose, provided that an entire copy thereof shall be distributed and the content thereof shall not be altered or modified in any way.

2. VERSION NUMBER AND DOCUMENT REVISION

The version number of POIX shall be represented by an integer numeral, plus a single decimal digit, where the integer portion denotes a major number, and the decimal digit defines a minor number. For small modification, such as any addition to the organization of the document, the minor number shall be updated. For significant modification that requires change in the organization or deletion thereof, the major number shall be updated.

For any modification to the document that does not require a POIX version update, such as errata or change in the interpretation, the Document Revision shall be updated. For any change that requires a POIX version update, the Document Revision shall remain 1.

3. REVISION HISTORY

POIX
version Document
Revision Changes Date

version 1.0 1 First release 4.1.1999

version 1.1 1 Change of element name: "code"to"datum" 5.17.1999

version 2.0 1 change of definition sub-element of "name" 6.14.1999

4. SUMMARY

POIX is a location-related information descriptive language prepared with the aim of exchanging location-related information over the Internet, and is designed with XML 1.0* (Extensible Markup Language [W3C Recommendation]). Not only does POIX denote a simple location, but it also provides an environment capable of representing various information comprehensively with the targeted location.

* XML is a registered trademark of W3C.

5. INTRODUCTION

5.1. Study Organization

POIX was created by the POI Working Group among the MOSTEC and examined by all the members of the MOSTEC. Experts and specialists in the field of mobile technology as a whole, including car navigation systems, digital maps, and personal digital assistants (PDAs), participated as the members in the examination and functional verification. The MOSTEC members are indicated in APPENDIX.

5.2. Purpose of Use and Design Policy

POIX has been created for the purpose of exchanging location-related information over the Internet. At present, many services utilizing location-related information are available; and the use of POIX enables exchanging of location-related information among those services. In addition to realizing the exchange of location-related information among the different services, it has been designed to implement sufficient functions for a terminal connected directly to the Internet to make reference to the POIX-described information.

Design policy for POIX is described below.

POIX is intended only to indicate a location of a target and its location-related information; various representations of information about the target, such as business time of a shop, are made in a main document or its equivalent and are not defined in POIX that is positioned as a complementary vehicle.
For location-related information, because localized items by country or region, such as geodetic handling, exist, descriptive flexibility is enhanced as a language specification, and semantics for the notation are defined as an operational specification. This is intended to minimize the influence of the localized items on the POIX structure.
The structure of POIX is defined simply so that POIX can be supported by portable terminals and car navigation systems.
A target indicative of a location, no matter whether it is fixed, such as a building, or movable, such as a car, may be described in a consistent manner.
Information for realizing the capability of route guidance to an indicated location is defined. If multiple routes to the indicated location exist, means are provided to describe them all.
If any generic specification or standard is available, such as for notation, they are used as extensively as possible to enhance the general-purpose nature of POIX.
In order to avoid too much complication of the POIX structure and its excessive description, only one piece of location-related information is described in one POIX. However, if it is necessary to indicate multiple locations for a single facility, such as exits of a station, then means are provided to realize this capability in such a manner that reference is made from one POIX to another POIX.
In consideration of the above rules, POIX is designed so that one piece of location-related information is exchanged at a time. Thus, no consideration should be given to applications, such as classification of categories by building or purpose of action, as in the case of implementation of location-related information search databases, or efficient interchange of multiple location-related information at once.

5.3. Language Specification and Operational Specification

At present, methods of representing locations differ according to the country, region, and organization, because different geodetic or angle units are used. POIX is intended in its language specification to provide capability of defining geodetic or coordinate system specifications with flexibility. In actual use, however, it is necessary to standardize on these specifications and terminology among users. This document first covers the Language Specification, followed by the Operational Specification. For geodetic and angle units, international standardization is under way; once they are decided and come into widespread use, multiple location notations defined in the operational specification will be standardized, so that POIX will assume a single location notation.

6. LANGUAGE SPECIFICATION

6.1. Document Type Definition POIX.DTD

<!ELEMENT   poix   (format,poi) >
<!ATTLIST   poix version   NMTOKEN   #REQUIRED >

<!ELEMENT   format   (datum,unit,type?,author*,time?) >

<!ELEMENT   datum   (#PCDATA) >
<!ELEMENT   unit   (#PCDATA) >
<!ELEMENT   type   EMPTY >
<!ATTLIST   type object   (fix | move)   "fix" >
<!ELEMENT   author   (#PCDATA) >
<!ATTLIST   author   xml:lang   NMTOKEN   #IMPLIED >
<!ELEMENT   time   (#PCDATA) >

<!ELEMENT   poi   (point,move?,name*,access*,contact*,note*,mate*) >

<!ELEMENT   point   (pos) >
<!ELEMENT   pos   (lat,lon,herror?,alt?,verror?) >
<!ELEMENT   lat   (#PCDATA) >
<!ELEMENT   lon   (#PCDATA) >
<!ELEMENT   herror   (#PCDATA) >
<!ELEMENT   alt   (#PCDATA) >
<!ELEMENT   verror   (#PCDATA) >

<!ELEMENT   move   (method?,speed?,dir?,locus?) >
<!ELEMENT   method   (#PCDATA) >
<!ELEMENT   speed   (#PCDATA) >
<!ELEMENT   dir   (#PCDATA) >
<!ELEMENT   locus   (pos*) >

<!ELEMENT   name   (nb,rt?) >
<!ATTLIST   name   style   (formal | popular)   "formal" >

<!ELEMENT   nb   (#PCDATA) >
<!ELEMENT   rt   (#PCDATA) >

<!ELEMENT   note   (#PCDATA) >
<!ATTLIST   note   xml:lang   NMTOKEN   #IMPLIED >

<!ELEMENT   access   (method,ipoint,tpoint,route?,note?) >

<!ELEMENT   ipoint   (iclass,pos,name?) >
<!ELEMENT   iclass   (#PCDATA) >

<!ELEMENT   tpoint   (tclass,pos,name?) >
<!ELEMENT   tclass   (#PCDATA) >

<!ELEMENT   route   (pol) >
<!ELEMENT   pol   (pos*) >

<!ELEMENT   contact   (#PCDATA) >
<!ATTLIST   contact
xml:lang   NMTOKEN   #IMPLIED
xml:link   NMTOKEN   #FIXED   "simple" 
href       CDATA     #REQUIRED
>

<!ELEMENT   mate (#PCDATA) >
<!ATTLIST   mate
xml:lang   NMTOKEN   #IMPLIED
xml:link   NMTOKEN   #FIXED   "simple"
href       CDATA     #REQUIRED
>

6.2. Terminology

Information type name
A candidate of an attribute value for an attribute list declaration is called an information type name.
Representative location
It refers to a representative location of a target; an information creator sets an appropriate point in the boundary of the target. It is recommended to set a point in the center of the institutional or administrative boundary. For a mobile entity, the point where it actually is set.
Introductory Point
It refers to an end point through which to go to the target; an appropriate point is set by an information creator. It is recommended to set a point that serves as an eventual mark, such as a station, intersection, or stop.
Terminal Point
It refers to an eventual destination point for the target; an information creator sets an appropriate point within the boundary of the target. It is recommended to set a point where an eventual arrival is completed, such as a parking lot, entrance, or gate.
Moving method
It refers to moving method used from the start point to the destination point.
Guidance route
It refers to a route from the start point to the destination point.

Route coordinate point string
The route from the introductory point to the terminal point is represented by a string of coordinate points. The points are numbered in ascending order from the introductory point to the terminal point. The introductory and terminal points are excluded from the numbering of points. It is recommended to set coordinate points at branches of the route or points where the route changes in shape significantly, between the introductory and terminal points.

String of locus coordinate points
In order to indicate a route up to the current point for a mobile entity, the past locus from the current point is represented by a string of coordinate points. Points are indicated in reverse historical order starting from the current point, which is excluded from the numbering of points. In order to represent the locus properly, it is recommended to set coordinate points at branches of the route or points where the route changes in shape significantly.

Horizontal error
With a point expressed in terms of latitude and longitude, an expected error in the horizontal direction is represented by a circle, and the length of its radius serves as a horizontal error of its latitude and longitude.

Vertical error
With a point expressed in terms of altitude, an error expected upward or downward, with the indicated altitude as a starting point, serve as a vertical error. If values differ between upward and downward errors, the greater of the two is used.

6.3. Common Items

Unless specifically noted, alphanumeric letters used in the language specification and operational specification shall be described in half-width (single-byte) character notation.

Italic notation in a format item indicates that an appropriate numeral or character string as described in its explanation should be described in that portion.

6.4. Abbreviations

XML Extensible Markup Language

POI Point Of Interest

RFC Request For Comments

URL Uniform Resource Locator

DTD Document Type Definition

UTC Coordinated Universal Time

WGS84 World Geodetic System 1984

ITRF International Terrestrial Reference Frame

6.5. Description of Elements and Attributes

6.5.1. poix

<!ELEMENT poix (format,poi) >
<!ATTLIST poix version NMTOKEN #REQUIRED >

Root element
Indicates that it is data described in POIX as a root element.

Attribute:
version=NMTOKEN
Format:

  <poix version=
"POIX version number">···</poix>

Explanation:
The POIX version number used is described. For this specification, version "2.0" should be used.
Example of description:
<poix version="2.0">···</poix>

6.5.2. format

<!ELEMENT format (datum,unit,type?,author*,time?) >

Format information
The geodetic datum, coordinate system, target type (whether it is mobile or not), information creator, and information creation date/time that are used in the POIX described are indicated as format information. This realizes simplification of processing, description, and administration. It also prevents mixing of location-related information having different angle units and thus complication of information contents. Its individual elements will be presented hereinbelow.

6.5.3. datum

<!ELEMENT datum (#PCDATA) >

Geodetic datum
Indicates the geodetic datum used.

Format:

  <datum>
geodetic datum name</datum>

Explanation:
One of the notations defined in Section 7.1 of Operational Specification is designated as the geodetic datum name.
Example of description:
<datum>wgs84</datum>

6.5.4. unit

<!ELEMENT unit (#PCDATA) >

Angle Units
Indicates the angle units used.

Format:

  <unit>angle units name</unit>

Explanation:
One of the notations defined in Section 7.2 of Operational Specification is designated as the angle units name.
Example of description:
<unit>degree</unit>

6.5.5. type

<!ELEMENT type EMPTY >
<!ATTLIST type object (fix | move) "fix" >

Information type
It is an empty element, and indicates whether the location target to be represented is mobile or not.

Attribute:
object=(fix | move)"fix"
Format:

  <type object=
"information type name" />

Explanation:
  The location target to be represented is selected and designated from the information type names.
   · fix ... Not mobile (buildings, such as facilities, that do not move in a short time)
   · move ... Mobile (entities, such as cars and airplanes, that move over time)
Example of description:
  <type object="fix" />

6.5.6. author

<!ELEMENT author (#PCDATA) >
<!ATTLIST author xml:lang NMTOKEN #IMPLIED >

Information creator
Indicates an author of information.

Attribute:
xml:lang=NMTOKEN
Format:

  <author xml:lang=
"language identifier">
name</author>

Explanation:
  The name of the author is described. If you want to explicitly indicate the description language in the
  application, an RFC1766-compliant language identifier should be designated for the attribute, xml:lang.
Example of description:
  <author xml:lang="en">Hiroyuki Kanemitsu</author>

6.5.7. time

<!ELEMENT time (#PCDATA) >

Information creation date/time
Indicates the date and time when the POIX information is created.

Format:

  <time>
information creation date/time</time>

Explanation:
  The year/month/day/hour/minute/second format in compliance with the Internet Draft,
  "Date and Time on the Internet," plus TZD (Time Zone Designator), is used.

  YYYY = four-digit year (1998)
  MM = two-digit month (a value from 01 to 12)
  DD = two-digit day (a value from 01 to 31)
  hh = two-digit hour (a value from 00 to 23 in 24-hour notation)
  mm = two-digit minute (a value from 00 to 59)
  ss = two-digit second (a value from 00 to 59)
  TZD = it is described in the form of +hh:mm or -hh:mm according to the time zone. For UTC, Z is designated.

Example of description:
  <time>1998-08-25T15:05:07Z</time>
  <time>1997-07-16T19:20:30+09:00</time>

6.5.8. poi

<!ELEMENT poi (point,move?,name*,access*,contact*,note*,mate*) >

POI information
Indicates the main body of POI information. The POI information is made up of the target location, name, how to go to the target indicated, contact of the target, explanation of the target, and relevant POIX information. For a mobile entity, the past locus point string may described as needed. Its individual elements will be presented hereinbelow.

6.5.9. point

<!ELEMENT point (pos) >

Representative location
Indicates the representative location of a target. The representative location is expressed by the following subelement, pos, which indicate the position.

6.5.10. pos

<!ELEMENT pos (lat,lon,herror?,alt?,verror?) >

Position
Indicates the position and accuracy. The position is expressed in terms of latitude, longitude, horizontal error, altitude, and vertical error.

6.5.11. lat

<!ELEMENT lat (#PCDATA) >

Latitude
Indicates the latitude of a point.

Format:

  <lat>
latitude</lat>

Explanation:
  It is described in the notation defined in Section 7.2 of Operational Specification in accordance with
  the geodetic and angle units defined in Sections 6.5.3 and 6.5.4 hereof.
Example of description:
  <lat>35.5000</lat>

6.5.12. lon

<!ELEMENT lon (#PCDATA) >

Longitude
Indicates the longitude of a point.

Format:

  <lon>
longitude</lon>

Explanation:
  It is described in the notation defined in Section 7.2 of Operational Specification in accordance with the geodetic and
  angle units defined in Sections 6.5.3 and 6.5.4 hereof.
Example of description:
  <lon>-135.75</lon>

6.5.13. herror

<!ELEMENT herror (#PCDATA) >

Horizontal Error
Indicates a horizontal error for a position represented by elements, lat and lon.

Format:

  <herror>
horizontal error</herror>

Explanation:
It is described in the notation defined in Section 7.4 of Operational Specification.
Example of description:
<herror>10</herror>

6.5.14. alt

<!ELEMENT alt (#PCDATA) >

Altitude
Indicates the altitude of a point.

Format:

  <alt >
altitude</alt>

Explanation:
   It is described in the notation defined in Section 7.3 of Operational Specification in accordance with
   geodetic and angle units defined in Section 6.5.3 and 6.5.4 hereof.
Example of description:
  <alt>100</alt>

6.5.15. verror

<!ELEMENT verror (#PCDATA) >

Vertical Error
Indicates the vertical error.

Format:

  <verror>
vertical error</verror>

Explanation:
It is described in the notation defined in Section 7.4 of Operational Specification.
Example of description:
<verror>50</verror>

6.5.16. move

<!ELEMENT move (method?,speed?,dir?,locus?) >

Movement status of a mobile entity
Indicates the movement status in terms of mobile method, moving speed, moving direction, and locus,
if the target is a mobile entity.

6.5.17. method

<!ELEMENT method (#PCDATA) >

Moving method
Indicates the current moving method of a mobile entity. It is the same as the subelement, method,
of the element, access, in both format and content.

Format:

  <method>
moving method</method>

Explanation:
One of the notations defined in Section 7.5 of Operational Specification is designated.
Example of description:
<method>car</method>

6.5.18. speed

<!ELEMENT speed (#PCDATA) >

Moving speed
Indicates the current moving velocity of a mobile entity.

Format:

  <speed>
moving speed</speed>

Explanation:
It is described in the notation defined in Section 7.6 of Operational Specification.
Example of description:
<speed>40</speed>

6.5.19. dir

<!ELEMENT dir (#PCDATA) >

Moving direction
Indicates the current moving direction of a mobile entity.

Format:

  <dir>
moving direction</dir>

Explanation:
It is described in the notation defined in Section 7.7 of Operational Specification.
Example of description:
<dir>178</dir>

6.5.20. locus

<!ELEMENT   locus   (pos*) >

Indicates the string of locus coordinate points.
The coordinate point is indicated by the method designated in the element, pos.

Format:

  <locus>
string of locus coordinate points</locus>

Explanation:
  The positions of the coordinate point string are described in accordance with the definition
  for the string of locus coordinate points in Section 6.2 "Terminology" hereof.
Example of description:
  <locus>
    <pos><lat>35.7700</lat><lon>139.8800</lon></pos>
    <pos><lat>35.8800</lat><lon>138.9900</lon></pos>
    <pos><lat>35.9900</lat><lon>139.0000</lon></pos>
  </locus>

6.5.21. name

<!ELEMENT name (nb,rt?) >
<!ATTLIST name style (formal | popular) "formal" >

Name
Indicates the name of a target.

Attribute:
style = (formal | popular) "formal"

Format:

  <name style = "information type name">···</name>

Explanation:
  The name of a target is expressed by the following sub-element, nb, rt. Whether it is a formal name or popular name is designated for the attribute, style, by use of the following information type names.
   ·formal ... formal name
   ·popular ... popular name

6.5.22. nb

<!ELEMENT nb (#PCDATA) >

Name body
Indicates body of the name of a target.

Format:


  <nb>Body of the name of a target</nb>

Explanation:
If you want to explicitly indicate it's punctuation, it is able to describe following sub-element, rt.
Example of description:


  <name><nb>Kinkakuji temple</nb></name>

6.5.23. rt

<!ELEMENT rt (#PCDATA) >

Ruby Text
Indicates the punctuation for the name of a target.

Explanation:
The punctuation for the name of a target is described in text.
Example of description:


  <name style = "popular" ><nb></nb><rt>
</rt></name>


  <name style = "popular" ><nb>NRT</nb><rt>
Narita Airport</rt></name>

6.5.24. access

<!ELEMENT access (method,ipoint,tpoint,route?,note?) >

Access method
It consists of the moving means, introductory point, terminal point, guidance route, and explanation, and indicates a method by which to go to the location of a target. The explanation is indicated by the method designated in the element, note.

6.5.25. method

<!ELEMENT method (#PCDATA) >

Moving method
Indicates the moving method used from the introductory point to the terminal point.

Format:

  <method>
moving means</method>

Explanation:
The name of the moving means is described in the notation defined in Section 7.5 of Operational Specification.
Example of description:
<method>car</method>

6.5.26. ipoint

<!ELEMENT ipoint (iclass,pos,name?) >

Introductory Point
The introductory point is indicated by the class, location, and name of that introductory point. Its location and name are indicated by the methods designated in the elements, pos and name, respectively.

6.5.27. iclass

<!ELEMENT iclass (#PCDATA) >

Introductory Point Class
Indicates the class of the introductory point.

Format:

  <iclass>
introductory point class</iclass>

Explanation:
The name of the introductory point class is described in the notation defined in Section 7.8 of Operational Specification. Example of description:
<iclass>station</iclass>

6.5.28. tpoint

<!ELEMENT tpoint (tclass,pos,name?) >

Terminal Point
The terminal point is indicated by the class, location, and name of that destination point. Its location and name are indicated by the methods designated in the elements, pos and name, respectively.

6.5.29. tclass

<!ELEMENT tclass (#PCDATA) >

Terminal Point Class
Indicates the class of the terminal point.

Format:

  <tclass>
terminal point class</tclass>

Explanation:
The name of the terminal point class is described in the notation defined in Section 7.9 of Operational Specification. Example of description:
<tclass>entrance</tclass>

6.5.30. route

<!ELEMENT route (pol) >

Guidance route
The route from the introductory point to the terminal point is indicated by the subelement, pol.

6.5.31. pol

<!ELEMENT pol (pos*) >

Route coordinate point string (Polyline)
Indicates the string of route coordinate points. The coordinate point is indicated by the method designated in the element, pos.

Format:

  <pol>
route coordinate point string</pol>

Explanation:
  The position is described in accordance with the definition of the route coordinate point string in Section 6.2 "Terminology" hereof.
Example of description:
  <pol>
    <pos><lat>35.7700</lat><lon>139.8800</lon></pos>
    <pos><lat>35.8800</lat><lon>138.9900</lon></pos>
    <pos><lat>35.9900</lat><lon>139.0000</lon></pos>
  </pol>

6.5.32. contact

<!ELEMENT contact (#PCDATA) >
<!ATTLIST contact
          xml:lang     NMTOKEN #IMPLIED
          xml:link     NMTOKEN #FIXED "simple"
          href         CDATA #REQUIRED
>

Contact
Indicates the contact for a target. The contact is designated by a contact hyper reference. A supplementary note for the contact is indicated by a character string.

Attribute:
  xml:lang=NMTOKEN
  href=CDATA
Format:

  <contact xml:lang=
"language identifier" href=
"hyper reference">

  
note for contact</contact>

  <contact xml:lang=
"language identifier" href=
"hyper reference" />

Explanation:
  The note for the contact and hyper reference are described in the notation defined in Section 7.12.1 of Operational Specification. If you want to explicitly indicate the description language in the application, an RFC1766-compliant language identifier should be designated for the attribute, xml:lang.
Example of description:
  <contact href="tel:81-559-97-7814">This gallery</contact>
  <contact href="tel:81-559-97-7800">management office</contact>

6.5.33. mate

<!ELEMENT mate (#PCDATA) >
<!ATTLIST mate
        xml:lang NMTOKEN #IMPLIED
        xml:link NMTOKEN #FIXED "simple"
        href CDATA #REQUIRED
>

Relevant POIX
Indicates another POIX related to a target. It is designated by a relevant POIX hyper reference. A note for the relevance is indicated by a character string.

Attribute:
  xml:lang = NMTOKEN
  href = CDATA
Format:

  <mate xml:lang=
"language identifier" href=
"hyper reference">

  
note for relevance</mate>

Explanation:
The hyper reference for the relevant POIX is described in the notation defined in Section 7.12.2 of Operational Specification. If you want to explicitly indicate the description language in the application, an RFC1766-compliant language identifier should be designated for the attribute, xml:lang.
Example of description:
<mate href="http://server.toyota.co.jp/1.poi">annex</mate>

6.6. POIX file type

For using POIX via the Internet and the other data processing systems, POIX file extension and media type must be defined.

6.6.1. POIX file extension

POIX file extension is .poi or .poix.

6.6.2. POIX media type

Media Type of POIX file is follow.
application/x-poi

7. OPERATIONAL SPECIFICATION

7.1. Geodetic datum

The geodetic datum names described in the element, code, are presented below. In the present version, it is recommended to use WGS84.

Geodetic datum name	Notation	Example of description
WGS84	WGS84	`<code>wgs84</code>`
ITRF	itrf	`<code>itrf</code>`
Japanese geodetic datum	tokyo	`<code>tokyo</code>`

In the future, it is likely to be merged into the ITRF that is currently implemented as global standards; however, the coordinate system used at a country of interest should be added in combination, in consideration of the current situation at each country.

7.2. Angle Units

The angle units names described in the element, unit, are presented below. It is recommended to use the unit of degrees.

Angle units	Notation	Example of description
Units of degrees	degree	`<unit>degree</unit>`
Unit of degrees, minutes, and seconds	dms	`<unit>dms</unit>`

7.2.1. Unit of degrees

The latitude and longitude are represented in signed degrees. For the sign, "+" is assigned to the north latitude and east longitude, while "-" is assigned to the south latitude and west longitude. "+" may be omitted. For the number of digits, it is denoted to the accuracy for that numerical value.

Coordinates	Notation	Example of description
Latitude 35 degrees 30 minutes 00 seconds north	35.5000	`<lat>35.5000</lat>`
Longitude 135 degrees 45 minutes west	-135.75	`<lon>-135.75</lon>`

7.2.2. Unit of Degrees, Minutes, and Second

The latitude and longitude are represented in signed degrees, minutes, and seconds, each concatenated by ",". For the sign, "+" is assigned to the north latitude and east longitude, while "-" is assigned to the south latitude and west longitude. "+" may be omitted. For the number of digits, it is denoted to the accuracy for that numerical value.

Coordinates	Notation	Example of description
Latitude 35 degrees 30 minutes 00 seconds north	35,30,00	`<lat>35,30,00</lat>`
Longitude 135 degrees 45 minutes west	-135,45	`<lon>-135,45</lon>`

7.3. Altitude

The altitude is represented in meters. For the number of digits, it is denoted to the accuracy for that numerical value. If the altitude is higher than the reference of the geodetic datum used, it is assigned "+", while it is assigned "-" if it is lower. "+" may be omitted.

Altitude	Notation	Example of description
35.5m higher than reference	35.5	`<alt>35.5</alt>`
20m lower than reference	-20	`<alt>-20</alt>`

7.4. Horizontal and Vertical Errors

The horizontal and vertical errors are represented as an integer in meters. Neither decimals nor unit symbol should be described.

7.5. Moving Method

The moving method described in the element, method, is presented below.

Moving method	Notation	Example of description
Car	car	`<method>car</method>`
Motorcycle	motorcycle	`<method>motorcycle</method>`
Railway	railway	`<method>railway</method>`
onfoot	onfoot	`<method>onfoot</method>`
Bus	bus	`<method>bus</method>`
Airplane	airplane	`<method>airplane</method>`
Ship	ship	`<method>ship</method>`
Others	others	`<method>others</method>`

7.6 Moving Speed

The moving speed described in the element, speed, is represented in km/h, and indicated as a positive integer. Neither decimals nor unit symbol should be described.

7.7. Moving Direction

The moving direction described in the element, dir, is represented as a positive integer in degrees, counted clockwise from north as zero. Neither decimals nor unit symbol should be described.

7.8. Introductory Point Class

The introductory point classes described in the element, iclass, are presented below.

Introductory point class	Notation	Example of description
Crossing	crossing	`<iclass>crossing</iclass>`
Street	street	`<iclass>street</iclass>`
Station	station	`<iclass>station</iclass>`
Stop	stop	`<iclass>stop</iclass>`
Airport	airport	`<iclass>airport</iclass>`
Harbor	harbor	`<iclass>harbor</iclass>`
Others	others	`<iclass>others</iclass>`

7.9. Terminal Point Class

The terminal point classes described in the element, tclass, are presented below.

Terminal point class	Notation	Example of description
Parking lot	parking	`<tclass>parking</tclass>`
Entrance	entrance	`<tclass>entrance</tclass>`
Others	others	`<tclass>others</tclass>`

7.10. Route Coordinate Point String

The maximum number of points designated for the route coordinate point string shall be 10.

7.11. Locus Coordinate Point String

The maximum number of points designated for the locus coordinate point string shall be 10.

7.12. Contact

7.12.1 Contact Hyper Reference

The contact hyper reference described in the element, contact, is designated by a URI (Uniform Resource Identifier). "tel:" and "fax:" are in the phase of Internet Draft, and thus care should be exercised when using them.

http://
The URI for the contact is described in its absolute address.
Example of description:
<contact href="http://www.toyota.co.jp" />
tel:
The telephone number for the contact is described. The telephone number is designated by International Diaking Format. Letter that may be used, except numerals, shall be "#", ",", ".", "+","-", "(", and ")".
Example of description:
<contact href="tel:+81-559-97-7814" />
fax:
The facsimile number for the contact is described. The facsimile number is designated by International Diaking Format. Letter that may be used, except numerals, shall be "#", ",", ".", "+","-", "(", and ")".
Example of description:
<contact href="fax:+81-559-97-7878" />
mailto:
The e-mail address for the contact is described.
Example of description:
<contact href="mailto:kanemitu@fantasia.ml.toyota.co.jp" />

7.12.2 Note for Contact

The note for contact used in the element, contact, is employed when it is necessary to explicitly indicate multiple contacts, if any, of a target. For example, there may be cases, such as a public institution, where there are contacts for the facility itself and for the administrative office that is in charge of that facility, respectively. To indicate multiple contacts in such cases, simple words for identifying their respective contacts are used to give explanation about the contacts. If the same hyper reference is used many times, the note for contact should always be described.

Example of description:
<contact href="tel:81-559-97-7814">This gallery</contact>
<contact href="tel:81-559-97-7800">management office</contact>

7.13. Relevant POIX

7.13.1 Relevant POIX Hyper Reference

http://
The URI for the file that describes the relevant POIX is described in its absolute address.

Example of description:
<contact href="http://www.toyota.co.jp/012.poi">tokyo office</contact>

7.13.2 Note for Relevant

The note for relevance used in the element, mate, is employed when the target has another relevant facility and its information needs to be indicated explicitly. For example, when a POIX that describes the annex is pointed from a POIX that describes the main building of a department store, a explanation for relevance should be given by use of a simple word to identify what is represented by that POIX. If the element, mate, is described, the note for relevance should always be described as well.

Example of description:
<mate href="http://www.toyota.co.jp/01.poi">annex</mate>

8. EXAMPLES OF DESCRIPTIONS

8.1. Example of Simple Description for Notifying the Location

<?xml version="1.0" encoding="Shift_JIS" ?>
<!DOCTYPE poix PUBLIC "-//MOSTEC//POIX V2.0//EN" "poix.dtd">
<poix version="2.0">
<format>
<datum>wgs84</datum>
<unit>degree</unit>
</format>
<poi>
<point>
<pos>
<lat>35.7611</lat>
<lon>139.7700</lon>
</pos>
</point>
<name><nb>Tokyo Station</nb></name>
</poi>
</poix>

8.2. Example of Description with Access Method Appended

<?xml version="1.0" encoding="Shift_JIS" ?>
<!DOCTYPE poix PUBLIC "-//MOSTEC//POIX V2.0//EN" "poix.dtd">
<poix version="2.0">
<format>
<datum>wgs84</datum>
<unit>degree</unit>
</format>
<poi>
<point>
<pos>
<lat>35.6680</lat>
<lon>139.76887</lon>
</pos>
</point>
<name><nb>MItsukoshi Ginza Store</nb></name>
<access>
<method>onfoot</method>
<ipoint>
<iclass>station</iclass>
<pos>
<lat>35.66805</lat>
<lon>139.76833</lon>
</pos>
<name><nb>Ginza station of Ginza subway line</nb></name>
</ipoint>
<tpoint>
<tclass>entrance</tclass>
<pos>
<lat>35.667778</lat>
<lon>139.7686</lon>
</pos>
<name><nb>Subway entrance</nb></name>
</tpoint>
<note>
You may enter the store from entrance A7 of Ginza station of Ginza subway line.
</note>
</access>
<contact href="tel:81-3-3562-1111" />
<note>Not closed on Monday</note>
<mate href="http://www.toyota.co.jp/0223.poi">Annex</mate>
</poi>
</poix>

8.3. Example of Description for Location-related information on Mobile Entity

<?xml version="1.0" encoding="Shift_JIS" ?>
<!DOCTYPE poix PUBLIC "-//MOSTEC//POIX V2.0//EN" "poix.dtd">
<poix version="2.0">
<format>
<datum>wgs84</datum>
<unit>dms</unit>
</format>
<poi>
<point>
<pos>
<lat>35,41,28.7</lat>
<lon>139,45,02.4</lon>
<herror>30</herror>
</pos>
</point>
<move>
<method>car</method>
<speed>30</speed>
<dir>45</dir>
<locus>
<pos><lat>35,41,29.3</lat><lon>139,45,04.3</lon></pos>
<pos><lat>35,41,30.1</lat><lon>139,45,07.4</lon></pos>
<pos><lat>35,41,30.6</lat><lon>139,45,09.0</lon></pos>
</locus>
</move>
</poi>
</poix>

9. APPENDIX

9.1. MOSTEC Members

This document summarizes the results of studies conducted by the following members of the MOSTEC.

Hiroyuki Kanemitsu TOYOTA MOTOR CORPORATION

Makoto Adachi SHARP CORPORATION

Takahiro Kobayashi SEIKO EPSON CORPORATION

Masahito Koike Access Co.,Ltd.

Shingo Shiratori Access Co.,Ltd.

Yoshiyuki Nezu Sony Corporation

Masayuki Ono ZENRIN CO.,LTD.

Masanori Hosoya TOPPAN PRINTING CO.,LTD.

Kazuhide Kobayashi ALPS Mapping Co.,Ltd.

Shuzo Fukuzumi COMPASSLINK CORPORATION

Takashi Takenaga INCREMENT P CORPORATION

Yasuhiro Mizukoshi NEC Corporation

Yukio Aso Xanavi Informatics Corporation

Tatsuya Mitsugi MITSUBISHI ELECTRIC CORPORATION

Yoshihiro Iwasaki Aplix Corporation

Koji Koga PIONEER ELECTRONIC CORPORATION

Kenji Ohishi NISSAN MOTOR CO., LTD.

Shigeki Ibara Daihatsu Motor Co.,Ltd.

Hiroshi Ohmura Mazda Motor Corporation

Motoki Hirano Microsoft Product Development Ltd.

10. References

Extensible Markup Language(XML)1.0 W3C Recommendation
Dave Raggett , Arnaud Le Hors , Ian Jacobs
http://www.w3.org/TR/1998/REC-xml-19980210
XML Linking Language (XLink) W3C Working Draft
Dave Raggett , Arnaud Le Hors , Ian Jacobs
http://www.w3.org/TR/1998/WD-xlink-19980303
HTML 4.0 Specification
Dave Raggett , Arnaud Le Hors , Ian Jacobs
http://www.w3.org/TR/REC-html40
RFC1123 Requirements for Internet Hosts -- Application and Support
R. Braden
October 1989
RFC2368 The mailto URL scheme * Updates: RFC1738, RFC1808
P. Hoffman , L. Masinter , J. Zawinski
July 1998
RFC2396 Uniform Resource Identifiers (URI): Generic Syntax
T. Berners-Lee , R. Fielding , L. Masinter
August 1998
RFC1766 Tags for the Identification of Languages
H. Alvestrand
March 1995
INTERNET-DRAFT URLs for Telephone Calls
<draft-antti-telephony-url-08.txt>
http://www.ietf.org/internet-drafts/draft-antti-telephony-url-08.txt
INTERNET-DRAFT Date and Time on the Internet
<draft-newman-datetime-02.txt>
http://www.ietf.org/internet-drafts/draft-newman-datetime-02.txt
RUBY W3C Working Draft
Marcin Sawicki
http://www.w3.org/TR/1999/WD-ruby-19990322
DoD World Geodetic System 1984 - Its Definitions and Relationships with local Geodetic Systems-TR8350.2
ftp://ftp.nima.mil/pub/gg/tr8350.2/wgs84rpt.pdf
ITRF97
INTERNATIONAL EARTH ROTATION SERVICE (IERS)
http://lareg.ensg.ign.fr/ITRF/ITRF97/

POIX version	Document Revision	Changes	Date
version 1.0	1	First release	4.1.1999
version 1.1	1	Change of element name: "code"to"datum"	5.17.1999
version 2.0	1	change of definition sub-element of "name"	6.14.1999

XML	Extensible Markup Language
POI	Point Of Interest
RFC	Request For Comments
URL	Uniform Resource Locator
DTD	Document Type Definition
UTC	Coordinated Universal Time
WGS84	World Geodetic System 1984
ITRF	International Terrestrial Reference Frame

Hiroyuki Kanemitsu	TOYOTA MOTOR CORPORATION
Makoto Adachi	SHARP CORPORATION
Takahiro Kobayashi	SEIKO EPSON CORPORATION
Masahito Koike	Access Co.,Ltd.
Shingo Shiratori	Access Co.,Ltd.
Yoshiyuki Nezu	Sony Corporation
Masayuki Ono	ZENRIN CO.,LTD.
Masanori Hosoya	TOPPAN PRINTING CO.,LTD.
Kazuhide Kobayashi	ALPS Mapping Co.,Ltd.
Shuzo Fukuzumi	COMPASSLINK CORPORATION
Takashi Takenaga	INCREMENT P CORPORATION
Yasuhiro Mizukoshi	NEC Corporation
Yukio Aso	Xanavi Informatics Corporation
Tatsuya Mitsugi	MITSUBISHI ELECTRIC CORPORATION
Yoshihiro Iwasaki	Aplix Corporation
Koji Koga	PIONEER ELECTRONIC CORPORATION
Kenji Ohishi	NISSAN MOTOR CO., LTD.
Shigeki Ibara	Daihatsu Motor Co.,Ltd.
Hiroshi Ohmura	Mazda Motor Corporation
Motoki Hirano	Microsoft Product Development Ltd.

POIX: Point Of Interest eXchange Language Specification

W3C Note - 24 June 1999

Contents