odcs 0.9.1

Reference implementation of the Open Data Contract Standard (ODCS)
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

# Diagnostics Guide

Diagnostics mirror DTCS style.

Implemented Rust types in [`src/diagnostics/`](../../src/diagnostics/):

```rust
pub enum Severity {
    Error,
    Warning,
    Information,
}

pub enum DiagnosticStage {
    Parse,
    CanonicalObjectModel,
    Validation,
    Analysis,
    Planning,
    Compilation,
    Runtime,
}

pub enum DiagnosticCategory {
    Syntax,
    Structure,
    Type,
    Reference,
    Semantic,
    Compatibility,
    Capability,
    Runtime,
    Extension,
}

pub struct Diagnostic {
    pub id: String,
    pub severity: Severity,
    pub stage: DiagnosticStage,
    pub category: DiagnosticCategory,
    pub message: String,
    pub object_ref: Option<String>,
    pub remediation: Option<String>,
    pub validation_phase: Option<ValidationPhase>, // JSON: validationPhase
}
```

Validation-stage diagnostics are built with `validation_error(phase, id, category, message)`, which sets `stage: Validation` and `validation_phase: Some(phase)`. Parse-stage diagnostics omit `validationPhase`.

Standard diagnostic identifiers live in [`src/diagnostics/codes.rs`](../../src/diagnostics/codes.rs).

Diagnostics are stable enough for tests and CLI output. The Rust and Python CLIs include `object_ref` and `remediation` in text output when present.