# Query a remote rdf file from studio

**URL:** <https://community.stardog.com/t/query-a-remote-rdf-file-from-studio/1351>\
**Category:** Stardog Studio\
**Created:** [October 24, 2018, 12:11am UTC](https://community.stardog.com/t/query-a-remote-rdf-file-from-studio/1351 "2018-10-24T00:11:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicholsn](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/nicholsn/32/284_2.png) [@nicholsn](https://community.stardog.com/u/nicholsn)\
**Post date:** [October 24, 2018, 12:11am UTC](https://community.stardog.com/t/query-a-remote-rdf-file-from-studio/1351/1 "2018-10-24T00:11:31Z")

</div>

Hello,

How would I go about querying a remote RDF file?

I was thinking that including a web accessible turtle file in the FROM clause would issue an HTTP GET of the file, but when I execute this is Studio, I don't get any results.

```
SELECT *
FROM <https://w3id.org/phuse/study#> 
WHERE {?s ?p ?o .}

```

Thanks!

Nolan

---

<div class="post-metadata">

**Author:** ![zachary.whitley](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/zachary.whitley/32/94_2.png) [@zachary.whitley](https://community.stardog.com/u/zachary.whitley)\
**Post date:** [October 24, 2018, 10:08am UTC](https://community.stardog.com/t/query-a-remote-rdf-file-from-studio/1351/2 "2018-10-24T10:08:21Z")

</div>

Stardog doesn’t support that but you can load the data with `load data <url>`

[https://www.w3.org/TR/sparql11-update/#load](https://www.w3.org/TR/sparql11-update/#load)

---

<div class="post-metadata">

**Author:** ![nicholsn](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/nicholsn/32/284_2.png) [@nicholsn](https://community.stardog.com/u/nicholsn)\
**Post date:** [October 24, 2018, 2:50pm UTC](https://community.stardog.com/t/query-a-remote-rdf-file-from-studio/1351/3 "2018-10-24T14:50:16Z")

</div>

OK thanks! It would be a handy feature to have, but this works.

---

<div class="post-metadata">

**Author:** ![zachary.whitley](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/zachary.whitley/32/94_2.png) [@zachary.whitley](https://community.stardog.com/u/zachary.whitley)\
**Post date:** [October 24, 2018, 3:03pm UTC](https://community.stardog.com/t/query-a-remote-rdf-file-from-studio/1351/4 "2018-10-24T15:03:32Z")

</div>

I can see how it might be handy. The Stardog documentation mentions how it's not supported at [Home | Stardog Documentation Latest](https://www.stardog.com/docs/#_why_don_t_my_queries_work) . I think the specs say that supporting this is up to the implementation. I personally have found it to be unnecessarily confusing as it really overloads FROM and FROM NAMED. What if there's something already in the default graph? Is it added or does it shadow? What if query all graphs is enabled? What if I use just FROM or just FROM NAMED? Maybe I just over think it but it seems to cause a lot of combinations of what _could_ happen to justify the convenience but that's just my opinion especially since there is the LOAD DATA command.

The docs have also listed this limitation under [Home | Stardog Documentation Latest](https://www.stardog.com/docs/#_known_issues_2) which seems to imply that it might change in the future so I'm not quite sure where this stands.

---

<div class="post-metadata">

**Author:** ![nicholsn](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/nicholsn/32/284_2.png) [@nicholsn](https://community.stardog.com/u/nicholsn)\
**Post date:** [October 24, 2018, 7:21pm UTC](https://community.stardog.com/t/query-a-remote-rdf-file-from-studio/1351/5 "2018-10-24T19:21:04Z")

</div>

Ya I can see that there are a lot of things that 'could' happen - thanks for the pointer to the docs.

Part of why I was thinking this way is that the source will be updated frequently (data catalog) but isn't that big, so I'll need to drop the old dataset before each "LOAD INTO GRAPH "... no biggie though.