Skip to content

Class: SequenceFeature (SequenceFeature)

An annotated sequence interval; explicit conversion profiles define its source representation.

URI: bfs:class/SequenceFeature

 classDiagram
    class SequenceFeature
    click SequenceFeature href "../../classes/SequenceFeature/"
      SequenceFeature : attributes





        SequenceFeature --> "*" Attribute : attributes
        click Attribute href "../../classes/Attribute/"



      SequenceFeature : coordinate_system





        SequenceFeature --> "1" CoordinateSystemEnum : coordinate_system
        click CoordinateSystemEnum href "../../enums/CoordinateSystemEnum/"



      SequenceFeature : dbxref

      SequenceFeature : end

      SequenceFeature : feature_id

      SequenceFeature : generated_by

      SequenceFeature : is_representative

      SequenceFeature : is_selected

      SequenceFeature : location





        SequenceFeature --> "0..1" FeatureLocation : location
        click FeatureLocation href "../../classes/FeatureLocation/"



      SequenceFeature : method





        SequenceFeature --> "0..1" MethodEnum : method
        click MethodEnum href "../../enums/MethodEnum/"



      SequenceFeature : name

      SequenceFeature : note

      SequenceFeature : ontology_term

      SequenceFeature : parent





        SequenceFeature --> "*" SequenceFeature : parent
        click SequenceFeature href "../../classes/SequenceFeature/"



      SequenceFeature : phase

      SequenceFeature : product

      SequenceFeature : product_source

      SequenceFeature : score

      SequenceFeature : score_type





        SequenceFeature --> "0..1" ScoreTypeEnum : score_type
        click ScoreTypeEnum href "../../enums/ScoreTypeEnum/"



      SequenceFeature : seqid

      SequenceFeature : source

      SequenceFeature : source_files

      SequenceFeature : stable_identifiers

      SequenceFeature : start

      SequenceFeature : strand





        SequenceFeature --> "0..1" StrandEnum : strand
        click StrandEnum href "../../enums/StrandEnum/"



      SequenceFeature : target





        SequenceFeature --> "0..1" AlignmentTarget : target
        click AlignmentTarget href "../../classes/AlignmentTarget/"



      SequenceFeature : translated_sequence

      SequenceFeature : type

Slots

Name Cardinality and Range Description Inheritance
feature_id 1
String
Identity unique within this Dataset; supplied by the source or assigned by an... direct
stable_identifiers *
String
Identifiers an authority assigns to this feature and keeps across releases, a... direct
seqid 1
String or 
Contig or 
SequenceFeature
The reference sequence that start and end are measured along, such as GFF3 co... direct
source 0..1
String
GFF3 column 2, the producing tool and version, e direct
type 0..1
String
GFF3 column 3, nominally a Sequence Ontology term or accession direct
method 0..1
MethodEnum
The annotation method or reference database whose search produced this featur... direct
start 1
Integer
1-based inclusive start; when location is present this is only the minimum re... direct
end 1
Integer
1-based inclusive end, always >= start; when location is present this is only... direct
coordinate_system 1
CoordinateSystemEnum
Which coordinate space start/end are measured in direct
score 0..1
Float
GFF3 column 6 direct
score_type 0..1
ScoreTypeEnum
What kind of number score is direct
strand 0..1
StrandEnum
GFF3 column 7 direct
phase 0..1
Integer
GFF3 column 8 direct
parent *
SequenceFeature
GFF3 column-9 Parent tag(s) direct
attributes *
Attribute
Additional source annotations, metadata, and evidence, including GFF tags not... direct
generated_by 0..1
String
The workflow execution (or tool run) that produced this ContigCollection, Con... direct
source_files *
uri
Source artifact URLs supporting this record, including any annotation sidecar... direct
is_selected 0..1
Boolean
Whether the annotation pipeline chose this call as canonical for its locus direct
is_representative 0..1
Boolean
Whether the source names this transcript as its gene's representative isoform... direct
product 0..1
String
Human-readable functional product name for a gene, e direct
product_source 0..1
String
What justified the product call, e direct
name 0..1
String
Human-readable name, not an identifier and not unique: for a contig collectio... direct
note *
String
GFF3 Note values, free-text remarks about the feature, in source order direct
dbxref *
String
GFF3 Dbxref values, db:id references to records in other databases, in source... direct
ontology_term *
String
GFF3 Ontology_term values, ontology term CURIEs such as GO:0003677, in source... direct
translated_sequence 0..1
String
Amino-acid translation of a CDS feature, from the workflow's protein FASTA ou... direct
location 0..1
FeatureLocation
Explicit location parts; parent links and BED drawing blocks are separate con... direct
target 0..1
AlignmentTarget
Where this hit aligns on the thing it matched; absent for features that are n... direct

