Open GoogleCodeExporter opened 8 years ago
Further investigation shows that we thought about this but decided otherwise.
Documentation:
<xsd:complexType name="ProteinDetectionHypothesisType">
<xsd:annotation>
<xsd:documentation>A single result of the ProteinDetection analysis (i.e. a protein).</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="IdentifiableType">
<xsd:sequence>
<xsd:element name="PeptideHypothesis" type="PeptideHypothesisType" maxOccurs="unbounded"/>
<xsd:group ref="ParamGroup" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Scores or parameters associated with this ProteinDetectionHypothesis e.g. p-value</xsd:documentation>
</xsd:annotation>
</xsd:group>
</xsd:sequence>
<xsd:attribute name="dBSequence_ref" type="xsd:string">
<xsd:annotation>
<xsd:documentation>A reference to the corresponding DBSequence entry. This optional and redundant, because the PeptideEvidence elements referenced from here also map to the DBSequence. </xsd:documentation>
</xsd:annotation>
Making this attribute optional seems rather odd, since it forces readers to
look at PeptideHypothesis_ref instead. However, for now code will have to do
this.
Original comment by andrewro...@googlemail.com
on 23 Jan 2013 at 3:31
Discussed at PSI2013 - decision to make an update to the specification
document, encouraging exporters to include the attribute, but noting that
reading software will have to check for the attribute and otherwise read it
from PeptideEvidence.
ACTION: Andy to draft update to spec doc.
Issue will be closed when the spec doc update has been made
Original comment by andrewro...@googlemail.com
on 17 Apr 2013 at 12:19
Original issue reported on code.google.com by
andrewro...@googlemail.com
on 2 Nov 2012 at 11:03