- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 May 2017 13:37:09 +0000
- To: public-poe-archives@w3.org
For rightsstatements.org we had a bit of a hard time navigating in the landscape of existing classes of policies/statements and the properties available to connect to them (see pages 7-8-9 at http://rightsstatements.org/files/170106requirements_for_the_technical_infrastructure_for_standardized_international_rights_statements_v1.2.pdf) But indeed we ended up judging that dct:license was too specific for our rightstatements (though it could be used for some). We opted for dct:rights as the most general level of property relevant. Still it may be that even dct:rights is too specific for ODRL. Some policies may not be about rights, may they? In which case we'd have the hierarchy dct:license subPropertyOf dct:rights subPropertyOf odrl:hasPolicy That said it could be that dct:rights can have values that are not really specifying permissions and obligations. I.e. a string like "copyright holder: X" is not really saying anything about what should/can be done. In this case dct:rights is not really comparable with odrl:hasPolicy and the only hierarchical link that's correct is dct:license subPropertyOf odrl:hasPolicy @vroddon the specialization links in the CC license vocabulary (CCrel) should be taken with a pinch of salt. When working on rightstatements.org we were a bit puzzled by the subclass/property relations, and we asked some friends at CC. Their (unofficial) answer was that dct:RightsStatement and LicenseDocument did not exist until 2008 and some CCrel decisions predate this. Ideally CCrel should be updated so that cc:license is a subproperty of dct:rights rather than dct:license and cc:License a subclass of dct:RightsStatement rather than dct:LicenseDocument. And in fact CCrel should ideally have used them directly rather than creating cc:License... -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/poe/issues/184#issuecomment-304662982 using your GitHub account
Received on Monday, 29 May 2017 13:37:15 UTC