Session Date/Time: 22 Mar 2024 05:00

mediaman

Summary

This mediaman meeting focused on the definition and usage of media type suffixes, particularly multiple suffixes, and the implications for interoperability and security. The discussion centered around a proposal to register several media types with multiple suffixes, specifically related to JSON-LD, Decentralized Identifiers (DIDs), and Verifiable Credentials (VCs). Concerns were raised about the lack of clear guidance on the meaning and appropriate use of suffixes, leading to potential misuse and ambiguity. The meeting concluded with an action plan to investigate the feasibility of removing suffixes from related specifications and the definition of next steps for several registry related tasks.

Key Discussion Points

Suffix Meaning and Usage: The core issue revolves around the lack of clear definitions and guidelines for media type suffixes. Concerns were voiced that the proliferation of suffixes, especially multiple suffixes, without well-defined semantics could lead to confusion, interoperability problems, and even security vulnerabilities.
Multiple Suffixes: The specific use case of multiple suffixes (e.g., +ld+json) was debated. There was disagreement on whether these suffixes provided meaningful information or were simply conventions for naming.
Existing Registrations: Concerns about existing registered suffixes, some of which might be misused (e.g., +gzip), which led to suggestions for reviewing and potentially re-evaluating their usage.
JSON-LD, DIDs, and VCs: The need to register media types for JSON-LD, DIDs, and VCs with multiple suffixes has driven the discussion. However, there is reluctance to register these types without addressing the fundamental issues surrounding suffixes.
Backward Compatibility: Changing the media type conventions for JSON-LD would create a compatibility problem because it has been deployed for a while.
Proposed Solutions: Several solutions were proposed, including:
- Documenting use cases for suffixes and providing guidance on appropriate usage.
- Grandfathering in existing registrations for JSON-LD, DIDs, and VCs, but discouraging future use.
- Treating plus signs and dashes as equivalent and removing the special meaning of suffixes.
- Removing suffixes from all related specifications (JSON-LD, VC, DID) and use dashes instead.

Decisions and Action Items

Action Item: Investigate the feasibility and impact of removing plus signs (suffixes) from all related specifications (JSON-LD, VC, DID) and using dashes instead. This will be discussed on the relevant mailing lists. (Owner: mediaman working group)
Action Item: Harold to facilitate introduction to write people at the W3C for discussion about potential impact of the change. (Owner: Harold)
Action Item: Escalate organization's documents and ID that have expired to the working group. Working group to plus call for it.
Action Item: Create a repository for the registration document and find an editor to start the rewrite process. Update the registry with the "instructions to the reviewer to the type review." (Owner: mediaman working group)
Action Item: Magnus Westerland to update registry with RTP metadata, and delete the old one. (Owner: Magnus Westerland)
Action Item: Get a list from Manu of the types they want grandfathered. (Owner: Manu)

Next Steps

Discussion on Mailing Lists: The potential for removing suffixes and using dashes will be discussed on the relevant mailing lists.
Liaison with W3C: Coordination with the W3C will be initiated to assess the impact of changes on JSON-LD, DIDs, and VCs.
Revisit Suffix Definition: The mediaman working group will revisit the fundamental definition and purpose of media type suffixes.
Document Review: Review existing RFCs for registry related updates.