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

Alignment of terminology with other observation models #26

Open
dr-shorthair opened this issue Oct 9, 2019 · 2 comments
Open

Alignment of terminology with other observation models #26

dr-shorthair opened this issue Oct 9, 2019 · 2 comments

Comments

@dr-shorthair
Copy link

Annex B is "Mapping O&M terminology to common usage"
Additional mappings should be added, e.g. DDI
(probably:
ddi:Unit == feature of interest,
ddi:Universe == ultimate feature of interest,
ddi:Variable =~ observed property
)

@KathiSchleidt
Copy link
Contributor

I'm starting to wonder if we might even need this type of mapping within our current discussions

I've now put up a google sheet with the alignment (as far as I can divine it) between O&M 2.0, SOSA, and our first stab at O&M 3.0: https://docs.google.com/spreadsheets/d/1RbZtW8rDRk7n7oDoNH0SONPm1uZ29dkAPByXwddOvOY/edit?usp=sharing
(the link gives you comment rights, if you want more, please request!)

@dr-shorthair
Copy link
Author

Looking at https://github.com/opengeospatial/om-swg/blob/master/iso_19156_issues/om_core_uml_draft.png I am concerned that the rolenames relating to the feature or interest and sampling do not match either O&M v2 (i.e. ISO 19156:2011) or SSN/SOSA. I can infer that domainFeature and samplingInfo are supposed to satisfy the same requirements as hasFeatureOfInterest and hasUltimateFeatureOfInterest from SSN and SSN-ext but I find the proposed terminology less explicit.

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