# DO.COM.02 Name

### DO.COM.02 Name

This class is crucial for accurately representing and storing an individual's name in a structured and machine-readable format.

### Example

```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#",
        "owl": "http://www.w3.org/2002/07/owl#"
    },
    "@id": "spdci:Name_1",
    "@type": "spdci:Name",
    "surname": "Al-Maliki",
    "given_name": "Nouri",
    "second_name": "Kamil",
    "prefix": "Dr.",
    "suffix": "PhD"
}
```

In this example, the `spdci:Name` instance describes the full name of an individual, breaking down the name into its constituent parts: surname, given name, second name, prefix, and suffix. The structured format allows for precise representation and retrieval of name information, which is critical for identification and personal data management in various applications.

### JSON-LD File on GitHub

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


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://standards.spdci.org/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-objects/do.com.02-name.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.