289   Instatiation of DATA

Created: 07 Feb 2006

Status: In Force (green)

Part: Part 7-2 (2003)

Links:

Page:

Clause: 10 and 19

Paragraph:

Category: Issue for edition 2 of this part

Issue

Part 7-4 GGIO has DATA that can be instatiated, e.g., Ind -> Ind1, Ind2, Ind3, ... This instatiation of DATA is not defined in 7-2.

Proposal

A rule on how to instatiate DATA should be defined in clauses 10 and 19.

Discussion Created Status
Status set to green. 17 Mar 07 In Force (green)
Status changed to final proposal.

Proposed text added to clause 19. 		14 Feb 07 Ballot Period
Accepted. Observe that with introducing the Data name as Data class name you formalize what is already implicitely used in 7-4: a Data name has only one unique semantic, even if used in different LN classes! So also consider to have a 'weak' general semantics specified for a 'Data class' with more details of interpretation added for a usage within a LN class (like already done e.g. with OpCnt). 01 Mar 06 Discussion (red)
In 19.2. / p 157 of 61850-7-2, rules are given that LNName consists of LN-Prefix, LN class name and LN-Instance-ID.

To be consistent, it should be defined that
DataName =Data class name [Data-Instance-ID]
Data class name = up to 10 characters
Data-Instance-ID = n numeric characters, optional; n shall be equal for all instances of the same data
14 Feb 06 Discussion (red)
The rules are defined in 7-4. They belong to the data model, and not to the services, so they should not be repeated in 7-2. May be, that 7-1 can contain a hint to these possibilities. Better however would be some general rules on modeling, which again would fit into 7-4.
I propose to reject to add something in 7-2 		07 Feb 06 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1