441   LN inheritence

Created: 21 Nov 2006

Status: In Force (green)

Part: Part 7-4 (2003)

Links:

Page:

Clause:

Paragraph:

Category: Issue for edition 2 of this part

Issue

In almost all the domain specific classes in Part 7-4, there is a "Common Logical Node Information" clause.

As an example, refer to PDIF in §5.4.2 page 21.

1/ In the clause "Common Logical Node Information" of the class PDIF, it is written that "LN shall inherit all Mandatory Data from Common Logical Node Class". It is true but not complete because inheritence includes as well the optional attributes as the mandatory ones.

2/ In the clause "Common Logical Node Information" of the class PDIF, the attribute OpCntRs is defined.
But it is defined with the same type (INC) and the same multiplicity (Optional) than it is in the inherited class "Common LN".

Proposal

1/ I suggest either to replace the phrase "LN shall inherit all Mandatory Data from Common Logical Node Class" by "LN shall inherit all Data from Common Logical Node Class" or better to suppress the corresponding line.

2/ I suggest to suppress all attribute references for attribute already defined in the inherited class "Common LN" except when multiplicity is modified (restricted).

Discussion Created Status
solved and accepted 14 Feb 08 In Force (green)
see draft of edition 2 24 May 07 Ballot Period
In general accepted.

Proposal is: all mandatory remain in the common LN class, all references and statistical data (optional) will remain in the common LN class, all data, that are very specific for dedicated LN will be taken out because there are already in the specific LNs.
The phrase in each LN will be changed in to "LN shall inherit all Data from Common Logical Node Class".
12 Apr 07 Discussion (red)
Sorry for the delay. We will comment before next editors meeting in Seoul. 16 Mar 07 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1