Class: Serial

This class may rarely be instantiated except if use cases of a given knowledge graph support its utility.

URI: biolink:Serial


Identifier prefixes

  • issn


  • is_a: Publication - Any published piece of information. Can refer to a whole publication, its encompassing publication (i.e. journal or book) or to a part of a publication, if of significant knowledge scope (e.g. a figure, figure legend, or section highlighted by NLP). The scope is intended to be general and include information published on the web, as well as printed materials, either directly or in one of the Publication Biolink category subclasses.

Referenced by class



  • serial➞id 1..1
    • Description: Serials (journals) should have industry-standard identifier such as from ISSN.
    • Range: String
  • serial➞type 1..1
    • Description: Should generally be set to an ontology class defined term for ‘serial’ or ‘journal’.
    • Range: String

Inherited from entity:

  • id 1..1
    • Description: A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI
    • Range: String
    • in subsets: (translator_minimal)
  • iri 0..1
    • Description: An IRI for an entity. This is determined by the id using expansion rules.
    • Range: IriType
    • in subsets: (translator_minimal,samples)
  • category 0..*
    • Description: Name of the high level ontology class in which this entity is categorized. Corresponds to the label for the biolink entity type class.
  • In a neo4j database this MAY correspond to the neo4j label tag.
  • In an RDF database it should be a biolink model class URI. This 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, … In 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}
  • type 0..1
  • description 0..1
    • Description: a human-readable description of an entity
    • Range: NarrativeText
    • in subsets: (translator_minimal)
  • source 0..1
    • Description: a lightweight analog to the association class ‘has provider’ slot, which is the string name, or the authoritative (i.e. database) namespace, designating the origin of the entity to which the slot belongs.
    • Range: LabelType
    • in subsets: (translator_minimal)
  • provided by 0..*
    • Description: connects an association to the agent (person, organization or group) that provided it
    • Range: Agent
  • has attribute 0..*
    • Description: connects any entity to an attribute
    • Range: Attribute
    • in subsets: (samples)

Inherited from information content entity:

Inherited from named thing:

Inherited from publication:

  • authors 0..*
    • Description: connects an publication to the list of authors who contributed to the publication. This property should be a comma-delimited list of author names. It is recommended that an author’s name be formatted as “surname, firstname initial.”. Note that this property is a node annotation expressing the citation list of authorship which might typically otherwise be more completely documented in biolink:PublicationToProviderAssociation defined edges which point to full details about an author and possibly, some qualifiers which clarify the specific status of a given author in the publication.
    • Range: String
  • publication➞pages 0..*
    • Description: When a 2-tuple of page numbers are provided, they represent the start and end page of the publication within its parent publication context. For books, this may be set to the total number of pages of the book.
    • Range: String
  • summary 0..1
    • Description: executive summary of a publication
    • Range: String
  • keywords 0..*
    • Description: keywords tagging a publication
    • Range: String
  • mesh terms 0..*
    • Description: mesh terms tagging a publication
    • Range: Uriorcurie
  • publication➞id 1..1
    • Description: Different kinds of publication subtypes will have different preferred identifiers (curies when feasible). Precedence of identifiers for scientific articles is as follows: PMID if available; DOI if not; actual alternate CURIE otherwise. Enclosing publications (i.e. referenced by ‘published in’ node property) such as books and journals, should have industry-standard identifier such as from ISBN and ISSN.
    • Range: String
  • publication➞name 0..1
    • Description: the ‘title’ of the publication is generally recorded in the ‘name’ property (inherited from NamedThing). The field name ‘title’ is now also tagged as an acceptable alias for the node property ‘name’ (just in case).
    • Range: LabelType
  • publication➞type 1..1
    • Description: Ontology term for publication type may be drawn from Dublin Core types (, FRBR-aligned Bibliographic Ontology (, the MESH publication types (, the Confederation of Open Access Repositories (COAR) Controlled Vocabulary for Resource Type Genres (, Wikidata (, or equivalent publication type ontology. When a given publication type ontology term is used within a given knowledge graph, then the CURIE identified term must be documented in the graph as a concept node of biolink:category biolink:OntologyClass.
    • Range: String

Domain for slot:

  • serial➞id 1..1
    • Description: Serials (journals) should have industry-standard identifier such as from ISSN.
    • Range: String
  • serial➞type 1..1
    • Description: Should generally be set to an ontology class defined term for ‘serial’ or ‘journal’.
    • Range: String

Other properties

Aliases:   journal
In Subsets:   model_organism_database