-
Notifications
You must be signed in to change notification settings - Fork 35
Design Objective: Follow Best Practices
- http://www.w3.org/DesignIssues/LinkedData.html
- http://linkeddata.org/guides-and-tutorials
- http://www.w3.org/TR/cooluris/
- http://www.w3.org/2001/tag/doc/httpRange-14/2007-05-31/HttpRange-14
- http://www4.wiwiss.fu-berlin.de/bizer/pub/LinkedDataTutorial/20070727/
- http://ontologydesignpatterns.org/wiki/Main_Page
- http://www.opendatacookbook.net/
- http://opendatamanual.org/ sponsored by the open knowledge foundation.
- http://linkeddatabook.com/editions/1.0/
- http://csarven.ca/how-to-create-a-linked-data-site
- http://pedantic-web.org/
- http://allinthehead.com/retro/245/
- http://tools.ietf.org/html/draft-gregorio-uritemplate-04
- http://www.ietf.org/id/draft-hausenblas-csv-fragment-00.txt
- http://dublincore.org/documents/dcmi-namespace-generic/
- http://www.w3.org/QA/2011/05/hash_uris.html
- http://nuts.geovocab.org/
- http://www.w3.org/DesignIssues/Abstractions.html
- http://www.companieshouse.gov.uk/about/miscellaneous/URI.shtml
- http://blog.opencorporates.com/2011/10/24/why-we-helped-design-the-new-uk-companies-house-uris/
- http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
- http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.1
- http://www.w3.org/2008/01/rdf-media-types
- http://www.w3.org/Provider/Style/URI.html
- http://www.cs.tut.fi/~jkorpela/tilde.html
- http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook#Ingredients_for_High_Quality_Linked_Data
- http://validator.linkeddata.org/vapour
- RFC uri templates http://www.w3.org/mid/4F2D2E6D.7030106@zoo.ox.ac.uk
- "Together with REEEP (Renewable Energy and Energy Efficiency Partnership) the Semantic Web Company (SWC) has composed a fundamental publication on the topic of Linked Open Data. Linked Open Data: The Essentials - is a a quick start guide for decision makers who need to quickly get up to speed with the Linked Open Data (LOD) concept and who want to make their organisation a part of this movement." http://www.semantic-web.at/news/swc-publishes-linked-open-data-essentials-book http://www.semantic-web.at/LOD-TheEssentials.pdf http://www.reeep.org/LOD-the-Essentials.pdf
- http://www.w3.org/TR/Content-in-RDF10/
- http://pydanny.blogspot.com/2011/08/github-is-my-resume.html
- Harry Halpin, Valentina Presutti. "An Ontology of Resources: Solving the Identity Crisis" In ESWC 2009.
- http://richard.cyganiak.de/blog/2008/03/what-is-your-rdf-browsers-accept-header/ this returns an RDF description of the Accept header that the tool submits.
- http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
- http://patterns.dataincubator.org/book/index.html
- http://www.cambridgesemantics.com/semantic-university/learn-semantic-web-design-patterns
- http://kerfors.blogspot.se/p/uri-design.html?m=1
- file path URIs: https://github.com/digital-preservation/droid/issues/4#issuecomment-19378109
- "Study on Persistent URIs with identification of best practices and recommendations on the topic for the Member States and the European Commission" by Phil Archer.
- http://richard.cyganiak.de/blog/2006/06/an-rdf-design-pattern-inverse-property-labels/
- http://www.bigdata.com/whitepapers/reifSPARQL.pdf
- Internet of Trees: http://ibmdatamag.com/2014/03/the-internet-of-trees/
- http://www.w3.org/TR/ld-bp
http://vivo.ufl.edu/individual/n1225880055 303s to http://vivo.ufl.edu/display/n1225880055, which includes:
<link rel="alternate" type="application/rdf+xml" href="/individual/n1225880055/n1225880055.rdf" />
<link rel="alternate" type="application/rdf+xml" href="http://id.loc.gov/vocabulary/countries.rdf"/>
rapper -q -g -o turtle http://id.loc.gov/vocabulary/countries.html
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix : <http://www.w3.org/1999/xhtml> .
<http://id.loc.gov/vocabulary/countries.html>
<http://www.w3.org/1999/xhtml/vocab#alternate> <http://id.loc.gov/vocabulary/countries.json>, <http://id.loc.gov/vocabulary/countries.nt>, <http://id.loc.gov/vocabulary/countries.rdf>, <http://id.loc.gov/vocabulary/countries/feed/1> ;
<http://www.w3.org/1999/xhtml/vocab#stylesheet> <http://id.loc.gov/static/css/loc_print_v2.css>, <http://id.loc.gov/static/css/loc_standard_v2.css> .
- SemanticOverflow
- http://answers.semanticweb.com/questions/?
- http://www.quora.com/Semantic-Web?q=Semantic+Web
That's an ongoing argument in http circles. The spec clearly allows it, and a lot of people think it's the implied recommended behavior. However, the spec has this informative note:
""" Note: HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request. In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of an incoming response to determine if it is acceptable. """
I think it's stupid, and clearly has an anti-user feel to it. If you're using Accept headers/conneg, then you have to be checking the content-type of the response anyway, so there shouldn't be any problem with sending them back a response with a type they didn't request if you can't satisfy their conneg preferences directly. But doing the 406 thing ends up fucking people up like you who try to do curl or something and end up with a zero-length content body. It's stupid (especially if there's no content body that tells you what media types are acceptable which IS recommended by the spec).
At the very least our system should include a list of acceptable media types. I'd suggest it should just be picking a canonical one, though, and returning that in case of conneg failure.
-g