search

jackie1929 / linked-data-api

Automatically exported from code.google.com/p/linked-data-api
0 stars 0 forks source link

Non-existant resources returned by Item Endpoint #12

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
http://reference.data.gov.uk/doc/department/co/post/93.json

This API call returns a post with the ID "93" all fine and dandy, within my 
JavaScript I can test for the usual values such as primaryTopic._about to check 
it's been returned ok.

http://reference.data.gov.uk/doc/department/co/post/412.json

This API call uses a random (and non-existant) post ID I've typed in, yet it 
seems to still return an item, which appears to be valid - just lacking data. 

This gives the impression that this post exists within the data when I was 
hoping for something more along the lines of primaryTopic:[] (similar to 
items:[] when there are no results from a List Endpoint).

Dan

Original issue reported on code.google.com by danpaulsmith on 13 Apr 2011 at 2:34

GoogleCodeExporter commented 8 years ago 
It makes sense that item._about should signal an item exists and result._about 
should resemble the API request made.

Original comment by danpaulsmith on 13 Apr 2011 at 2:37