Fix: #8. ld+yaml mediatype

[ioggstream]

This PR

• registers the application/ld+yaml media type
• registers the .yamlld file extension

[pchampin]

I like the idea of YAML-LD :)
Although it should is relatively straightforward, the devil is in the detail, and I believe some details should be explicitly ironed up. For example, IIRC, YAML is a superset of JSON. What is a processor supposed to do with YAML construct that do not map to JSON? Ignore them? Reject them as an error? Note that the answer may be different depending on where this happens (in data vs. in context).

[gkellogg]

As both @pchampin and @msporny mentioned (in #8 (comment)), it is important that the YAML used be restricted to just use native JSON features to insure backwards and forwards compatibility with JsON-LD.

[ioggstream]

Moved to another project: https://github.com/json-ld/yaml-ld

[VladimirAlexiev]

Hi @ioggstream @pchampin @iherman!

• Could you please clarify the status of this PR?
• The content type doesn't appear at https://www.iana.org/assignments/media-types/media-types.xhtml#application
• In addition to this PR, https://json-ld.github.io/yaml-ld/spec/#iana defines the same type

Once resolved, we should also close w3c/json-ld-syntax#385

[ioggstream]

Hi @VladimirAlexiev. This PR has been closed because we decided to move the LD stuff to github.com/json-ld/yaml-ld :)

I will double-check the w3c/json-ld-syntax#385 to ensure that all registration parameters are ok.