Pattern:Person Pattern

Description

An English description of the definition (what distinguishes this sense of the term?).

Persons are a key category in Smart City Models. It is the combination of decisions of persons in the population that result in changes to travel behaviour. For example, consider a person's decision to change places of employment. Among other things, this change will likely impact their daily travel behaviour. The Person Pattern enables the representation of persons and their attributes of interest. Factors such as a person's age, income, and place of residence are defined as properties of a person. The Change Pattern is used to specify which attributes may change over time (e.g. income), and which attributes are constant (e.g. date of birth).

Key Concepts and Classes

The key classes and properties are formalized in Table 8 and Table 9, respectively. Person has the following properties: • hasPersonID: links zero or more to instances of PersonID. Can be a driver’s license, passport, etc. • hasName: links to zero or more instances of PersonName – a person can have multiple names. • hasAddress: links to zero or more Address for the Person. • hasPhoneNumber: links to zero or more PhoneNumbers for the Person. • hasEmail: specifies zero or more email addresses as xsd:strings. • cityresident:citizenOf: links to instances of ISO5087-2:Citizenship that specify the country they are/were a citizen of, and the time period. • schema:birthdate: A time:Instant when the person was born. • schema:birthplace: An address for where the person was born. • schema:deathDate: A time:Instant when the person died. • schema:deathplace: An address for where the person died. • schema:parent: links to zero or more Persons who are their parent. Note that we define the parent relation as the legal relation as opposed to biological. This property may be specialized and restricted, for example hasBiologicalMother: exactly 1 Person. • schema:spouse: links to zero or more Persons who are their spouse. • schema:children: links to zero or more Persons who are their children. • hasSex: A Person has exactly 1 sex, and sex may be one of only male or female. The definition of sex is distinct from that of a person’s gender: “Sex refers to sex assigned at birth. Sex is typically assigned based on a person's reproductive system and other physical characteristics.” • hasGender: A Person may also have an associated Gender. The value of this may or may not differ from a person’s sex at birth. Precisely how Gender is defined and instantiated varies based upon context and so may be defined by the user of this standard as appropriate. • hasIncome: specifies the annual income for ther person. • hasSkill: identifies the Skills the Person has. • hasEducation: identifies the education the Person has. Note the Skill and Education classes are not defined and are left to the application to define. PersonName represents the parts of a person’s name: • schema:givenName: a string that is the given or first name of the Person. • schema:additionalName: a string that is the middle or additional names of the Person. • schema:familyName: as single string that is the family or last name of the Person. PersonID represent a unique identifier for the Person issued by an Organization. It has the following properties • schema:identifier: a string that encodes the unique id of the person. • hasIDType: specifies the type of ID, including passport an driversLicense. • photoID: A Boolean that specifies whether the ID contains a photo. • time:hasTime: defines a time interval during which the ID is valid. • schema:issuedBy: an Organiztaion that issued the id.

Has Class(es)

Person, PersonID, Sex

Status

Pending Approval

Supplementary Figures

Figure	Caption