Page History

...

CU Boulder is closed today due to severe flooding in the area – we hope all is well with Stephen, Alex, and Liz and their colleagues.

Release update

There are still open blocker issues for the 1.6 release – and we expect to need about 3 weeks for testing, so look for a mid-October release.

...

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

...

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 ]You can't request Mike Conlon himself over the Internet, so if you issue a request for his URI, VIVO redirects you to an HTML page (information about Mike Conlon) that is not the same as Mike Conlon himself. If you request RDF (in your HTTP request's accept headers), VIVO redirects you to still another URL for RDF data (http://vivo.ufl.edu/individual/n25562.rdf).
- The question is whether search engines get confused by this – is this causing practical problems?
- Where this might make a difference is when we generate an HTML VIVO page, should we show links to other pages in VIVO in the /display form (HTML), rather than the /individual form of the true URI?
- VIVO sends a 303 redirect ("see other") – and search engines can't assume that the 303 they are redirected to will be the same every time they come to the /individual URI, so they can't cache it.
Jira
server DuraSpace JIRA
key VIVO-282
will implement content negotiation for VIVO's internal SPARQL endpoint

...