This proposal makes provisions for mirroring enclosure data on several servers, which can possibly be located in different geographical regions. This would allow one to distribute traffic among them and optmize download performance by choosing a server located near the client.
The ``location'' attribute could be used to specify spatial location (a
place name or geographic co-ordinates) of a server providing enclosure
data. This specification does not impose format of this attribute.
However it is recommended to use some well-known format or name from
common vocabulary. In RSS 2.0 the value must be a single string. In RSS 1.0
``location'' property could belong to any well-known RDF class
representing spatial information. Examples of usable formats are:
| Format | Compatible RSS versions |
| WGS 84 Geographic Point URI Space | 1.0 and 2.0 |
| Getty Thesaurus of Geographic Names | 1.0 and 2.0 |
| ``address:'' URI Scheme | 1.0 and 2.0 |
| An RDF Geo vocabulary | 1.0 |
| RDFMap | 1.0 |
| DCMI Point Encoding Scheme | 1.0 and 2.0 |
In the future, we hope that some of these (or other) formats will emerge as de-facto standards for specifying spatial information in RSS feeds.
The ``location'' property is optional. If not specified, the client should chose any listed download location randomly.