Collect result as array

[linonetwo]

Can I do something likes:

{ ... on Container { contains contains { type[] } } }

To collect type field into an array?

Since currently

{ ... on Container { contains contains { type } } }

Returns

{​
"?contains": Object { id: "https://new-japanese-concise-tutorial.solid.authing.cn/public/textbook/new-japanese-concise-tutorial-chapter-1-table.csv" },
"?contains_type": Object { id: "http://www.w3.org/ns/iana/media-types/text/csv#Resource" }
}
​
{
"?contains": Object { id: "https://new-japanese-concise-tutorial.solid.authing.cn/public/textbook/new-japanese-concise-tutorial-chapter-1-table.csv" },
"?contains_type": Object { id: "http://www.w3.org/ns/ldp#Resource" }
​}

Object { "?contains_type": {…}, "?contains": {…} }
Object { "?contains_type": {…}, "?contains": {…} }

Which is quite redundent, it's better if I can collect ?contains_type field into an array and destructure the id:

{
"?contains": "https://new-japanese-concise-tutorial.solid.authing.cn/public/textbook/new-japanese-concise-tutorial-chapter-1-table.csv" },
"?contains_type": ["http://www.w3.org/ns/ldp#Resource", "http://www.w3.org/ns/iana/media-types/text/csv#Resource"]
​}

I've tried this to destructure, but it doesn't work on my endpoint ( and I didn't find a way to collect them into an array):

{ ... on Container { contains { id } contains { type { id } } } }

SELECT ?contains_id ?contains_type_id WHERE {
  OPTIONAL {
    ?b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/ns/ldp#Container>;
      <http://www.w3.org/ns/ldp#contains> ?contains.
    ?contains <http://www.w3.org/1999/02/22-rdf-syntax-ns#id> ?contains_id.
    ?b1 <http://www.w3.org/ns/ldp#contains> ?contains.
    ?contains <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> ?contains_type.
    ?contains_type <http://www.w3.org/1999/02/22-rdf-syntax-ns#id> ?contains_type_id.
  }
}

[rubensworks]

You should be able to achieve this using our custom @singular JSON-LD context keyword.

Here's an example query of how this works: http://query.linkeddatafragments.org/#transientDatasources=http%3A%2F%2Ffragments.dbpedia.org%2F2016-04%2Fen&query=%7B%0A%20%20label%0A%20%20director%20%7B%0A%20%20%20%20label%0A%20%20%7D%0A%20%20starring(label_en%3A%20%22Brad%20Pitt%22)%0A%7D&queryContext=%7B%0A%20%20%22%40context%22%3A%20%7B%0A%20%20%20%20%22label%22%3A%20%7B%20%22%40id%22%3A%20%22http%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23label%22%2C%20%22%40singular%22%3A%20true%20%7D%2C%0A%20%20%20%20%22label_en%22%3A%20%7B%20%22%40id%22%3A%20%22http%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23label%22%2C%20%22%40language%22%3A%20%22en%22%20%7D%2C%0A%20%20%20%20%22director%22%3A%20%7B%20%22%40id%22%3A%20%22http%3A%2F%2Fdbpedia.org%2Fontology%2Fdirector%22%2C%20%22%40singular%22%3A%20true%20%7D%2C%0A%20%20%20%20%22director_label%22%3A%20%7B%20%22%40singular%22%3A%20false%20%7D%2C%0A%20%20%20%20%22starring%22%3A%20%7B%20%22%40id%22%3A%20%22http%3A%2F%2Fdbpedia.org%2Fontology%2Fstarring%22%2C%20%22%40singular%22%3A%20true%20%7D%0A%20%20%7D%0A%7D&resultsToTree=true&queryFormat=graphql

You should be able to make this work by setting @singularize to true on contains and to false on contains_type.

[linonetwo]

But executing graphql-to-sparql ~/Desktop/context.json "{ ... on Container { contains contains { type } } }" on

  "contains": { "@id": "http://www.w3.org/ns/ldp#contains", "@singular": true },
  "contains_type": { "@singular": false },

and

"contains": "http://www.w3.org/ns/ldp#contains",

results are the same, they are both:

SELECT ?contains ?contains_type WHERE {
  OPTIONAL {
    ?b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/ns/ldp#Container>;
      <http://www.w3.org/ns/ldp#contains> ?contains, ?contains.
    ?contains <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> ?contains_type.
  }
}

And, what is @singularize? Is that a graphql directive?

---

update

Oh, this @singular seems to be a feature in comunica engine, so graphql-to-sparql cli don't use it.

But I can't get a list with comunica engine too.

[rubensworks]

@linonetwo How are you invoking Comunica exactly?

[linonetwo]

This is the code trying to query SoLiD POD:

https://github.com/linonetwo/new-japanese-concise-tutorial-interactive/blob/0db7b64c1b52b7da8a2c4449a3c9e3340008b52d/src/store/texts.ts#L107

And I'm using this JSON-LD context:

https://github.com/linonetwo/new-japanese-concise-tutorial-interactive/blob/0db7b64c1b52b7da8a2c4449a3c9e3340008b52d/src/store/ldpContext.json#L103

We are planning to use GraphQL in our SoLiD app to reduce developers' learning curve, so I made this demo project for a prior-art search, preparing some example codes.

[rubensworks]

This is the code trying to query SoLiD POD

Your code looks fine to me, so this must be a bug in GraphQL-LD or Comunica. I'll look into it when I have time.

We are planning to use GraphQL in our SoLiD app to reduce developers' learning curve, so I made this demo project for a prior-art search, preparing some example codes.

I see, interesting!