support PDB format version 3.3 about bioruby HOT 6 OPEN

Are there many PDBs that this issue affects, and are there any workarounds? I am using bioruby to process all the .ent files from wwPDB, and I want to know if I should worry about many of the PDB files.

from bioruby.

112aa28 is a fix.
Careful check of PDB format spec is still needed.

from bioruby.

Hi @ngoto, I'm going to attempt to tackle this as it relates to some of my research. Do you know of anywhere else this is an issue, i.e. anywhere else that the PDB spec may differ?

from bioruby.

Please read PDB official documents provided by wwPDB http://www.wwpdb.org/docs.html

from bioruby.

I was going through the code and noticed that there are some vestigial structures such as TURN that don't seem to exist in the current PDB spec. Should these be removed or kept even though they're deprecated and not used anymore? The same occurs with Pdb_StringRJ even though this isn't used anymore and all occurrences within the official documents are for Pdb_LString.

from bioruby.

For backward compatibility when parsing a file downloaded in the old days, it is good to keep deprecated records if possible.

The "Pdb_StringRJ" is introduced to parse right-justified ID string in helixId, sheetId, and turnId in HELIX, SHEET, and TURN records. In the PDB definition, these are specified as LString(3). If LString(3) is used, these ids should often contain spaces, for example " HA", " HB", " A", " B". PDB spec says that any spaces in LString should be kept, but I think it is unfriendly for uses to show ids begins with spaces, and I've decided to introduce StringRJ to cut the left spaces for convenience.

from bioruby.