Usages

used by used in type used
Dataset features range SequenceFeature
SequenceFeature seqid any_of[range] SequenceFeature
SequenceFeature parent range SequenceFeature
LocationPart seqid any_of[range] SequenceFeature

Rules

Rule Applied Preconditions Postconditions Elseconditions
slot_conditions {'score_type': {'value_presence': 'PRESENT'}} {'score': {'value_presence': 'PRESENT'}}

Notes

  • Used for both gene/CDS-level calls and for finer-grained per-database evidence hits (Pfam, COG, CATH-FunFam, SUPERFAMILY, KO, EC) that a functional annotation pipeline reports about a gene, linked via parent rather than a second, parallel class. See docs/columns-and-discretion.md section 5 for the non-GFF formats (EC, KO, CRISPR Terms) this same class also holds.

Identifier and Mapping Information

Schema Source

Mappings

Mapping Type Mapped Value
self bfs:SequenceFeature
native bfs:SequenceFeature
close SO:0000110

LinkML Source

Direct

name: SequenceFeature
description: An annotated sequence interval; explicit conversion profiles define its
  source representation.
title: SequenceFeature
notes:
- Used for both gene/CDS-level calls and for finer-grained per-database evidence hits
  (Pfam, COG, CATH-FunFam, SUPERFAMILY, KO, EC) that a functional annotation pipeline
  reports about a gene, linked via `parent` rather than a second, parallel class.
  See docs/columns-and-discretion.md section 5 for the non-GFF formats (EC, KO, CRISPR
  Terms) this same class also holds.
from_schema: https://w3id.org/ber-data/feature-schemas
close_mappings:
- SO:0000110
slots:
- feature_id
- stable_identifiers
- seqid
- source
- type
- method
- start
- end
- coordinate_system
- score
- score_type
- strand
- phase
- parent
- attributes
- generated_by
- source_files
- is_selected
- is_representative
- product
- product_source
- name
- note
- dbxref
- ontology_term
- translated_sequence
- location
- target
slot_usage:
  feature_id:
    name: feature_id
    identifier: true
  name:
    name: name
    exact_mappings:
    - gff3:Name
    - biolink:name
rules:
- preconditions:
    slot_conditions:
      score_type:
        name: score_type
        value_presence: PRESENT
  postconditions:
    slot_conditions:
      score:
        name: score
        value_presence: PRESENT
  description: A score_type qualifies a score, so it needs one (issue 46).

Induced

name: SequenceFeature
description: An annotated sequence interval; explicit conversion profiles define its
  source representation.
title: SequenceFeature
notes:
- Used for both gene/CDS-level calls and for finer-grained per-database evidence hits
  (Pfam, COG, CATH-FunFam, SUPERFAMILY, KO, EC) that a functional annotation pipeline
  reports about a gene, linked via `parent` rather than a second, parallel class.
  See docs/columns-and-discretion.md section 5 for the non-GFF formats (EC, KO, CRISPR
  Terms) this same class also holds.
from_schema: https://w3id.org/ber-data/feature-schemas
close_mappings:
- SO:0000110
slot_usage:
  feature_id:
    name: feature_id
    identifier: true
  name:
    name: name
    exact_mappings:
    - gff3:Name
    - biolink:name
