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://OPCFoundation.org/errata
Revision 1.00.04 Highlights
The following table includes the Mantis issues resolved with this revision.
| MantisID | Scope | Summary | Resolution |
| 7843 | Feature | Need to be able to indicate which descriptor describes a given Asset (or FunctionalEntity) | Added a reference Type that links a ACDescriptorType instance to an Asset or FunctionalEntity. |
| 9841 | Clarification | The use of the AddSecurityGroup and AddPushTarget methods is not required | Added text to explain that the illustration are for external SKS, an internal SKS could be configured in any manner. |
| 9803 | Clarification | Hierarchical Assets | Added additional text to point to examples |
| 9846 | Feature | Addition of GDS configuration to an ConnectionManager | Added a field for configuring a list of GDS addresses. Also update the GDS related examples |
| 10131 | Clarification | CM should (or shall) 'remember' and use same name when establishing same connection to an AC | Updated the ConnectionConfigurationSet to describe this in the connection Name Field |
| 10133 | Clarification | The PubSub Model does not expose a state for enable, the EnableCommunicationCmd should explain what is expected | Updated the description to indicate that a successful invocation of the command results in no object in the disabled state, but that the target of Operation might be affected by other factor. |
| 10142 | Errata | Figure 65 needed updating, also text related to GDS needs updating, also text related to besttavailable needs to be updated. | Added text to Clause 13 to include both a GDS and an LDS illustration , also clarified that an Empty /null string indicates the best security policy shall be used that is supported by both the Server and CM |
| 10144 | Errata | Need clarification for ReferenceTypes to be used in folders. | Fixed all FolderType object to have an OptionalPlaceholder that describe the reference type that should be used |
| 10145 | Feature | Provide an alternate to the requirement to always create references from an Endpoint to a Reader/Writer. | Added a variable that can expose a poor mans reference (i.e. an array of browse names that indicates the DatasetRead or DatasetWriter |
| 10161 | Clarification | Clarification on the CommuniationFlowQosDataType | Added text explain that this field is only used in multicast cases, were subscriber have different settings |
| 10264 | Clarification | Need CM event / log reporting for CM-as-a-server | Added text to explain LogRecord requirements in multiple places. |
| 10382 | Clarification | Clarify usage of QosDataType match Part 14 | Updated text to match what is in part 14 |
| 10388 | Clarification | Clarification needed for BestEffort vs. None/Untagged QoS capability. | Updated description to clearly describe QoS setting and it matches what is defined in part 14 |
| 10429 | Feature | Publishing interval in PubSubCommunicationFlowConfigurationType datatype issue | Added an AvailableInterval property to allow a client to prompt for interval that can be used in the selection list |
| 10430 | Clarification | All of the listed eventtype should be referenced from the object type | All EventType defined in the specification are referenced from at least one ObjectType |
| 10444 | Clarification | Subclause D.3.7.5 need more figures and explanation (ControlGroups) | Initial fixes applied, but more might be needed pending review (issue will be closed during RC) |
| 10573 | Feature | Protocol information (ETH,UDP,MQTT, etc. tag) for Publisher/Subscriber capabilities | Added new object to PublisherCapabilities and Subscribercapabilities |
| 10626 | Feature | The mandatory capabilities should allow omitting instance as needed. | Updated all capabilities to be Optional. Some will become mandatory via Profiles. Also removed text describing empty arrays [Note: this is a breaking change] |
| 10721 | Clarification | Which Interfaces are required for Assets? | Updated text to indicate that profiles define what interface are needed in an object to be an Asset (FXAsset definition). |
| 10812 | Errata | Remove the SystemStatusChangeEvent from AC | Removed this event - it is already required in a server and covered by existing server profiles, not needed in our information model |
| 10851 | Errata | Audit Events are missing | Added reference and definition as needed for Audit events |
| 10855 | Clarification | CleanupTimeout: Make usage of time delay period more clear | Changed text to: The time delay is reset to its original value when the Status changes back to Operational.as suggested in mantis issue |