- From: Colby Russell <w3-public-webhistory@x.colbyrussell.com>
- Date: Sun, 25 Jan 2026 15:08:36 -0600
- To: Dan Connolly <dckc@madmode.com>, public-webhistory@w3.org
See full text below; also available from: - <https://web.archive.org/web/20000902025047/http://www.lists.ic.ac.uk/hypermail/xml-dev/xml-dev-Jul-1999/0464.html> - <https://web.archive.org/web/20220810133646/http://mailman.ic.ac.uk/pipermail/xml-dev/1999-July/013723.html> On 6/7/04 17:14, david at megginson.com (David Megginson) wrote: > I have placed a medium-sized RDF sample online at the following > location: > > http://www.megginson.com/samples/rdf/airports.rdf > > This document is 811,388 bytes long, and contains entries for 2,963 > international airports. These are taken from > (not-entirely-consistently-formatted) text file available at > > http://www.primenet.com/~rfwatts/uteworld/airports.txt > > and the information is sometimes pretty spotty. Soon, I'd like to add > RDF versions of a few METAR (surface weather observation) files > pointing into this one, so that people can experiment with relations > among multiple RDF documents. > > > Samples > ------- > > Here are sample records for the four airports I'll happen to be flying > through next week: > > <apt:Airport rdf:about="http://www.megginson.com/exp/id/airports/CYOW"> > <apt:icao>CYOW</apt:icao> > <apt:name>Ottawa Int'L. Ont., Canada </apt:name> > <apt:iata>YOW</apt:iata> > <apt:latitude>45-19N</apt:latitude> > <apt:longitude>075-40W</apt:longitude> > <apt:elevation>114M</apt:elevation> > </apt:Airport> > > <apt:Airport rdf:about="http://www.megginson.com/exp/id/airports/KLGA"> > <apt:icao>KLGA</apt:icao> > <apt:name>New York, La Guardia Airport, NY, United States </apt:name> > <apt:iata>LGA</apt:iata> > <apt:latitude>40-46-45N</apt:latitude> > <apt:longitude>073-52-48W</apt:longitude> > <apt:elevation>11M</apt:elevation> > </apt:Airport> > > <apt:Airport rdf:about="http://www.megginson.com/exp/id/airports/KORD"> > <apt:icao>KORD</apt:icao> > <apt:name>Chicago, Chicago-O'Hare International Airport, IL, United States </apt:name> > <apt:iata>ORD</apt:iata> > <apt:latitude>41-59-00N</apt:latitude> > <apt:longitude>087-55-00W</apt:longitude> > <apt:elevation>200M</apt:elevation> > </apt:Airport> > > <apt:Airport rdf:about="http://www.megginson.com/exp/id/airports/KSFO"> > <apt:icao>KSFO</apt:icao> > <apt:name>San Francisco, San Francisco International Airport, CA, United States </apt:name> > <apt:iata>SFO</apt:iata> > <apt:latitude>37-37-11N</apt:latitude> > <apt:longitude>122-21-53W</apt:longitude> > <apt:elevation>26M</apt:elevation> > </apt:Airport> > > > RDF/Namespace Information > ------------------------- > > This document uses an experimental Namespace with the following URI: > > http://www.megginson.com/exp/ns/airports# > > This namespace contains one RDF class, "Airport", and five RDF > properties, all of which are literals: > > icao > The four-letter ICAO code for the airport, such as "KLAX". > > name > The name and location of the airport. > > iata > The three-letter IATA code for the airport, such as "LAX", if known. > > latitude > The approximate latitude of the airport, if known. > > longitude > The approximate longitude of the airport, if known. > > elevation > The approximate elevation of the airport, if known. > > > Future Plans > ------------ > > In real life, the last three properties would probably be specified > separately for each runway. Perhaps some day I'll make this more > interesting, and add ATIS frequencies, better lat/lon information, ILS > approach information, etc. > > > All the best, > > > David >
Received on Wednesday, 4 February 2026 23:26:31 UTC