- From: Alex Robin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Apr 2023 07:59:32 +0000
- To: public-sdwig@w3.org
@rob-metalinkage @dr-shorthair I don't know if you looked at the changes in the [PR](https://github.com/w3c/sdw/pull/1402) but I tried to follow the exact same patterns as the ones that were already employed in SOSA and SSN. This means the SOSA file defines classes and properties with loose constraints using `schema:domainIncludes`and `schema:rangeIncludes` axioms while the SSN file tightens things further with `owl:Restriction`. Personally I like keeping the two namespaces separate. SOSA is a good abstract core while SSN brings more implementation level details. I think the only class that is in OMS and not in SOSA is Deployment. And so some relationships from SOSA namespace to Deployment may be an issue. Happy to have a telecon with the initial SOSA team to discuss design patterns. -- GitHub Notification of comment by alexrobin Please view or discuss this issue at https://github.com/w3c/sdw/pull/1402#issuecomment-1512631507 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 April 2023 07:59:33 UTC