1457   Multiple DOI nodes with the same name.

Created: 22 Oct 2015

Status: In Force (green)

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


Page: 72

Clause: 1

Paragraph: 2

Category: Issue for edition 2 of this part


Multiple instances of DOI within the <LN> with the same "name" values as follows:

<DOI name="LocSubst">
<DAI name="dataNs">
<Val>VENDOR IEC61850DCS:2013</Val>
<DOI name="LocSubst">
<DAI name="ctlModel">


This should be considered error and a single <DOI> node should be used to provide instances values for all applicable <DAI>. <DAI> instance value should not be scattered in several <DOI>
Provide explicit rules for above, whether valid or not, and in particular, if <DAI> can be scattered over several <DOI> of the same name and what is the action if the same <DAI> appears more than once.

Discussion Created Status
Explicit rules are added to the text of part 6.
Unfortunately the schema can not check all possible combinations, thus the tools must do the checking.
08 Dec 15 In Force (green)
Unfortunately there is no way I know of to address the 2nd issue raised by Thierry.

The uniqueness constraint only works for sub-elements where all optional attributes (without default value) have a value. The W3C standard is quite "clear" on this, see http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#d0e13819

Thus the tools must ensure the uniqueness in case at least one optional attribute (without default value) is not provided.
10 Nov 15 Ballot Period
Multiple DOI for the same name inside the same level (LN) are already considered as an error - see SCL schema constraints.
The same is valid for multiple SDI and multiple DAI. They are only allowed if they have an ix attribute, and in case that several of them with ix attribute exist, with different ix values.
The appropriate constraints will be checked and if necessary and possible be revised in the SCL schema.
04 Nov 15 Ballot Period
There are already constraints in the schema :
scl:uniqueDOIinLN0, and scl:uniqueDOIinLN to cover the first aspect.

scl:uniqueSDI_DAIinSDI to cover the second aspect.
However it seems that this unique constraint using both @name and @ix is not working properly.

27 Oct 15 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.