LogoLogo
WebsiteGitHubSlack
Social Registry v1.0.0
Social Registry v1.0.0
  • Social Registry and SP-MIS Interface
    • Introduction
    • Assumptions
    • Exception Handling
    • Social Registry with SP-MIS Standards
      • Process
        • PRS.SR.01: SP-MIS queries the social registry to verify eligibility for programme enrolment
          • Example 1: Unconditional Household Cash Transfer Scheme
          • Example 2: Widow Cash Transfer Scheme
          • Example 3: Conditional Girl’s Education Cash Transfer Scheme
          • Example 4: Conditional Child Benefit Cash Transfer Scheme
        • PRS.SR.02: SP-MIS updates attributes for a batch of beneficiaries in the social registry
          • Example 1: Conditional Girl’s Education Cash Transfer Scheme
        • PRS.SR.03: Social registry updates attributes for a batch of beneficiaries in SP-MIS
          • Example 1 : Conditional Child Benefit Cash Transfer Scheme
        • PRS.SR.04: Social registry updates attributes for a batch of beneficiaries in the IBR
      • Data
        • Data Objects
          • DO.SR.01 Person
          • DO.SR.02 Group
          • DO.SR.03 Member
          • DO.SR.04 RelatedPerson
          • DO.SR.05 DisabilityInfo
        • Code Directory
          • CD.COM.01 identifier_type
          • CD.COM.02 marital_status
          • CD.COM.03 sex
          • CD.COM.07: relationship_type
          • CD.COM.10: disability_type
          • CD.COM.11: functional_limitation_type
          • CD.COM.12: functional_severity
          • CD.COM.17: education_level
          • CD.SR.02 employment_status
          • CD.SR.03 income_level
          • CD.SR.04 occupation
        • Data Types and Formats
          • DF.COM.STRING.01 date_time
          • DF.COM.STRING.02 phone_number
          • DF.COM.STRING.07 email
          • DT.COM.03 integer
          • DT.COM.02 string
          • DT.COM.04 decimal
          • DT.COM.05 array
          • Copy of DT.COM.05 array
          • DT.COM.06 boolean
      • API
        • Design Principles
        • Versioning
        • Methods
          • API.COM.01 ASY Search (Async approach)
          • API.COM.01 SYN Search (Sync approach)
          • API.COM.02 Event Subscription
          • API.COM.03 Event Notification
          • API.COM.04 ASY Status (Async approach)
          • API.COM.04 SYN Status (Sync approach)
    • Previous Versions
  • Resources
    • Interoperability in Action #6
    • Standards Committee & Acknowledgments
Powered by GitBook
On this page
  • DO.SR.01 Person
  • Example of JSON Data for the Person Data Object
  • JSON-LD File on GitHub

Was this helpful?

  1. Social Registry and SP-MIS Interface
  2. Social Registry with SP-MIS Standards
  3. Data
  4. Data Objects

DO.SR.01 Person

DO.SR.01 Person

This data object contains specific information that can be used to identify an individual.

The data object may include information received from other registries, including CRVS and disability registries. It may be queried by the SP-MIS to determine an applicant's eligibility.

Attribute
Type
Cardinality
Description

identifier

0...*

Unique identifier for a person

name

0...1

Full name in a displayable form, possibly including titles and suffixes, in the order of the applicant's locale norms and/or preferences

sex

0...1

Sex of the person, represented as an enumeration (male, female, others, unknown)

birth_date

0...1

Date of birth of the person, formatted according to schema:DateTime.

death_date

0...1

Date of death of the person, if applicable, formatted according to schema:DateTime

address

0...*

Current residential address of the person, represented as an address object

phone_number

0...*

Person's preferred phone number, format E.164 is recommended

email

0...*

Person's preferred email address, format must comply with RFC 5322 addr-spec

registration_date

DF.COM.STRING.01 date_time

0...1

Date the details of the person were registered

last_updated

DF.COM.STRING.01 date_time

0...1

Date the details of the person were last updated

Example of JSON Data for the Person Data Object

{
  "@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/sr_person/847951632",
  "@type": "spdci:SR_Person",
  "identifier": [
    {
      "@type": "Identifier",
      "identifier_type": "UIN",
      "identifier_value": "847951632"
    }
  ],
  "name": {
      "@type": "Name",
      "surname": "Phumchai",
      "given_name": "Sudarat",
      "prefix": "Dr.",
      "suffix": "PhD"
    },
  "birth_date": "1995-09-21T11:20:00",
  "sex": "female",
  "address": [
    {
      "@type": "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",
    }],
  "phone_number": ["+66891234567"],
  "email": ["sudarat.phumchai@example.com"],
  "registration_date": "1995-10-21T11:20:00"
}

JSON-LD File on GitHub

Last updated 1 month ago

Was this helpful?

DO.COM.01 Identifier
DO.COM.02 Name
CD.COM.03 sex
DF.COM.STRING.01 date_time
DF.COM.STRING.01 date_time
DO.COM.03 Address
DF.COM.STRING.02 phone_number
DF.COM.STRING.07 email
https://github.com/spdci/schemas/blob/main/extensions/social/v1/SRPerson.jsonld
{
  "@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": "spdci:SR_Person",
  "@type": "rdfs:Class",
  "rdfs:comment": "This data object contains the information on people and households held in the social registry.",
  "rdfs:label": "SR Person",
  "rdfs:subClassOf": [
    {
      "@type": "rdfs:Class",
      "rdfs:label": "Structured Entity"
    }
  ],
  "rdfs:property": [
    {
      "@id": "spdci:identifier",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": {
           "@id": "common:Identifier",
           "@type": "rdfs:Class",
           "@container": "@list"
      },
      "rdfs:comment": "The person's identification number."
    },
    {
      "@id": "spdci:name",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": {
           "@id": "common:Name",
           "@type": "rdfs:Class"
      },
      "rdfs:comment": "Full name in a displayable form, possibly including titles and suffixes, in the order of the applicant's locale norms and/or preferences."
    },
    {
      "@id": "spdci:sex",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": "common:SexCategoryEnum",
      "rdfs:comment": "Sex of the applicant, represented as an enumeration ."
    },
    {
      "@id": "spdci:birth_date",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": "common:DateTime",
      "rdfs:comment": "The date of birth of the applicant, formatted according to schema:DateTime."
    },
    {
      "@id": "spdci:death_date",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": "common:DateTime",
      "rdfs:comment": "The date of birth of the applicant, formatted according to schema:DateTime."
    },
    {
      "@id": "spdci:address",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": {
           "@id": "common:Address",
           "@type": "rdfs:Class",
           "@container":"@list"
      },
      "rdfs:comment": "Current residential address of the applicant, represented as an address object."
    },
    {
      "@id": "spdci:phone_number",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": {
        "@type":  "xsd:string",
        "@container":"@list"
      },
      "rdfs:comment": "Person's preferred phone number. The format E.164 is recommended."
    },
    {
      "@id": "spdci:email",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": {
        "@type":  "xsd:string",
        "@container":"@list"
      },
      "rdfs:comment": "Person's preferred email address. The format must comply with RFC 5322 addr-spec."
    },
    {
      "@id": "spdci:registration_date",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": "common:DateTime",
      "rdfs:comment": "The date of registration of the applicant, formatted according to schema:DateTime."
    },
    {
      "@id": "spdci:last_updated",
      "@type": "rdfs:Datatype",
      "rdfs:domain": "spdci:SR_Person",
      "rdfs:range": "common:DateTime",
      "rdfs:comment": "The date when person details got updated , formatted according to schema:DateTime."
    }
  ]
}