Skip to content
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

Represent hazards #14

Open
pbuttigieg opened this issue Sep 7, 2015 · 4 comments
Open

Represent hazards #14

pbuttigieg opened this issue Sep 7, 2015 · 4 comments
Assignees

Comments

@pbuttigieg
Copy link
Contributor

Examine GEMET:hazard and its narrower terms for preliminary types and definitions. Linked to #13.

@pbuttigieg pbuttigieg self-assigned this Sep 7, 2015
@pbuttigieg
Copy link
Contributor Author

As with disasters, the actual entities that constitute hazards will be present in ENVO, however, the logic that defines them as hazards is likely to be in SDGIO.

ENVO has an annotation property in_subset:environmental_hazards which may be useful here. Right now it does not distinguish hazards from disasters.

@phismith
Copy link

phismith commented Sep 7, 2015

One should not be using annotation properties when representing entities in the real world.
Hazards are entities in the real world. They are e.g. a bend in a road with a disposition to cause traffic accidents. The hazard is the disposition.

@pbuttigieg
Copy link
Contributor Author

The 'in_subset' AP is just for creating subset exports. It does not suggest any semantics. The various hazards are expressed as classes representing real world entities.

@pbuttigieg
Copy link
Contributor Author

Link to #13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants