API Response structure defined vs expected by validator

[deepananbu]

MOD API spec defined the response structure for endpoint "/artefact/{artefactID}" as below,

But the validator expects the attributes directly and not under the object "mod:SemanticArtefact", which looks like,

{
"@context": {
"adms": "http://www.w3.org/ns/adms#",
"cc": "http://creativecommons.org/ns#",
"dc": "http://purl.org/dc/elements/1.1/",
"dcat": "http://www.w3.org/ns/dcat#",
"dcterms": "http://purl.org/dc/terms/",
"doap": "http://usefulinc.com/ns/doap#",
"foaf": "http://xmlns.com/foaf/0.1/",
"ical": "http://www.w3.org/2002/12/cal/ical#",
"mod": "https://w3id.org/mod#",
"odrl": "http://www.w3.org/ns/odrl/2/",
"owl": "http://www.w3.org/2002/07/owl#",
"pav": "http://purl.org/pav/",
"prov": "http://www.w3.org/ns/prov#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"schema": "https://schema.org/",
"sd": "http://www.w3.org/ns/sparql-service-description#",
"skos": "http://www.w3.org/2004/02/skos/core#",
"vann": "https://vocab.org/vann/",
"vcard": "http://www.w3.org/2006/vcard/ns#",
"void": "http://rdfs.org/ns/void#",
"xsd": "http://www.w3.org/2001/XMLSchema#"
},
"@id": "https://example.org/SemanticArtefact/SemanticArtefactID",
"@type": "mod:SemanticArtefact",
"dcterms:accessRights": "string",
"dcterms:conformsTo": "string",
"dcat:contactPoint": {
"@id": "https://example.org/vcardKind/vcardKindID",
"@type": "vcard:Kind",
"vcard:fn": "Corky Crystal",
"vcard:nickname": "Corks"
}
}

@syphax-bouazzouni - Correct me if I'm wrong.

@jonquet - Could you please confirm which structure needs to be followed?

[jonquet]

Looks like a duplicate of #48 Do you confirm?
If yes, it let you close. @antony-wilson is looking into #48

[deepananbu]

@jonquet - It is not about the prefix in the attributes as stated in #48 . It is about whether we need attributes under "mod:semanticArtefact" or not. Does the fix for #48 covers this change as well?

[syphax-bouazzouni]

@jonquet here it is about having in the /artefacts/{acronym}, all the attribute are under mod:SemanticArtefact

[jonquet]

Sorry, I got it. (doing other things in // today). I believe we do not need the attributes to be under mod:SemanticArtefact

What is the JSON-LD spec saying?

@antony-wilson Any info?$
If we decide not to have the attributes under mod:SemanticArtefact can you regenerate the spec?

[antony-wilson]

updated in commit c964188

@syphax-bouazzouni should the same changes be made for endpoints /artefacts/{artefactID}/distributions/{distributionID}, /artefacts/{artefactID}/distributions/latest, /artefacts/{artefactID}/record, /, and /records/{artefactID}