§ 2.1 Common Schema Elements

Many additional schema items are reusable throughout the schema, such as the various address forms found throughout different tables.

§ 2.1.1 PostalAddress

‌The address to which physical mail and packages are delivered.

‌§ 2.1.2 SocialAddresses

‌The various Internet locations that help disambiguate a person, group, or organization, such as their FaceBook, LinkedIn, YouTube, and Twitter Address. As each of these addresses are in Internet Message format, they must be entered in lowercase following the manual of style set HERE.

§ 2.1.3 PhoneNumbers

A collection of phone numbers. All telephone number fields will follow international ITU-T E.164 international phone number formatting of [+] [country code] [area code] [local phone number]. The styles for phone numbers are found HERE.

§ 2.1.4 NonStandardNames

Additional legal names used by an item.

§ 2.1.5 HierarchicalMetaData

MetaData about a JSON Type's hierarchical information. If the record is in a non-hierarchical array this will be nulled.

§ 2.1.6 local_reference_id

This individual value is found in every record that can be changed. It was created for the sole purpose of contributors being able to track POST calls when creating new records with contents found in subtables within their database that become arrays within the JSON structure.

§ 2.1.7 Emails

The only difference between email and Emails is that Emails is a list of email.

§ 2.1.8 AuditData

AuditData is a key element in managing federated information. In short, the two main objects within AuditData are current_object and previous_object which store exactly what they say – a snapshot of the current state of the record and the previous state of the record.

Last updated