Skip to content

Slot: SequenceFeature ID (feature_id)

Identity unique within this Dataset; supplied by the source or assigned by an explicit profile.

URI: bfs:slot/feature_id

Applicable Classes

Name Description Modifies Slot
SequenceFeature An annotated sequence interval; explicit conversion profiles define its sourc... yes

Properties

Type and Range

Property Value
Range String
Domain Of SequenceFeature

Cardinality and Requirements

Property Value

Notes

  • A mapping whose Datasets can hold hits of several methods forms a hit's feature_id as || 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 |.

Identifier and Mapping Information

Schema Source

Mappings

Mapping Type Mapped Value
self bfs:feature_id
native bfs:feature_id
close gff3:ID

LinkML Source

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
domain_of:
- SequenceFeature
range: string