- From: Jeni Tennison <jeni@jenitennison.com>
- Date: Sun, 27 Nov 2011 20:52:20 +0000
- To: Jayson Lorenzen <Jayson.Lorenzen@businesswire.com>
- Cc: "HTML Data Task Force WG" <public-html-data-tf@w3.org>
Jayson, On 21 Nov 2011, at 17:30, Jayson Lorenzen wrote: > Should there be a note that consumers should look for usage rights and/or attribution instructions on the pages or in the data they are consuming (when provided)? Schema.org does not support much beyond defining the rights holder or source org (at least for news) but it is something. Good thinking. I added this for Publisher Good Practice: The goal of publishing HTML data is to enable consumers to reuse it. To make it clear how the HTML data you publish can be reused, you should include information about the rights holder and license that the information is made under. There are a number of vocabularies that enable you to do this, such as schema.org, rel-license, Creative Commons and Dublin Core. Your target consumers should indicate which formats they understand when it comes to expressing licensing information and which licenses they know about, and you should choose a relevant format in the same way as you do for the core data that you are publishing. and this for Consumer Good Practice: The presence of HTML data within a website does not imply that the data can be used without restriction. Publishers may license the information provided through HTML data, for example to restrict it to non-commercial use or to use only with attribution. It is good practice for a consumer to honour licenses and to indicate to publishers which formats they recognise for expressing licensing information within HTML pages, and which licenses they recognise as indicating that the data within the page is consumable. Typical vocabularies for expressing this information are schema.org, rel-license, Creative Commons or Dublin Core. Even when the use of data is unrestricted, it is good practice for consumers to record the source of the information that they use and, when republishing that data, provide metadata about the rights holder, source and license under which the information is available, using the same vocabularies as those listed above. Does that address the issue? Thanks, Jeni -- Jeni Tennison http://www.jenitennison.com
Received on Sunday, 27 November 2011 20:52:52 UTC