A record about a missing or found person. Unique identifier for this record, which consists of a domain name followed by a slash and a local identifier. The domain name identifies this record's home repository, which is the authority for this record. The format of the local identifier is up to the home repository. When the person_record_id begins with a domain other than the application's own domain, it means this record is a clone of a record from another source. (string in the form "yyyy-mm-ddThh:mm:ssZ"): Date in UTC that this record was stored in the local application (not the date of creation in the home repository). 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 or equal to 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. The name of the home repository of this record. The date in UTC that the record was originally created in its home repository. The URL to the record in the home repository (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. The sex of the person sought or found. Exact date of birth (in YYYY-MM-DD format) or approximate date of birth (in YYYY-MM format or YYYY format) of the person sought or found. Age of the person sought or found, as of the source_date of this record. The value of this field is either a single decimal integer, or an inclusive range given as two decimal integers separated by a hyphen. This field has no defined meaning when source_date is missing. (string, all capitals, no accents): Street name (no number) of the home address of the person sought or found. (string, all capitals, no accents): Name of the home neighborhood 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. Postal code of the home address of the person sought or found. Two-letter uppercase ISO 3166-1 country 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. When a record is converted from some other form to PFIF by a machine process, the field "automated-record-creator" should be present and should name the program that produced the PFIF. 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". automated-record-creator: ScrapeMatic 0.5 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 timestamped note about a particular missing or found person. This type describes stand-alone note elements, which must specify the person_record_id of the person element to which they belong. The parent person element need not be present in the same document as the note. Unique identifier for this record, which consists of a domain name followed by a slash and a local identifier. The domain name identifies this record's home repository, which is the authority for this record. The format of the local identifier is up to the home repository. When the note_record_id begins with a domain other than the application's own domain, it means this record is a clone of a record from another source. The person_record_id of the person record to which this note belongs. A timestamped note about a particular missing or found person. This type describes note elements nested within person elements, which may or may not specify the person_record_id of the person record to which they belong. Unique identifier for this record, which consists of a domain name followed by a slash and a local identifier. The domain name identifies this record's home repository, which is the authority for this record. The format of the local identifier is up to the home repository. When the note_record_id begins with a domain other than the application's own domain, it means this record is a clone of a record from another source. The person_record_id of the person record to which this note belongs. The person_record_id of another person record which this note claims to be for the same person as this note's person record. (string in the form "yyyy-mm-ddThh:mm:ssZ"): Date in UTC that this record was stored in the local application (not the date of creation in the home repository). 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 or equal to the entry_date of the last received record. 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. (string in the form "yyyy-mm-ddThh:mm:ssZ"): The date in UTC that this note was originally created in its home repository. In most cases, notes should be sorted by this field for display. The status of the person sought or found. The author of this note is seeking information on the person in question. The author of this note is the person in question. The author of this note has received information that the person in question is alive. The author of this note has reason to believe that the person in question is still missing. The author of this note has received information that the person in question is dead. True if the missing person has been personally contacted or seen, or false otherwise. The text field of this note should 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 should describe HOW the person's contact information was determined. The preferred contact phone number of the FOUND person. This field is present ONLY if the person has been FOUND. The text field of this note should describe HOW the person's contact information was determined. A free-form description of the last known location of the person being sought, including the city, state, and as much detail as possible. The text field of this note should describe HOW 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. A dateTime in UTC. A single decimal integer or an inclusive range given as two integers separated by a hyphen. An exact or approximate Gregorian date in YYYY, YYYY-MM, or YYYY-MM-DD format.