Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated.

Unique code or number identifying the location to its users.

Organization label locations in registries, need to keep track of those.

Name of the location as used by humans. Does not need to be unique.

Description of the Location, which helps in finding or referencing the place.

Humans need additional information to verify a correct location has been identified.

Indicates the type of function performed at the location.

The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites.

Physical location.

If locations can be visited, we need to keep track of their address.

This was kept as 0..1 as there is no use property on the address, so wouldn't be able to identify different address types.

Physical form of the location, e.g. building, room, vehicle, road.

For purposes of showing relevant locations in queries, we need to categorize locations.

The absolute geographic location of the Location, expressed in a KML compatible manner (see notes below for KML).

For mobile applications and automated route-finding knowing the exact location of the Location is required.

Longitude. The value domain and the interpretation are the same as for the text of the longitude element in KML (see notes below).

Latitude. The value domain and the interpretation are the same as for the text of the latitude element in KML (see notes below).

Altitude. The value domain and the interpretation are the same as for the text of the altitude element in KML (see notes below).

The organization that is responsible for the provisioning and upkeep of the location.

Need to know who manages the location.

active | suspended | inactive.

Another Location which this Location is physically part of.

For purposes of location, display and identification, knowing which locations are located within other locations is important.

Indicates whether a resource instance represents a specific location or a class of locations.

When using a Location resource for scheduling or orders, we need to be able to refer to a class of Locations instead of a specific Location.