[ 
https://issues.apache.org/jira/browse/JENA-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne resolved JENA-2344.
---------------------------------
      Assignee: Andy Seaborne
    Resolution: Not A Problem

> Invalid JSON-LD context generated for CONSTRUCT query
> -----------------------------------------------------
>
>                 Key: JENA-2344
>                 URL: https://issues.apache.org/jira/browse/JENA-2344
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: ARQ, Fuseki, JSON-LD
>    Affects Versions: Jena 4.1.0, Jena 4.5.0
>            Reporter: Stefan Bischof
>            Assignee: Andy Seaborne
>            Priority: Major
>
> For URIs having a slash / in the fragment identifier an invalid JSON-LD 
> context is generated.
>  
> Steps to reproduce:
>  # Add a triple with with a slash in the fragment identifier to some graph, 
> e.g., "[] 
> <[https://smart-data-models.github.io/data-models/terms.jsonld#/definitions/category]>
>  "meter" .
>  # Retrieve the triple in a CONSTRUCT query, e.g., CONSTRUCT WHERE \{ ?s ?p 
> ?o }
>  # Set "Accept" header in HTTP call or "Content-Type (Graph)" in Fuseki WebUI
>  # The context at the end of the response includes the invalid key 
> "/definitions/category"
> {
>   "@id" : "_:b0",
>   "/definitions/category" : "meter",
>   "@context" : {
>     "/definitions/category" : {
>       "@id" : 
> "https://smart-data-models.github.io/data-models/terms.jsonld#/definitions/category";
>     }
>   }
> }
>  
> Although I couldn't find a formal grammar for JSON-LD, the python parser I 
> used and the parser on the JSON-LD playground 
> [https://json-ld.org/playground/] did not accept this: jsonld.SyntaxError: 
> Invalid JSON-LD syntax; term in form of IRI must expand to definition.
> I could replicate the same behaviour on the cli with ARQ 4.5.0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to