lobid / lodmill

This repo is replaced by i.a. https://github.com/hbz/lobid-resources/
19 stars 8 forks source link

URIs in morph don't resolve anymore #795

Closed ChristophEwertowski closed 7 years ago

ChristophEwertowski commented 7 years ago

Two URIs in morph-hbz01-to-lobid.xml don't resolve anymore.

  1. http://purl.org/ontology/daia/label which is referenced in line 778. The ontology moved to [GitHub] but I don't know if we really should link to the daia.schema.json file.
  2. http://rdvocab.info/termList/prodManuscript/1002 in line 325.
acka47 commented 7 years ago

@nichtich Is it intended that DAIA property and class URIs don't resolve anymore?

curl -i -L -H "Accept: application/rdf+xml" http://purl.org/ontology/daia/ even gives a 404:

HTTP/1.1 404 NOT FOUND
Server: nginx/1.4.6 (Ubuntu)
Date: Tue, 17 Jan 2017 10:43:53 GMT
Content-Type: text/html
Content-Length: 233
Connection: keep-alive

curl -i -L -H "Accept: application/rdf+xml" http://purl.org/ontology/daia gives a redirect to an empty .owl file on GitHub:

HTTP/1.1 302 FOUND
Server: nginx/1.4.6 (Ubuntu)
Date: Tue, 17 Jan 2017 10:44:06 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 194
Connection: keep-alive
Location: http://uri.gbv.de/ontology/daia
Access-Control-Allow-Origin: *

HTTP/1.1 303 See Other
Date: Tue, 17 Jan 2017 10:44:06 GMT
Server: Apache/2.2.22 (Ubuntu)
X-Powered-By: PHP/5.3.10-1ubuntu3.25
Location: http://gbv.github.io/daiaspec/daia.owl
Vary: Accept-Encoding
Content-Length: 0
Content-Type: text/html

HTTP/1.1 200 OK
Server: GitHub.com
Content-Type: application/octet-stream
Last-Modified: Mon, 28 Sep 2015 09:05:33 GMT
Access-Control-Allow-Origin: *
Expires: Tue, 17 Jan 2017 10:47:53 GMT
Cache-Control: max-age=600
X-GitHub-Request-Id: C71B4C21:2DB6D:B2A9DD4:587DF401
Content-Length: 116
Accept-Ranges: bytes
Date: Tue, 17 Jan 2017 10:44:06 GMT
Via: 1.1 varnish
Age: 373
Connection: keep-alive
X-Served-By: cache-hhn1532-HHN
X-Cache: HIT
X-Cache-Hits: 1
X-Timer: S1484649846.988947,VS0,VE0
Vary: Accept-Encoding
X-Fastly-Request-ID: 4a831d9301c950559d25c71e6e3549d4cfd15c0d

<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
</rdf:RDF>
ChristophEwertowski commented 7 years ago

As an alternative (indeed it's the only alternative) we could take http://purl.org/ontology/bibo/Manuscript for the second URI. Even Schema.org doesn't seem to have this publication type (maybe internet firms don't deal with it). If I adjust the redirected URI to http://www.rdaregistry.info/termList/prodManuscript/1002 I get the message that "GitHub Pages is temporarily down for maintenance." So maybe that would be the right URI.

acka47 commented 7 years ago

There also is bf:Manuscript. They have two different underlying meanings of the term "Manuscript", though:

There are currently 530 resources with this medium type in lobid, see http://alpha.lobid.org/resources/search?q=*&medium=http%3A%2F%2Frdvocab.info%2FtermList%2FprodManuscript%2F1002. Obviously, "Manuskript" is used in both meanings of the term in the union catalogue. If you look at the oldest resources, these are obviously manuscripts in the bibframe sense. If you look at the latest resources these are definitely manuscripts in the bibo sense. However, as we are only talking about 530 resources, we shouldn't put much more effort into it as we already did.

I also tend to using bibo:Manuscript as it sounds a bit to be the more general class. (I think for some reason we aimed at using skos:Concepts on the dct:medium property but we already have some exceptions. Thus, we can as well use bibo:Manuscript (which is an owl:Class).)

ChristophEwertowski commented 7 years ago

Another reason is the depiction of the publication year on the right side. Most of the publications are from ca. 1775 and later. Since typewriters were used in mass not until much later one can suppose that most of the works are (unpublished) prints.

ChristophEwertowski commented 7 years ago

Looked in the documentation of the DAIA ontology (2015-04-22) for the namespace. In point 2.1 it's written there that http://purl.org/ontology/daia# may be the new namespace and in fact it is. It forwards one to the documentation of the API of 2016-02-26. Update: Unter point 2.3 it is written that the namespace is the URI they wrote down in 2.1. You still can't get rdf.

ChristophEwertowski commented 7 years ago

@nichtich I tried to get an RDF file of the DAIA ontology but got none by curl-ing: curl -i -L -H "Accept: application/rdf+xml" http://purl.org/ontology/daia. Am I looking at the wrong place or is the RDF offline?

ChristophEwertowski commented 7 years ago

http://id.loc.gov/ontologies/bibframe/ShelfMark.rdf (HTML)would be a good replacement for daia/label. What do you mean @acka47 ?

acka47 commented 7 years ago

The problem with bf:shelfMark is that it is an owl:ObjectProperty. Speaking to @ChristophEwertowski offline, we decided to add a property to lobid vocab, see https://github.com/hbz/lobid-vocabs/pull/59.

acka47 commented 7 years ago

After merging https://github.com/hbz/lobid-vocabs/pull/59 we have to replace daia:label by lv:callNumber and http://rdaregistry.info/termList/prodManuscript/1002 by bibo:Manuscript.

dr0i commented 7 years ago

Deployed to stage. @fsteeg ready for UI update. The only change is that Medium changed to bibo/Manuscript, see e.g. http://stage.lobid.org/resources/TT001726537?format=json.

fsteeg commented 7 years ago

Deployed to staging, see medium facet: http://stage.lobid.org/resources/search

acka47 commented 7 years ago

+1

ChristophEwertowski commented 7 years ago

+1