Fix: #156. Update media type registration information.

[ioggstream]

This PR

• update references to RFC9512
• minor fixes to the media type registration data.

fixes #156.

Question

IMHO we can ask IESG / Mediaman if this doc is enough for the registration. If needed, I can investigate further.

If the fragment identification stuff is not clear, we could add a couple of examples.

---

Preview | Diff

[gkellogg]

Apparently, the practice is to use the working group mailing list (and name) as the contact now. That would be “W3C JSON- LD Working Group” and [email protected].

[ioggstream]

Apparently, the practice is to use the working group mailing list (and name) as the contact now. That would be “W3C JSON- LD Working Group” and [email protected].

Can you please point to the lines to be changed? :) Thx++, R:

[davidlehn]

Apparently, the practice is to use the working group mailing list (and name) as the contact now. That would be “W3C JSON- LD Working Group” and [email protected].

Can you please point to the lines to be changed? :) Thx++, R:

~1224, the [email protected] line. Maybe needs to say "Group & email" instead of "Person & email". Not sure what the restrictions on wording is there.

[gkellogg]

~1224, the [email protected] line. Maybe needs to say "Group & email" instead of "Person & email". Not sure what the restrictions on wording is there.

I updated the line; the registration template uses "Person & email"; it probably wouldn't fail if it use "Group & email", but who knows what scripts map be using.