BSDO

About

A domain ontology, and a reader for it.

Domain ontology for battery swap ecosystems for electric two-wheelers. TBox derived from Formal Concept Analysis over four artefact-family contexts (batteries, station devices, service flows, vehicles), following METHONTOLOGY with FCA substituting the informal conceptualisation activity. Where a class comes from a formal concept, only concepts robust across pessimistic and optimistic readings of unarticulated data were promoted. Classes that are not formal concepts are marked as such: every class carries bsdo:derivationPath, whose value begins with one of lattice, composed, reuse or structural. Every class additionally carries bsdo:reuseStatus, recording separately whether it is reused, aligned or native, since a class may be derived from a formal concept and still borrow an external superclass. Aligned to EMMO domain-battery, domain-electrochemistry and chemical-substance (the vocabulary layer profiled by BattINFO), to the General Process Ontology, and to W3C SOSA and PROV-O.

37

Classes

domain classes, excluding alignment stubs

8

Alignment stubs

declared locally, not imported

35

Properties

object and data properties

64

Individuals

across both ecosystems

The artefact

Ontology language
OWL 2 DL
Namespace
https://w3id.org/bsdo#
Version
0.4.1
Method
Formal Concept Analysis + METHONTOLOGY
Licence
CC-BY-4.0
Creator
Sido Dea Auvia

Cite as

Dea Auvia, S. (2026). BSDO: Battery Swap Domain Ontology. Zenodo. https://doi.org/10.5281/zenodo.21683493

Aligned to

  • MatterTransportProcess (GPO)

    gpo:GPO_890abbc3_d75b_4f3f_a5b7_e1b0e898655b

  • EnergyTransportProcess (GPO)

    gpo:GPO_04b6cbaf_a63a_4130_974a_8cc9c2a612f1

  • Battery (EMMO domain-battery)

    bat:battery_74ed2670_657d_4f0b_b0a6_3f13bc2e9c17

  • LithiumIonBattery (EMMO domain-battery)

    bat:battery_96addc62_ea04_449a_8237_4cd541dd8e5f

  • Agent (PROV-O)

    prov:Agent

  • Observation (SOSA)

    sosa:Observation

  • RoadVehicle (GPO)

    gpo:GPO_bc07577b_1e4b_4d60_aa8d_3cfd09e7c03a

  • TransportProcess (GPO)

    gpo:GPO_c4600586_ccc8_4d4b_b7a2_123d5aa2d77d

Alignment is by reference rather than by import. Referenced classes are declared locally with labels and a pointer to their defining module, so the artefact presents no undeclared entities. Importing the modules in full would add several thousand classes to obtain eight alignment targets.

Terminology and population

The terminology (TBox) defines the classes and properties. The population (ABox) contains individuals for two Indonesian operators, drawn from operator applications, official websites and manufacturer documentation. All identifiers are pseudonymised; what is kept is the pattern of each identifier scheme, because the mutual uninterpretability of the two schemes is itself part of the finding.

The inconsistency test

A third file asserts that a lithium iron phosphate pack from one ecosystem is accepted by a device of the other that admits lithium-ion packs only. Loaded together with the terminology and population, it is expected to make the knowledge base inconsistent. That is the point: incompatibility is detected as logical unsatisfiability rather than as an empty query result, which distinguishes a genuine conflict from missing data.

About this demonstrator

This site is a reader, not a second source. It parses the published Turtle at build time and renders every figure, badge, axiom and verdict from it. There is no database and no editorial copy of the ontology’s content — where this site states a fact about BSDO, that fact came out of the files.

The ontology is vendored at a pinned commit so a build is reproducible. This build reads a22fe4d from 2026-08-15.

Ontology repository →DOI 10.5281/zenodo.21683493 →