Submissions:City Resident Pattern - Revision history

MarkFox at 15:37, 16 August 2020

2020-08-16T15:37:32Z

MarkFox at 15:31, 16 August 2020

2020-08-16T15:31:44Z

MarkFox at 15:19, 16 August 2020

2020-08-16T15:19:42Z

MarkFox: Imported from OWL file.

2020-08-16T15:12:32Z

Imported from OWL file.

New page

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=
}}
{{Content OP Proposal Template
|SubmittedBy=MarkFox
|ReusableOWLBuildingBlock=http://ontology.eil.utoronto.ca/cdm/Resident.owl
|Name=City Resident Pattern
}}
{{Element list header}}

{{Additional information header}}

{{Scenarios about me}}
{{Reviews about me}}{{Modeling issues about me}}{{My references}}

← Older revision		Revision as of 15:37, 16 August 2020
Line 74:		Line 74:
	{{Modeling issues about me}}		{{Modeling issues about me}}
	{{My references}}		{{My references}}
		+	{{Submission to event
		+	\|Event=WOP:2020
		+	}}

@@ Line 1: / Line 1: @@
 {{Content_OP_Proposal_toolbar}}
 {{Graphical representation header}}
-{{Graphical representation}}
+{{Graphical representation
 {{Content OP Proposal Template
 |SubmittedBy=MarkFox
 |Name=City Resident Pattern
 |Intent=This file defines an ontology design pattern for City "Resident.” Why is the development a Resident pattern important for the development of a city data on-tology? In the PolisGnosis project (Fox, 2017), where ontologies have been developed for measuring city performance across the 17 themes  defined in ISO37120:2104 (e.g., Education, Public Safety, Health, Water & Sanitation), one of the concepts that recurs across themes is “(city) Resident”.  The provisioning of city services is often contingent upon whether the person is a resident of the city.  Whether it is access to swimming lessons provided by Parks and Recreation, or affordable housing provided by Shelters and Housing, many are contingent upon satisfying the residency requirement. This ontology pattern make it possible to define the semantics of residency for a city, and use the definition to automate the classification of a person as a resident or not of a city.
 |Domain=Smart City,
 |CompetencyQuestion=1.	Does the person reside in the city/country?
 .	How long has the person resided in the city?
 .	Is the person a citizen of the country which contains the city?
 .	Does the person have a residence/home/domicile in the city?
 .	If the person has more than one residence, where does the person spend the most time?
 .	Does the person own property or business in the city?
 .	Does the person operate a business in the city?
 .	Is the person an official resident of the city?
 |ContentODPDescription=The Resident class is a subclass of Person. The properties of the Resident class are used to construct the definition of a resident for a particular city.  These properties are:
 •	a residence property hasResidence that specifies one or more individuals of Residence, where each individual specifies a residence distinguished by city, address and/or time interval. A resident can have more than one residence;
-•	a citizenship property citizenOf that specifies one or more Citizenship’s, each specifying the country (Country) and time interval (time:ProperInterval) the resident is a citizen. A person can be a citizen of more than country and for dif-ferent time intervals;
 •	an ownership property owns, that specifies zero or more ControlledEntity’s where entity’s are buildings (Building) and/or land areas (LandArea) that the resident owns; and
-A major part of determining whether a person is a resident of a city is the specifica-tion of where and when they have resided. The hasResidence property links a Res-ident to a Residence. The cardinality of the property is greater than one as over time a person may reside in more than one place/address, in the same city and/or different cities.
+•	a business operate property operate, that specifies zero or more ControlledEntity where the entity is an Organization that the resident operates.
 The Residence class specifies
 •	a location property forCity whose range is a single city (City),
 •	a time interval property time:hasTime whose range is a single time interval,
 •	the home type property hasHomeType whose range is a single type of home, such house, apartment, etc.,
 •	an address property hasAddress whose range is a single address, and
 •	a property hasResidentialRelationship whose range specifies whether the resident rents, owns, etc. the home.
 |ReusableOWLBuildingBlock=http://ontology.eil.utoronto.ca/cdm/Resident.owl
 |Scenario=The definition of Resident varies from city to city and country to country.  We use as our use cases definitions of Resident as provided by four cities:  Toronto Canada: “you are identified as a resident if you reside in, own property, or own or operate a business in Toronto” (311 Toronto).   Beijing China: Beijing uses the Hukou system which is a household registration program that results in a government issued permit. Beijing residents are “all indi-viduals holding the nationality of the People’s Republic of China who [have]a domicile in Beijing and nowhere else. If the individual maintains a regular dwell-ing somewhere else, the more regular dwelling is considered their place of resi-dence” (Li, 1991).   New York USA: a resident is defined by “Regulation 105.20 (d)(1)” which stipu-lates, “the place which an individual intends to be his permanent home –the place to which he intends to return. It is the home with range of sentiment, feeling and permanent association. One must be domiciled in New York and maintain a home in New York, the time spent in the State is irrelevant” (McGladrey, 2009).   Germany: “a resident of Germany generally refers to an individual who has a dom-icile in Germany or spends more than six consecutive months in Germany (habitu-al place of abode)” (Seidel, 2011).   As different cities have different definitions of Resident the design pattern must con-tain the properties required by each.
@@ Line 45: / Line 64: @@
           ⊔ ∃operates.(ControlledEntity
   	   ⊓ entity. (Organization ⊓ ∃hasAddress.( ∃city. gn:6167865))))
 |ReengineeredFrom=http://ontology.eil.utoronto.ca/GCI/Innovation/GCI-Innovation.owl
 |RelatedCP=OWL-Time: http://www.we.org/2006/time  icontact: http://ontology.eil.utoronto.ca/tove/icontact.owl