- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Apr 2020 07:09:45 +0000
- To: public-dxwg-wg@w3.org
I take most solace from @tombaker comment that > DCMI went perhaps a step too far when it originally assigned a formal range of rdfs:Class [for dct:type] because rdf:type already had a range of rdfs:Class I had always seen `dct:type` as a way of adding additional classifiers that were *not* `rdfs:Class` since there was already a home for those (i.e. `rdf:type`!) `dct:type` should not duplicate the functionality of `rdf:type`. It appears this has not been fixed in the most recent version of DC - https://www.dublincore.org/specifications/dublin-core/dcmi-terms/terms/type/ has no range restriction any more. So I think we can close this issue as it is no longer valid. -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/dxwg/issues/314#issuecomment-617594485 using your GitHub account
Received on Wednesday, 22 April 2020 07:09:47 UTC