- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Oct 2022 10:58:58 +0000
- To: public-sdwig@w3.org
I think this is somewhat more complicated - depending on what you mean by "equivalent" and "realize" - I would say SOSA is a realisation of ISO 19156, but extends it in some ways on the other hand. OGC's Observations and Measurements version 3 is explictly semantically aligned with these extensions - so this is "more true". I wouldnt call the UML for 19156 a realization on the other hand - its the normative model - the OWL equivalent is a realization perhaps. Both SOSA and ISO1956 -as-owl could be seen as logical models derived from the same conceptual model - what relation you would use to describe this is not obvious - we model this explicitly in the OGC's knowledge graph.... I would say rather that https://isotc211.geolexica.org/concepts/1442/ identifies the concept which is the SKOS realisation of the http://def.isotc211.org/iso19156/2011/Observation#OM_Observation identifier for the UML object. For OGC we are using content-negotiation-by profile to have the same URI for model elements resolve to both SKOS and OWL (and other forms) of the model - but we are looking at how to add explicit relations to these alternatives. Its not owl:sameAS - and rdfs:seeAlso is a bit weak - prov:wasDerivedFrom might be better. (of course SOSA being a joint OGC/W3C specification in a W3C namespace its harder to make it behave the way we want to ... but nevertheless understanding the most useful and explicit approach is something we can put into a knowledge graph that does link these different components and alternatives.) -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/sdw/issues/1372#issuecomment-1273138009 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 October 2022 10:59:00 UTC