RNA_product_config.yaml

# metamodel_version: 1.7.0# version: 3.0.3id: RNA_product
schema_generating: true
display_name: RNA product
document_category: RNA product
weight: 20
fields:
- id: id
  description: A unique identifier for an entity. Must be either a CURIE shorthand
    for a URI or a complete URI
  display_name: id
- id: iri
  description: An IRI for an entity. This is determined by the id using expansion
    rules.
  display_name: iri
- id: type
  display_name: type
- id: name
  description: A human-readable name for an attribute or entity.
  display_name: name
- id: description
  description: a human-readable description of an entity
  display_name: description
- id: source
  display_name: source
- id: has_attribute
  description: connects any entity to an attribute
  display_name: has attribute
  cardinality: multi
- id: provided_by
  description: The value in this node property represents the knowledge provider that
    created or assembled the node and all of its attributes.  Used internally to represent
    how a particular node made its way into a knowledge provider or graph.
  display_name: provided by
  cardinality: multi
- id: xref
  description: Alternate CURIEs for a thing
  display_name: xref
  cardinality: multi
- id: category
  description: "Name of the high level ontology class in which this entity is categorized.\
    \ Corresponds to the label for the biolink entity type class.\n * In a neo4j database\
    \ this MAY correspond to the neo4j label tag.\n * In an RDF database it should\
    \ be a biolink model class URI.\nThis field is multi-valued. It should include\
    \ values for ancestors of the biolink class; for example, a protein such as Shh\
    \ would have category values `biolink:Protein`, `biolink:GeneProduct`, `biolink:MolecularEntity`,\
    \ ...\nIn an RDF database, nodes will typically have an rdf:type triples. This\
    \ can be to the most specific biolink class, or potentially to a class more specific\
    \ than something in biolink. For example, a sequence feature `f` may have a rdf:type\
    \ assertion to a SO class such as TF_binding_site, which is more specific than\
    \ anything in biolink. Here we would have categories {biolink:GenomicEntity, biolink:MolecularEntity,\
    \ biolink:NamedThing}"
  display_name: named thing_category
  cardinality: multi
- id: trade_name
  description: ''
  display_name: trade name
- id: available_from
  description: ''
  display_name: available from
  cardinality: multi
- id: max_tolerated_dose
  description: The highest dose of a drug or treatment that does not cause unacceptable
    side effects. The maximum tolerated dose is determined in clinical trials by testing
    increasing doses on different groups of people until the highest dose with acceptable
    side effects is found. Also called MTD.
  display_name: max tolerated dose
- id: is_toxic
  description: ''
  display_name: is toxic
- id: has_chemical_role
  description: A role is particular behaviour which a material entity may exhibit.
  display_name: has chemical role
  cardinality: multi
- id: is_metabolite
  description: indicates whether a molecular entity is a metabolite
  display_name: is metabolite
- id: has_biological_sequence
  description: connects a genomic feature to its sequence
  display_name: has biological sequence
- id: in_taxon
  description: connects an entity to its taxonomic classification. Only certain kinds
    of entities can be taxonomically classified; see 'thing with taxon'
  display_name: in taxon
  cardinality: multi
- id: synonym
  description: Alternate human-readable names for a thing
  display_name: synonym
  cardinality: multi