385   GetLogicalNodeDirectory and DATA classes

Created: 14 Sep 2006

Status: In Force (green)

Part: Part 7-2 (2003)

Links:

Page: 041

Clause: 09.2.2.3

Paragraph: InstanceName [0..n]

Category: Issue for edition 2 of this part

Issue

The following specification is currently contained in 9.2.2.3 GetLogicalNodeDirectory service response:

"InstanceName [0..n]
The parameter InstanceName shall contain an ObjectName of one requested ACSI class model."

In case of ACSI class equals DATA it is not defined how to handle the nested DATA definitions. E.g., in common data class WYE we have two levels of DATA:

In the logical node MMXU we have two levels of data e.g. (PhV of CDC WYE):

PhV.phsA
PhV.phsB
...

The GetLogicalNodeDirectory should for ACSI class DATA return the instance names of the first DATA level and the partial ObjectReferences of the underlying DATA levels:

Return:
PhV
A
W
...
PhV.PhsA
PhV.PhsB
...
A.PhsA
A.PhsB
...

There may also be a need to add some specification for the GetDataDefinition service. Because the GetDataDefinition operates on the lowest level of a nested DATA definition ... even this is not explicitly said.

Proposal

GetLogicalNodeDirectory Service:

Replace current text:

"InstanceName [0..n]
The parameter InstanceName shall contain an ObjectName of one requested ACSI class model."

by

"InstanceName [0..n]

ACSI class model requested equals DATA-SET, BRCB, URCB, LCB, LOG, SGCB, GoCB, GsCB, MSVCB, or USVCB:

The parameter InstanceName shall contain an ObjectName of the requested class.

ACSI class model requested equals DATA:

The parameter InstanceName shall contain an ObjectName (in case of one level of DATA) or a concatenation of ObjectNames separated by "." (in case of several levels of DATA)."

GetDataDefinition service:

to be discussed.