[amc-corey-cox]

#263 changed status in meta.yaml (range uriorcurie → string, bibo:status moved from slot_uri to close_mappings), but it merged after #279 branched. So main currently has source and generated artifacts that disagree: meta.py, JSON-LD, OWL, ShEx and SHACL still say bibo:status / uriorcurie.

This regenerates at the same linkml pin as #279 (b07d0a0fd), with no other changes. Every content change is status-related:

• slot_uri is now linkml:status, with bibo:status as skos:closeMatch
• The range is string in meta.py, JSON Schema, OWL and ShEx
• The examples are testing / unstable instead of bibo:draft

The large SHACL diff is canonical blank-node relabelling set off by the datatype change. SQL reordering and date-only stamp changes are left out, as in #279.

This blocks cutting v1.12.0-rc1.

[Copilot]

Copilot review overview

🔵 Needs a closer look

It is a large machine-generated regeneration whose RDF blank-node canonicalization semantics cannot be fully verified by inspection, and the largest referenced artifact (meta.shacl.ttl) is outside the provided review scope.

Review effort: Balanced
Findings: None

What changed in this PR

This PR regenerates the committed derived artifacts so they agree with the status slot change already merged into meta.yaml via #263 (range uriorcurie → string; bibo:status moved from slot_uri to close_mappings; examples changed from bibo:draft to testing/unstable). It uses the same linkml pin (b07d0a0fd) as #279 and introduces no source changes — every content change traces back to the status slot. This unblocks cutting v1.12.0-rc1.

I verified:

• meta.py: all 14 status-bearing classes consistently updated to Optional[str] with str() coercion, and slots.status now uses LINKML.status; no URIorCURIE/BIBO.status remnants.
• JSON-LD: status now renders with close_mappings, slot_uri: linkml:status, range: string — matching the existing deprecated slot pattern (also close_mappings-based).
• OWL: owl:ObjectProperty is a generator convention shared by other string slots (source, title, description), not a defect.
• ShEx: the bibo: prefix was correctly dropped (no longer referenced anywhere in the file).
• source_file_size stamp (102070) exactly matches the current meta.yaml byte size.
• The remaining bibo:status "testing" instance-data predicates in the RDF are unchanged context lines originating from linkml-runtime's vendored metamodel vocabulary (documented in #279), not introduced here.

Changes:

• Regenerated Python, JSON Schema, JSON-LD (+context), OWL, ShEx, and RDF/SHACL artifacts to reflect status as a string slot with linkml:status slot_uri and bibo:status as a close mapping.
• Updated status examples to testing/unstable and refreshed the source_file_date/source_file_size stamps.

File	Description
linkml_model/​meta.py	status typed as Optional[str] with str() coercion in every class; slots.status uses LINKML.status
linkml_model/​jsonld/​meta.jsonld	status slot def: close_mappings, slot_uri linkml:status, range string, new examples
linkml_model/​jsonld/​meta.context.jsonld	status context entry drops @type: xsd:anyURI/bibo:status, now bare @id: status
linkml_model/​jsonschema/​meta.schema.json	status examples updated to testing/unstable across all classes
linkml_model/​owl/​meta.owl.ttl	status range → String, adds skos:closeMatch bibo:status, restriction moved
linkml_model/​shex/​meta.shex	status becomes <status> @<String>; unused bibo: prefix removed
linkml_model/​rdf/​meta.ttl	status slot def updated + blank-node canonical relabeling + stamp refresh
linkml_model/​rdf/​meta.model.ttl	Same regeneration as meta.ttl

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[matentzn]

I am fine with this but please handle the follow up at some point soon after 1.12: linkml/linkml#4041

[amc-corey-cox]

@matentzn Yes, linkml/linkml#4041 will be one of my next priorities.