# Reporting errors and proposing changes — IOCE Core Ontology v0.1

The ontology is provisional. Criticism, correction, translation and competing interpretations are welcome.
You do not need to agree with IOCE's conclusions to use or improve this material.

## Where to send reports
- **Web form:** https://www.alkhemy.com/ioce-feedback/ (no account needed; name and email are optional)
- **Email:** trr@alkhemy.com (put the term IRI in the subject line)
- **Public issue tracker:** https://github.com/Mulkitis/ioce-commons/issues (needs a free GitHub account; reports are public and discussable)

You can also take part without contacting anyone. Publish your critique or amendment anywhere public, cite the term IRIs
and the version (below), and reuse the material under its licences (CC0 structure, CC BY 4.0 text).

## What makes a report useful
1. **The term, property or assertion IRI** and the version, e.g. `https://ioce.alkhemy.com/ontology/ioce-core#OCDI` in v0.1.
2. **The kind of problem**:
   - *misquotation*: the `definition` or `evidenceQuote` does not match the source page;
   - *wrong status*: e.g. something marked `documented` is really `inferred`, or the reverse;
   - *missing term or relation* that the IOCE pages do support (give the URL and quote);
   - *unsupported item* that should be removed or downgraded to `proposed`;
   - *provenance or licence error*;
   - *disagreement with the substance*: welcome, but kept separate from errors of representation. The ontology records what
     IOCE says; it does not referee whether IOCE is right.
3. **Evidence**: a URL and a verbatim quote, or a reproducible check.

## Amendment format (machine-readable)
```json
{
  "ontologyVersion": "0.1",
  "target": "https://ioce.alkhemy.com/ontology/ioce-core#StewardshipScore",
  "kind": "missing-definition",
  "proposedChange": {"definition": "…", "status": "documented"},
  "evidence": [{"url": "https://ioce.alkhemy.com/…", "quote": "…"}],
  "author": "optional",
  "licence": "CC0-1.0"
}
```

## How changes are made
Accepted changes go into `tools/ontology_data.py` and are released as a **new version** (v0.2, …) with new versioned
file names. Published versions are never edited in place. A change of status is always recorded in the term's `notes`.
