Bug #453
ExtRef definition and the expected semantic of intAddr
Status:
Closed
Priority:
High
Assignee:
-
Category:
Already captured with TISSUE
Start date:
Due date:
% Done:
0%
Estimated time:
ID:
10
Source:
IOP_2013
TF Unique ID:
10 # IOP_2013
WG10 Proposal:
refer to 1402 TISSUE (related to the 1257)
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
Short Proposal:
see ISSUE #36. This should be addressed as well wth the clarification provided by WG10
Standard(s):
IEC 61850-6
Needs More Information:
Assigned TF:
Description
Although 61850-6 allows the standardized expression of an ExtRef, the IntAddr typically associated with it is a proprietary vendor format. Therefore, there is no easy mechanism to express, in a standard way, the semantics expectation of what the ExtRef is to provide or the IntAddr.
The use/specification of ExtRef is not 100% defined.
One SCL tool expects it to be initialized as part of a DOI, others require it to be a DAI.
Updated by Carlos Rodriguez del Castillo about 3 years ago
- Subject changed from Although 61850-6 allows the standardized expression of an ExtRef, the IntAddr typically associated with it is a proprietary vend to ExtRef definition and the expected semantic of intAddr
- Category changed from Standard clarification required to Already captured with TISSUE
- Status changed from New to Closed
- Standard(s) set to IEC 61850-6
- Discuss in Upcoming Meeting set to No
Checking done