...
- 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: 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.
-
will implement content negotiation for VIVO's internal SPARQL endpointJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-282
Configuring Fuseki
- How-To___: install a Joseki SPARQL endpoint for VIVO– is this as current as it can be?
Image upload – see
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Call-in Information
...