This is less of a problem than people imagine. One *can* put a copyright notice on any project material and then distribute it widely. Sometimes you want to put a notice of expiration on the materials to better protect your future vendor. The versions one distributes are usually not as finished as a vendor needs, so there is an incentive for any user of your free stuff to trade up to a bullet-proof, full-function version. You can sell your vendor on this by using the Netscape model--build market share with free stuff. r >I am Kurt Maly at Old Dominion where we are in the second year of a >distance learning project targeted for college audiences. In this >discussion so far I see one theme emerging: everyone has a different >idea as to what dissemination means. Examples are: >being recognized in academic circles >local community knows about project >participants know how to use results >In my mind the true test for successful dissemination is that products >are getting used by other than project participants in both the local >community(first goal) and the national community(or even international). >We are aiming at eventual commercializing of our system but are >running into a classical catch 22. On the one hand we want to give our >source to other researchers for experimentation, on the other hand our >research office tells us we need to protect the code for eventual >commercialization. >Any comments? >kurt maly Robert Tinker, president The Concord Consortium 37 Thoreau St., Concord, MA 01742 508-371-3476, fax: 508 371-0696 bob@concord.org http://www.concord.org Educational innovation through creative technologies.