Agreement of Use
COPYRIGHT RESTRICTIONS
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 FOUNDATION 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.00.03 Highlights
The following table includes the Mantis issues resolved with this revision.
| Mantis ID | Scope | Summary | Resolution |
| 8266 | Clarification | Missing requirement to validate Certificate Revocation List (CRL) | Updated the Revocation List description in Table 3. |
| 9117 | Clarification | Describe how to define configuration of individual variables are constants or stored in non-volatile memory | Added AccessLevelEx to Table A.6. |
| 9214 | Clarification | Table "Mapping UA Base NodeClass attributes to SUC UaMethodNodeClass, BaseObjectType ... attributes" is not updated | Updated chapter A.4 with additions to the content of the OPC UA Base NodeClass and the NodeId attribute in Table A.4. |
| 9231 | Clarification | Handling of nodeids for interfaceclasses of inverse referencetypes | Added to the NodeId row in table A.8: "This Attribute only appears on InterfaceClasses that represent the forward or symmetric Reference ( i.e not on inverse references). " |
| 9264 | Errata | Invalid characters are used in Annex J "DescriptorInfo XML Schema" and Annex K "OpcUaLibInfo Schema" | Corrected the quotation marks used in Annex J and Annex K to use the (U+0022) font. |
| 9322 | Clarification | References using ExplicitNodeId (e.g., NodeId, BrowsePath) are not according to AutomationML concepts | NodeIds are now included in DataTypes with updates to chapter A.7. |
| 9352 | Clarification | Allow RSASSA_PSS padding scheme for Descriptor signatures | Updated the links in Annex I for the CanonicaliationMethod algorithm and the Transform alogorithm to use the RFC 9231 version 1,1. |
| 9449 | Clarification | Addresses the use of BrowsePath that is present and not empty | Updated chapter A.3.7 to explain the use of BrowsePath in a NodeId that is present and not empty and the use of the RootNodeId. Added new paragraph section A.11.5 to show an example of the use of BrowsePath and NodeId. Also, broke paragraph section A.11 in to other sub-sections. |
| 9457 | Clarification | Need to clarify "one manfest" rule in part 83 | This was resolved in Mantis issue 9545 |
| 9514 | Clarification | Structure field information missing in AML | Added text to Part 83 draft in A.11.2 to explain the "OPC:TypeOnly" rules. |
| 9517 | Clarification | Explains how the NodeId relates to a BrowsePath that is empty or not present is identified | Updated chapter A.3.7 to explain how the NodeID relates to a BrowseParth that is empty or not present in identified. |
| 9532 | Clarification | Allow RSASSA_PSS padding scheme for Descriptor signatures | Updated the XML Signature Syntax reference. |
| 9545 | Clarification | Implement recommendations of OPAS-UAFX OE Harmonization group | Updated chapter 7.3.2 to explicitly state there will be exactly one UAFX Descriptor manifest in a Descriptor. Explains how to handle embedded Descriptor manifests from other consortia outside of UAFX. |
| 9561 | Clarification | NodeId of data types are not available for AML attribute types | NodeIds are now included in DataTypes with updates to chapter A.7. |
| 9610 | Clarification | Reference Type Mapping - Which attributes should be used on an instance | Added text to Part 83 draft in A.11.2 to explain the "OPC:TypeOnly" rules. |
| 9613 | Clarification | Usage of the attribute UaNodeNamespaceUri is unclear | Changed the header is column 1 of Table A.4 to “OPC UA Attribute”. Reworded A.3.7.1 QualifiedName DataType |
| 9614 | Clarification | The attribute NodeId isn't marked that it may be included in SystemUnitClass and/or instances | Updated Table A.4 to show the NodId may be included in the SystemUnitClass and/or instances. |
| 9615 | Clarification | Usage of the attribute UaNodeNamespaceUri is unclear | Changed the row heading in Table A.4 from Attribute name to OPC UA Attribute name. UaNodeNamespaceUri is not an OPC UA Attribute name. |
| 9657 | Clarification | Clarify usage of sub-attributes for BrowseName | The handling of BrowseName sub-attributes was updated. |
| 10010 | Clarification | Added text in Table A.4 to DisplayName and Description | DisplayNames and Descriptions included in the server must be present in the AML. Updated the notes column for each. |
| 10011 | Clarification | Review (or define) default values for AccessLevel and AccessLevelEx | Added AccessLevelEx to Table A.6. |
| 10012 | Clarification | Added text in Table A.4 to the WriteMask and AccessRestrictions | The notes in Table A,4 for WriteMask and AccessRestrictions were updated to state the usage more clearly |
| 10013 | Clarification | Clarify usage of EventNotifier attribute | added a statement ay beginning of A.4 on how that check marks in the table should be interpreted. |
| 10014 | Clarification | Clarify usage of ValueRank attribute in AM | Added clarification to the wording for ValueRank in Table A.6. |
| 10155 | Clarification | ValueRank default value differs between Nodeset and AML. | The attribute ValueRank in Table A.7 was changed to -1 to match the ValueRank default value used in the Nodeset file schema. |
| 10271 | Clarification | All Attributes of all InterfaceClasses should be marked "TypeOnly" | Update the Notes in Table A.8 for all attributes except ModelingRule. |