oxiland 0.3.0

Safe Redland-shaped RDF models, SPARQL query/update/results, and stream-oriented RDF I/O on Oxigraph
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

# Oxiland documentation

Choose a path by role. Planning documents describe intended work; the
[parity ledger](parity.md) records what is verified now.

API reference (rustdoc): [docs.rs/oxiland](https://docs.rs/oxiland).

## Users

Product guides for writing applications against the published crate:

1. [Getting started](users/getting-started.md) — install, toolchain, first workflows
2. [RDF I/O](users/io.md) — syntaxes, GraphTarget, progressive vs collecting load
3. [SPARQL](users/sparql.md) — Query, Update, and results
4. [Persistence](users/persistence.md) — experimental Fjall stores and export
5. [FAQ and troubleshooting](users/faq.md)

## Evaluators

Adoption and compatibility decision material:

1. [Positioning](evaluators/positioning.md) — vs Oxigraph, Sophia, and Redland
2. [Migration from Redland](evaluators/migration-from-redland.md)
3. [Parity ledger](parity.md) — scoped verified claims
4. [0.3 compatibility report](reports/0.3.md)
5. [0.2 compatibility report](reports/0.2.md)
6. [Compatibility contract](COMPATIBILITY.md)

## Contributors

Process and planning (compatibility work is vertical-slice driven):

1. [Contributing](contributing.md)
2. [Project charter](CHARTER.md)
3. [Roadmap](ROADMAP.md) — next release is **0.4**
4. [Milestone 0.3](milestones/0.3.md) (complete) · [0.2](milestones/0.2.md)
5. [Execution plan](EXECUTION.md)
6. [Architecture](ARCHITECTURE.md)
7. [Verification](VERIFICATION.md)
8. [Decisions](DECISIONS.md)
9. [Risks](RISKS.md)
10. [Reports and release checklists](reports/0.3.md) · [0.3.0 release](reports/0.3.0-release.md)

### Document authority (contributors)

| Question | Authority |
|---|---|
| Who is Oxiland for and what does 1.0 promise? | [Charter](CHARTER.md) |
| What exists and is verified now? | [Parity ledger](parity.md) |
| What release comes next? | [Roadmap](ROADMAP.md) |
| What must the active release deliver? | [milestones/0.3.md](milestones/0.3.md) (complete); next is 0.4 |
| How is work sliced and completed? | [Execution](EXECUTION.md) |
| Where does code belong? | [Architecture](ARCHITECTURE.md) |
| What does compatibility mean? | [Compatibility](COMPATIBILITY.md) |
| What evidence is sufficient? | [Verification](VERIFICATION.md) |
| Why was a durable choice made? | [Decisions](DECISIONS.md) |
| What could block the plan? | [Risks](RISKS.md) |

## Maintenance rules

- Plans use `planned`, `in progress`, `blocked`, and `complete`.
- Only verified implementation is marked complete in the parity ledger.
- User and evaluator guides must not describe planned work as available.
- Historical reports are amended only to correct errors.
- This MkDocs site is configured by [`mkdocs.yml`](https://github.com/eddiethedean/oxiland/blob/main/mkdocs.yml)
  and [`.readthedocs.yaml`](https://github.com/eddiethedean/oxiland/blob/main/.readthedocs.yaml).