View Issue Details

IDProjectCategoryView StatusLast Update
0008049Part 81: UAFX Connecting Devices and Information ModelApi Changepublic2022-07-22 13:40
ReporterDavid Fort Assigned ToGeorg Biehler  
PrioritynormalSeveritytrivialReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.00.00 
Summary0008049: 10000-81 clause 9.2.2 awkward grammar
Description

In 10000-81 clause 9.2.2 and several other similar sections, there is a construct like this:

The possible selections and, if entry is allowed, is configured in the engineering tool.....

I find this a difficult sentence to understand.
"selections" is plural, which means "is configured" should be "are configured", but beyond that it I don't understand what it is trying to say.

Is the point that the engineering tool will present the possible selection and (perhaps) allow entry of other choices?

Maybe it could be phrased something like
The engineering tool will present choices for selection, and if allowed, accept entry of other choices.
(and instead of "choices" perhaps the specific thing being chosen or entered could be stated, e.g. "address uri", like "the engineering tool will present Address URIs for selection and if allowed accept entry of other other Address URIs").

Additional Information

This construct is used several places in this area of the spec. maybe searching for ", and if entry" will find them.

(and all this aside, I wonder if saying things get selected or entered in some tool is "in scope" for the spec or whether it should say something more like "this Component of the ServerAddressType can be Written via OPC UA" and not talk about where it actually came from. (and fwiw, I am completely happy to have it say the engineering tool or whatever, because that helps the reader understand the intent - I'm just trying to make sure we are being consistent).

TagsNo tags attached.

Activities

Paul Hunkar

2022-07-15 13:25

manager   ~0017140

reviewed in call - agree that changes are needed.
the selection list has three options , pick from a list , enter something or no choice. the text should be updated as needed

Georg Biehler

2022-07-18 09:54

developer   ~0017144

In an earlier version we had in clause 6.8.1 the following text:

The SelectionListType, as defined in OPC 10000-5, is used in many places, where modification is possibly mandated. This type allows providing values selectable from the Selections and an optional description using SelectionDescriptions.
If the generator set the optional RestrictToList to value True, only values from the list can be applied to the element. With this, the generator of the data may restrict changes by supplying a list of accepted values. As an example, the PublishingInterval could be restricted to the values 2 ms, 4 ms, and 17 ms by adding these values to Selections and set RestrictToList to True.
Setting RestrictToList to value False allows in opposite to apply any value to the element.

Now the text is reduced to:

The SelectionListType (see OPC 10000-5) is used to indicate where support for modifications is required by this specification. The possible selections, and if entry is allowed, is provided by the engineering tool that generated the ConnectionConfigurationSet. The selections may include an optional description.

Updated 6.8.1 as follows:

The SelectionListType (see OPC 10000-5) is used to indicate where support for modifications is required by this specification. This type allows the engineering tool to provide a list of Selections and an optional description of them.
If the engineering tool sets the optional RestrictToList to True, a Client changing the Variable is restricted to the provided Selections. If set to False or missing, a Client may change the Variable to any value including one of the Selections.
As an example, an engineering tool may restrict the PublishingInterval to the values 2 ms, 4 ms, and 8 ms by adding these values to Selections and setting RestrictToList to True.

Cross-referenced the description in 6.8.1 from clauses 9.2.2 and 9.2.3 and updated text there.

Georg Biehler

2022-07-18 09:56

developer   ~0017145

updated 6.8.1, 9.2.2, and 9.3.2

Paul Hunkar

2022-07-22 13:40

manager   ~0017178

reviewed in call agreed to changes and closed issue

Issue History

Date Modified Username Field Change
2022-06-14 14:18 David Fort New Issue
2022-06-14 14:48 David Fort Project FLC Requirements => Part 81: UAFX Connecting Devices and Information Model
2022-06-14 14:48 David Fort Category N/A => Api Change
2022-07-15 13:24 Paul Hunkar Assigned To => Georg Biehler
2022-07-15 13:24 Paul Hunkar Status new => assigned
2022-07-15 13:25 Paul Hunkar Note Added: 0017140
2022-07-18 09:54 Georg Biehler Note Added: 0017144
2022-07-18 09:56 Georg Biehler Status assigned => resolved
2022-07-18 09:56 Georg Biehler Resolution open => fixed
2022-07-18 09:56 Georg Biehler Note Added: 0017145
2022-07-22 13:40 Paul Hunkar Status resolved => closed
2022-07-22 13:40 Paul Hunkar Fixed in Version => 1.00.00
2022-07-22 13:40 Paul Hunkar Note Added: 0017178