<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Dear Paul, <div><br></div><div>Yes, you can still map to <a href="http://rs.tdwg.org/dwc/terms/#dcterms:license">dcterms:license</a> and <a href="http://rs.tdwg.org/dwc/terms/#dcterms:rightsHolder">dcterms:rightsHolder</a>. What’s new in this version is that the publisher must apply a license to the dataset on the basic metadata page. Best practice is that the license applied to the dataset should not contradict the license(s) applied at the record level.</div><div><br></div><div>Best regards,</div><div><br></div><div>Kyle</div><div><br></div><div><div><div>On 02 Mar 2015, at 19:12, Paul J. Morris <<a href="mailto:mole@morris.net">mole@morris.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Thu, 26 Feb 2015 14:41:03 +0100<br>Kyle Braak <<a href="mailto:kbraak@gbif.org">kbraak@gbif.org</a>> wrote:<br><blockquote type="cite">Also please be aware that starting with this version, publishers are<br>required to publish their data under a CC0 1.0, CC-BY 4.0 or CC-BY-NC<br>4.0 declaration. <br></blockquote><br>Kyle,<br><br>Will this version of IPT be capable of publishing a resource where<br>different rows in the resource have different rights holders and<br>license terms? <br><br>-Paul<br>-- <br>Paul J. Morris<br>Biodiversity Informatics Manager<br>Harvard University Herbaria/Museum of Comparative Zoölogy<br><a href="mailto:mole@morris.net">mole@morris.net</a> AA3SD PGP public key available<br><br></blockquote></div><br></div></body></html>