Ontology

edam.operation

EDAM Operation

A function that processes a set of inputs and results in a set of outputs, or associates arguments (inputs) with values (outputs). Special cases are: a) An operation that consumes no input (has no input arguments). Such operation is either a constant function, or an operation depending only on the underlying state. b) An operation that may modify the underlying state but has no output. c) The singular-case operation with no input or output, that still may modify the underlying state.

ontology
D44

FAIR 30/48

Version 1.2

Evaluated 26 Oct 2026

How scores work

Source & access

Homepageedamontology.org Repositorygithub.com DownloadCanonical file / PURL

Automated evaluation

F Findable FAIR1/12
  • Persistent identifier (F1)no PURL / w3id / DOI for the artefact0
  • Indexed in services (F4)1: Bioregistry+1
  • Citable reference (F2)no reference publication listed0
A Accessible FAIR12/12
  • Homepage reachableHTTP 200+3
  • Artefact retrievable over HTTP(S) (A1)download HTTP 200+6
  • Metadata persists in a registry (A2)Bioregistry+3
I Interoperable FAIR8/12
  • Formal machine-readable format (I1)OBO+5
  • Semantic-web IRIs (I2)OBO+3
  • References other vocabularies (I3)no imported vocabularies found0
R Reusable FAIR9/12
  • Clear license (R1.1)CC-BY-SA-4.0+5
  • Release provenance (R1.2)1.2 (version info in the artefact)+4
  • Community standards (R1.3)no independent compliance report (not on the OBO Dashboard)0
Q Ontology consistency & quality0/20
  • Logical consistencynever checked by a reasoner0
  • OWL 2 DL profileprofile not checked0
  • Upper-ontology alignmentno BFO/COB/DOLCE import found0
  • Standard relations (RO)does not import the Relation Ontology0
  • ROBOT report: no errorsno ROBOT report available0
  • ROBOT report: warning densityno ROBOT report available0
  • Pitfall scan: no critical pitfallsno pitfall scan or ROBOT report yet0
M Maintenance10/16
  • Recency2026-06-27 → 3.9 months (≤ 6 months)+8
  • Release cadence (12 months)1 release (GitHub releases)+2
U Community adoption4/16
  • Documented adopting projects0 projects0
  • Reused by other ontologies00
  • Community signalmax(stars 151 → 4, citations 0 → 0)+4
P Penalties (inactivity & inconsistency)0
  • Time since last activity0.3 years → 4 × max(0, 0.3 − 1)0
  • Inactive statusnot archived, legacy or inactive0
  • Consistencynot yet checked by a reasoner0

FAIR subtotal 30/48 · earned 44/100 = 44/100 → grade D

Community adoption 0

No adopting projects documented yet.

Know a project that uses edam.operation? Suggest it.

History & changes 1 run

History starts with the first archived run; changes appear after the next evaluation.

RunScoreFAIRVersion evaluatedTermsSnapshot
26 Oct 2026, 03:31 UTC44 D301.2—JSON

Provenance

Every fact on this page was fetched automatically. Each row shows where it came from and when. If a source fails, the last good value is kept and marked “carried forward”.

FactSourceRetrieved
Homepage link check (HTTP 200)edamontology.org26 Oct 2026, 02:53 UTC
Repository link check (HTTP 200)github.com26 Oct 2026, 02:53 UTC
Download link check (HTTP 200)github.com26 Oct 2026, 02:53 UTC
Artefact header (version info)raw.githubusercontent.com26 Oct 2026, 02:53 UTC
Git refs (commit 3a6e2ca, latest tag 1.25.20260626T1230Z)github.com26 Oct 2026, 02:53 UTC
GitHub repository statisticsapi.github.com26 Oct 2026, 02:53 UTC
Bioregistry mappings, dependencies & reusebioregistry.io26 Oct 2026, 02:53 UTC

Run 2026-10-26T02-37-38Z · evaluator v2.0.0 · rubric v3.4 · entry.json · run snapshot