BrasidataCenter
Brasidata's ontology collection, packaged for Python so every tool that consumes it — OntoBDC, InfoBIM, and others — gets the same deterministic set of RDF/Turtle sources after pip install, with no network fetch and no path guessing.
Browse the published ontologies at datacenter.app.br. The Turtle sources under ontology/ are authoritative; the site is just a human-readable index of them.
Repository layout
| Path | What it is |
|---|---|
ontology/ |
The authoritative RDF/Turtle sources, grouped by domain. Currently: domain/aeco (core schema, geometry/IFC representation, kind/material taxonomy, catalog) and domain/social. |
src/brasidatacenter/ |
The installable Python package: the resource API (resources.py) and the brasidatacenter CLI. |
kind_geometric_representation_mapping*.csv |
Reference mapping from AECO element kinds to their geometric representation (IFC class, predefined type, primitive), alongside domain/aeco/taxonomy/kind.ttl. |
legacy/ |
Superseded tooling (e.g. the old OntoMaker ontology editor), kept for reference and not part of the installed package. |
index.html |
Source of the datacenter.app.br landing page. |
Only ontology/, src/brasidatacenter/ and README.md ship to the production mirror this repository deploys to on release — everything else here is development-only.
Install
pip install brasidatacenter
For local development, install this repository itself in editable mode:
./reinstall.sh # or: pip install -e . --no-build-isolation
Use
As a resource API
from brasidatacenter import ontology_root, ontology_path, iter_ontology_files
root = ontology_root()
aeco_schema = ontology_path("domain", "aeco", "core", "schema.ttl")
for resource in iter_ontology_files():
print(resource)
ontology_root(), ontology_path() and iter_ontology_files() return importlib.resources-compatible Traversable objects, so callers never need to know whether the package was installed from a wheel or is running from this source checkout. During development, ontology_root() falls back to this repository's own ontology/ tree, so files are never duplicated under src/.
As a CLI
brasidatacenter --help
brasidatacenter tool
Commands are discovered by convention: any class under src/brasidatacenter/<component>/plugin/command/ that implements CommandPort is picked up automatically and listed in --help. Adding a command is a matter of dropping a file in the right place, not registering it anywhere.
License
Apache 2.0 — see LICENSE.
Metadata
Release files for brasidatacenter 0.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| brasidatacenter-0.10.1.tar.gz | 91.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brasidatacenter-0.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 193.2 kB
Release files / brasidatacenter-0.10.1.tar.gz
| Download URL | brasidatacenter-0.10.1.tar.gz |
|---|---|
| Size | 91.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f129d9c7470c4775f2e9ffd3e57e8a639cba238d63ae8eb591a65f1986f0723
|
|
BLAKE2b-256 checksum How to use checksums |
93a83b764fe714e3aea212a6dc37b8c3c3630390e8649f0c7db59e23edbd72b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / brasidatacenter-0.10.1-py3-none-any.whl
| Download URL | brasidatacenter-0.10.1-py3-none-any.whl |
|---|---|
| Size | 101.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f07f360c0dcee141a8ac228e2248aa832dd9057d91b398af6f1406c4b8d60ff
|
|
BLAKE2b-256 checksum How to use checksums |
df15f1089c9a2905decc01c04a092b5587e0a263c6b3e895213eb4c99b6c011f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency log