1185 Valkind value Conf for EX FC data
- Created
- 06 Nov 2013
- Status
- In Force (green)Closed: the solution is part of the standard. No further comments are taken. Show the workflow
- Part
- Part 6 (2009-12; Edition 2)
- Links
- None
- Page
- 100
- Clause
- Table 46
- Paragraph
- Category
- Issue may impact interoperability of implementations of Edition 2
Issue
EX functional constrained data is non operational and it should be possible for this type of data to exist in IED configuration (SCL) only as well. Table 46 refers to operational data generally and for non operational data only CF and DC FCs are separately mentioned.
Proposal
Allow Valkind value Conf for EX functional constrained data.
| Discussion | Created |
|---|---|
| In Force (green) | 15 Oct 14 |
|
Ballot Period
For dataNs a valKind=Conf together with a valid name space value is allowed. Rationale: an application either 'knows' the data it needs, or will anyhow ignore it. Humans can look into the SCL file.
For lnNs and ldNs however an online value is a must enabling clients to establish the semantic context. |
11 Sep 14 |