My guess is that Talis is balking at my libraries accept header which
lists a whole load of MIME types including some that the platform
doesn't support and this might be the cause the error - or it could be
something else entirely?
Sample queries are the following and executed against the space store
(http://api.talis.con/stores/space/) Leigh demo'd at the London Linked
Data Meetup:
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
PREFIX space: <http://purl.org/net/schemas/space/>
DESCRIBE ?spacecraft WHERE
{
?launch a space:Launch ;
space:spacecraft ?spacecraft ;
space:launched ?launched .
FILTER(?launched > "2010-01-01"^^xsd:date)
} LIMIT 10
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
PREFIX space: <http://purl.org/net/schemas/space/>
CONSTRUCT
{
?spacecraft space:launched ?launched .
}
WHERE
{
?launch a space:Launch ;
space:spacecraft ?spacecraft ;
space:launched ?launched .
FILTER(?launched > "2009-01-01"^^xsd:date)
}
The accept header my library sends is the following:
application/rdf+xml,text/xml,text/n3,text/rdf+n3,text/
turtle,application/x-turtle,application/turtle,text/plain,application/
json;q=0.9,*/*;q=0.8
Cheers,
Rob Vesse
Rob
Hi Rob
I've updated the ticket you raised - see http://talisplatform.zendesk.com/tickets/64.
This is a known issue and the workaround for the moment is to remove
text/turtle from the accept header.
cheers
Amanda
I have made this change as a workaround and pushed it out as part of
the new release of my API
Rob