The dataNs definition in table 12 may be confusing with the extension rules in part 7-4 annex A.6
Part 7-3: "dataNs: The DATA-ATTRIBUTE dataNs shall be included if the name space of the DATA deviates from the definition in the specification in which the LOGICAL-NODE and its DATA are defined."
Part 7-4: "When in a standardised LN, data are missing or for a new LN data are needed, the data names from Clause 6 shall be used if applicable. If no standardised data fulfils the needs for a special
instance of a standardised LN class, a “new” data may be created. ... New Data names shall be marked by a “name space attribute”
Proposal
Clarify/simplify the name spaces rules & definitions:
dataNs: The DATA-ATTRIBUTE dataNs shall be included if the logical node attribute is not defined in IEC 61850-7-4 clause 6
cdcNs: The DATA-ATTRIBUTE cdcNs shall be included if the common data class is not defined in IEC 61850-7-3 clause 7
lnNs: The DATA-ATTRIBUTE lnNs shall be included if the logical node is not defined in IEC 61850-7-4 clause 6
ldNs: The DATA-ATTRIBUTE ldNs shall always be included in the local node LLN0. The value for edition 1 is "IEC 61850-7-4:2003"
This tissue impacts part 7-1, and 7-4 as well.
Discussion
Created
Status
19 May 08
Ballot Period
Please note that the 2nd paragraph of the previous comment is wrong. It should be:
In that case, for the core Power Utility Automation domain, the namespace value is IEC 61850-7-4:2003 and shall be present in the attribute ldNs. The attribute lnNs shall contain the value “NewSpecification>IEC 61850-7-4:2003” where NewSpecification is the name space name specifying the extended LN, which is based on the IEC 61850-7-4:2003 specification. dataNs is not necessary since it inherits the value from lnNs. This means that the concerned data must be specified in the “NewSpecification” document.
The concept of inheritance is explained in 7-1.
08 Apr 08
Discussion (red)
The original issue behind this Tissue was if an existing 7-4 data object is re-used from one existing LN into another existing LN, shall the attribute dataNs be used ?
In that case, for the core Power Utility Automation domain, the namespace value is IEC 61850-7-4:2003 and shall be present in the attribute ldNs. The attributes lnNs and dataNs are not necessary since both (the existing LN and the existing data) are from the same namespace and inherit the value from ldNs. The concept of inheritance is explained in 7-1.
New proposal:
Harmonize the current definition of dataNs in table 12 of 7-3 with the definition of AC_DLN_M in clause 5.
Harmonize 1rst paragraph in Clause 14.4.4 in 7-1 Ed. 1 as well.
28 Mar 08
Discussion (red)
The proposal is wrong except for ldNs. It should be:
dataNs is included if the DATA name space is different to the LN name space. The lnNs is included, if the LN name space is different to the LD name space. The cdcNs is included, if it is different to that CDC name space implied by the LN name space or the DATA name space.