-
Notifications
You must be signed in to change notification settings - Fork 954
/
LICENSE.txt
47 lines (33 loc) · 1.86 KB
/
LICENSE.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
https://opcfoundation.org/license/source/1.11/index.html
License information for OPC Source Deliverables
A. Introduction
The OPC Foundation provides source code as sample code/reference
implementation. The source code is provided as-is, with no warranty,
support, or misrepresentation of the quality of code.
The OPC Foundation provides communication stacks, sample libraries,
sample applications and utilities. All sources are available either as a
downloadable ZIP file or in a repository on github
(https://github.com/OPCFoundation/ <https://github.com/OPCFoundation/>).
B. License models
The OPC Foundation provides different licenses depending on the
component and on the membership status of the user of the sources. A
single ZIP file or a single repository can contain multiple components
where the sources have different license models. The valid license is in
the header of each source file.
Following are basic rules on how the OPC Foundation licenses the
different components:
1. OPC UA core components (OPC UA Stacks, OPC UA Local Discovery Server
- LDS) follow a dual-license model:
* *OPC Foundation Corporate Members*: RCL
<https://opcfoundation.org/license/rcl.html>
enables OPC Foundation corporate members to deploy their
applications using the core component sources without being
required to disclose the application code.
* *Users that are not OPC Foundation corporate-members*: GPL 2.0
<https://opcfoundation.org/license/gpl.html>
Based on the GPL 2.0 license terms these users must disclose
their application code when using the core component sources.
2. Samples and Utilities:
All samples and most of the utilities are provided under the MIT
license <https://opcfoundation.org/license/mit.html> for OPC
Foundation Members and Non-Members.