docs(rdf): declare DCMI annotation values and OWL roles

[jdsika]

2026-10-14: the example and tests are unchanged. #33 now renders a curie-typed annotation value as a string literal and follows --xsd-anyuri-as-iri for uri values; this example uses nodeidentifier for the publisher and string for the creator label, so its output is unchanged.

DCMI agent metadata can contain identifier nodes or textual identifiers. This documentation/test PR demonstrates the existing generic instantiates and scalar-range mechanism completed in #33, together with implements: [owl:AnnotationProperty] for OWL projection. It adds no compiler algorithm, vocabulary table, metamodel field or generator flag.

The published YAML is included directly in the OWL documentation and executed in tests. Its creator is a literal and its publisher is an IRI; both predicates are annotation properties and occur in no logical restrictions. A declared string containing a URL remains literal. The same mechanism works for custom predicates, as demonstrated by #33's generic example.

Standards and existing alternatives

DCMI Metadata Terms use rangeIncludes to suggest Agent values. This is not an rdfs:range restriction or an IRI-coercion algorithm. Creator and rightsHolder recommend URI identifiers while permitting literals. Declared LinkML ranges select the RDF terms; the established implements mapping selects the independent OWL annotation-property role. OWL typing constraints exclude incompatible logical roles.

Use native contributors for ordinary contributor identifiers. Native created_by maps to PAV, rather than DCMI creator. The publisher slot is declared in the metamodel but is not attached to CommonMetadata, Element or SchemaDefinition in the reviewed checkout; its constructor rejects a top-level publisher keyword. This declaration is therefore not a working native-field alternative here. The example uses explicit publisher annotations. Native license remains authoritative and string-valued.

Validation and boundaries

• 270 focused tests passed, including all 18 required OWLAPI cases; four new cases execute the actual DCMI YAML with both native-URI modes and both type-object modes, metaclasses disabled. Every child artifact loads, saves and reloads with zero OWL 2 DL profile violations and retained creator/publisher annotations.
• All 37 original child cases remain: four properties, OWL/SHACL value parity, CURIE/absolute nodes, names and URL literals, native contributor parity and undeclared-value preservation. Additional checks cover property declarations/restrictions and the native PAV creator mapping.
• Existing OWL, SHACL, JSON Schema, ShEx, RDF, JSON-LD and Python generator suites: 393 passed, 6 skipped; 261 subtests passed.
• Strict Sphinx, rendered shared-YAML equality, primary reference/fragment checks, Ruff and applicable hooks passed. Current DCMI deep links, including the inherited license guidance link, are corrected.
• Production is unchanged from feat(rdf): preserve declared annotation terms and OWL roles #33 (owlgen.py SHA-256 c80049db…). Annotation metadata does not become instance validation; other formats retain their existing contracts. This does not add complete metadata-extension validation, structured agents, native-field RDF export policies, or all-schema/default-metaclass OWL 2 DL conformance. Prerequisite datatype/type-object limitations remain documented. No downstream files or migration artifacts are changed.

Rebased 2026-10-14 onto the updated #33 (stacked on #32). Full compiler suite 12,676 passed; strict Sphinx build passed. CI: see the checks on the current head (including the required OWLAPI consumer job).

Merge order

Merge #32 and #33 into main first. This PR is stacked on feat/owlgen-iri-valued-metadata (#33, itself on #32). After #33 merges, rebase #36 onto the resulting main commit, retarget its base to main, retain one feature commit and rerun all applicable CI for its resulting head. Squash merging #33 changes the prerequisite SHA. Do not merge #36 into the feature branch as a substitute for merging it into main. This review performs no merge or upstream PR creation.