Person

Pattern

This class has been associated with the following pattern:

Subclass Of

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 Ontology 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. Person has the following properties: •hasPersonID: links zero or more to instances of PersonID. Can be a driver’s license, passport, etc. •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. •hasAddress: links to zero or more Address for the Person. •hasPhoneNumber: links to zero or more PhoneNumbers for the Person. •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 shall vary based upon context and so must 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.

Class Diagram Description

Required by Use Case(s)

(why is this specialized definition needed?)

CDM References

What other classes or properties reference this term?

Interface Specification References

This class has been associated with the following interface specification items:

Sources

Sources considered when developing the class:

Status

Pending Approval

Has Subclass(es)

Annotations

Annotation	Value

Manchester Syntax Specification

Property	Restriction	Value
HasPersonID	only	PersonID
Schema:givenName	only	xsd:string
Schema:additionalName	only	xsd:string
Schema:familyName	exactly 1	xsd:string
HasAddress	only	ISO5087-2:Address
HasPhoneNumber	only	PhoneNumber
Schema:birthDate	exactly 1	time:Instant
Schema:birthplace	exactly 1	ISO5087-2:Address
Schema:deathDate	max 1	time:Instant
Schema:deathPlace	max 1	ISO5087-2:Address
Schema:parent	only	Person
Schema:children	only	Person
HasSex	exactly 1	Sex
HasGender	only	Gender
HasIncome	only	MonetaryValue
HasSkill	only	Skill

Supplementary Figures

Figure	Caption