# Service URI as a variable in Stardog 5

**URL:** <https://community.stardog.com/t/service-uri-as-a-variable-in-stardog-5/511>\
**Category:** Feature Request\
**Created:** [August 14, 2017, 2:30pm UTC](https://community.stardog.com/t/service-uri-as-a-variable-in-stardog-5/511 "2017-08-14T14:30:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndyVanDerHoeven](https://avatars.discourse-cdn.com/v4/letter/a/65b543/32.png) [@AndyVanDerHoeven](https://community.stardog.com/u/AndyVanDerHoeven)\
**Post date:** [August 14, 2017, 2:30pm UTC](https://community.stardog.com/t/service-uri-as-a-variable-in-stardog-5/511/1 "2017-08-14T14:30:55Z")

</div>

The Stardog manual states that “Stardog doesn’t support variables for the service URL (SERVICE ?serviceURL)”.

Will this feature be added in the upcoming version of Stardog?

It would be a very useful feature for geospatial querying using endpoints built dynamically from the coordinates of the start point.

---

<div class="post-metadata">

**Author:** ![mike](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/mike/32/14_2.png) [@mike](https://community.stardog.com/u/mike)\
**Post date:** [August 14, 2017, 2:44pm UTC](https://community.stardog.com/t/service-uri-as-a-variable-in-stardog-5/511/2 "2017-08-14T14:44:44Z")

</div>

While that syntax is valid SPARQL, queries of that type have _no_ defined semantics in the specification for us to implement. However, some vendors do have ad-hoc implementations for queries of this type. We have an open ticket to consider an implementation strategy for this, but it is not associated with any near-term milestone. That could change depending on customer feedback.