asudoh / web-namespace-registry

A registry for namespaces (prefixes) for custom elements, data attributes, custom attributes and css properties

Web Namespace Registry

Welcome to the web namespaces registry.

The goal of this project:
If someone is planning to develop a web framework, they can check to see if there might be a naming conflict with another framework.

Check if a namespace is used

Check a namespace on webnamespaces.org

Add your own framework

Make a fork, extend registry.v1.json and make a pull request.
Extend it like this:

    ...
    "myns": [
        {
            "name":"Name of your Framework",
            "url":"https://github.com/xxx/xxx",
            "affected":["ce","class"]
        }
    ],
    ...

url: Preferably a repository or project home on github
affected means:

• ce = custom elements <x-box>
• ca = custom attributes <div x-color=red> (non standard)
• data-a = data attributes <div data-x-color=red>
• class = class attributes <div class="x-color">
• css-cp = css custom properties (css variables) --x-color:red;

There can be multiple frameworks using the same namespace.

Add a badge

[![Registred on webnamespaces.org](https://img.shields.io/static/v1?label=webnamespaces.org&color=blue&message=myns)](https://webnamespaces.org)

Replace "myns" with your namespace.

Contribute

Discussion: A project-specific namespace?

Can we, the frontend community, agree on a project-specific namespace?
This should not be used for frameworks, so it can be used in a project without hesitation.
So far I have always used "cd", (customer data) but maybe another one is more suitable.

• c- (customer)
• p- (project)
• ps- (project specific)

What is your opinion?

Help wanted

Any help is welcome.
In particular: expand the list and share the project.