1170 Name uniqueness within a logical node
- Created
- 04 Oct 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
- 70
- Clause
- 9.3.5
- Paragraph
- Category
- Issue for edition 3 of this part
Issue
There is currently no constraint (neither in Part 6 text nor in SCL XSD) that the direct sub-elements of a logical node (LN or LN0) shall have a unique name.
This means that a report control block, a goose control block and a DOI (for instance) can all have the same name. Then we do not have ACSI reference (Part 7-2) uniqueness anymore.
Note: In the SCL schema there are identity constraints that check that within a logical node the name of ReportControl is unique, the name of a LogControl is unique, the name of a GSEControl is unique, etc.
Proposal
Add this constraint to text of Part 6 as well as to XSD as identity constraint.
The identity constraint applying to specific children (e.g., ReportControl name unicity within an LN) can then be removed.
| Discussion | Created |
|---|---|
| In Force (green) | 14 Nov 13 |
| Ballot Period The issue will be considered as input to part 7-2 Ed.3 and be discussed in the WG. | 28 Oct 13 |
| Discussion (red) The current SCL constraints follow the contstraints defined in 7-2. Thus, an appropriate naming rule needs to be supplied in part 7-2 first. | 16 Oct 13 |
| Discussion (red) The proposal make sense. I would however postponed the change to the next version of the standard. i.e. not 2007 B, but 2007 C, or other. | 14 Oct 13 |