1957   The XSD of SCL defines a pattern for DO names that does not allow underscores '_', which appears to

Created: 31 Jan 2025

Status: Verify Draft Implementation

Part: Part 7-2 (2020; Edition 2.1)

Links:

Page: 184

Clause: E.2 Base types

Paragraph: SCL_BaseSimpleTypes.xsd

Issue

LNodeType/DO.name and LN/DOI.name attributes are defined in SCL XSD with the type "tDataName"

tDataName is a simple type with base "tRestrName1stU", and "tRestrName1stU" defines this pattern to follow: "[A-Z][0-9A-Za-z]*"

Thus, data object names containing a underscore "_" character raise XSD validation errors.

On the other hand, in IEC 61850-7-2, DataObjectName is defined as type "ObjectName", which can contain underscores "_"

Proposal

Clarify if data object names can contain underscores (update IEC 61850-7-2 or IEC 61850-6)

Discussion Created Status
Proposed change : Table 44 - Explanation to DataObjectName:
Append the explanation with ";no underscore is allowed in the name.". 		17 Jun 25 Verify Draft Implementation
Proposed change : Table 44 - Explanation to DataObjectName:
Append the explanation with ";no underscore is allowed in the name.". 		13 May 25 Drafting Implementation
please discuss 01 Apr 25 Discussion (red)
This change in 7-2 in DataObjectName should not create a lot of issues, as no ICD/IID files would have been conformant to SCL for DO with Underscores in their name.
Propose to restrict DataObjectName to exclude underscore. 		01 Apr 25 Accepted
Should this be moved/copied as a 7-2 issue to update type of ObjectName? 11 Feb 25 Triage
Putting a less stringent format in future on the DOName will introduce compability problem, as the SCL will create validation error unless the compatibility rules mandate to remove the objects.
Therefore we should restrict the DataObjectName in 7-2 to the tRestrName1stU format to avoidscenario where objects are not interoperable (compatibility rule remove objects) because of their name. 		10 Feb 25 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 25.7.7.1