Document ID: chunk:federal_register_of_legislation:F2024L01443:schedule:3:p9
Version: federal_register_of_legislation:F2024L01443
Segment Type: schedule
Provision Reference: sch 3 (pt 9/21)
Character Range: 269563–273092

joining character SHOULD be a space.
family_name            RequiredNameString   MUST NOT be an empty string.
given_name             NameString           MAY be excluded from attribute responses when value is an empty string.
middle_name            NameString           MAY be excluded from attribute responses when value is an empty string.
birthdate              Date                 SHOULD be validated to ensure dates that satisfying the RFC 3339 format and are reasonable.
updated_at             Unix Timestamp       MUST be derived from the most recently updated Core Attribute.
tdif_core_updated_at   Unix Timestamp       IXPs MUST NOT broker this claim to PRPs.

                                            ISPs MUST supply this claim.

4.3.2      Validated Contact Details

 As outlined in section 2.1.2 of this Schedule the Validated Contact attributes cover the individual's validated email and phone. The data types applied to the claims in the attribute response MUST conform to the values outlined in Table 46 above.

 All claims MUST be returned when fulfilling the email and phone scopes.

 An ISP MUST not fulfill this request if the related email or phone number have not been validated.

 Table 54 Requirements for Validated Email claims

Claim                   AGDIS           Required for scope  Constraints
                        data type
email                   Email           Y
email_verified          Boolean         Y                   If the email has not been successfully validated the scope for these claims should not be fulfilled.
tdif_email_updated_at   Unix Timestamp  Y

 Table 55 Requirements for Validated Phone Number claims

Claim                          AGDIS            Required for scope   Constraints
                               data type
phone                          Phone Number     Y
phone_verified                 Boolean          Y                    If the phone number has not been validated successfully the scope for these claims should not be fulfilled.
tdif_phone_number_updated_at   Unix Timestamp   Y

4.3.3      Verified Other Names

 The Verified Other Names scope and claim uses the Other Names object for each of the verified other names returned in an attribute request.

 An ISP fulfilling this request MAY return a single Other Name object or a JSON array containing the single value when only one Verified Other Name set is available.

 An ISP fulfilling this request MUST return a JSON array of Other Name object when two or more Other Verified Names are available.

 Table 56 Requirements for Verified Other Names claims

Claim                         AGDIS                                                    Required for scope   Constraints
                              data type
tdif_other_names               Other Names Object or an Array of Other Names Objects   Y                    Returning a single OtherNameObject is only permitted when a single other name has been verified.
tdif_other_names_updated_at   Unix Timestamp                                           Y                    -

4.3.4      Verified Documents

 A Verified Document MUST be represented as a JSON Object with a structure conformant to the schema outlined in Table 10 above with the literal field names and data types outlined in Table 58 below.

 The responses to an attribute request for a single verified document MAY be serialised as a single Verified Document Object or as wrapped in a JSON Array.

 An attribute response for multiple verified documents MUST