Skip to content

Proteoform lists and line lengths #30

Open

Description

@trishorts

wondering about reading/writing multiple proteoforms. Does a proteoform have to be completely on a single line? if not, is there a line length (like fasta). Does each proteoform have to start with a specific character to know when the thing begins, like ">"?

Activity

  1. rfellers commented on Feb 21, 2018

    @rfellers
    Member

    Excellent question, I've wondered the same thing. I don't believe that the standard addresses this, right? I've always imagined a file with a single ProForma Term on each line, but the idea of a FASTA-like setup is interesting. Would provide a place for metadata ... but honestly, I'm not sure that there would be that much to say about specific proteoforms.

  2. changed the title [-]proteoform lists and line lengths[/-] [+]Proteoform lists and line lengths[/+] on Feb 27, 2018
  3. acesnik commented on Apr 4, 2018

    @acesnik
    Contributor

    This is being discussed here, too: topdownproteomics/ProteoformNomenclatureStandard#11

    Personally, I'm in favor of FASTA-like setup to allow specifying metadata (accessions, ontologies).

  4. acesnik commented on Sep 9, 2018

    @acesnik
    Contributor

    Should we allow the files to be split at 60 characters per line? That could be pretty strange if tags get split in the middle.

    Examples:
    PROTEOFORMPROTEOFORMPROTEOFORMPROTEOFORMPROTEOFORMPROT[Phosp
    ho]EOFORM
    ROTEOFORMPROTEOFORMPROTEOFORMPROTEOFORMPROTEOFORMPROT[mass:7
    9.98]EOFORM

  5. added this to the ProForma 2.0 milestone on Sep 10, 2018
  6. acesnik commented on Nov 25, 2018

    @acesnik
    Contributor

    FASTQ files are never split at 60 characters, so there is precedent for requiring no line breaks. But if we're going to call it a ProForma FASTA file, we should allow line breaks.

  7. rfellers commented on Nov 26, 2018

    @rfellers
    Member

    my 2 cents: One should allow line breaks if we expect people to manually edit these files. Given the specific set of modifications that users might want, I assume this will be the case. That being said, should we allow tags to be broken across 2 lines? That seems messy, but parsers wouldn't really care as we'd just mash everything together

  8. acesnik commented on Nov 26, 2018

    @acesnik
    Contributor

    Despite the mess, I think we should allow tags to be broken across lines. Mashing together worked for all sorts of potatoes last week, so it should work for us here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    QuestionFurther information is requested

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions