...
VIVO's implementation of linked data (Jim)
A linked data best practices document indicates that sending a license statement is recommended. VIVO has a Terms of Use statement that included a statement about content in linked data, and we will add that to each linked data response.
Sites should be aware of this text and make sure they agree with its terms: To the extent copyrightable, the information presented on the VIVO website and available as Resource Description Framework (RDF) data from VIVO at [ your institution name ] is intended for public use and is freely distributed under the terms of the Creative Commons CC-BY 3.0 license which allows you to copy, distribute, display and make derivatives of this information provided you give credit to [ your institution name ]. Any non-copyrightable information is available to you under a CC0 waiver.
This is the tutorial: http://wifo5-03.informatik.uni-mannheim.de/bizer/pub/LinkedDataTutorial/#deref, referenced from linkeddata.org
Content negotiation for VIVO and for VIVO's SPARQL endpoint
- Should VIVO redirect a request for http://vivo.ufl.edu/individual/n25562 to http://vivo.ufl.edu/display/n25562 when there's no accept header?
- VIVO's content negotiation is based on http://www.w3.org/TR/swbp-vocab-pub
- BrianL: [ your institution name ]
-
will implement content negotiation for VIVO's internal SPARQL endpointJira server DuraSpace JIRA key VIVO-282
...