1318   SSD will not validate against XSD

Created: 15 Oct 2014

Status: In Force (green)

Part: Part 6 (2009-12; Edition 2)

Links:

Page: 52

Clause: 9.2.6

Paragraph: Note 2

Category: Issue for edition 2 of this part

Issue

Although Note 2 allows the same LNode to be used within a substation section for a SSD, the XSD does not. This means a SSD will not validate against the schema if the same LNode is used more than once in the substation section.


Proposal

The XSD needs to be changed in order that XML validation can occur against an XSD.

Discussion Created Status
17 Apr 15 In Force (green)
Accepted that the Note 2 part about functional naming is misleading. This should be removed and replaced by a Note 3 about application-related naming (see also 8.5.4).
Reason: see texts below 		12 Mar 15 Ballot Period
Note that with Edition 2 and Ed.2.1 this can be avoided completely by using Function / SubFunction elements.If we take the PTOC example, one instance could be ander Function name=OCstep1, the second under Function name=OCstep2. 20 Nov 14 Discussion (red)
There is a 3rd solution. As mentioned in the SSD file defintion (clause 7 - SCL description file types)
"If logical nodes allocated to the Substation section are not already allocated to an IED, the IED name reference (value of iedName attribute of the LNode element) shall be None."

Here obviously, we need several virtual IEDs to model the specification of a substation, and "None" can not be used.

The engineering process in part 6 should forseen the case and force the specification of several virtual IEDs to maintain the uniqueness of the LNode in the substation section and therefore restrict the use of "None" to specification where the uniqueness of LNode is granted.
20 Oct 14 Discussion (red)
There are two issues with this:
1. a logical node from an IED can be assigned only once to the Substation section. This is clearly stated in the restrictions of 9.2.6 above Note 2.
2. as consequence logical nodes of a pure specification (iedName="None") having identical lnClass need to differentiate in some other value as stated in Note 2. This is checked in the SCL schema.

Accepted that the Note 2 part about functional naming is misleading. This should be removed and replaced by a Note 3 about application-related naming (see also 8.5.4). 		15 Oct 14 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 24.12.6.1