> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-objects/do.com.03-address.md).

# DO.COM.03 Address

The spdci:Address object represents an Address.

### DO.COM.03 Address

An address is a structured entity that represents the details and components of an address.

<table><thead><tr><th width="183">Property Key</th><th width="238">Data Type (and Restrictions)</th><th width="118">Cardinality</th><th>Description</th></tr></thead><tbody><tr><td>address_line_1</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>First line of a mailing address (Person-agnostic)</td></tr><tr><td>address_line_2</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>Second line of a mailing address (Person-agnostic)</td></tr><tr><td>locality</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>City or locality component.</td></tr><tr><td>sub_region_code</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>District or sub-regional code</td></tr><tr><td>region_code</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>State, province, prefecture, or region component</td></tr><tr><td>postal_code</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>Zip code or postal code component</td></tr><tr><td>country_code</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>Country part of an address </td></tr><tr><td>geo_location</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-objects/do.com.04-geolocation.md">DO.COM.04 GeoLocation</a></td><td>0...1</td><td>Location information </td></tr></tbody></table>

### Example&#x20;

```json
{
  "@context": {
    "spdci": "https://schema.spdci.org/core/v1/data",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "code": "https://schema.spdci.org/core/v1/code"
  },
  "@id": "spdci:Address_1",
  "@type": "spdci:Address",
  "address_line1": "Bophut Koh Samui",
  "address_line2": "Surat, Near Big Buddha Beach",
  "locality": "Thani",
  "sub_region_code": "SH",
  "region_code": "A205",
  "postal_code": "84320",
  "country_code": "TH",
  "geo_location": {
    "@id": "spdci:GeoLocation_1",
    "@type": "spdci:GeoLocation",
    "latitude": 33.3128,
    "longitude": 44.3615,
    "altitude": 1000.0123,
    "plus_code": " "
      }
}
```

In this example, the spdci:Address describe an instance of an address location&#x20;

### JSON-LD File on GitHub

{% embed url="<https://schema.spdci.org/core/v1/data/Address.jsonld>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://standards.spdci.org/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-objects/do.com.03-address.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.