W3C home > Mailing lists > Public > public-dwbp-comments@w3.org > March 2016

License comments

From: Renato Iannella <r@iannel.la>
Date: Wed, 2 Mar 2016 10:10:05 +1000
Message-Id: <130B0634-7338-4102-86CF-BDDEDFA2F3A2@iannel.la>
To: public-dwbp-comments@w3.org
Hi, some feedback on “Data on the Web Best Practices”: http://www.w3.org/TR/2016/WD-dwbp-20160112/ <http://www.w3.org/TR/2016/WD-dwbp-20160112/>
section "9.3 Data Licenses”.

It is important to clearly define the ways that licenses work on the Web.
1 - A link (URI) to a human-readable license (and possible community-defined values)
2 - A link/embedded machine-readable license

In the "Possible Approach” section you mention 4 vocabs that include properties for linking (Case 1 above).
Wouldn’t it be more useful to list the actual properties than a link to the entire vocab?

Note that CC does not provide a linking property (CC uses xhtm;:license or dc:license etc)
The reference for CC points to CCRel, when in fact, it should refer to the CC license URL set:
https://creativecommons.org/licenses/ <https://creativecommons.org/licenses/>

The CC license URLs are examples of the _values_ for the properties for Case 1 above.

The second part lists 3 machine readable rights languages.
Note that ODRL is the “Open Digital Rights Language” not "Open Data Rights Language”

Example 6 shows a "Machine-readable" example.
But seems to only show a link to a CC fixed license URL, not one of the listed 3 machine readable rights languages?

Example 6 then shows a “Human-readable” example.
But it only has a link to an example showing the full description of a distribution?
(I would expect it to show a human-readable license)


Received on Wednesday, 2 March 2016 00:10:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 00:10:44 UTC