http:\/\/data.southampton.ac.uk\/payments\/201106\/payment-50350344.html<\/a><\/p>\n“This page shows raw data about this resource. We have not yet had the time to build a pretty viewer for this type of item. Don’t worry if it seems a bit arcane — you are looking under the hood of our service into the data inside! You can download this data in the following formats: rdf, ttl, json, xml.”<\/p>\n
I think just telling people that this page isn’t the droids they are looking for will help them move along without distress, and should be considered good practice.<\/p>\n
ps. The Linked Data API does one thing I have a real issue with, it can only be configured to follow “forward” relationships from a resource. So you can show a person and their name & phonebumber and follow the link to their address and follow the link from their to their city. What you can’t do is follow an inverse link like “foaf:member” which links from a group to a person, not a person to a group. It could easily be fixed by a tiny tweak where you define an inverse relationship for the property and give that a label, and the system will look for both it and its reverse. This is much cleaner (and semantic) than having people create inverse triples for every membership in their database to appease the whims of the linked data API. I know I should join the community, and argue for it there, but I don’t have time. Sorry.<\/p>\n","protected":false},"excerpt":{"rendered":"
I don’t like the linked data API, but not because it’s a bad design, but because you end up with scary confusing HTML webpages which people end up on by accident and have no cue as to what to do next. It’s my strong opinion that when producing a system that will mass produce HTML […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[198,136],"tags":[],"class_list":["post-744","post","type-post","status-publish","format-standard","hentry","category-best-practice","category-rdf"],"_links":{"self":[{"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/posts\/744","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/comments?post=744"}],"version-history":[{"count":5,"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/posts\/744\/revisions"}],"predecessor-version":[{"id":759,"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/posts\/744\/revisions\/759"}],"wp:attachment":[{"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/media?parent=744"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/categories?post=744"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/webteam\/wp-json\/wp\/v2\/tags?post=744"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}