Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Clarify semantics of dust and aerosol; and add subclasses #378
Comments
|
Why does dust need to be airborne: when it settles is it not still, dust? The solid material parentage refers to the invidual particles, but are the Perhaps we should use object aggregate semantics for a collection of dust On 5 Aug 2016 15:45, "Chris Mungall" notifications@github.com wrote:
|
|
On 5 Aug 2016, at 16:33, Pier Luigi Buttigieg wrote:
it is, agreed.
I think they are important.
this makes sense. the collection could have different shapes, such as
I'm still not totally clear on this point. Would 'aerosolised dust' be a |
|
Perhaps aerosol would then be a defined class like solid or liquid, and any On 9 Aug 2016 04:19, "Chris Mungall" notifications@github.com wrote:
|
cmungall
added a commit
that referenced
this issue
Sep 16, 2016
|
|
cmungall |
792fb84
|
cmungall
added a commit
that referenced
this issue
Sep 16, 2016
|
|
cmungall |
8d27c52
|
cmungall
added a commit
that referenced
this issue
Sep 16, 2016
|
|
cmungall |
b50fc2d
|
cmungall commentedAug 5, 2016
ENVO has both dust and aerosol:
These are not connected together, but they presumably should be.
The definition of dust uses a pluralized genus "particles", and the genus does not reflect actual parentage.
Once we figure this out, we can decide how classes such as
mineral dustshould be added