+yaml MUST use application/yaml fragids. - Githubissues

ietf-wg-httpapi / mediatypes

Other

5 stars 4 forks source link

+yaml MUST use application/yaml fragids. #54

Closed ioggstream closed 2 years ago

ioggstream commented 2 years ago

This PR

follows the long thread we had on #50 and #51.

+yaml SSS references application/yaml fragids.

Note

Point 1. means that:

according to RFC 6838 any xxx+yaml such as openapi+yaml, schema+yaml and ld+yaml MUST support application/yaml fragments including alias nodes resolution, and that client implementations, viewers and browsers might legitimately expect that behavior;
xxx+yaml media types cannot override any of the above behavior;
if one day the YAML community decides to define a fragid for plain names, it will legitimately prevail on all other plain name use in xxx+yaml.

ioggstream commented 2 years ago

@cabo @handrews @eemeli I have merged the refactoring of fragid section in #51 since there was agreement on that.

In this PR we only discuss about having the same fragid of application/yaml and +yaml.

ioggstream commented 2 years ago

Discussed at IETF-114. The general idea was to leave +yaml unspecified to avoid inconsistencies with existing implementations of xxx+yaml.

ioggstream commented 2 years ago

Closed according to the discussion in IETF-114