remove fields from croissant once it's provided by the Hub API
Once the Hub provides an API to access the croissant metadata (https://github.com/huggingface/moon-landing/pull/9106, internal), we will be able to remove the following fields from the croissant response:
- `name`
- `description`
- `license`
- `url`

Also: we could provide `identifier` (DOI) from the Hub API, and remove it here.

Finally: it might be better to rename the datasets server endpoint /croissant-fragment, or something that indicates that it's a partial answer, not the full specification. The endpoint will only provide:
```json
{
  "@context": context,
  "@type": "sc:Dataset",
  "conformsTo": "http://mlcommons.org/croissant/1.0",
  "distribution": distribution,
  "recordSet": record_set
}
```
remove fields from croissant once it's provided by the Hub API: Once the Hub provides an API to access the croissant metadata (https://github.com/huggingface/moon-landing/pull/9106, internal), we will be able to remove the following fields from the croissant response:
- `name`
- `description`
- `license`
- `url`

Also: we could provide `identifier` (DOI) from the Hub API, and remove it here.

Finally: it might be better to rename the datasets server endpoint /croissant-fragment, or something that indicates that it's a partial answer, not the full specification. The endpoint will only provide:
```json
{
  "@context": context,
  "@type": "sc:Dataset",
  "conformsTo": "http://mlcommons.org/croissant/1.0",
  "distribution": distribution,
  "recordSet": record_set
}
```