Agreement of Use

Any unauthorized use of this specification may violate copyright laws, trademark laws, and communications regulations and statutes. This document contains information which is protected by copyright. All Rights Reserved. No part of this work covered by copyright herein may be reproduced or used in any form or by any means--graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems--without permission of the copyright owner.

OPC Foundation members and non-members are prohibited from copying and redistributing this specification. All copies must be obtained on an individual basis, directly from the OPC Foundation Web site http://www.opcfoundation.org.

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC specifications may require use of an invention covered by patent rights. OPC shall not be responsible for identifying patents for which a license may be required by any OPC specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

WARRANTY AND LIABILITY DISCLAIMERS

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this specification is borne by you.

RESTRICTED RIGHTS LEGEND

This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation,. 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830

COMPLIANCE

The OPC Foundation shall at all times be the sole entity that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials. Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.

Trademarks

Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.

GENERAL PROVISIONS

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

This Agreement shall be governed by and construed under the laws of the State of Minnesota, excluding its choice or law rules.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.

ISSUE REPORTING

The OPC Foundation strives to maintain the highest quality standards for its published specifications; hence they undergo constant review and refinement. Readers are encouraged to report any issues and view any existing errata here: http://www.opcfoundation.org/errata.

Revision 1.05.02 Highlights

The following table includes the major Mantis issues resolved with this revision.

Mantis ID	Scope	Summary	Resolution
2906	Errata	Deprecate Kerberos	Changed status of Issued Token Facets to “deprecated”.
6990	Feature	New Conformance Units used in Node Tables	A number of conformance units have been added to cover all nodes defined in UA parts that define base information elements. A few CUs have been replaced by new CUs. New Facet “Exposes Type System Server Facet” created.
6995	Errata	Create Minimum Client Facet mainly for companion specifications	Created this Facet as suggested. In addition, the Core 2022 Client Facet has been modified to match the requirements for Minimum UA Client and Standard UA Client.
7041	Feature	Add ECC Security Policy	ECC-curve25519 is the required policy for low-end UA applications where security was not required. Added proper conformance units to Nano Server and Minimum Client.
7034	Errata	Client support for unencrypted passwords is mandatory	Split the CU into 2 where one requires encryption of the password and the other does not. The CU that requires encryption is mandatory.
7000	Errata	Clients shall support a deadband filter	Support / use of the absolute deadband filter is now mandatory in the DataChange Subscriber Client Facet.
6538	Feature	Conformance units missing for well defined roles	Added CU “Security Role Well Known Group 2” and “Security Role Well Known Group 3” to cover the remaining user roles.
5938	Errata	Remove limit requirements	All limit requirements have been removed. In case where a functional requirement was implied, this requirement has been transformed into a base functional unit. Added mandatory “documentation” CUs for limits.
4413	Feature	Security Default ApplicationInstance Certificate missing for Clients	Added as mandatory to Core 2022 Client Facet.
6673	Feature	No time synchronization for existing full-featured profiles	Added the time sync Facet to Core Client and Core Server Facets.
7003	Feature	Require OperationLimits for all supported features	The Capability CUs are now mandatory in all facets Core 2022 (Base Info Server Capabilities 2) Node Mgmt 2022 (Base Info Node Mgmt Capabilities) Method 2022 (Method Capabilities) User Role Base 2022 (Base Info Security Role Capabilities) Subscription 2022 (Base Info Server Capabilities Subscriptions) Event Subscr 2022 (Base Info Events Capabilities, Base Info Server Capabilities Subscriptions) Hist Data 2022 (Base Info History Read Capabilities, Base Info History ReadData Capabilities, Base Info History UpdateData Capabilities) Hist Events 2022 (Base Info History ReadEvents Capabilities, Base Info History UpdateEvents Capabilities)
6993	Feature	Require ECC Policy	Either ECC-curve25519 or ECC-nist256 are required for low-end UA applications where security was not required. Added proper conformance units to Nano Server and Minimum Client.
7390	Feature	Add support for server user management	Created a CU for Server and Client and added as optional to the User Role Management Facets.