-
## What
Produce a JSON Schema that defines the minimal, simplest JSON representation of OpenAssetIO Traits and Specifications, such that it can also be auto-generated from other declarations such a…
-
## What
Determine where the time is going in the various CI checks in order to define next steps to optimize build/test times. This could include experimental implementation of various tricks/impro…
-
## What
Update to use the new traits system.
## ACs
- Existing Specifications migrated to the new Traits-based approach (no changes).
- Updated to use `resolve`.
- Reference `OpenAssetIO` b…
-
# What
Add macro definitions for short-form versions of C API symbols, e.g.
```c++
#define oa_InfoDictionary_h OPENASSETIO_NS(InfoDictionary_h)
```
# Why
The prevalence of the `OPENASSE…
-
# What
Presently, we define no practically useful specifications of any kind. Just the base `EntitySpecification`, `LocaleSpecification` and `RelationshipSpecification` classes. It feels like inclu…
-
## What
Produce a minimal prototype [OpenTimelineIO plugin](https://github.com/OpenTimelineIO/otio-plugin-template) that allows `MediaReferences` to be resolved through OpenAssetIO.
## Why
En…
-
## What
Investigate the structure and means of development for our C API
## ACs
- A plan for how we build out the C API (manual, or generated)
- Sketch(s) for the `C` API for `ManagerInterfa…
-
# What
Add `identifier` and `displayName` methods to the C++ `ManagerInterface` and inherit their default implementations in Python.
# Why
This is a necessary step toward a C++ manager plugin…
-
## What
The initial work that starts the migration of the core OpenAssetIO model to `C++`.
## Why
OpenAssetIO functionality must be available to both `C++` and `Python` hosts, and so the core…
-
Due to a find-replace error `Test_FixtureAugmentedTestCase_init` is asserting on a mock instance rather than a real instance.