Issue 8711: Attributes in a subtype                                                                                                                                                                                 (snp-ftf)
Source: Japan Biological Informatics Consortium (Mr. Martin Senger, martin.senger@gmail.com)
Nature: Uncategorized Issue
Severity: 
Summary:  As I was reading the spec, I found out that attributes in a subtype
are bold and the inherited ones are not.  Would be nice if these
conventions are spelled out somewhere in a 'how to read the spec
section'.


Discussion:


It will probably be also solved by writing the new software conversion
tool, and by re-generating the PSM part of the specification. But I
would not rely on fonts indicating some meaning - they may be
unintentionally changed by formatting the document. The inheritance
is, however, already indicated by text like "defined at ..." that
accompanies every attribute.


Proposed solution:


Reject the issue
Resolution: 
Revised Text: 
Actions taken:
April 26, 2005: received issue
November 1, 2005: closed issue
Discussion: 
Discussion:

It will probably be also solved by writing the new software conversion tool, and by re-generating the PSM part of the specification. But I would not rely on fonts indicating some meaning - they may be unintentionally changed by formatting the document. The inheritance is, however, already indicated by text like "defined at ..." that accompanies every attribute.

Disposition:	Rejected

End of Annotations:=====
s I was reading the spec, I found out that attributes in a subtype
are bold and the inherited ones are not.  Would be nice if these
conventions are spelled out somewhere in a 'how to read the spec
section'.


Discussion:


It will probably be also solved by writing the new software conversion
tool, and by re-generating the PSM part of the specification. But I
would not rely on fonts indicating some meaning - they may be
unintentionally changed by formatting the document. The inheritance
is, however, already indicated by text like "defined at ..." that
accompanies every attribute.


Proposed solution:


Reject the issue