@@ -10469,16 +10469,30 @@ <h3>application/ld+json</h3>
10469
10469
It is RECOMMENDED that profile URIs are dereferenceable and provide
10470
10470
useful documentation at that URI. For more information and background
10471
10471
please refer to [[RFC6906]].</ p >
10472
- < p > This specification defines three values for the < code > profile</ code > parameter.
10473
- To request or specify < a href ="#expanded-document-form "> expanded JSON-LD document form</ a > ,
10474
- the URI < code > http://www.w3.org/ns/json-ld#expanded</ code > SHOULD be used.
10475
- To request or specify < a href ="#compacted-document-form "> compacted JSON-LD document form</ a > ,
10476
- the URI < code > http://www.w3.org/ns/json-ld#compacted</ code > SHOULD be used.
10477
- To request or specify < a href ="#flattened-document-form "> flattened JSON-LD document form</ a > ,
10478
- the URI < code > http://www.w3.org/ns/json-ld#flattened</ code > SHOULD be used.
10479
- Please note that, according [[HTTP11]], the value of the < code > profile</ code >
10480
- parameter has to be enclosed in quotes (< code > "</ code > ) because it contains
10481
- special characters and, if multiple profiles are combined, whitespace.</ p >
10472
+ < p > This specification defines four values for the < code > profile</ code > parameter.</ p >
10473
+ < dl >
10474
+ < dt > < code > http://www.w3.org/ns/json-ld#expanded</ code > </ dt >
10475
+ < dd > To request or specify < a href ="#expanded-document-form "> expanded JSON-LD document form</ a > .</ dd >
10476
+ < dt > < code > http://www.w3.org/ns/json-ld#compacted</ code > </ dt >
10477
+ < dd > To request or specify < a href ="#compacted-document-form "> compacted JSON-LD document form</ a > .</ dd >
10478
+ < dt > < code > http://www.w3.org/ns/json-ld#flattened</ code > </ dt >
10479
+ < dd > To request or specify < a href ="#flattened-document-form "> flattened JSON-LD document form</ a > .</ dd >
10480
+ < dt > < code > http://www.w3.org/ns/json-ld#framed</ code > </ dt >
10481
+ < dd > To request or specify < a href ="#framed-document-form "> framed JSON-LD document form</ a > .</ dd >
10482
+ </ dl >
10483
+ < p >
10484
+ When used as a < a data-cite ="RFC2048#section-2.2.3 "> media type paramter</ a > [[RFC2048]]
10485
+ in an < a data-cite ="rfc7231#section-5.3.2 "> HTTP Accept header</ a > [[RFC7231]],
10486
+ the value of the < code > profile</ code > parameter MUST be enclosed in quotes (< code > "</ code > ) if it contains
10487
+ special characters such as whitespace, when multiple profiles are combined.</ p >
10488
+ < p > In addition to the < code > profile</ code > values described above,
10489
+ the < code > profile</ code > parameter MAY include one additional URL, which is interpreted as
10490
+ the location of either a < a > context</ a > or < a > frame</ a > , depending on the other profile
10491
+ parameters included. When used without an defined profile URI, such a URL
10492
+ is interpreted as the location of a < a > context</ a > .</ p >
10493
+ < p > JSON-LD processors MAY place restrictions on supported profiles,
10494
+ MAY provide defaults for < a > context</ a > and < a > frame</ a > URLs,
10495
+ and MAY restrict client-provided URLs for < a > contexts</ a > and < a > frames</ a > .</ p >
10482
10496
< p > When processing the "profile" media type parameter, it is important to
10483
10497
note that its value contains one or more URIs and not IRIs. In some cases
10484
10498
it might therefore be necessary to convert between IRIs and URIs as specified in
@@ -10488,9 +10502,9 @@ <h3>application/ld+json</h3>
10488
10502
</ dl >
10489
10503
</ dd >
10490
10504
< dt > Encoding considerations:</ dt >
10491
- < dd > See < a data-cite ="RFC6839 #section-3.1 "> RFC 6839 , section 3.1 </ a > .</ dd >
10505
+ < dd > See < a data-cite ="RFC8259 #section-11 "> RFC 8259 , section 11 </ a > .</ dd >
10492
10506
< dt > Security considerations:</ dt >
10493
- < dd > See [[RFC8259]]
10507
+ < dd > See < a data-cite =" RFC8259#section-12 " > RFC 8259, section 12 </ a > [[RFC8259]]
10494
10508
< p > Since JSON-LD is intended to be a pure data exchange format for
10495
10509
directed graphs, the serialization SHOULD NOT be passed through a
10496
10510
code execution mechanism such as JavaScript's < code > eval()</ code >
0 commit comments