> 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/dci-standards/wip-social-registry-v1.0.0/social-registry/1.-crvs/data/data-objects/do.sr.02-member.md).

# DO.SR.02 Member

### DO.SR.02 Member

A member is an individual who belongs to a specific group or unit, such as a family or household. This data object describes the individual's attributes.

<table><thead><tr><th width="175.6800537109375">Attribute</th><th width="166.21893310546875" data-type="content-ref">Type</th><th width="125.1802978515625">Cardinality</th><th>Description</th></tr></thead><tbody><tr><td>member_identifier</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-objects/do.com.01-identifier.md">DO.COM.01 Identifier</a></td><td>0...*</td><td>Unique identifier assigned to each individual</td></tr><tr><td>demographic_info</td><td><a href="/standards/dci-standards/wip-social-registry-v1.0.0/social-registry/1.-crvs/data/data-objects/do.sr.01-person.md">DO.SR.01 Person</a></td><td>0...1</td><td>Personal details of the individual</td></tr><tr><td>related_person</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-objects/do.com.11-relatedperson.md">DO.COM.11 RelatedPerson</a></td><td>0...*</td><td>Persons related to the individual and their relationship type</td></tr><tr><td>self_id_disability</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.06-boolean.md">DT.COM.06 boolean</a></td><td>0...1</td><td>Self identification as person with disablities yes(1) or no(0)</td></tr><tr><td>disability_info</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-objects/do.com.12-disabilityinfo.md">DO.COM.12 DisabilityInfo</a></td><td>0...*</td><td>Additional attributes for people with disabilities</td></tr><tr><td>marital_status</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/code-directory/cd.com.02-marital_status.md">CD.COM.02 marital_status</a></td><td>0...1</td><td>Marital status of the individual</td></tr><tr><td>employment_status</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/code-directory/cd.com.16-employment_status.md">CD.COM.16 employment_status</a></td><td>0...1</td><td>Employment status of the individual</td></tr><tr><td>occupation</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/code-directory/cd.com.18-occupation.md">CD.COM.18 occupation</a></td><td>0...1</td><td>Occupation of the individual</td></tr><tr><td>income_level</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/code-directory/cd.com.17-income_level.md">CD.COM.17 income_level</a></td><td>0...1</td><td>Income level of the individual</td></tr><tr><td>language_code</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/code-directory/cd.com.14-language_code.md">CD.COM.14: language_code</a></td><td>0...*</td><td>Languages spoken by the individual</td></tr><tr><td>education_level</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/code-directory/cd.com.15-education_level.md">CD.COM.15: education_level</a></td><td>0...1</td><td>Individual's education level</td></tr><tr><td>additional_attributes</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.05-array.md">DT.COM.05 array</a></td><td>0...1</td><td>Additional characteristics of the individual</td></tr><tr><td>registration_date</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string/data-formats/df.com.string.01-date_time.md">DF.COM.STRING.01 date_time</a></td><td>0...1</td><td>Date the household individual was registered</td></tr><tr><td>last_updated</td><td><a href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string/data-formats/df.com.string.01-date_time.md">DF.COM.STRING.01 date_time</a></td><td>0...1</td><td>Date the individual's details were last updated</td></tr></tbody></table>

## **Example of JSON Data for the Member Data Object**

```json
{
  "@context": {
    "spdci": "https://schema.spdci.org/extensions/social/v1/",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "owl": "http://www.w3.org/2002/07/owl#",
    "common": "https://schema.spdci.org/common/v1/"
  },
  "@id": "https://example.org/member/987654321",
  "@type": "spdci:Member",
  "member_identifier": [{
      "@type": "Identifier",
      "identifier_type": "UIN",
      "identifier_value": "42343545654"
    } ],
  "demographic_info": {
    "@type": "SRPerson",
    "identifier": [ {
      "@type": "Identifier",
      "identifier_type": "NationalID",
      "identifier_value": "9876543210"
    } ],
    "name":{
      "@type": "Name",
      "surname": "Smith",
      "given_name": "Alice",
      "prefix": "Ms.",
      "suffix": ""
    },
    "sex": "female",
    "birth_date": "1985-05-20"
  },
  "related_person": [
    {
      "@type": "RelatedPerson",
      "relationship_type": "spouse",
      "related_member": {
        "@type": "Member",
        "@id": "https://example.org/member/123456789",
        "member_identifier": "M123456789"
      }
    },
    {
      "@type": "RelatedPerson",
      "relationship_type": "child",
      "related_member": {
        "@type": "Member",
        "@id": "https://example.org/member/987654322",
        "spdci:member_identifier": "M987654322"
      }
    }
  ],
  "is_disabled": false,
  "marital_status": "married",
  "employment_status": "employed",
  "occupation": "teacher",
  "income_level": "middle",
  "language_code": ["en", "es"],
  "education_level": "bachelor",
  "additional_attributes": ["extra_work": "volunteer"],
  "registration_date": "2022-01-10T08:00:00Z",
  "last_updated": "2023-06-15T10:00:00Z"
}

```

### JSON-LD File on GitHub

{% @github-files/github-code-block url="<https://github.com/spdci/schemas/blob/main/extensions/social/v1/Member.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/dci-standards/wip-social-registry-v1.0.0/social-registry/1.-crvs/data/data-objects/do.sr.02-member.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.