Nick Simicich <njs@scifi.squawk.com> wrote:
> it is not clear whether this standard should or should not
> allow for the assertion of a compilation copyright.
In the RFC, I want to avoid making any statements about how copyright
law may or may not apply to mailing lists. I've included an example
Compilation Copyright assertion in the examples section though.
> Which argues that one may repeat the header because one may have multiple
> comments (for example, an assertion of copyright and a URL pointing to the
> long policy)
Why not put both into the same header (possibly folded across multiple
lines)?
List-Policy-Archive: Ask (Compilation Copyright © 2002 Example Inc.
All Rights Reserved. For policy details refer to
<http://example.com/policy/will-sue-unauthorised-archivers.html>)
> They should be respected by a program no matter where they appear - in a
> plain text section, in the mime headers, in the unlabled area that follows
> the RFC822 headers and precedes the first mime headers, or in the top level
> RFC822 headers. If they are put into a html section, or a section that is
> encoded in a scheme other than seven bit ascii (uuencode, base64,
> quoted-printable), they must be repeated in one of the above places for
> programmatic access.
If the policy file is HTML, it could be required that the
specifications are enclosed in <PRE> .. </PRE>.
> [..]
Many other good comments deleted, but still appreciated! :-)
The newest version of the draft is at
http://maillist.info/rfc-draft.txt
Greetings, Norbert.
--
Founder & Steering Committee member of http://gnu.org/projects/dotgnu/
Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland)
Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch
List hosting with GNU Mailman on your own domain name http://cisto.com
Follow-Ups:
References:
|
|
