Motorola WiNG 5 System Reference Manual page 791

protection scheme limited to Licensees and a click-on, download certification of Licensee status required of those
attempting to download from the server. An example of an acceptable certification is attached as Attachment A-2.
c) Notices. All Error Corrections and Shared Modifications You create or contribute to must include a file documenting
the additions and changes You made and the date of such additions and changes. You must also include the notice
set forth in Attachment A-1 in the file header. If it is not possible to put the notice in a particular Source Code file due
to its structure, then You must include the notice in a location (such as a relevant directory file), where a recipient
would be most likely to look for such a notice.
d) Redistribution.
(i) Source. Covered Code may be distributed in Source Code form only to another Licensee (except for students
as provided below). You may not offer or impose any terms on any Covered Code that alter the rights,
requirements, or responsibilities of such Licensee. You may distribute Covered Code to students for use in
connection with their course work and research projects undertaken at accredited educational institutions. Such
students need not be Licensees, but must be given a copy of the notice set forth in Attachment A-3 and such notice
must also be included in a file header or prominent location in the Source Code made available to such students.
(ii) Executable. You may distribute Executable version(s) of Covered Code to Licensees and other third parties only
for the purpose of evaluation and comment in connection with Research Use by You and under a license of Your
choice, but which limits use of such Executable version(s) of Covered Code only to that purpose.
(iii) Modified Class, Interface and Package Naming. In connection with Research Use by You only, You may use
Original Contributor's class, interface and package names only to accurately reference or invoke the Source Code
files You modify. Original Contributor grants to You a limited license to the extent necessary for such purposes.
(iv) Modifications. You expressly agree that any distribution, in whole or in part, of Modifications developed by
You shall only be done pursuant to the term and conditions of this License.
e) Extensions.
(i) Covered Code. You may not include any Source Code of Community Code in any Extensions;
(ii) Publication. No later than the date on which You first distribute such Extension for Commercial Use, You must
publish to the industry, on a non-confidential basis and free of all copyright restrictions with respect to
reproduction and use, an accurate and current specification for any Extension. In addition, You must make
available an appropriate test suite, pursuant to the same rights as the specification, sufficiently detailed to allow
any third party reasonably skilled in the technology to produce implementations of the Extension compatible with
the specification. Such test suites must be made available as soon as reasonably practicable but, in no event,
later than ninety (90) days after Your first Commercial Use of the Extension. You must use reasonable efforts to
promptly clarify and correct the specification and the test suite upon written request by Original Contributor.
(iii) Open. You agree to refrain from enforcing any Intellectual Property Rights You may have covering any
interface(s) of Your Extension, which would prevent the implementation of such interface(s) by Original
Contributor or any Licensee. This obligation does not prevent You from enforcing any Intellectual Property Right
You have that would otherwise be infringed by an implementation of Your Extension.
(iv) Class, Interface and Package Naming. You may not add any packages, or any public or protected classes or
interfaces with names that originate or might appear to originate from Original Contributor including, without
limitation, package or class names which begin with "sun", "java", "javax", "jini", "net.jini", "com.sun" or their
equivalents in any subsequent class, interface and/or package naming convention adopted by Original
Contributor. It is specifically suggested that You name any new packages using the "Unique Package Naming
Convention" as described in "The Java Language Specification" by James Gosling, Bill Joy, and Guy Steele, ISBN
0-201-63451-1, August 1996.
Section 7.7 "Unique Package Names", on page 125 of this specification which states, in part:
"You form a unique package name by first having (or belonging to an organization that has) an Internet domain
name, such as "sun.com". You then reverse the name, component by component, to obtain, in this example,
Appendix B Publicly Available Software B - 29