View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009125 | 10000-010: Programs | Spec | public | 2023-08-25 12:45 | 2023-09-26 15:18 |
| Reporter | Jouni Aro | Assigned To | Jim Luth | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 1.05.00 | ||||
| Summary | 0009125: ProgramStateMachineType methods defined as OptionalPlaceholders | ||||
| Description | I am wondering about the method definitions at https://reference.opcfoundation.org/Core/Part10/v105/docs/5.2 It defines that the methods are OptionalPlaceholders, which usually means that there can be any number of such components and there names are usually defined as '<Start>' etc. However, here the methods are defined in a way that resembles normal Optional components. So, the question arises - is the ModellingRule OptionalPlaceholder correct for them or should they just be Optional? If it is correct, some explanation would be necessary to describe how they are expected to be used. The nodeset follows the specification, so should be changed or course, if a change to the spec is to be defined. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
