Align media types with gistMediaTypes

[cmungall]

Adds semantic web and RDF-related media types from gist ontology to align with https://w3id.org/semanticarts/ontology/gistMediaTypes

Changes:

• Added gist prefix for proper ontology alignment
• Added 6 new semantic web media types: N-Quads, N-Triples, RDF/XML, SPARQL results formats, and TriG

Fixes #18

Generated with Claude Code

[claude]

Claude finished @cmungall's task —— View job

---

PR Review: Align media types with gistMediaTypes

Todo List:

• Read and understand the modified file
• Check project guidelines and structure
• Validate LinkML schema compliance
• Review for code quality and best practices
• Check for potential bugs or issues
• Assess security and performance considerations
• Evaluate test coverage needs
• Provide comprehensive feedback

Review Feedback

✅ Code Quality & Best Practices

• Excellent: Changes follow existing patterns and LinkML conventions
• Good: Proper YAML structure, indentation, and naming conventions (UPPER_CASE for permissible values)
• Good: Meaningful descriptions for all new media types
• Good: Consistent with project structure in src/valuesets/schema/computing/mime_types.yaml:83-100

✅ Schema Validation

• All new media types use proper IANA mappings with valid CURIE format
• Media types align with official IANA registry:
  • application/n-quads, application/n-triples, application/rdf+xml
  • application/sparql-results+json, application/sparql-results+xml, application/trig
• LinkML enum structure is correct and consistent

⚠️ Minor Inconsistency

The PR description mentions "aligning with gistMediaTypes" and adds the gist prefix (src/valuesets/schema/computing/mime_types.yaml:13), but none of the new media types actually use the gist prefix - they all use IANA mappings. This seems inconsistent.

Questions:

1. Should some of these media types map to gist: terms instead of or in addition to iana: terms?
2. Is the gist prefix intended for future use, or should it map existing terms?

✅ Security & Performance

• No security concerns: Only adds metadata/enum definitions
• No performance impact: Static enum definitions don't affect runtime performance
• Safe: All URLs point to legitimate ontology/registry sources

✅ Semantic Web Additions

The added RDF/SPARQL media types are valuable additions for semantic web applications:

• N-Quads/N-Triples: Essential RDF serialization formats
• RDF/XML: Standard W3C RDF serialization
• SPARQL Results: Standard query result formats
• TriG: Named graph RDF serialization

📝 Test Coverage

No tests appear to be affected by these enum additions. Static enums typically don't require additional test coverage beyond schema validation.

Recommendation

Approve with minor clarification needed on the intended use of the gist prefix. The changes are technically sound and add valuable semantic web media types to the schema.

--- | Branch: claude/issue-18-20251030-1536

[Copilot]

Pull Request Overview

This PR adds support for additional RDF and SPARQL-related MIME types to the valuesets schema. The additions expand coverage for Semantic Web technologies by including standard RDF serialization formats and SPARQL query result formats.

• Adds 7 new RDF-related MIME type entries
• Introduces a new gist prefix declaration

[claude]

Claude finished @cmungall's task —— View job

---

PR Review: Align media types with gistMediaTypes

Todo List:

• Read and understand the modified file
• Check project guidelines and structure
• Validate LinkML schema compliance
• Review for code quality and best practices
• Check for potential bugs or issues
• Assess security and performance considerations
• Evaluate test coverage needs
• Provide comprehensive feedback

Review Feedback

✅ Code Quality & Best Practices

• Excellent: Changes follow existing patterns and LinkML conventions
• Good: Proper YAML structure, indentation, and naming conventions (UPPER_CASE for permissible values)
• Good: Meaningful descriptions for all new media types
• Good: Consistent with project structure in src/valuesets/schema/computing/mime_types.yaml:83-100

✅ Schema Validation

• All new media types use proper IANA mappings with valid CURIE format
• Media types align with official IANA registry:
  • application/n-quads, application/n-triples, application/rdf+xml
  • application/sparql-results+json, application/sparql-results+xml, application/trig
• LinkML enum structure is correct and consistent

✅ Resolved Issue: Gist Prefix

I noticed the git history shows the gist prefix was correctly removed in the most recent commit (0cc4024) by @cmungall, addressing the Copilot reviewer's feedback about the unused prefix declaration. This was the right solution since all media types use IANA mappings.

✅ Security & Performance

• No security concerns: Only adds metadata/enum definitions
• No performance impact: Static enum definitions don't affect runtime performance
• Safe: All URLs point to legitimate ontology/registry sources

✅ Semantic Web Additions

The added RDF/SPARQL media types are valuable additions for semantic web applications:

• N-Quads/N-Triples: Essential RDF serialization formats
• RDF/XML: Standard W3C RDF serialization
• SPARQL Results: Standard query result formats
• TriG: Named graph RDF serialization

✅ Compliance with Project Guidelines

Following CLAUDE.md guidelines:

• ✅ Proper enum organization by domain (computing)
• ✅ CamelCase enum names (MimeType)
• ✅ UPPER_CASE permissible values
• ✅ Uses meaning: for ontology mappings
• ✅ Uses CURIEs with declared prefixes (IANA)

📝 Test Coverage

No tests appear to be affected by these enum additions. Static enums typically don't require additional test coverage beyond schema validation.

Recommendation

✅ APPROVE - This is a clean, well-structured addition that:

• Adds valuable semantic web media types
• Follows all project conventions
• Uses proper IANA mappings
• Resolved the unused prefix issue correctly

---

| Branch: claude/issue-18-20251030-1536