permit Titanium JsonLD compactArrays property configuration

[ndr-brt]

Feature Request

As reported in various issues as:

• [contract definition] Error when retrieving a single contract definition  #3137
• DSP catalog dataset is an object instead of a list with only 1 asset in the DB #3232
• DSP dataset hasPolicy is supposed to be a list #3233
  (this issue will supersede them)

Seems that it would be useful for some users to have the jsonld array not compacted by default when they have a single entry.
To solve this, we could set compactArrays to false by default, leaving the possibility to enable it with a configuration setting.

However, just for the record, the rule of thumb is to always expand a json-ld before processing it, because the compaction process can have different outputs.

Which Areas Would Be Affected?

json-ld extension

[juliapampus]

As decided in the DSP group, an array with only one item should never be compacted to an object on the DSP layer. Thus, the current behaviour needs to be changed, and the requested configuration should only apply to EDC-specific APIs.

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale.

[florianrusch-zf]

Still an open point. We discovered this also in the catalog regarding the distribution field. We received an object instead of an array. We also looked into the swagger documentation, where is pointed out, that the distribution should be an array, also if only one object is within the array.

From the swagger docu for 0.5.3:

"dcat:distribution": [
      {
        "@type": "dcat:Distribution",
        "dct:format": {
          "@id": "HttpData"
        },
        "dcat:accessService": "5e839777-d93e-4785-8972-1005f51cf367"
      }
    ]

And btw. the @id is wrong in the example response...

From an 0.5.3 EDC catalog request:

            "dcat:distribution": {
                "@type": "dcat:Distribution",
                "dct:format": {
                    "@id": "HttpProxy"
                },
                "dcat:accessService": "812ea4ba-d691-4926-a191-d34f25780032"
            },

[ndr-brt]

@florianrusch-zf in fact the two representations you pasted are equivalent for the json-ld specs. the committer group decided that this issue is not so important to be put in a milestone, the general suggestion is to always expand the json-ld response body before processing (as this typescript client and this java client do).

anyway, we're open for contributions, feel free to provide one.

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale.