Include Appendix A media type registration

[guybedford]

This includes the media type registration as an Appendix A in the specification text, according to the process for W3C registrations outlined at https://www.w3.org/2002/06/registering-mediatype2014.html.

I have included myself as the contact for further information for now, but would be happy to change this if another contact would like to be listed - I just didn't want to incorrectly assume this responsibility for anyone else.

---

Preview | Diff

[yoavweiss]

@wseltzer / @plehegar - Thoughts on the right contact person here?

[plehegar]

I don't recommend putting individual email address there since it needs to survive individuals moving on but I have no objection if you folks feels otherwise. At the end of the day, the best way to reach out is through GitHub as far as I know.
Basically, we'd need an email address that someone can see and redirect to the right person if needed. Some ideas, with various pros/cons:

• Domenic Denicola [email protected]
• Domenic Denicola [email protected]

[domenic]

You may want to consult https://html.spec.whatwg.org/#application/microdata+json which illustrates how you can (should?) defer a lot to application/json.

[guybedford]

I've included all the feedback here now. Note that for both the required parameters and optional parameters, referring to the JSON specification is effectively referring to the N/A values. Using an N/A field is very specifically requested to be provided for non-applicable fields in the template, so directly providing this value seems better. I did refer to the JSON spec for the Mac filetype code though, being the only one of these references that is not N/A.

Let me know if there is any further feedback to merge further.

[guybedford]

The CI error here seems to be an unrelated issue with the lockfile in the reference implementation.