JSON-LD syntax and multiple outputs

[jonquet]

During the call yesterday we had a question related to the JSON-LD format that was not necessarily anwser with all the elements I realized afterwards.

Question was :
Is this syntax ok for accessRights? ...

...In comparison to OntoPortal's team prototype:

...And with respect to MOD ttl:

Accessible here: https://github.com/FAIR-IMPACT/MOD/blob/main/mod.ttl#L985

The response is yes. The syntax exemplified by the MOD-API spec is valid. It's JSON-LD compliant. This supposes the information about the access rights (that in this exemple is of type dct:rightsStatement) is an object which URI is 'https://example.org/RightsStatement/RightsStatementID'
But this is not the unique exmple of response. MOD. ttl being flexible on the range of the 'dct:accessRights' property (i.e., there is no formal rdfs:range property but only a 'dct:rangeIncludes') it accepts a value of any type for 'dct:accessRights' and also a 'dct:RightsStamtent'.

Thus a response where the "value" of accessRights would be the string "public" like in the OntoPortal exemple is also valid response. But the syntax exemplified is not right (as said, OntoPortal's implementaiton is not yet finished). The right sentence that the second example should have returned is:

 "dct:accessRights": {
        "@type": "xsd:string",
        "@value": "public"
      }

[jonquet]

Note that we also discussed the discrepancy with the prefix 'dct' uses in MOD-API spec and 'dcterms' used in mod.ttl.
I have created an issue to address this soon: #6

[manuelfiorelli]

Hi @jonquet, I'm facing this exact problem in my implementation. Should I be pedantic about following the JSON schema or allow any valid representation?

Another problematic property is dct:description, which is described in the schema as having a resource reference as value, while a simple literal would be sufficient (and more practical) in many cases. Additionally, this property is currently single valued, while in a multilingual scenario someone might want to declare multiple descriptions in different languages.

[manuelfiorelli]

I've noticed so far that other occurrencesa of dct:description and dct:title are defined with a literal value. I thus filed an issue: #26