Skip to content

Content format negotiation (markdown vs HTML vs structured) #16

Description

@possiblyshellen

Summary

Standardize how readers request and negotiate content format (markdown, HTML, structured blocks) from content endpoints.

Context

Currently the spec shows example responses in various formats (JSON with html/md fields) but doesn't define a standard negotiation mechanism (e.g., Accept headers, format query params, or a dedicated negotiation endpoint).

Responsibilities

  • Define an Accept header value (e.g., application/vnd.ope.content+json)
  • Specify format query parameter behavior
  • Document the response schema for each format type
  • Ensure consistency with existing batch endpoint format negotiation

Related

Spec sections: 10 Content Retrieval, 10.2 Batch Retrieval, Future Work

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions