gnomonlearn
Docs/Shared RDF domain identity audit

Shared RDF domain identity audit

Versioned draft snapshot

RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.

Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.

This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.

Status: normative release gate blocked. No public RDF release has been made.

The domain projections reuse 196 subject IRIs across RFCs. All 196 carry different summary literals, which can describe a shared concept from different contexts and are informational in the audit. No subject now has conflicting RDF classes, 18 subjects have conflicting FQN literals, and 21 shared declaration IRIs have conflicting kindClass values. The release gate rejects all three identity-conflict categories; python3 tools/check_domain_identity.py prints the complete inventory.

These current conflict counts follow the retained October 16 nonrelease identity inventory. This documentation correction does not change RDF identities or establish proof, runtime conformance, or release acceptance.

The owner approved separating project.gnm from the project declaration kind. RFC-0008 retains https://gnomon.sh/domain/declaration/project, while RFC-0017 now uses https://gnomon.sh/domain/declaration/file/project.gnm. This removed the sole RDF class conflict and one FQN conflict. The approved SourceFile class now distinguishes that manifest and RFC-0001’s 19 other .gnm file nodes from declaration instances; see the exact correction record.

The remaining FQN conflicts occur in three groups: RFC-0040 versus RFC-0048 capability scope names; RFC-0025 versus RFC-0033 authentication scheme names; and RFC-0053 versus several earlier RFCs on primitive type capitalization and generic notation.

The kindClass check exposed a separate transform collision: RFC-0006 and RFC-0040 call declaration/transform a Migrations declaration, RFC-0021 calls it Operations, and RFC-0044 calls it Composition. RFC-0044 §7 explicitly distinguishes its build-time manifest transform from the runtime data transform. The RFC-0044 proposal separates those identities and lists the RDF consumer checks before correction. Some may be valid aliases, but a single fqn predicate cannot carry two canonical names without an explicit alias model. Review the authored concept and consumers for each group before changing public IRIs or FQNs.

The scope collision needs more than a spelling pass. RFC-0040 §5.1.1 gives root token scope to capabilities resolvable from any context, while RFC-0048 §5.2 says a session with root scope can resolve all capabilities. These are opposite sides of the capability check. Verify the intended resolution relation before declaring the two RDF nodes identical or renaming either FQN. Both authored tables spell the five values without a scope. prefix.

The authentication collision also crosses API direction: RFC-0025’s auth: value selects credentials and headers for an outbound HTTP client, whereas RFC-0033’s schemes list describes accepted inbound API authentication. api-key can use a query parameter inbound but RFC-0025 describes an X-Api-Key outbound header. Keep the directional contract visible while deciding whether each scheme has one shared identity or separate inbound/outbound identities. The authored enum values themselves are bare api-key, basic, bearer-token, and none.

RFC-0008 and RFC-0009 both refer to the formatter command as gnomon fmt. RFC-0008’s gnomon-fmt FQN was corrected to gnomon fmt in its source projection and regenerated Turtle; this removed one shared-IRI FQN conflict without changing the subject IRI. The 16 claim queries and projection drift check passed after this correction. RFC-0053 §4 uses lowercase field type labels in its SQL cast table, while earlier type definitions use capitalized Gnomon type names. This may be a source-level type spelling discrepancy, not an RDF alias. Resolve the field type vocabulary before normalizing the eight case conflicts. The separate List versus List<T> conflict concerns the type constructor’s canonical notation and should be reviewed independently. The RFC-0053 type-mapping proposal also records the substantive Integer width and reference-storage conflicts with RFC-0006/RFC-0051, and distinguishes UI field labels from value types. The eight shared type IRIs remain unchanged pending that contract decision.

Acceptance: each shared IRI has one RDF class, one canonical FQN, and one declaration kindClass across all projections; alternate names use an explicit alias property where the source supports them. Rebuild Turtle, rerun the 16 checked-in claim queries, inspect semantic triples changed, and run check_domain_identity.py --release and the full normative release gates. Exact-IRI RDF consumers remain unverified.