Return-Path: <@JHUVM.HCF.JHU.EDU:wsn@CSF.COLORADO.EDU> Received: from JHUVM (NJE origin JHUSMTP@JHUVM) by JHUVM.HCF.JHU.EDU (LMail V1.1d/1.7f) with BSMTP id 8768; Wed, 1 Sep 1993 14:57:14 -0400 Received: from csf.Colorado.EDU by JHUVM.HCF.JHU.EDU (IBM VM SMTP V2R2) with TCP; Wed, 01 Sep 93 14:57:13 EDT Received: from (localhos [127.0.0.1]) by csf.Colorado.EDU (8.5/8.5/CNS1.0) with SMTP id MAA17528; Wed, 1 Sep 1993 12:56:22 -0600 Date: Wed, 1 Sep 1993 12:56:22 -0600 Message-Id: <199309011853.MAA17421@csf.Colorado.EDU> Errors-To: chriscd@jhuvm.hcf.jhu.edu Reply-To: CHRISCD@jhuvm.hcf.jhu.edu Originator: wsn@csf.colorado.edu Sender: wsn@csf.colorado.edu Precedence: bulk From: chris chase-dunn To: Multiple recipients of list Subject: new w-s journal X-Listserver-Version: 6.0 -- UNIX ListServer by Anastasios Kotsikonas X-Comment: WORLD SYSTEMS NETWORK I should mention that I am collecting all the contributions to the discussion of the journal proposal and will archive them in the "seminars" subdirectory of wsystems at csf.colorado.edu The format problems mentioned by Tieting Su will be solved in time. For now I would suggest that we use ascii text files. These are easily moved over internet by ftp and gopher. If authors want to make hard copy figures, graphs, maps, etc available to readers by request through snail mail they can. eventually the technology will be able to move graphics. there will soon be an easily used program that tranlates binary files into ascii files and back. that will make all things possible. the questions raised by Timmons Roberts are good ones. I would like to see what others have to say on these matters. chris chase-dunn (respond to the net) wsn@csf.colorado.edu