Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

id in GraphQl query bug for text/turtle request #95

Open
renevds opened this issue Jul 28, 2021 · 3 comments
Open

id in GraphQl query bug for text/turtle request #95

renevds opened this issue Jul 28, 2021 · 3 comments

Comments

@renevds
Copy link
Contributor

renevds commented Jul 28, 2021

When requesting text/turtle for a set of queries that has id, all queries must have id in their query.

Minimal failing config:

openapi: 3.0.2
info:
  title: Test site
  version: 0.1.0
paths:
  /example:
    get:
      summary: A simple path
      responses:
        '200':
          description: A simple response
          x-walder-input-text/html: template.pug
      x-walder-query:
        graphql-query:
          first: |
            {
              id @single
              comment @single @optional
            } 
#adding id @single to this query makes it work correctly
          second: |
            {
              comment @single @optional
            }
        json-ld-context: |
          {
            "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
            "comment": "rdfs:comment"
          }
        datasources:
          sources:
            - http://localhost:8080/example.ttl
RDF source for reference:
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix odapps: <http://apps4eu.eu/vocab/odapps#>.
@prefix apps4X: <http://semweb.mmlab.be/ns/apps4X#>.
@prefix schema: <http://schema.org/> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix time: <http://www.w3.org/2006/time#> .
@prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix lode: <http://linkedevents.org/ontology/> .
@prefix dul: <http://www.loa-cnr.it/ontologies/DUL.owl#> .
@prefix rev: <http://purl.org/stuff/rev#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#>.


# ---------------------------------------- Metadata----------------------------------------------

<http://semweb.mmlab.be/ns/apps4X#>
	a owl:Ontology;
	rdfs:comment "odapps is an RDF vocabulary defined to facilitate the description of Open-Data-based ideas and applications published on the Web.";
	dct:title "The vocabulary for (L)OD ideas and applications"@en;
	dct:issued "2013-05-10"^^xsd:date;
        dct:modified "2013-07-24"^^xsd:date;
	dct:creator [foaf:mbox "[email protected]"; foaf:name "Anastasia Dimou"];
	dct:creator [foaf:mbox "[email protected]"; foaf:name "Pieter Colpaert"].


# ------------------------------------------ Classes --------------------------------------------

# Co-creation Event

# need to decide on the proper word to call it, is co-creation event? is it co-creation competition? is it competition? is it contest? 
# or use alternative labels.
# A cocreation event may be an event on its own or it could be a competition in the frame of a broader event
apps4X:CocreationEvent a rdfs:Class ;
	rdfs:subClassOf lode:Event, schema:Event ; 
	rdfs:label "Co-creation event" ;
	rdfs:comment "A co-creation event is a competition, a contest, a challenge etc. It's a subproperty as it is an event but with a certain scope" ;
	rdfs:isDefinedBy <http://apps4europe.eu/vocab/apps4X#>  .

# ---------------------------------------- Properties --------------------------------------------


#apps4X:award

#it could be more than one awards offered
apps4X:award a rdf:Property ;
	rdfs:label "award offered" ;
	rdfs:comment "one or more awards offered at this co-creation event" ;
	rdfs:isDefinedBy <http://apps4europe.eu/vocab/apps4X#> ;
	rdfs:domain apps4X:CocreationEvent , apps4X:Jury ;
	rdfs:range apps4X:Award .
@pheyvaer
Copy link
Collaborator

We will need the full config file. This is not a full minimal failing example.

@renevds
Copy link
Contributor Author

renevds commented Jul 28, 2021

We will need the full config file. This is not a full minimal failing example.

Is this ok?

@pheyvaer
Copy link
Collaborator

Yes, great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants