Add registration process.

[wes-smith]

This PR adds a description of the registration process for requesting registry entries.

Fixes #46.

---

Preview | Diff

[dlongley]

We might want to say that the spec/standard must be with an SDO -- or something similar. I think it would be challenging (for reviewers) to determine whether any "spec" document is otherwise "mature" or stable, etc. This could, for example, be based on similar rules that W3C uses today for normative references.

[TallTed]

Suggested change

	<b>65,536+</b>: First come, first serve
	<b>65,536+</b>: First come, first served

[TallTed]

Suggested change

	from a fork of the repository. These requests must include:
	via a fork of the repository. These requests must include:

[TallTed]

Suggested change

	A .yml file added to the `tables` directory, with the Registry Entry ID requested as the filename,
	A `.yml` file added to the `tables` directory, with the Registry Entry ID requested as the filename,

[TallTed]

Suggested change

	the registry repository maintainers on a first-come-first-serve basis without additional review.
	the registry repository maintainers on a "first-come, first-served" basis, without additional review.

[iherman]

A minor, editorial comment: 65,535 (and other) numbers use the US approach to separate the thousands. It is not the same in other languages and/or countries (for the fun, you can look at the wikipedia page). I realize W3C standards use American English, but numbers are sometimes more difficult to "switch" for a reader.

All this to say that may be probably better to write 65535.

[iherman]

Some questions that we may want to discuss:

• Who does the review? Is it the responsibility of the JSON-LD WG while it exists, and W3C team otherwise? Or do we want to gather a list of volunteers as for the DID method registry?
  -Do we plan to have a safe backup of the registry, or do we simply want to trust github (ie, Microsoft) for something like this?
• Will the registry entries have a stable URL to refer to, ie, to retrieve the registry if necessary, or do we simply say to the implementer: "get it from github using whatever tool you want"?
• (This question will obviously come:) why not a W3C registry? (Whatever that means...)

[pchampin]

Guidelines for non-W3C normative references:
https://www.w3.org/guide/process/tilt/normative-references.html

[TallTed]

Also note https://www.w3.org/guide/tools/
and its link to the dysfunctional normative references checker

[wes-smith]

• Who does the review? Is it the responsibility of the JSON-LD WG while it exists, and W3C team otherwise? Or do we want to gather a list of volunteers as for the DID method registry?

Maintainers of the various JSON-LD specifications are responsible for this, with W3C staff as backup.

We will move the other questions into a separate issue for tracking and to unblock this PR.