<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE document PUBLIC "-//CNX//DTD CNXML 0.5//EN" "http://cnx.rice.edu/technology/cnxml/schema/dtd/0.5/cnxml_plain.dtd">
<document xmlns="http://cnx.rice.edu/cnxml" xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="new">
  <name xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/">Collection permanence</name>
  <metadata xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/">
  <md:version xmlns:bib="http://bibtexml.sf.net/">1.1</md:version>
  <md:created xmlns:bib="http://bibtexml.sf.net/">2006/05/27 01:12:30.533 GMT-5</md:created>
  <md:revised xmlns:bib="http://bibtexml.sf.net/">2006/05/27 01:52:59.332 GMT-5</md:revised>
  <md:authorlist xmlns:bib="http://bibtexml.sf.net/">
      <md:author xmlns:bib="http://bibtexml.sf.net/" id="jgrimes">
      <md:firstname xmlns:bib="http://bibtexml.sf.net/">Joseph</md:firstname>
      <md:othername xmlns:bib="http://bibtexml.sf.net/">E.</md:othername>
      <md:surname xmlns:bib="http://bibtexml.sf.net/">Grimes</md:surname>
      <md:email xmlns:bib="http://bibtexml.sf.net/">joe_grimes@sil.org</md:email>
    </md:author>
  </md:authorlist>

  <md:maintainerlist xmlns:bib="http://bibtexml.sf.net/">
    <md:maintainer xmlns:bib="http://bibtexml.sf.net/" id="jgrimes">
      <md:firstname xmlns:bib="http://bibtexml.sf.net/">Joseph</md:firstname>
      <md:othername xmlns:bib="http://bibtexml.sf.net/">E.</md:othername>
      <md:surname xmlns:bib="http://bibtexml.sf.net/">Grimes</md:surname>
      <md:email xmlns:bib="http://bibtexml.sf.net/">joe_grimes@sil.org</md:email>
    </md:maintainer>
  </md:maintainerlist>
  
  <md:keywordlist xmlns:bib="http://bibtexml.sf.net/">
    <md:keyword xmlns:bib="http://bibtexml.sf.net/">copyright</md:keyword>
    <md:keyword xmlns:bib="http://bibtexml.sf.net/">Creative Commons</md:keyword>
    <md:keyword xmlns:bib="http://bibtexml.sf.net/">GNU Documentation</md:keyword>
    <md:keyword xmlns:bib="http://bibtexml.sf.net/">license</md:keyword>
    <md:keyword xmlns:bib="http://bibtexml.sf.net/">Open Source</md:keyword>
    <md:keyword xmlns:bib="http://bibtexml.sf.net/">rights</md:keyword>
  </md:keywordlist>

  <md:abstract xmlns:bib="http://bibtexml.sf.net/">Every collection needs a place where a physical copy of the results is kept safe, and a way to keep track of what rights collaborating scholars have, and a means of extending some of those rights to others. An undefinitive beginning of a guide to something that's usually simple, but can get complex.</md:abstract>
</metadata>
  <content xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/">
    <figure xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-482"><media xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" type="image/jpeg" src="Coll-Perm.jpg"/>
<caption xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/">Information from the Collections panel about permanence of the collection.</caption></figure><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="delete_me">The question of permanence has already come up in regard to what can be considered a <cnxn xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" document="m13635">published source</cnxn> in the age of digital archiving. Digital data repositories in universities, museums, and national archives are likely to be able to furnish your data to scholars after more than a century. Personal Web sites and your computer's hard disk are not.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-511">Once you have a permanent home for your collection, you can enter the name or URL of the archive in the collection itself as "Stable copy." In the example above, the location of the stable copy is still up in the air. Eventually it will need to be settled.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-91">Who has the right to allow reproduction of a work? That's a broader question than who holds the copyright.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-803">If you share your Wordcorr collection with a colleague, and the colleague fills out a new analytical view of the data in the collection, the collection with the new view’s analysis added is a derivative work ― a hefty intellectual project that takes your original collection as its point of departure. It builds on it in the tradition of good scholarship. But it’s still your collection, modified by someone else with your knowledge, and quite possibly with a good deal of communication between the two of you.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-416">New questions of ownership have developed as computer usage grows. Computers create, store, copy, transform, and transmit information electronically. The medium opens up a potential for scientific and literary collaboration that did not exist when paper was about the only vehicle conceivable for writing, storing, copying, or disseminating information.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-486">So it's not surprising that it's the computer people who have put a lot of effort into clarifying ways in which the rights of each person involved in creating, modifying or using information can be kept clear. Their efforts fall under the general rubric of rights management.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-569">One of the best ideas that has come out of considerable discussion is that copyright is more than a means of preventing people from reproducing your work. It’s perfectly proper for you as copyright holder to permit, and even encourage, other people to develop what you own further.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-747">This has developed into the idea of <term xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/">licensing</term> the use of copyrighted material. And more and more nowadays, under the impetus of the <link xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" src="http://en.wikipedia.org/wiki/Open_Source">Open Source</link> movement, the license is granted without charge – provided you meet certain conditions that ensure that the information about you as originator of the document, and about changes in it that others have made, is sent along as part of the document itself. This tutorial, as you can see for yourself, is released under an open <link xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" src="http://creativecommons.org/">Creative Commons</link> license.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-968">Wordcorr gives you the option of choosing among three types of open license: <link xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" src="http://opencontent.org/openpub/">Open Publishing</link>, <link xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" src="http://creativecommons.org/">Common Content</link>, and <link xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" src="http://www.gnu.org/copyleft/fdl.html">GNU Documentation</link>.</para><para xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="element-369">You don’t have to copyright your collection. But if you do decide to, you want to put the year in which you assert copyright into the collection metadata. Then you can register it when it’s convenient.</para><note xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/">Things change constantly in rights management. Consider this tutorial probably out of date, and check around the Internet and in your institution to see what possibilities fit your situation best.</note>   
  </content>
  
</document>
