Ontology of Legal Bodies in Classical Athens v.1.0

Open data API in a single place

Provided by Zenodo

Get early access to Ontology of Legal Bodies in Classical Athens v.1.0 API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Zenodo catalog

Country of origin

EU institutions

Updated

2024.08.31 00:00

Created

2024.08.28

Available languages

English

Keywords

Datasource

Official portal for European data link

Quality scoring

Dataset description

This version includes: 1. The .otb file. To view it, please import it in Tedi ontoTerminology Editor 2. The .rdf file. To view it, please import it in Protégé ontology editor 3. The .html file that includes the terms (in English) 5. The .html file that includes the terms (in Ancient Greek) Software: This dataset was built with Tedi ontoTerminology Editor. Tedi ontoTerminology Editor is a software platform for the creation and management of ontoterminologies. Tedi software platform is distributed by the University of Crete (free for academic use, contact: christophe.roche@uoc.gr). The .rdf file is queryable via a SPARQL endpoint. Downloads: Download the RDF/OWL file; to view the ontology metrics import this file in Protégé (open access ontology editor); to visualize the ontology import this file in VOWL To view the .html files in your browser download them and rename them using the .html extension.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service