GenICam License 20072005 PDF
GenICam License 20072005 PDF
GenICam License 20072005 PDF
1 License
GenICam License
GenICam_License_20072005.doc Page 1 of 11
V1.1 License
GenICam_License_20072005.doc Page 2 of 11
V1.1 License
Table of Contents
1 OVERVIEW..........................................................................................................................5
4 WHAT ARE THE RULES FOR USING THE RUNTIME VERSION OF THE
REFERENCE IMPLEMENTATION? .....................................................................................5
5 WHAT ARE THE RULES FOR USING THE DEVELOPMENT VERSION OF THE
REFERENCE IMPLEMENTATION? .....................................................................................6
GenICam_License_20072005.doc Page 3 of 11
V1.1 License
HISTORY
0.3 10.07.2005 Dr. Friedrich Dierks, Basler Reformatted text; small changes
1.1 15.07.2005 Christoph Zierl, MVTec - Added logo and application form
- Rephrased GenICam compliance
- Improved textual consistency
- Deleted description of runtime /
development features
1.1.1 20.07.2005 Rupert Stelz, STEMMER Logos changed
IMAGING
GenICam_License_20072005.doc Page 4 of 11
V1.1 License
1 Overview
This document describes in non-legal wording what the GenICam license should state. Once
the GenICam standard group has agreed on this document some attorney will fix the wording
and make the document legally sound.
4 What are the rules for using the runtime version of the reference
implementation?
The runtime version of the reference implementation is available for free to anybody.
Everyone may download the latest version from the GenICam web site anonymously.
The runtime version can is distributed under a modified BSD license:
GenICam_License_20072005.doc Page 5 of 11
V1.1 License
Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
Neither the name of the GenICam standard group nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
In contrast to the BSD license the user may not modify the software except the installation
procedure. This is to make sure only properly tested and released GenICam versions are used in
the machine vision community and the support effort is restricted.
5 What are the rules for using the development version of the
reference implementation?
In order to get access to the development version of the GenICam reference implementation a
company must become associated member of the GenICam standard group. It can do so at no
cost by registering at the EMVA.
By registering the company gets the following benefits:
It can download the GenICam source code and use it for debugging.
1
The original BSD license reads here „with or without modification“.
GenICam_License_20072005.doc Page 6 of 11
V1.1 License
It is placed on the GenICam mailing list and can access the mailing list’s archive.
Through the GenICam mailing list it will receive technical support from the community.
Its name is listed on GenICam’s web site as an associated member.
By registering the company accepts the following obligations:
It may not give the source code to any 3rd party.
It may not do its own GenICam release besides of the official releases provided by the
GenICam standard group.
It may submit bug fixes to the GenICam standard group which will validate them and
provide a new release including the bug fix in a reasonable time-frame. While waiting for
the official bug fixed release the company may provide a self generated patch to its
customers (run-time only). The self generated patch must clearly indicate modifications
against the used official release.
It may submit improvements to the GenICam standard group which will validate them and
add them to the next GenICam release in a reasonable time-frame.
The company must declare any intellectual property owned by it that may conflict with
GenICam specifications. This is part of the application form.
GenICam_License_20072005.doc Page 7 of 11
V1.1 License
At the end of each meeting the contributing members define working packages available for
all companies who want to contribute for the next meeting. These working packages are
designed to put equal burden on each working company and take into account the various
interests and skills of each company. Any associated member can take a working package
and thus become contributing member at the next meeting provided the homework is
properly done. Spare working packages are defined so that companies wanting to join
between meetings can pick it up and become contributing member immediately on the next
meeting if they like.
Each module of the GenICam standard and its reference implementation has one contributing
member assigned to for coordinating the maintenance. This ensures each module’s code
integrity and makes sure that bug fixes and improvements are implemented within reasonable
time frame. In order to release bug fixes fast each of the contributing members can build and
test a GenICam maintenance release.
GenICam_License_20072005.doc Page 8 of 11
V1.1 License
Name:
Title:
Company:
Address:
City: State/Province:
E-mail:
Phone: FAX:
Signature of applicant:
Printed name:
Title:
Our technical competence is considered to be in: (check all areas that apply)
Camera / Camera Control API software
Frame grabber Machine Vision software
Other:
We have or are currently developing a GenICam compliant product: Yes No
GenICam_License_20072005.doc Page 9 of 11
V1.1 License
Type device(s):
Statement of qualification/interest:
Name: E-mail:
Name: E-mail:
Name: E-mail:
Name: E-mail:
GenICam_License_20072005.doc Page 10 of 11
V1.1 License
Standards developed by the EMVA generally should not include the use of a patented item.
However, technical reasons may justify such inclusion. In such cases the EMVA must place
statements from parties to the standard into our records to reflect whether they are a patent
holder or intend to hold any invention or intellectual property rights the use of which would
be required for compliance with the proposed standard, and their intention for exercising such
rights.
For acceptance as an associated member of the GenICam standard group the below listed
company, its officers, or controlling parties declares:
It does not hold and does not currently intend holding any invention or intellectual
property rights the use of which would be required for compliance with the
proposed GenICam standard.
It does hold or do currently intend holding an invention or intellectual property rights
the use of which would be required for compliance with the proposed GenICam
standard. A license will be made available to any and all applicants under the
following terms and conditions:
Signature: Date:
Name: Title:
Company:
GenICam_License_20072005.doc Page 11 of 11
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
Alternative Proxies: