Skip to content

Before 1.0 I would like to discuss extension "graduation" process. #201

@inlined

Description

@inlined

If extensions are a breeding ground for potential new standard fields, it would be helpful for us to define what graduation entails. Extensions are often compared to x- attributes in headers or CSS properties, though many of these are widely considered to be a mistake by some in the community. IMO, the worst case scenario is that an extension graduates, the early adopting event providers must double send all extension data, and the final customer code must be prepared to handle the same semantic data from two different locations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions