Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spec extension namespace #10

Open
innovate-invent opened this issue Feb 16, 2021 · 1 comment
Open

Spec extension namespace #10

innovate-invent opened this issue Feb 16, 2021 · 1 comment

Comments

@innovate-invent
Copy link

innovate-invent commented Feb 16, 2021

I would like to propose that the spec explicitly addresses implementation specific functions. Allowing a provision for functions specific to the implementation will free up those communities to expand features and functionality while not risking colliding with future additions to the spec.

I propose a prefix to non-spec functions. This will inform the end user that the function may change or be replaced in the future. Perhaps prefix these function names with an X, _, $, or #. Any custom functions provided by the library implementation or importing application will automatically be prefixed with this character.

Opening up the spec like this will allow innovation and test beds to be created. Non-spec functions that gain popularity can then be evaluated for inclusion into the spec. This will also alleviate any confusion when a custom function is encountered in the wild as it will be made clear that it is not supported by other implementations.

@springcomp
Copy link
Contributor

Third-Party Functions unofficial proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants