[Croissant] The API supports a parameter to produce either an abridged JSON-LD or a full-length JSON-LD
**Issue**: Croissant JSON-LD are embedded in Hugging Face's HTML page. As JSON-LD can get lengthy, they are truncated ([see the code](https://github.com/huggingface/datasets-server/blob/1759d65fa668f35067175cfb3210666c1b7c3f47/services/api/src/api/routes/croissant.py#L99)).

**Proposed solution**: Add a parameter `?full=true/false` (with a default to false) to toggle between the abridged version or the full-length version of the JSON-LD. Hugging Face would use the abridged version to embed in their HTML page, while still allowing users to retrieve the full version to produce a valid Croissant file. Ideally the description of the abridged version would state that it's (or may be) abridged, and provide the URL of the full version. This is a temporary solution while waiting for <meta> tags to support URLs rather than in-lined JSON.

@lhoestq @severo What do you think? Also, what convention do you usually use for the URL parameters? Do you have examples of such routes? If I have your go, I could implement this. Thanks for your input!
[Croissant] The API supports a parameter to produce either an abridged JSON-LD or a full-length JSON-LD: **Issue**: Croissant JSON-LD are embedded in Hugging Face's HTML page. As JSON-LD can get lengthy, they are truncated ([see the code](https://github.com/huggingface/datasets-server/blob/1759d65fa668f35067175cfb3210666c1b7c3f47/services/api/src/api/routes/croissant.py#L99)).

**Proposed solution**: Add a parameter `?full=true/false` (with a default to false) to toggle between the abridged version or the full-length version of the JSON-LD. Hugging Face would use the abridged version to embed in their HTML page, while still allowing users to retrieve the full version to produce a valid Croissant file. Ideally the description of the abridged version would state that it's (or may be) abridged, and provide the URL of the full version. This is a temporary solution while waiting for <meta> tags to support URLs rather than in-lined JSON.

@lhoestq @severo What do you think? Also, what convention do you usually use for the URL parameters? Do you have examples of such routes? If I have your go, I could implement this. Thanks for your input!