# HTTP Accept header when request an OWL ontology

**URL:** <https://community.stardog.com/t/http-accept-header-when-request-an-owl-ontology/710>\
**Category:** Support\
**Created:** [November 30, 2017, 1:47pm UTC](https://community.stardog.com/t/http-accept-header-when-request-an-owl-ontology/710 "2017-11-30T13:47:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbooth](https://avatars.discourse-cdn.com/v4/letter/d/a698b9/32.png) [@dbooth](https://community.stardog.com/u/dbooth)\
**Post date:** [November 30, 2017, 1:47pm UTC](https://community.stardog.com/t/http-accept-header-when-request-an-owl-ontology/710/1 "2017-11-30T13:47:40Z")

</div>

What HTTP Accept header does Stardog issue when it tries to GET an OWL ontology from a URL?

We have been working on an RDF representation of FHIR, the new HL7 standard for healthcare data interchange. We have noticed that when Protege does an HTTP request for an OWL ontology, it uses an Accept header that asks for RDF/XML but not Turtle. (The exact Accept header is “application/rdf+xml, application/xml; q=0.5, text/xml; q=0.3, _/_; q=0.2”.) This causes a problem with FHIR, because FHIR has XML (_not_ RDF/XML) and Turtle representations, so the FHIR server returns the XML instead of the desired Turtle. We are wondering if this will be a problem with other RDF tooling, such as Stardog. The proper fix, of course, is to update the Accept header that Protege issues, to include more OWL and RDF formats, including Turtle. We are also working with the Protege developers to get this fixed, but we are also pursuing an interim solution.

Again, my question is: What HTTP Accept header does Stardog issue when it tries to GET an OWL ontology from a URL?

---

<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:** [November 30, 2017, 2:52pm UTC](https://community.stardog.com/t/http-accept-header-when-request-an-owl-ontology/710/2 "2017-11-30T14:52:17Z")

</div>

You don't mention how you are getting Stardog to issue the GET but Stardog doesn't support importing owl:imports statements automatically.

> **[Home](https://docs.stardog.com/)**
>
> Documentation for Stardog, the world’s leading Knowledge Graph Platform for the Enterprise

If you add some more details about what you're looking to do I can possibly offer some suggestions.

---

<div class="post-metadata">

**Author:** ![dbooth](https://avatars.discourse-cdn.com/v4/letter/d/a698b9/32.png) [@dbooth](https://community.stardog.com/u/dbooth)\
**Post date:** [November 30, 2017, 3:15pm UTC](https://community.stardog.com/t/http-accept-header-when-request-an-owl-ontology/710/3 "2017-11-30T15:15:05Z")

</div>

Ok, then it may be moot. Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/e/ed66b48a616f505106a4acde3c9cee7e6da9bc67.svg) [@system](https://community.stardog.com/u/system)\
**Post date:** [December 14, 2017, 3:15pm UTC](https://community.stardog.com/t/http-accept-header-when-request-an-owl-ontology/710/4 "2017-12-14T15:15:09Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.