Pier Luigi Buttigieg

Greetings all - coming across this issue in ENV:earth_asia: now, wherever it ends up, we would definitely like to use terms like shrub, tree, epiphyte, etc.

>I am happy to have this class and any other material classes that are not specific to AGRO domain to ENVO. How should I proceed? Let's create a term request...

@marieALaporte points out that there may be no need for OWL subsets at this stage.We agree that generating flat files of all classes in each subset may have more immediate...

Since the "subset reports" will be SPARQL-driven, perhaps the other reports from #11 can be done en passant: > Over in ENVO, we create simple tabular files for non-owl-inclined software...

On aligning the usage of site : It seems that here we don't mean BFO:site (too general) but a BFO:'fiat object part' (like a plot in some ecosystem, with the...

Probably best to keep it simple and have several processes we can chain together freely. 'planned site visit' = A planned process during which an agent moves towards and enters...

PS: SDGIO has "access" semantics which may be useful here (ability, right, permission to approach and enter a site)

PS: The ENVO request asks for a synonym "remote sensing" which is actually quite a bit broader than satellite imagery. That's a great example of what should go in a...

@dr-shorthair >Separation of the act-of-observation from the feature-of-interest and the sensor allows them to be in different places if necessary. Yes, it was a wise design decision. This slots in...

Punt to ENVO? We've dealt with some of this in the past. important to weave geospatial abstractions with physical entities carefully (no one really samples sites that are not fully...