-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add term "Population" #479
Add term "Population" #479
Comments
Let's first find a definition, the classification arises from the definition. |
"A population is the number of people in a city or town, region, country or the world." |
To reuse terms we already have, what about: A population is the number of people in a spatial region. |
I don't think we should define a population as the number of people because that would make, e.g. "25" a population. Could we define it as an aggregate of people? |
Good idea, Janna! So: A population is an aggregate of people in a spatial region. The number of this population (e.g. 80 million in Germany) would then be a data property a specific instance of the population linked with a specific instance of a spatial region (Germany) right? |
So What about subdivisions by sex and age? Elaborate scheme or just a bunch of subclasses defined as needed, like "A population (female) is a population of female people." One subdivision of populations we are actually using is rural/urban. |
What about:
|
Probably there's no need to define "female" and "male". How do you feel about "rural" and "urban"? |
If you need that much detail, I would see these more of instances of population than classes. You have population age classes of 31-40 but another model might have age classes of e.g. 18-60 instead. @jannahastings : What do you think? |
I don't. But other's might ;) |
Okay, at the moment, we should focus on what we really need and not on what someone in future might need. |
I agree: let's focus on including the broader classes for now, and if we need specific sub-classes for annotation in the future, we can add them with a "just-in-time" approach as they are needed. These will be compositional in any case, so we can always add them dynamically as long as we can define or re-use from external sources the required properties such as age and urban vs. rural. (Incidentally, we should check ENVO for urban vs. rural, they may have definitions we could re-use) |
My concern is whether we set up a system akin to what is happening with sectors (#30, #460, #461), where there could be different definitions of "divisions of population" (for lack of a better term), or if we expect to add a bunch of subclasses as needed. Planning ahead could save us a lot of trouble. But I don't have strong feelings either way. |
I also prefer to stay simple now and concentrate on whats needed. |
If society is defined as an object aggregate of people, then it should be a synonym of population. |
Just jumping in while this popped up in my inbox: Wouldn't the difference between population and society be that society includes specific rules (laws, codes of conduct, governance) on how the people that make up the population interact with one another and as a whole? |
I tend to agree that there should be more to the definition of society than just the people in it. So we need to reconsider the definition of organisation role: is it society that is needed there, or population (aggregate of persons)? |
I don't think people have to have anything more in common than all being people to create an organisation. |
That sounds good to me. And if "population" sounds (by implication rather than definition) too large given that organisations might be small, we could also consider explicitly saying "aggregate of people" instead (which would indeed be a true synonym for population). |
I like the
|
@stap-m in the pull request I now pushed to just change the organisation role def to "aggregate of people", would you agree with that? |
add definitions for Population and rural/urban/working subclasses #479
We use lower case for class names. Also the issue numer #479 should be referenced in the term tracker item. I'll correct that. |
Description of the issue
Population, and subclasses thereof, are used by various energy models to e.g. drive demand. Also it's listed as missing in #192
Ideas of solution
Named missing classes (#192) so far:
There are many further subdivisions possible. The UN population division for example subdivides by sex and age group (in five-year cohorts). The OECD by different age groups (I think ten-year cohorts) and education level. Other @OpenEnergyPlatform/oeo-domain-expert-energy-modelling may have additional needs.
So do we need a scheme for subdividing populations analogous to sectors, with
sectors
conforming_to
sector divisions
(#460)?I think
Population
s would go underindependent continuant
->immaterial entity
, just like organisations. But strictly speaking, populations are composed ofpeople
, so it would beindependent continuant
->material entity
->object aggregate
, which … feels weird. Will need input from @OpenEnergyPlatform/oeo-general-expert-formal-ontology here.Workflow checklist
I am aware that
The text was updated successfully, but these errors were encountered: