IANA Considerations

This section has been submitted to the Internet Engineering Steering Group (IESG) for review, approval, and registration with IANA.

application/ld+yaml

Type name:

application

Subtype name:

ld+yaml

Required parameters:

N/A

Optional parameters:

profile

A non-empty list of space-separated URIs identifying specific constraints or conventions that apply to a YAML-LD document according to [[RFC6906]]. A profile does not change the semantics of the resource representation when processed without profile knowledge, so that clients both with and without knowledge of a profiled resource can safely use the same representation. The profile parameter MAY be used by clients to express their preferences in the content negotiation process. If the profile parameter is given, a server SHOULD return a document that honors the profiles in the list which it recognizes, and MUST ignore the profiles in the list which it does not recognize. It is RECOMMENDED that profile URIs are dereferenceable and provide useful documentation at that URI. For more information and background please refer to [[RFC6906]].

This specification allows the use of the `profile` parameters listed in and additionally defines the following:

http://www.w3.org/ns/json-ld#extended

To request or specify extended YAML-LD document form.

This is a placeholder for specifying something like an extended YAML-LD document form making use of YAML-specific features.

When used as a media type parameter [[RFC4288]] in an HTTP Accept header field [[RFC9110]], the value of the profile parameter MUST be enclosed in quotes (") if it contains special characters such as whitespace, which is required when multiple profile URIs are combined.

When processing the "profile" media type parameter, it is important to note that its value contains one or more URIs and not IRIs. In some cases it might therefore be necessary to convert between IRIs and URIs as specified in section 3 Relationship between IRIs and URIs of [[RFC3987]].

Encoding considerations:

See YAML media type.

Security considerations:

See .

Interoperability considerations:

See .

Published specification:

http://www.w3.org/TR/yaml-ld

Applications that use this media type:

Any programming environment that requires the exchange of directed graphs. Implementations of YAML-LD have been created for FIXME.

Additional information:

Magic number(s):

Not Applicable

File extension(s):

.yamlld

Macintosh file type code(s):

TEXT

Person & email address to contact for further information:

Philippe Le Hégaret <plh@w3.org>

Intended usage:

Common

Restrictions on usage:

N/A

Author(s):

Roberto Polli, Gregg Kellogg

Change controller:

W3C