- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Feb 2018 09:11:14 +0000
- To: public-dxwg-wg@w3.org
Hi @nicholascar I agree this is an important issue, but maybe the solution is not at the license level - or one that's called 'license' even though it could mean something else? I mean, the mechanism for machine-readable rights is probably going to be the same for rights that qualify as licenses, and for other types of rights statements (some of your agreements, ODRL's policies, CC's Public Domain). I work for an [initiative](http://rightsstatements/org) that use [dcterms:rights and dcterms:RightsStatements as 'anchors' for machine-readable rights](http://rightsstatements.org/files/170106requirements_for_the_technical_infrastructure_for_standardized_international_rights_statements_v1.2.pdf). The ODRL itself has [moved away](https://github.com/w3c/poe/issues/184) from refering too prominently to dcterms:license and they coined a new property odrl:hasPolicy as better alternative for direct asset-policy links. In practical terms, I guess my first proposal is to reword the issue and then have the discussion :-) -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/dxwg/issues/114#issuecomment-365540986 using your GitHub account
Received on Wednesday, 14 February 2018 09:11:18 UTC