attributes:
  feature_id:
    name: feature_id
    description: Identity unique within this Dataset; supplied by the source or assigned
      by an explicit profile.
    title: SequenceFeature ID
    notes:
    - A mapping whose Datasets can hold hits of several methods forms a hit's feature_id
      as <source ID>|<method>|<type> and keeps the source ID in attributes (https://github.com/turbomam/feature-table-corpus/issues/98).
      Hit files from different methods reuse one source ID for hits on the same span
      (1,138 IDs in one IMG isolate's seven files, counted 2026-09-28), so the bare
      ID would collide. The IMG per-method mapping and nmdc-lakehouse use this form.
      nmdc-pfam-protein reads one Pfam file, whose IDs are unique, and keeps the source
      ID as feature_id.
    - Uniqueness is a rule for the Dataset, not a property of sources. Older NMDC
      annotation runs repeat an ID within one file. In nmdc:wfmgan-12-2h43v434.1's
      Functional Annotation GFF, an INFERNAL misc_feature on + and a GeneMark CDS
      on - both have ID=Ga0495594_0816865_1_525, because the ID encodes the interval
      and not the strand (checked 2026-09-23; https://github.com/turbomam/feature-table-corpus/issues/38).
      Every mapping here validates its Dataset, so such a file is refused as "duplicate
      feature_id". nmdc-lakehouse instead qualifies a repeated ID with its strand,
      as <ID>|<strand>.
    from_schema: https://w3id.org/ber-data/feature-schemas
    close_mappings:
    - gff3:ID
    rank: 1000
    identifier: true
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
    required: true
  stable_identifiers:
    name: stable_identifiers
    description: Identifiers an authority assigns to this feature and keeps across
      releases, as opposed to feature_id, which only needs to be unique within this
      Dataset.
    title: Stable identifiers
    notes:
    - Added for https://github.com/turbomam/feature-table-corpus/issues/44. The AgBioData
      GFF3 recommendations advise "NOT using the ID attribute to specify the globally
      unique, persistent identifier", and NCBI says its GFF3 IDs are "not intended
      to be used as stable feature identifiers" (both read 2026-09-23). feature_id
      stays the file-local key.
    - Use a CURIE when a prefix exists, such as an NCBI GeneID. A locus tag has no
      registered prefix and is written as it appears. In the vendored RefSeq file
      corpus/sources/ncbi-refseq/NC_003888.3_2026-09-21.gff3, the gene with current
      locus tag SC_RS27595 also carries old_locus_tag SCO5087; list the current and
      legacy locus tags. That file has no GeneID Dbxrefs (checked 2026-09-25).
    - NMDC annotation files carry no such identifier for their own genes. The IMG
      gene oid in the KO and EC files (column 2 of Annotation KEGG Orthology, subject_gene_ids
      in KO_EC Annotation GFF) identifies the reference gene the query was aligned
      to, not the annotated gene, so it does not belong here. Checked 2026-09-25 on
      nmdc:wfmgan-11-grwgtd27.2, where both files give 2776147680 for the hit of nmdc:wfmgan-11-grwgtd27.2_0016_3_1208.
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
    multivalued: true
  seqid:
    name: seqid
    description: The reference sequence that start and end are measured along, such
      as GFF3 column 1 or BED chrom; interpreted within its assembly context. A contig
      for contig coordinates; for protein coordinates, the CDS whose translation they
      count residues of.
    title: Sequence ID
    notes:
    - Decided 2026-09-28 (https://github.com/turbomam/feature-table-corpus/issues/40);
      before, a protein-coordinate hit named its contig. GFF3 defines column 1 as
      the landmark that establishes the coordinate system, and NMDC's hit files put
      the protein there. docs/protein-coordinates.md gives the rule, queries, and
      the alternatives considered.
    - A protein-coordinate feature's parent is the same CDS. LocationPart.seqid stays
      a Contig.
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:seqid
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    - LocationPart
    range: string
    required: true
    any_of:
    - range: Contig
    - range: SequenceFeature
  source:
    name: source
    description: GFF3 column 2, the producing tool and version, e.g. "Prodigal v2.6.3_patched".
    title: Source
    notes:
    - Measured 2026-09-11 across 14 real NMDC GFF file types, blank in 3 of them (SMART,
      TIGRFAM, COG). A blank value is expected, not an error.
    - Confirmed 2026-09-18 on a real run, a workflow's own Annotation Info File sidecar
      names the exact database versions (e.g. "TIGRFAM v15.0", "SMART 01_06_2016")
      even where the individual GFF's own source column is empty; use `generated_by`
      plus that sidecar for full provenance when this is blank.
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:source
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
  type:
    name: type
    description: GFF3 column 3, nominally a Sequence Ontology term or accession.
    title: Type
    notes:
    - Range left as a plain string rather than SO-constrained. Measured 2026-09-11,
      7 of 14 real NMDC GFF file types put a bare database accession here instead
      (Pfam, COG, TIGRFAM, SMART, and others); an SO-constrained range would reject
      real production data. Unresolved from the 2026-09-11 kickoff, whether CURIEs
      should be required going forward even though today's data does not comply.
    - Confirmed 2026-09-18, the inconsistency runs both directions. A real RFAM/INFERNAL
      ncRNA hit used the generic term "misc_feature" here and put its actual identity
      (an Rfam covariance model accession) in a lowercase `model`/`accession` attribute
      pair instead, an accession where an SO term is expected in one case, a generic
      placeholder where an accession would be more specific in another.
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:type
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
  method:
    name: method
    description: The annotation method or reference database whose search produced
      this feature, such as Pfam or KEGG Orthology.
    title: Method
    notes:
    - Distinct from source, which is the tool and version (GFF3 column 2), and from
      generated_by, which is the run. Set it on evidence hits; leave it unset on gene
      and RNA calls, where source already names the caller.
    - feature_id has no required format, which is why method is a separate slot to
      filter on. The IMG per-method mapping forms a hit's feature_id as <source ID>|<method>|<type>
      (https://github.com/turbomam/feature-table-corpus/issues/98), and when method
      is set on such a hit it equals that middle part, except that the IMG TMHMM and
      SignalP mapping writes the file suffixes tmh and cleavage_sites there. The hand-built
      NMDC example in model/examples/one-biosample-sequencing/harmonized.yaml ends
      hit IDs in source-specific suffixes such as _pfam and _cath instead, which are
      not always MethodEnum values (_cath is cath_funfam), so a method taken from
      a feature_id needs mapping.
    - Added 2026-10-05 so one table can hold every method's hits and still be filtered
      or partitioned by method. Before it, the method was only inside feature_id,
      and scripts/img_per_method_gff.py and nmdc-lakehouse spelled SUPERFAMILY hits
      differently (supfam and superfamily).
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: MethodEnum
  start:
    name: start
    description: 1-based inclusive start; when location is present this is only the
      minimum reported part coordinate, not a claim that gaps are occupied.
    title: Start
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:start
    - biolink:start_coordinate
    close_mappings:
    - faldo:begin
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    - LocationPart
    range: integer
    required: true
    minimum_value: 1
  end:
    name: end
    description: 1-based inclusive end, always >= start; when location is present
      this is only the maximum reported part coordinate.
    title: End
    comments:
    - Cross-field comparison is enforced by scripts/validate_closed.py for Dataset
      instances.
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:end
    - biolink:end_coordinate
    close_mappings:
    - faldo:end
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    - LocationPart
    range: integer
    required: true
    minimum_value: 1
  coordinate_system:
    name: coordinate_system
    description: Which coordinate space `start`/`end` are measured in.
    title: Coordinate system
    notes:
    - Added 2026-09-18 after measuring a real functional-annotation hit against its
      own parent's translated protein length, a Pfam hit on a 159-residue protein
      reported start=61, end=136, alignment_length=76 (matching end-start+1 exactly
      in amino acids, not nucleotides), so the hit's coordinates are protein-relative
      while its parent CDS's own start/end are contig-relative. A table mixing both
      kinds of row without this field would silently let one be misread as the other.
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: CoordinateSystemEnum
    required: true
  score:
    name: score
    description: GFF3 column 6.
    title: Score
    notes:
    - The GFF3 specification itself says the semantics of the score are ill-defined.
      Meaning is tool-specific (an HMMER bit score, a Prodigal confidence value, and
      so on); do not compare scores across different `source` values.
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:score
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: float
  score_type:
    name: score_type
    description: What kind of number score is.
    title: Score type
    notes:
    - Added for https://github.com/turbomam/feature-table-corpus/issues/46, so an
      e-value and a bit score are not mistaken for each other. Each value maps to
      an EDAM data term.
    - Leave it unset when no source states what the score means. Unset says the meaning
      is not recorded, not that the score is generic.
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: ScoreTypeEnum
  strand:
    name: strand
    description: GFF3 column 7.
    title: Strand
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:strand
    - biolink:strand
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    - LocationPart
    range: StrandEnum
  phase:
    name: phase
    description: GFF3 column 8. One of 0, 1, 2; only meaningful when type is CDS.
    title: Phase
    notes:
    - Measured 2026-09-11, 366 of 368 real values are 0, so a handler that mishandles
      1 and 2 will still pass almost all real-data testing.
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:phase
    - biolink:phase
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: integer
    minimum_value: 0
    maximum_value: 2
  parent:
    name: parent
    description: GFF3 column-9 Parent tag(s).
    title: Parent
    notes:
    - Multivalued because one feature can belong to several parents, such as an exon
      shared by multiple transcripts. This differs from a discontinuous feature, which
      repeats the same ID across multiple GFF3 lines.
    - The 2026-09-17 BRIDGE discussion confirmed that this relationship does not have
      to be flattened into a join table.
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:Parent
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: SequenceFeature
    multivalued: true
  attributes:
    name: attributes
    description: Additional source annotations, metadata, and evidence, including
      GFF tags not given their own slots.
    title: Attributes
    notes:
    - See the Attribute class description for why this stays generic rather than typed.
    from_schema: https://w3id.org/ber-data/feature-schemas
    close_mappings:
    - gff3:attributes
    rank: 1000
    list_elements_ordered: true
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: Attribute
    multivalued: true
    inlined: true
    inlined_as_list: true
  generated_by:
    name: generated_by
    description: The workflow execution (or tool run) that produced this ContigCollection,
      Contig or SequenceFeature.
    title: Generated by
    notes:
    - Confirmed 2026-09-18 against a real biosample's full sequencing, a Contig and
      the Features on it typically come from two DIFFERENT workflow executions, not
      one. A metagenome assembly workflow (e.g. nmdc:wfmgas-11-19jh9v28.1) produces
      the Contig; a separate annotation workflow run against that assembly (e.g. nmdc:wfmgan-11-5xxrm214.2)
      produces the SequenceFeature rows on it. Do not assume one workflow execution
      id covers both.
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - Contig
    - ContigCollection
    - SequenceFeature
    range: string
  source_files:
    name: source_files
    description: Source artifact URLs supporting this record, including any annotation
      sidecars used.
    title: Source files
    notes:
    - A sidecar may come from a different workflow than generated_by, for example
      annotation lineage on an assembled Contig. Preserve each artifact's workflow
      in its URL or manifest.
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - Contig
    - ContigCollection
    - SequenceFeature
    range: uri
    multivalued: true
  is_selected:
    name: is_selected
    description: Whether the annotation pipeline chose this call as canonical for
      its locus.
    title: Is selected
    notes:
    - Measured 2026-09-18, Structural Annotation GFF (the roll-up) contains only the
      Prodigal calls for a locus where both Prodigal and GeneMark called competing
      boundaries, even though both tools' calls exist as separate DataObjects. Without
      this field, a table holding both calls has no way to say which is canonical,
      and naively adding the roll-up as a third source would silently duplicate the
      Prodigal rows. See model/examples/one-biosample-sequencing/ for the worked case.
    - 'Open question, found 2026-09-18 in that same worked case: is_selected=false
      does not always mean "a competing caller won". One real Prodigal call there
      (nmdc:wfmgas-11-19jh9v28.1_scf_1_c1_3_65) had no GeneMark call at all for the
      same locus, and still did not appear in the roll-up, most plausibly filtered
      for length or confidence. This schema does not yet distinguish "lost to a competitor"
      from "filtered despite no competitor"; a future revision may need a second field,
      or an enum instead of a boolean.'
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: boolean
  is_representative:
    name: is_representative
    description: Whether the source names this transcript as its gene's representative
      isoform, the one to use when a query wants a single transcript per gene.
    title: Is representative
    notes:
    - Phytozome writes longest=1 on one mRNA per gene and longest=0 on the others.
      In Athaliana_167_TAIR10.gene_exons.gff3, downloaded 2026-09-25, 27,416 of 35,386
      mRNA rows have longest=1, one for each gene. Despite the key name the flag is
      Phytozome's choice and not a length rule. In 16 of the 5,804 genes with more
      than one isoform, the flagged mRNA does not have the longest CDS (docs/phytozome-dialects.md).
      Other sources mark the same idea differently. Ensembl GFF3 lists Ensembl_canonical
      as one of the comma-separated values of an mRNA's tag attribute.
    - Unset means the source does not say. Set false only where the source says so,
      as Phytozome's longest=0 does. A marked feature needs a parent, its gene, and
      a gene has at most one representative; the Dataset validator checks both. Type
      names vary by source (mRNA, transcript, lnc_RNA; gene, ncRNA_gene, pseudogene),
      so the validator recognizes the gene by structure, as a top-level feature with
      no parent of its own, not by type.
    - Different from is_selected, which records which competing call an annotation
      pipeline kept for a locus, not which of a gene's isoforms stands for it (https://github.com/turbomam/feature-table-corpus/issues/48).
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: boolean
  product:
    name: product
    description: Human-readable functional product name for a gene, e.g. "transposase".
    title: Product
    notes:
    - Populated once, on the gene-level feature; not repeated per functional-evidence
      hit.
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
  product_source:
    name: product_source
    description: What justified the product call, e.g. a COG accession or "Hypo-rule
      applied".
    title: Product source
    notes:
    - Measured 2026-09-18, identical byte for byte to the parallel Product Names sidecar
      file for every protein-coding gene checked so far. Use this slot or that file,
      never both, so the same product assignment is never recorded twice under two
      different provenance stories.
    - Not for RNA rows. There, Product Names carries a third-column label such as
      rRNA_28S or tRNA where the Functional Annotation GFF has no product_source,
      across 50 NMDC runs (measured in nmdc-lakehouse 2026-09-23, not re-checked here;
      https://github.com/turbomam/feature-table-corpus/issues/38).
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
  name:
    name: name
    description: 'Human-readable name, not an identifier and not unique: for a contig
      collection an organism and strain or a bin label; for a feature the GFF3 Name,
      its display name.'
    title: Name
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:Name
    - biolink:name
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - ContigCollection
    - SequenceFeature
    range: string
  note:
    name: note
    description: GFF3 Note values, free-text remarks about the feature, in source
      order.
    title: Note
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:Note
    rank: 1000
    list_elements_ordered: true
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
    multivalued: true
  dbxref:
    name: dbxref
    description: GFF3 Dbxref values, db:id references to records in other databases,
      in source order. Unlike stable_identifiers, a cross-reference can point at a
      related record rather than at this feature itself, such as a GeneID on a CDS.
    title: Database cross-reference
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:Dbxref
    broad_mappings:
    - biolink:xref
    rank: 1000
    list_elements_ordered: true
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
    multivalued: true
  ontology_term:
    name: ontology_term
    description: GFF3 Ontology_term values, ontology term CURIEs such as GO:0003677,
      in source order.
    title: Ontology term
    notes:
    - name, note, dbxref and ontology_term hold the GFF3 reserved tags of the same
      names (https://github.com/turbomam/feature-table-corpus/issues/43). gff3-contig
      fills them and keeps every occurrence in attributes as well, as it does for
      ID, Parent and product; export refuses a SequenceFeature whose typed and generic
      copies disagree. Measured 2026-09-28 across the 51 GFF files in corpus/, Name
      is on 21,240 rows and never repeated, Note on 412, Dbxref on 8,315 (182 rows
      with more than one), and Ontology_term on 4,750 (3,567 with more than one).
      Alias and Derives_from occur in none of them, so they stay in attributes.
    from_schema: https://w3id.org/ber-data/feature-schemas
    exact_mappings:
    - gff3:Ontology_term
    rank: 1000
    list_elements_ordered: true
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
    multivalued: true
  translated_sequence:
    name: translated_sequence
    description: Amino-acid translation of a CDS feature, from the workflow's protein
      FASTA output.
    title: Translated sequence
    notes:
    - Not available anywhere else in structured form; GFF files reference a CDS by
      coordinate but never carry its sequence.
    - Confirmed 2026-09-18, this can legitimately be absent even for a real gene call.
      One short, partial Prodigal call had no entry at all in Annotation Amino Acid
      FASTA, apparently filtered before translation; treat a missing value as informative,
      not as a data gap to fill in.
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: string
  location:
    name: location
    description: Explicit location parts; parent links and BED drawing blocks are
      separate concepts.
    from_schema: https://w3id.org/ber-data/feature-schemas
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: FeatureLocation
    inlined: true
  target:
    name: target
    description: Where this hit aligns on the thing it matched; absent for features
      that are not alignments.
    title: Alignment target
    from_schema: https://w3id.org/ber-data/feature-schemas
    close_mappings:
    - gff3:Target
    rank: 1000
    owner: SequenceFeature
    domain_of:
    - SequenceFeature
    range: AlignmentTarget
    inlined: true
rules:
- preconditions:
    slot_conditions:
      score_type:
        name: score_type
        value_presence: PRESENT
  postconditions:
    slot_conditions:
      score:
        name: score
        value_presence: PRESENT
  description: A score_type qualifies a score, so it needs one (issue 46).