Normative references
Normative references are the machine-facing connection points for this profile. When prose in this MAP disagrees with published SHACL or the ontology at the URLs below, SHACL and the ontology win; gaps should be reported as GitHub issues.
Release bundle described here: CIDS 3.2.1 (2025-10-31) with current published SHACL and context files on ontology.commonapproach.org.
CIDS ontology
Section titled “CIDS ontology”| Artifact | URL |
|---|---|
| Ontology IRI (versioned) | https://ontology.commonapproach.org/cids/3.2.1 |
| Latest ontology document | https://ontology.commonapproach.org/cids.ttl |
| HTML class guide (non-normative prose) | https://ontology.commonapproach.org/cids-en.html |
| Alternate serializations | .owl, .jsonld, .nt via content negotiation on the ontology server |
| Source repository | github.com/commonapproach/CIDS — cids.ttl |
Preferred namespace: https://ontology.commonapproach.org/cids# (prefix cids:)
Imported ontologies (semantic dependencies)
Section titled “Imported ontologies (semantic dependencies)”CIDS imports these external ontologies (see Data model summary):
| Import | Base IRI |
|---|---|
| TOVE Organization | http://ontology.eil.utoronto.ca/tove/organization.owl |
| TOVE Activity | http://ontology.eil.utoronto.ca/tove/activity.owl |
| TOVE iContact | http://ontology.eil.utoronto.ca/tove/icontact.owl |
| ISO 21972 (measurement) | http://ontology.eil.utoronto.ca/ISO21972/iso21972.owl |
| W3C Time | http://www.w3.org/2006/time.rdf |
Modular SHACL for imports (optional in validation): organization.shacl.ttl, activity.shacl.ttl, icontact.shacl.ttl, iso21972.shacl.ttl, time.shacl.ttl under validation/shacl/.
SHACL shape files
Section titled “SHACL shape files”Published at https://ontology.commonapproach.org/validation/shacl/.
| File | Tier / module | Use when claiming… |
|---|---|---|
| cids.basictier.shacl.ttl | Basic | Basic Tier CIDS only |
| cids.essentialtier.shacl.ttl | Essential | Essential Tier |
| cids.fulltier.shacl.ttl | Full | Full Tier |
| cids.all.shacl.ttl | All CIDS tiers combined | Tooling / comprehensive validation |
| sff.shacl.ttl | SFF companion | Basic + SFF reporting |
Validation instructions: CIDS validation README and Alignment and conformance. Published filenames use the tier names above (for example cids.basictier.shacl.ttl, iso21972.shacl.ttl).
JSON-LD context files
Section titled “JSON-LD context files”| Context | URL |
|---|---|
| CIDS | https://ontology.commonapproach.org/contexts/cidsContext.jsonld |
| SFF companion | https://ontology.commonapproach.org/contexts/sffContext.jsonld |
Capsules SHOULD reference these contexts (see Serialization). Multiple contexts may appear in a single @context array; SFF capsules typically include both CIDS and SFF contexts.
Social Finance Fund companion module
Section titled “Social Finance Fund companion module”| Artifact | URL |
|---|---|
| SFF ontology (TTL) | https://ontology.commonapproach.org/sff.ttl |
| SFF HTML guide | https://ontology.commonapproach.org/sff-en.html |
| SFF implementation PDF (non-normative) | SFF Companion Module v2.0 PDF |
| Source | github.com/commonapproach/CIDS — sff.ttl |
Preferred namespace: https://ontology.commonapproach.org/sff# (prefix sff:)
Code lists
Section titled “Code lists”Normative concept URIs for controlled values are published at codelist.commonapproach.org. Turtle (.ttl) is the canonical serialization for each list; JSON-LD, CSV, OWL, and N-Triples are also available.
See Code lists for which lists apply to which CIDS properties.
Human-oriented alignment reference (non-normative)
Section titled “Human-oriented alignment reference (non-normative)”| Resource | URL |
|---|---|
| Alignment Checklist (Excel) | commonapproach.org — Alignment Checklist |
| Checklist usage guide | Alignment checklist guide |
The Excel checklist is derived from SHACL; if it diverges, SHACL is authoritative.
Example capsules (non-normative)
Section titled “Example capsules (non-normative)”Published JSON-LD examples (including Zero Waste Meal Kits Basic + SFF sample):
See Examples.
Conflict resolution
Section titled “Conflict resolution”| If… | Then… |
|---|---|
| Prose in HTML guides disagrees with SHACL | SHACL governs conformance |
| SHACL disagrees with OWL cardinality in edge cases | Report issue; SHACL is the validation contract for capsules |
| Context file prefix disagrees with ontology URI | Ontology IRIs are authoritative; context must expand to them |
| Code list server concept disagrees with local copy | Published server version at validation time wins |
| Excel Alignment Checklist disagrees with SHACL | SHACL wins |
| MAP prose (this site) disagrees with SHACL | SHACL wins; report a documentation issue |
Other MAP pages link here for conflict resolution rather than restating this table.
Related
Section titled “Related”- Versioning and governance — how release numbers relate
- Graph Cast capsules — hosted validation (non-normative implementation)