Hi, I think this is really confusing you must not use ## mirGFF3. VERSION 1.1 as top most line in the header. The mirGFF3, should be fully included within the GFF3 specification, otherwise you start a dichotomy with the official GFF3 specification.
The GFF3 specification requires already this type of header:
##gff-version 3.2.1
The GFF version follows the format of 3.#.# in this spec. This directive must be present, must be the topmost line of the file. The version number always begins with 3, the second and third numbers are optional and indicate a major revision and a minor revision respectively.
In top of that you create an header different, while it will be much easier to keep consistency, so instead of ## mirGFF3. VERSION 1.1 it must be ##mirGFF3 1.1. I would even be more keen to see something like ##mir 1.1.
So in my opinion the header for the mirGFF3 files must look like that:
##gff-version 3.2.1
##mirGFF3 1.1
The same with all other header lines, instead of:
## source-ontology: miRBasev21 doi:10.25504/fairsharing.hmgte8
## COLDATA: let7a-5p
it should be:
##source-ontolog: miRBasev21 doi:10.25504/fairsharing.hmgte8
##coldata let7a-5p
I'm really picky because I always met problems using the GFF and GTF formats because many groups have made their own flavour, and tools struggles from one flavour to another one (here a review I have done about it ). This was due because the formats have not not always been well defined and allowed some freedom in their interpretation. I would like as much as possible avoid to end up again in such situation while we have a well defined GFF3 specification.
Hi, I think this is really confusing you must not use
## mirGFF3. VERSION 1.1as top most line in the header. The mirGFF3, should be fully included within the GFF3 specification, otherwise you start a dichotomy with the official GFF3 specification.The GFF3 specification requires already this type of header:
In top of that you create an header different, while it will be much easier to keep consistency, so instead of
## mirGFF3. VERSION 1.1it must be##mirGFF3 1.1. I would even be more keen to see something like##mir 1.1.So in my opinion the header for the mirGFF3 files must look like that:
The same with all other header lines, instead of:
it should be:
I'm really picky because I always met problems using the GFF and GTF formats because many groups have made their own flavour, and tools struggles from one flavour to another one (here a review I have done about it ). This was due because the formats have not not always been well defined and allowed some freedom in their interpretation. I would like as much as possible avoid to end up again in such situation while we have a well defined GFF3 specification.