A record about a missing or found person. Unique identifier for the record, which consists of a domain name followed by a slash and a local identifier. Each application is assumed to reside at or belong to a particular domain. When the person_record_id begins with the application's own domain, it means this application is the authority for this record, and the format of the local identifier is up to the application. When the person_record_id begins with some other domain, it means this record is a mirror of a record from another source, and the other domain is the authority for this record. (string in the form "yyyy-mm-ddThh:mm:ssZ"): Date that this record was created in the local application, in UTC. The application must guarantee that this value increases monotonically so that a client can update a copy of a database by querying for all records with an entry_date greater than the entry_date of the last received record. The full name of the person who entered this record. The preferred contact e-mail address of the person who entered this record. The preferred contact phone number of the person who entered this record. If this data record is a mirror of a record from an external source, this field is present and contains the name of that external source. If this data record is a mirror of a record from an external source, this field is present and contains the date in UTC that this record was originally posted to that source location. If this data record is a mirror of a record from an external source, this field is present and contains the URL to that source record (as specific as possible, down to the URL of the individual record). (string, all capitals, no accents): First name of the person sought or found, optionally followed by a space and any middle names or middle initials. (string, all capitals, no accents): Last name of the person sought or found. (string, city name, all capitals, no accents): Home city of the person sought or found. (string, two-letter postal abbreviation): Home state of the person sought or found. (string, all capitals, no accents): Name of the home neighborhood of the person sought or found. (string, all capitals, no accents): Street name (no number) of the home address of the person sought or found. Zip code of the home address of the person sought or found. URL to an image of an identifying photograph of the person sought or found. Free-form text containing any other static data fields brought in from other sources. (Non-static data imported from other sources should go into a note record.) Short fields should be on a single line with the field name, a colon, and the field value. Long fields can be given as a line with the field name and a colon, then text indented on the following lines. Field names for data imported from other applications should begin with the domain name and a slash. For example, if a birthdate is imported from an ICRC record, it might look like this: icrc.org/birthdate: 1976-02-26 A description of the person in free-form text can also go here, with the field name "description". For example: description: Dark hair, in her late thirties. Also goes by the names "Kate" or "Katie". A timestamped note about a particular missing or found person. Unique identifier for the record, which consists of the application's domain name followed by a slash and a local identifier. For notes entered locally, the format of the local identifier is up to the application. For notes imported from external sources, the application should preserve the value of this field. (string in the form "yyyy-mm-ddThh:mm:ssZ"): Date that this note was added. The full name of the person who entered this note. The preferred contact e-mail address of the person who entered this note. The preferred contact phone number of the person who entered this note. This value is true if the missing person has been personally contacted or seen, false otherwise. The text field of this note MUST describe HOW and WHEN the person was contacted or seen. The preferred contact e-mail address of the FOUND person. This field is present ONLY if the person has been FOUND. The text field of this note MUST describe HOW the person's contact information was determined. The missing (but now found) person's preferred contact phone number. This field is present ONLY if the person has been FOUND. Any application that sets or changes this value MUST add a note to the notes field with a description of HOW and WHEN the person's contact information was determined or changed. A free-form description of the last known location of the person being sought, including the city, state, and as much detail as possible. Any application that sets or changes this value MUST add a note to the notes field with a description of HOW and WHEN the person's location was determined. Free-form text description of the person's current condition, situation and location details, where they were last seen, corrections to other information, etc.