Usage for profile parameter for JSON-LD requests
<p>The documentation of JSON-LD mentions that clients can provide a profile parameter to the <code>Accept</code> header can be used to control the representation. It defines the three defaults for requesting <strong>compacted</strong>, <strong>expanded</strong> or <strong>flattened</strong> JSON-LD documents. It does also say that </p>

<blockquote>
  <p>If the profile parameter is given, a server <code>should</code> return a document that honors the profiles in the list which are recognized by the server.</p>
</blockquote>

<p>It does not, however, explain whether there are any specific rules the server should follow. Is it completely up to the server to decide what the behavior is for custom profile URIs? Are there any discussions on that subject?</p>

<p>Would the examples below be correct?</p>

<p><strong>Example 1</strong></p>

<p>The client requests with</p>

<pre><code>Accept: application/ld+json; 
        profile="http://www.w3.org/ns/json-ld#compacted http://schema.org"
</code></pre>

<p>And the server returns compacted document with <code>http://schema.org</code> as <code>@context</code>?</p>

<p><strong>Example 2</strong></p>

<p>The client requests with</p>

<pre><code>Accept: application/ld+json; profile="http://schema.org"
</code></pre>

<p>And the server returns compacted document with <code>http://schema.org</code> as <code>@context</code>?</p>