- From: Nicholas Car via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Nov 2018 12:23:34 +0000
- To: public-dxwg-wg@w3.org
If we use a custom property like `prof:hasProfileObject` then we loose any speedup regarding easily understanding what the `prof:Profile` <-> `prof:ProfileObject` relationship is, although it may be able to be inferred from the class naming. I guess it depends what you think a 'profile' is. In the dummy DCAP profile I've made, https://github.com/CSIRO-enviro-informatics/csiro-epub-dcap, there is a PDF doc explaining things (Guidance) and Word form (`dct:hasFormat`) and constraints in RDF (not SHACL but DSP; equivalent to SHACL for this discussion's purposes). How would those all not be `dct:hasPart` from the main Profile object? They are all parts of it! -- GitHub Notification of comment by nicholascar Please view or discuss this issue at https://github.com/w3c/dxwg/issues/573#issuecomment-439875648 using your GitHub account
Received on Monday, 19 November 2018 12:23:36 UTC