- From: Rob via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Apr 2025 06:42:37 +0000
- To: public-dxwg-wg@w3.org
> so that it is clear, that you cannot distinguish a non-profile standard (e.g. a vocabulary) from a profile based on their types since both the vocabulary and the profile will be instances of both `dcterms:Standard` and `prof:Profile` when using `hasResource` like this. that is true - but there is no accepted vocabulary (or semantics) of standard types - so you would just need to define the additional standard types according to your needs. If you think its worth defining a class hierarchy for different styles of profiling and models i guess it could be considered - it would need for example to be able to handle things like OWL vs RDFS vs SHACL defined models, OWL-punning for SKOS concept schemes for soft-typing more abstract classes, recommendations vs conformance tests and all the other nuances around the "type of standard" in the wild. I suspect this would be useful, but best done in a different scope. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1624#issuecomment-2803985811 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 April 2025 06:42:38 UTC