1 01/03/83 protection notices and their names
2
3
4 Function: Segments with the pnotice suffix contain a software
5 protection notice file. These segments:
6
7 1) Are ASCII templates containing the text of a software protection
8 notice. They are input exactly as they are to appear in source or
9 in PNOTICE segments. For example:
10 Copyright, C Honeywell Information Systems Inc., 1981
11
12 No comment boxes or other highlights should be included.
13 2) Are used by the tools generate_pnotice and add_pnotice to
14 provide standardized, legal protection of Multics software.
15 3) Are indirectly used by the display_psp, display_pnotice and
16 list_pnotice_names commands to provide information as to what
17 notices are in modules.
18
19
20 Copyright naming conventions:
21 Copyright protection notices must conform to the following
22 naming conventions:
23
24 A) The primary name of a copyright pnotice file must consist of three
25 components. These three components are:
26 Component 1: <party or parties>_<version of this notice> where:
27 <party or parties> is, for example, HIS or MIT, or both, and
28 <version of this notice> is a single, uppercase letter, A through
29 Z. The version is used to indicate notices that are grammatically
30 different, exclusive of the year date. The default copyright notice,
31 and any other notices that are identical, with exception of the year
32 date, need NOT have a version letter.
33 Component 2: <4-digit year>
34 Component 3: "pnotice" suffix.
35
36
37 B) The copyright notice that is to be used as the default by the
38 add_pnotice command must have the added name "default.pnotice".
39 THIS IS THE ONLY ADDED NAME PERMITTED ON ANY COPYRIGHT NOTICE.
40
41 C) For Honeywell only copyright notices, the primary name must follow
42 the format: HIS_<version, if applicable>.<4-digit year>.pnotice.
43 For example, HIS.1981.pnotice may be the default copyright with text:
44
45 Copyright C by Honeywell Information Systems Inc., 1981
46 and HIS_A.1980.pnotice may have the following text:
47
48 Copyright C, 1980 by Honeywell Information Systems, Inc.
49 Other single party notices must follow a similar format.
50
51
52 D) For MIT and Honeywell joint copyright notices, the primary name must
53 follow the format:
54 MIT_HIS_<version, if applicable>.<4-digit year>.pnotice.
55 Other two party notices must follow a similar format.
56
57
58 E) An appropriate name for other joint copyright notices between
59 Honeywell and another party will be determined when such cases
60 arise.
61
62
63 Trade secret naming conventions:
64 Trade Secret pnotice file naming must follow these conventions:
65
66 F) The primary name of a Trade Secret pnotice file must consist of
67 three components. These three components are:
68 Component 1: <party or parties>_<version of this notice> where:
69 <party or parties> is, for example, HIS or MIT, or both, and
70 <version of this notice> is a single uppercase letter, A through Z.
71 The version is used to indicate notices that are grammatically
72 different.
73 Component 2: The literal string: trade_secret
74 Component 3: "pnotice" suffix.
75
76 G) For the Honeywell Trade Secret notice, the primary name must be:
77 HIS.trade_secret.pnotice.
78 No version is necessary. Other parties' trade secret notices should
79 follow a similar format.
80
81 H) The default Trade Secret notice must have the added name:
82 default_trade_secret.pnotice
83 THIS IS THE ONLY ADDED NAME PERMITTED ON ANY TRADE SECRET NOTICE.
84
85
86 Public domain naming conventions:
87 Public Domain pnotice file naming must follow these conventions:
88
89 I) The primary name of a Public Domain pnotice file must consist of
90 three components. These three components are:
91 Component 1: The literal string: public
92 Component 2: The literal string: domain
93 Component 3: "pnotice" suffix.
94
95 J) For the Public Domain notice, the primary name must be:
96 public.domain.pnotice
97 and the text of this notice must be:
98 "This is in the PUBLIC DOMAIN and may be copied without permission."
99
100
101 Notes:
102 As mentioned earlier, the only pnotice templates which are allowed
103 to have added names are the default templates. For reasons of
104 efficiency, the name default.pnotice or default_trade_secret.pnotice
105 must appear as the second name on the template. The primary name must
106 be the name described in paragraph A, F or J above.
107
108 The following command line is suggested to check all of the pnotice
109 templates for consistency, and should be used whenever new templates
110 have been created:
111 list_pnotice_names -check -all